Skip to content

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.

Information Security

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 →

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 →
PCI DSS 4.01 control

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?
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.
Why is Replay Attack important for compliance?
Replay Attack is a key concept in Information Security. Understanding replay attack helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Replay Attack?
Replay Attack appears in the requirement text of HL7 FHIR Security Framework, New Zealand Information Security Manual (NZISM), OWASP Top 10:2025, PCI DSS 4.0. Across these standards we have identified 4 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Replay Attack?
Explore our compliance framework pages to see how replay attack applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

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.

Written and maintained by Gerard Blokdyk, The Art of Service.