III - Administrative Public
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000023-DB-000001
Group -
PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or o...Rule High Severity -
SRG-APP-000033-DB-000084
Group -
PostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
Authentication with a DOD-approved PKI certificate does not necessarily imply authorization to access PostgreSQL. To mitigate the risk of unauthorized access to sensitive information by entities th...Rule High Severity -
SRG-APP-000080-DB-000063
Group -
PostgreSQL must protect against a user falsely repudiating having performed organization-defined actions.
Nonrepudiation of actions taken is required to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e...Rule Medium Severity -
SRG-APP-000089-DB-000064
Group -
PostgreSQL must provide audit record generation capability for DOD-defined auditable events within all DBMS/database components.
Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit rec...Rule Medium Severity -
SRG-APP-000090-DB-000065
Group -
PostgreSQL must allow only the information system security manager (ISSM), or individuals or roles appointed by the ISSM, to select which events are to be audited.
Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events. ...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 -
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-000092-DB-000208
Group -
PostgreSQL must initiate session auditing upon startup.
Session auditing is for use when a user's activities are under investigation. To ensure the capture of all activity during those periods when session auditing is in use, it needs to be in operation...Rule Medium Severity -
SRG-APP-000095-DB-000039
Group -
PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred.
Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate t...Rule Medium Severity -
SRG-APP-000096-DB-000040
Group -
PostgreSQL must produce audit records containing time stamps to establish when the events occurred.
Information system auditing capability is critical for accurate forensic analysis. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events re...Rule Medium Severity -
SRG-APP-000097-DB-000041
Group -
PostgreSQL must produce audit records containing sufficient information to establish where the events occurred.
Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events r...Rule Medium Severity -
SRG-APP-000098-DB-000042
Group -
PostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events.
Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events...Rule Medium Severity -
SRG-APP-000099-DB-000043
Group -
PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel cannot make an accurate assessment as to wheth...Rule Medium Severity -
SRG-APP-000100-DB-000201
Group -
PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of us...Rule Medium Severity -
SRG-APP-000101-DB-000044
Group -
PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough infor...Rule Medium Severity -
SRG-APP-000109-DB-000049
Group -
PostgreSQL must, by default, shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.
It is critical that when the DBMS is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include software/hardware errors; failur...Rule Medium Severity -
SRG-APP-000109-DB-000321
Group -
PostgreSQL must be configurable to overwrite audit log records, oldest first (first-in-first-out [FIFO]), in the event of unavailability of space for more audit log records.
It is critical that when PostgreSQL is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include software/hardware errors; fail...Rule Medium Severity -
SRG-APP-000118-DB-000059
Group -
The audit information produced by PostgreSQL must be protected from unauthorized read access.
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In ...Rule Medium Severity -
SRG-APP-000119-DB-000060
Group -
The audit information produced by PostgreSQL must be protected from unauthorized modification.
If audit data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be impossible to achieve. To ensure the verac...Rule Medium Severity -
SRG-APP-000120-DB-000061
Group -
The audit information produced by PostgreSQL must be protected from unauthorized deletion.
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracit...Rule Medium Severity -
SRG-APP-000121-DB-000202
Group -
PostgreSQL must protect its audit features from unauthorized access.
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Depending upon the log format and application, system and application log tools may ...Rule Medium Severity -
SRG-APP-000122-DB-000203
Group -
PostgreSQL must protect its audit configuration from unauthorized modification.
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on au...Rule Medium Severity -
SRG-APP-000123-DB-000204
Group -
PostgreSQL must protect its audit features from unauthorized removal.
Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on au...Rule Medium Severity -
SRG-APP-000133-DB-000179
Group -
PostgreSQL must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to PostgreSQL.
If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robus...Rule Medium Severity -
SRG-APP-000133-DB-000198
Group -
The PostgreSQL software installation account must be restricted to authorized users.
When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effec...Rule High 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.