DoD STIGs – V-32525


Title: The DBMS must generate a unique session identifier for each session.

Vulnerability ID: V-32525


IA Controls: None

Severity: medium

Description: This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted.

Unique session IDs are the opposite of sequentially generated session IDs which can be easily guessed by an attacker. Unique session identifiers help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions.

Check Text: Review DBMS settings and vendor documentation to determine whether the DBMS product generates unique session identifiers for each user session. If the DBMS does not generate unique session identifiers for each user session, this is a finding.

Fix Text: Utilize a DBMS product that generates unique session identifiers for each session.


Interpreting V-32525:

Coming Soon!

Return to the DoD STIGs – Database Security Requirements Guide

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.