DoD STIGs – V-32481


Title: The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

Vulnerability ID: V-32481


IA Controls: None

Severity: medium

Description: Non-organizational users include all information system users other than organizational users which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations).

Non-organizational users shall be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server.

Accordingly, a risk assessment is used in determining the authentication needs of the organization.

Scalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.

Check Text: Review DBMS settings to determine whether non-organizational users are uniquely identified and authenticated when logging onto the system. If non-organizational users are not uniquely identified and authenticated, this is a finding.

Fix Text: Configure DBMS settings to uniquely identify and authenticate all non-organizational users who log onto the system.


Interpreting V-32481:

First things first, the guest access to your SQL Server should be disabled (it is by default, but make sure). Then you will need to make sure any non-organizational users are given a login and account to use. An alternative would be to use an application login, but they require some more work to configure and the user would still need a login. This login would be used with an application login to help identify the individual while the application login would be the one able to grant the permissions appropriately.

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.