DoD STIGs – V-32356


Title: Databases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights.

Vulnerability ID: V-32356


IA Controls: None

Severity: medium

Description: Discretionary Access Control (DAC) is based on the premise that individual users are “owners” of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment.

DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user controlled file permissions. DAC models have the potential for the access controls to propagate without limit resulting in unauthorized access to said objects.

When applications provide a discretionary access control mechanism, the application must be able to limit the propagation of those access rights.

The DBMS must ensure the recipient of permissions possesses only the access intended. The database must enforce the ability to limit rights propagation if that is the intent of the grantor. If the propagation of access rights is not limited, users with rights to objects they do not own can continue to grant rights to those objects to other users without limit.

Check Text: Verify the DBMS has the ability to grant permissions without the grantee receiving the right to grant those same permissions to another user.

Review organization policies regarding access propagation. If an access propagation policy limiting the propagation of rights does not exist, this is a finding.

Review DBMS configuration to verify access propagation policies are enforced by the DBMS as configured. If the DBMS does not enforce the access propagation policy, this is a finding.

Fix Text: Create and document an access propagation policy that limits the propagation of rights.

Configure the DBMS to enforce the access propagation policy.


Interpreting V-32356:

This is basically saying, just because you can access something, doesn’t mean you can let anyone else access it.

SQL Server security can get very granular. This includes the setup of user accounts, groups and inheritances between them. In this situation you want to make sure that the accounts do not have the rights to grant security access to items that they have been granted access to as well. By restricting the grant capability to only a few key accounts, and properly monitoring the granting of access via SQL Audit or Policy manager you can easily maintain this compliance.

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.