The application server must ensure authentication of both client and server during the entire session.
This control focuses on communications protection at the session, versus packet level. At the application layer, session IDs are tokens generated by web applications to uniquely identify an application user's session. Web applications utilize session tokens or session IDs in order to establish application user identity. Proper use of session IDs addresses man-in-the-middle attacks, including session hijacking or insertion of false information into a session. Application servers must provide the capability to perform mutual authentication. Mutual authentication is when both the client and the server authenticate each other.
Configure the application server to mutually authenticate during the entire session as required by application design and policy.
Review the application server configuration and documentation to ensure the application server provides mutual authentication capabilities. If the application server does not provide the ability for applications to utilize mutual authentication, this is a finding.