Title

The DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur. (Cat II impact)

Discussion

Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Check Content

Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to add privileges/permissions/role membership. If the DBMS is not capable of this, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS denies the addition of privileges/permissions/role membership. If they are not produced, this is a finding. Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent the addition of privileges/permissions/role membership. If they are not produced, this is a finding.

Fix Text

Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to add privileges/permissions/role membership. Configure the DBMS to produce audit records when it denies attempts to add privileges/permissions/role membership. Configure the DBMS to produce audit records when other errors prevent attempts to add privileges/permissions/role membership.

Additional Identifiers

Rule ID: SV-206617r879866_rule

Vulnerability ID: V-206617

Group Title: SRG-APP-000495

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.