Control: The information system protects the authenticity of communications sessions.
Session Authenticity Supplemental Guidance:
This control addresses communications protection at the session, versus packet level (e.g., sessions in service-oriented architectures providing web-based services) and establishes grounds for confidence at both ends of communications sessions in ongoing identities of other parties and in the validity of information transmitted. Authenticity protection includes, for example, protecting against man-in-the-middle attacks/session hijacking and the insertion of false information into sessions.
Session Authenticity Control Enhancements:
SC-23 (1) Session Authenticity - Invalidate Session Identities at Logout
The information system invalidates session identifiers upon user logout or other session termination.
SupplementalGuidance: This control enhancement curtails the ability of adversaries from capturing and continuing to employ previously valid session IDs.
SC-23 (2) Session Authenticity - User-Initiated Logouts / Message Displays
[Withdrawn: Incorporated into AC-12 (1)].
SC-23 (3) Session Authenticity - Unique Session Identifiers with Randomisation
The information system generates a unique session identifier for each session with [Assignment: organisation-defined randomness requirements] and recognises only session identifiers that are system-generated.
SupplementalGuidance: This control enhancement curtails the ability of adversaries from reusing previously valid session IDs. Employing the concept of randomness in the generation of unique session identifiers helps to protect against brute-force attacks to determine future session identifiers.
Related control: SC-13.
SC-23 (4) Session Authenticity - Unique Session Identifiers with Randomisation
[Withdrawn: Incorporated into SC-23 (3)].
SC-23 (5) Session Authenticity - Allowed Certificate Authorities
The information system only allows the use of [Assignment: organisation-defined certificate authorities] for verification of the establishment of protected sessions.
Supplemental Guidance: Reliance on certificate authorities (CAs) for the establishment of secure sessions includes, for example, the use of Secure Socket Layer (SSL) and/or Transport Layer Security (TLS) certificates. These certificates, after verification by the respective certificate authorities, facilitate the establishment of protected sessions between web clients and web servers.
Related control: SC-13