| Vuln ID | Severity | Asset | STIG | Title | Status | Doc Status | Assigned To | Actions |
|---|---|---|---|---|---|---|---|---|
| V-206627 | CAT II | MONT-DB-002 | Database Security Requirements Guide | The DBMS must generate audit records when unsucces... | - | |||
Check TextIf the DBMS architecture makes it impossible for any user, even with the highest privileges, to drop its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding. Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to drop security objects. 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 system denies attempts to drop security objects. 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 attempts to drop security objects. If they are not produced, this is a finding. Fix TextDeploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to delete security objects. Configure the DBMS to produce audit records when it denies attempts to delete security objects. Configure the DBMS to produce audit records when other errors prevent attempts to delete security objects. CommentsPage 2 of reference document SQL Anywhere 17 - Auditing Options.pdf specifies the types of auditing events captured in the audit log. A setting of ‘all’ includes auditing of successful and unsuccessful executions of DDL statements.
Source: Montford Point ShipCLIP DB V4R4.ckl
Scan Date: 2026-03-06T12:50:21.809591
Technology Area: Database Review
|
||||||||