Crunchy Data PostgreSQL Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
<VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, i...Rule Medium Severity -
PostgreSQL must be able to generate audit records when privileges/permissions are retrieved.
<VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, i...Rule Medium Severity -
SRG-APP-000498-DB-000347
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.
<VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go un...Rule Medium Severity -
SRG-APP-000507-DB-000357
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when unsuccessful accesses to objects occur.
<VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it ...Rule Medium Severity -
SRG-APP-000504-DB-000354
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records for all privileged activities or other system-level access.
<VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to a...Rule Medium Severity -
SRG-APP-000494-DB-000345
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.
<VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go ...Rule Medium Severity -
SRG-APP-000492-DB-000332
<GroupDescription></GroupDescription>Group -
PostgreSQL must be able to generate audit records when security objects are accessed.
<VulnDiscussion>Changes to the security configuration must be tracked. This requirement applies to situations where security data is retriev...Rule Medium Severity -
SRG-APP-000499-DB-000330
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when privileges/permissions are deleted.
<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unautho...Rule Medium Severity -
SRG-APP-000506-DB-000353
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur.
<VulnDiscussion>For completeness of forensic analysis, it is necessary to track who logs on to PostgreSQL. Concurrent connections by the sam...Rule Medium Severity -
SRG-APP-000501-DB-000337
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur.
<VulnDiscussion>The removal of security objects from the database/PostgreSQL would seriously degrade a system's information assurance posture...Rule Medium Severity -
SRG-APP-000495-DB-000328
<GroupDescription></GroupDescription>Group -
PostgreSQL must generate audit records when privileges/permissions are modified.
<VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unautho...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.