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

Frameworks that govern replay attack

PCI DSS v4.0View framework →ISO 27001:2022View framework →NIST Cybersecurity Framework 2.0View framework →

What the standards actually require on replay attack

Requirements naming replay attack across 5 standards, quoted from the control text.

PCI DSS 4.01 control

MFA systems are implemented as follows: • The MFA system is not susceptible to replay attacks. • MFA systems cannot be bypassed by any users, including administrative users unless specifically documented, and authorized by

8.5.1 · MFA systems are implemented as follows: • The MFA system is not susceptible to replay attacks. • MFA systems cannot be bypassed by any users, including administrative users unless specifically documented, and authorized by →
HL7 FHIR Security Framework1 control

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 →
ISO/IEC 29115:2023 - Entity Authentication Assurance Framework1 control

Threats during the authentication event including replay attacks, man-in-the-middle, and session hijacking

29115-9.4 · Authentication mechanism threats →
OWASP Top 10:20251 control

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 →
W3C Verifiable Credentials (VC) Data Model 2.01 control

Presentations are typically short-lived and must include temporal validity constraints to prevent replay attacks.

VP-3 · Presentation Validity →

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 686 frameworks with 311K cross-framework control mappings.
Which compliance frameworks address Replay Attack?
Replay Attack appears in the requirement text of PCI DSS 4.0, HL7 FHIR Security Framework, ISO/IEC 29115:2023 - Entity Authentication Assurance Framework, OWASP Top 10:2025, W3C Verifiable Credentials (VC) Data Model 2.0. Across these standards we have identified 5 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 686 frameworks.

See how Replay Attack applies across compliance frameworks

Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.

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