STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Crunchy Data Postgres 16 Security Technical Implementation Guide

Version

V1R2

Release Date

Feb 27, 2026

SCAP Benchmark ID

CD_Postgres_16_STIG

Total Checks

111

Tags

other
CAT I: 10CAT II: 101CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (111)

V-261857MEDIUMPostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.V-261858HIGHPostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-261859HIGHPostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-261860MEDIUMPostgreSQL must protect against a user falsely repudiating having performed organization-defined actions.V-261861MEDIUMPostgreSQL must provide audit record generation capability for DOD-defined auditable events within all DBMS/database components.V-261862MEDIUMPostgreSQL 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.V-261863MEDIUMPostgreSQL must be able to generate audit records when privileges/permissions are retrieved.V-261864MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-261865MEDIUMPostgreSQL must initiate session auditing upon startup.V-261866MEDIUMPostgreSQL must produce audit records containing sufficient information to establish what type of events occurred.V-261867MEDIUMPostgreSQL must produce audit records containing time stamps to establish when the events occurred.V-261868MEDIUMPostgreSQL must produce audit records containing sufficient information to establish where the events occurred.V-261869MEDIUMPostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events.V-261870MEDIUMPostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.V-261871MEDIUMPostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.V-261872MEDIUMPostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.V-261873MEDIUMPostgreSQL 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.V-261874MEDIUMPostgreSQL 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.V-261875MEDIUMThe audit information produced by PostgreSQL must be protected from unauthorized read access.V-261876MEDIUMThe audit information produced by PostgreSQL must be protected from unauthorized modification.V-261877MEDIUMThe audit information produced by PostgreSQL must be protected from unauthorized deletion.V-261878MEDIUMPostgreSQL must protect its audit features from unauthorized access.V-261879MEDIUMPostgreSQL must protect its audit configuration from unauthorized modification.V-261880MEDIUMPostgreSQL must protect its audit features from unauthorized removal.V-261881MEDIUMPostgreSQL must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to PostgreSQL.V-261882HIGHThe PostgreSQL software installation account must be restricted to authorized users.V-261883MEDIUMDatabase software, including PostgreSQL configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-261884MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/PostgreSQL principals authorized for ownership.V-261885MEDIUMThe role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to PostgreSQL, etc.) must be restricted to authorized users.V-261886MEDIUMUnused database components, PostgreSQL software, and database objects must be removed.V-261887MEDIUMUnused database components that are integrated in PostgreSQL and cannot be uninstalled must be disabled.V-261888MEDIUMAccess to external executables must be disabled or restricted.V-261889MEDIUMPostgreSQL 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.V-261890MEDIUMPostgreSQL must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-261891HIGHIf passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords.V-261892HIGHIf passwords are used for authentication, PostgreSQL must transmit only encrypted representations of passwords.V-261893MEDIUMPostgreSQL, when using PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.V-261894HIGHPostgreSQL must enforce authorized access to all PKI private keys stored/used by PostgreSQL.V-261895MEDIUMPostgreSQL must map the PKI-authenticated identity to an associated user account.V-261896HIGHPostgreSQL must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations.V-261897MEDIUMPostgreSQL must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users).V-261898MEDIUMPostgreSQL must separate user functionality (including user interface services) from database management functionality.V-261899MEDIUMPostgreSQL must invalidate session identifiers upon user logout or other session termination.V-261900MEDIUMPostgreSQL must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-261901HIGHPostgreSQL must protect the confidentiality and integrity of all information at rest.V-261902MEDIUMPostgreSQL must isolate security functions from nonsecurity functions.V-261903MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-261904MEDIUMAccess to database files must be limited to relevant processes and to authorized, administrative users.V-261905MEDIUMPostgreSQL must check the validity of all data inputs except those specifically identified by the organization.V-261906MEDIUMPostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it.V-261907MEDIUMPostgreSQL and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.V-261908MEDIUMPostgreSQL must provide nonprivileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.V-261909MEDIUMPostgreSQL must reveal detailed error messages only to the information system security officer (ISSO), information system security manager (ISSM), system administrator (SA), and database administrator (DBA).V-261910MEDIUMPostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-261911MEDIUMPostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-261912MEDIUMPostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in process.V-261913MEDIUMPostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-261914MEDIUMPostgreSQL must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.V-261915MEDIUMPostgreSQL must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-261916MEDIUMExecution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.V-261917MEDIUMPostgreSQL must use centralized management of the content captured in audit records generated by all components of PostgreSQL.V-261918MEDIUMPostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-261919MEDIUMPostgreSQL must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-261920MEDIUMPostgreSQL must provide an immediate real-time alert to appropriate support staff of all audit log failures.V-261921MEDIUMPostgreSQL must record time stamps in audit records and application data that can be mapped to Coordinated Universal Time (UTC), formerly Greenwich Mean Time (GMT).V-261922MEDIUMPostgreSQL must generate time stamps for audit records and application data with a minimum granularity of one second.V-261923MEDIUMPostgreSQL must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-261924MEDIUMPostgreSQL must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).V-261925MEDIUMPostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s).V-261926MEDIUMPostgreSQL must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accordance with the Ports, Protocols, and Services Management (PPSM) guidance.V-261927MEDIUMPostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.V-261928HIGHPostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.V-261929MEDIUMPostgreSQL must only accept end entity certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.V-261930MEDIUMPostgreSQL must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-261931MEDIUMPostgreSQL must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-261932MEDIUMPostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission.V-261933MEDIUMPostgreSQL must maintain the confidentiality and integrity of information during reception.V-261934MEDIUMWhen invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.V-261935MEDIUMWhen updates are applied to the PostgreSQL software, any software components that have been replaced or made unnecessary must be removed.V-261936MEDIUMSecurity-relevant software updates to PostgreSQL must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).V-261938MEDIUMPostgreSQL must be able to generate audit records when security objects are accessed.V-261939MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to access security objects occur.V-261940MEDIUMPostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.V-261941MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.V-261942MEDIUMPostgreSQL must generate audit records when privileges/permissions are added.V-261943MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-261944MEDIUMPostgreSQL must generate audit records when privileges/permissions are modified.V-261945MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-261946MEDIUMPostgreSQL must generate audit records when security objects are modified.V-261947MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur.V-261948MEDIUMPostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) are modified.V-261949MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.V-261950MEDIUMPostgreSQL must generate audit records when privileges/permissions are deleted.V-261951MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-261952MEDIUMPostgreSQL must generate audit records when security objects are deleted.V-261953MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur.V-261954MEDIUMPostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.V-261955MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.V-261956MEDIUMPostgreSQL must generate audit records when successful logons or connections occur.V-261957MEDIUMPostgreSQL must generate audit records when unsuccessful logons or connection attempts occur.V-261958MEDIUMPostgreSQL must generate audit records for all privileged activities or other system-level access.V-261959MEDIUMPostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.V-261960MEDIUMPostgreSQL must generate audit records showing starting and ending time for user access to the database(s).V-261961MEDIUMPostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-261962MEDIUMPostgreSQL must be able to generate audit records when successful accesses to objects occur.V-261963MEDIUMPostgreSQL must generate audit records when unsuccessful accesses to objects occur.V-261964MEDIUMPostgreSQL must generate audit records for all direct access to the database(s).V-261965MEDIUMPostgreSQL must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.V-261966MEDIUMPostgreSQL must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners' requirements.V-261967MEDIUMPostgreSQL must offload audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for standalone systems.V-283674HIGHPostgreSQL products must be a version supported by the vendor.