Network logins can't be captured and replayed by an attacker.
What it actually means
Authentication over the network must resist replay attacks — where someone captures a login exchange and re-sends it. Modern protocols handle this for you: Kerberos, modern TLS-based authentication, and FIDO2 are replay-resistant. The work is usually confirming you're not relying on something legacy.
Pass or fail — an assessor needs a "yes" to each
- Network authentication uses replay-resistant protocols (Kerberos / modern TLS / FIDO2).
- Legacy, replayable mechanisms are disabled.
What to have ready
- Identity-provider / protocol configuration
- Confirmation that legacy auth is disabled
Where teams trip up
- Legacy authentication left enabled in Entra/AD
- Assuming replay resistance without checking the protocols in use
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in Identification & Authentication (3.5)
3.5.1 — Uniquely identify users, processes, and devices3.5.2 — Authenticate before access3.5.3 — Multifactor authentication (MFA)3.5.5 — Don't recycle identifiers3.5.6 — Disable dormant accounts3.5.7 — Enforce password complexity3.5.8 — Block password reuse3.5.9 — Force change of temporary passwords3.5.10 — Protect stored and transmitted passwords3.5.11 — Obscure authentication feedback