Communications Authenticity

Session authenticity is confidence that each end is who it claims, for the whole session.

The threats are interception in the middle, session hijacking, and injected traffic. A current version of TLS, the standard encryption protocol for internet connections, with valid certificates provides the protection. The handshake authenticates the endpoint, and the session keys defend the exchange against takeover.

Enforce current TLS and keep certificates from expiring.

Configure servers, the VPN, and management interfaces to current TLS with weak protocol versions disabled, and renew certificates before expiry so the trust chain never lapses. This is largely the same configuration work as SC.L2-3.13.8, evidenced from the authenticity side.

Sweep for the sessions that are not browser traffic.

VPN tunnels, SFTP transfers, and application integrations each ride a protocol with its own authentication story. List the session types in your environment, and confirm each uses a protocol that authenticates the endpoints. Keep a policy naming the approved protocols, so a new one does not arrive unexamined.