DISA STIG PostgreSQL 9.x on RHEL DB v2r4

Warning! Audit Deprecated

This audit file has been deprecated and will be removed in a future update.

View Next Version

Audit Details

Name: DISA STIG PostgreSQL 9.x on RHEL DB v2r4

Updated: 8/26/2024

Authority: DISA STIG

Plugin: PostgreSQLDB

Revision: 1.2

Estimated Item Count: 71

File Details

Filename: DISA_STIG_PostgreSQL_9-x_on_RHEL_v2r4_Database.audit

Size: 190 kB

MD5: e2741f033f1ef25ca6638cbbc6994bb3
SHA256: 0336f57d1d4b961fbb43c25d375b987f21f832402226ebf52a9f74e114e08dea

Audit Items

DescriptionCategories
PGS9-00-000100 - PostgreSQL must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.
PGS9-00-000200 - PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
PGS9-00-000300 - Security-relevant software updates to PostgreSQL must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).
PGS9-00-000600 - PostgreSQL must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
PGS9-00-001200 - PostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
PGS9-00-001800 - PostgreSQL must check the validity of all data inputs except those specifically identified by the organization.
PGS9-00-001900 - PostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it.
PGS9-00-002000 - PostgreSQL and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.
PGS9-00-002400 - PostgreSQL must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
PGS9-00-002700 - PostgreSQL must provide an immediate real-time alert to appropriate support staff of all audit log failures.
PGS9-00-003000 - PostgreSQL must maintain the confidentiality and integrity of information during reception.
PGS9-00-003200 - The PostgreSQL software installation account must be restricted to authorized users.
PGS9-00-003500 - PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
PGS9-00-003600 - Execution of software modules (to include functions and trigger procedures) with elevated privileges must be restricted to necessary cases only.
PGS9-00-003700 - When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.
PGS9-00-003800 - PostgreSQL must utilize centralized management of the content captured in audit records generated by all components of PostgreSQL.
PGS9-00-004100 - PostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s).
PGS9-00-004400 - PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed.
PGS9-00-004500 - PostgreSQL must generate audit records when unsuccessful attempts to access security objects occur.
PGS9-00-004600 - PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur.
PGS9-00-004700 - PostgreSQL must generate audit records showing starting and ending time for user access to the database(s).
PGS9-00-004800 - PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur.
PGS9-00-004900 - PostgreSQL must generate audit records when privileges/permissions are added.
PGS9-00-005000 - PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.
PGS9-00-005100 - PostgreSQL must generate audit records when successful logons or connections occur.
PGS9-00-005200 - PostgreSQL must generate audit records when security objects are deleted.
PGS9-00-005300 - PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
PGS9-00-005400 - PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
PGS9-00-005500 - PostgreSQL must be able to generate audit records when privileges/permissions are retrieved.
PGS9-00-005600 - PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.
PGS9-00-005700 - PostgreSQL must generate audit records when unsuccessful accesses to objects occur.
PGS9-00-005800 - PostgreSQL must generate audit records for all privileged activities or other system-level access.
PGS9-00-005900 - PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.
PGS9-00-006000 - PostgreSQL must be able to generate audit records when security objects are accessed.
PGS9-00-006100 - PostgreSQL must generate audit records when privileges/permissions are deleted.
PGS9-00-006200 - PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur.
PGS9-00-006300 - PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur.
PGS9-00-006400 - PostgreSQL must generate audit records when privileges/permissions are modified.
PGS9-00-006500 - PostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
PGS9-00-006600 - PostgreSQL must generate audit records when security objects are modified.
PGS9-00-006700 - PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is modified.
PGS9-00-006800 - PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
PGS9-00-006900 - PostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur.
PGS9-00-007100 - PostgreSQL must produce audit records containing sufficient information to establish where the events occurred.
PGS9-00-007200 - PostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission.
PGS9-00-007400 - PostgreSQL must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.
PGS9-00-007700 - PostgreSQL must generate time stamps, for audit records and application data, with a minimum granularity of one second.
PGS9-00-007800 - PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
PGS9-00-008100 - PostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.
PGS9-00-008300 - PostgreSQL must protect the confidentiality and integrity of all information at rest.