Replay Attack
What is Replay Attack?
A network attack in which a valid data transmission is maliciously repeated or delayed. The attacker intercepts data and retransmits it at a later time to gain unauthorised access or duplicate a transaction.
Frameworks that govern replay attack
What the standards actually require on replay attack
Requirements naming replay attack across 4 standards, quoted from the control text.
HL7 FHIR Transport Security. TRANSPORT LAYER SECURITY (TLS) - all FHIR APIs MUST use TLS 1.2+ for production + TLS 1.3 recommended; certificate validation + trust chain + certificate pinning where appropriate + HSTS + secure session establishment + cipher suit...
HL7-FHIR-Transport-TLS-Communication · HL7 FHIR Transport Security - TLS 1.2+, Communication Security, Time Keeping, Server CapabilityStatement →Agencies must make sure that any authentication method open to replay attacks is turned off.
new-zealand-information-security-manual-nzism::16.1.39.C.01/CID7554 · 16.1.39.C.01 Disable replay-susceptible authentication methods →Address OWASP Top 10 A07 Identification and Authentication Failures per OWASP Top 10:2025. Identification and Authentication Failures arise from weak password + session management + credential storage + recovery + reuse attacks + credential stuffing + session...
OWASPTOP10-7 · A07:2025 Identification and Authentication Failures →MFA systems must be implemented so that: the MFA system resists replay attacks; no user, including administrative users, can bypass MFA unless this is specifically documented and authorized by management by exception for a limited time;
8.5.1 · 8.5.1 MFA system resistant to replay and bypass →Questions people ask about replay attack
What is Replay Attack?
Why is Replay Attack important for compliance?
Which compliance frameworks address Replay Attack?
Where can I learn more about Replay Attack?
See how Replay Attack applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.