The DBMS must generate audit records when successful logons or connections occur.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-206630SRG-APP-000503-DB-000350SV-206630r961824_ruleCCI-000172medium
Description
For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.
STIGDate
Database Security Requirements Guide2024-12-04

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
AU-12
1.00
  • DISA · 4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.3.1
1.00
  • DISA · 4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.3.2
1.00
  • DISA · 4 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000172
1.00
  • DISA · 4 · disa_xccdf · related

Details

Check Text (C-206630r961824_chk)

Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) logs on or connects to the DBMS, this is a finding.

Fix Text (F-6890r291559_fix)

Configure DBMS audit settings to generate an audit record each time a user (or other principal) logs on or connects to the DBMS. Ensure that the audit record contains the time of the event, the user ID, and session identifier.