II - Mission Support Sensitive
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000503-DB-000351
Group -
PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur.
For completeness of forensic analysis, it is necessary to track failed attempts to log on to PostgreSQL. While positive identification may not be possible in a case of failed authentication, as muc...Rule Medium Severity -
SRG-APP-000505-DB-000352
Group -
PostgreSQL must generate audit records showing starting and ending time for user access to the database(s).
For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to PostgreSQL lasts. This can be achieved by recording disconnections, in addition...Rule Medium Severity -
SRG-APP-000496-DB-000335
Group -
PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur.
Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail,...Rule Medium Severity -
SRG-APP-000495-DB-000326
Group -
PostgreSQL must generate audit records when privileges/permissions are added.
Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevat...Rule Medium Severity -
SRG-APP-000502-DB-000349
Group -
PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.
Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. To aid in diagnosis, it is necessary to keep track of failed ...Rule Medium Severity -
SRG-APP-000503-DB-000350
Group -
PostgreSQL must generate audit records when successful logons or connections occur.
For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to PostgreSQL.Rule Medium Severity -
SRG-APP-000501-DB-000336
Group -
PostgreSQL must generate audit records when security objects are deleted.
The removal of security objects from the database/PostgreSQL would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.Rule Medium Severity -
SRG-APP-000091-DB-000325
Group -
PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. PostgreSQLs typical...Rule Medium Severity -
SRG-APP-000499-DB-000331
Group -
PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
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...Rule Medium Severity -
SRG-APP-000091-DB-000066
Group -
PostgreSQL must be able to generate audit records when privileges/permissions are retrieved.
Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. PostgreSQLs typical...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.