UCF STIG Viewer Logo

Crunchy Data PostgreSQL Security Technical Implementation Guide


Overview

Date Finding Count (113)
2020-12-11 CAT I (High): 7 CAT II (Med): 105 CAT III (Low): 1
STIG Description
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.

Available Profiles



Findings (MAC II - Mission Support Public)

Finding ID Severity Title
V-233623 High The DBMS must be configured on a platform that has a NIST certified FIPS 140-2 installation of OpenSSL.
V-233585 High PostgreSQL must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owner’s requirements.
V-233583 High PostgreSQL must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.
V-233515 High PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
V-233619 High PostgreSQL must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
V-233614 High PostgreSQL must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
V-233602 High PostgreSQL must enforce authorized access to all PKI private keys stored/utilized by PostgreSQL.
V-233622 Medium PostgreSQL must generate audit records for all direct access to the database(s).
V-233588 Medium PostgreSQL must separate user functionality (including user interface services) from database management functionality.
V-233589 Medium PostgreSQL must initiate session auditing upon startup.
V-233586 Medium PostgreSQL must protect the confidentiality and integrity of all information at rest.
V-233587 Medium PostgreSQL must prohibit user installation of logic modules (functions, trigger procedures, views, etc.) without explicit privileged status.
V-233584 Medium PostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owner’s requirements.
V-233582 Medium PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
V-233580 Medium PostgreSQL must be configured to provide audit record generation for DoD-defined auditable events within all DBMS/database components.
V-233581 Medium PostgreSQL must generate time stamps, for audit records and application data, with a minimum granularity of one second.
V-233519 Medium If passwords are used for authentication, PostgreSQL must transmit only encrypted representations of passwords.
V-233518 Medium PostgreSQL must limit privileges to change functions and triggers, and links to software external to PostgreSQL.
V-233511 Medium 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.
V-233513 Medium 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).
V-233512 Medium PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-233514 Medium The audit information produced by PostgreSQL must be protected from unauthorized modification.
V-233517 Medium Privileges to change PostgreSQL software modules must be limited.
V-233516 Medium 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.
V-233618 Medium PostgreSQL must protect its audit configuration from unauthorized modification.
V-233612 Medium PostgreSQL must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-233613 Medium PostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
V-233610 Medium PostgreSQL must off-load 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 stand-alone systems.
V-233611 Medium PostgreSQL must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.
V-233616 Medium Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
V-233617 Medium Access to database files must be limited to relevant processes and to authorized, administrative users.
V-233615 Medium PostgreSQL must map the PKI-authenticated identity to an associated user account.
V-233591 Medium PostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events.
V-233590 Medium PostgreSQL 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-233593 Medium Access to external executables must be disabled or restricted.
V-233592 Medium Unused database components, PostgreSQL software, and database objects must be removed.
V-233595 Medium PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in process.
V-233594 Medium Unused database components that are integrated in PostgreSQL and cannot be uninstalled must be disabled.
V-233597 Medium PostgreSQL must enforce access restrictions associated with changes to the configuration of PostgreSQL or database(s).
V-233596 Medium If passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords.
V-233599 Medium The system must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.
V-233598 Medium PostgreSQL must protect against a user falsely repudiating having performed organization-defined actions.
V-233568 Medium PostgreSQL must generate audit records when privileges/permissions are deleted.
V-233569 Medium PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur.
V-233564 Medium PostgreSQL must generate audit records when unsuccessful accesses to objects occur.
V-233565 Medium PostgreSQL must generate audit records for all privileged activities or other system-level access.
V-233566 Medium PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur.
V-233567 Medium PostgreSQL must be able to generate audit records when security objects are accessed.
V-233560 Medium PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
V-233561 Medium PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
V-233562 Medium PostgreSQL must be able to generate audit records when privileges/permissions are retrieved.
V-233563 Medium PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.
V-233609 Medium PostgreSQL must protect its audit features from unauthorized removal.
V-233608 Medium PostgreSQL must produce audit records containing time stamps to establish when the events occurred.
V-233605 Medium PostgreSQL must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.
V-233604 Medium PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred.
V-233607 Medium PostgreSQL must protect its audit features from unauthorized access.
V-233606 Medium PostgreSQL must invalidate session identifiers upon user logout or other session termination.
V-233601 Medium PostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.
V-233600 Medium PostgreSQL must provide the means for individuals in authorized roles to change the auditing to be performed on all application components, based on all selectable event criteria within organization-defined time thresholds.
V-233603 Medium PostgreSQL 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-233579 Medium PostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission.
V-233578 Medium PostgreSQL must produce audit records containing sufficient information to establish where the events occurred.
V-233577 Medium PostgreSQL, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.
V-233576 Medium PostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur.
V-233575 Medium PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
V-233574 Medium PostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) is modified.
V-233573 Medium PostgreSQL must generate audit records when security objects are modified.
V-233572 Medium PostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
V-233571 Medium PostgreSQL must generate audit records when privileges/permissions are modified.
V-233570 Medium PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur.
V-233542 Medium PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
V-233543 Medium Execution of software modules (to include functions and trigger procedures) with elevated privileges must be restricted to necessary cases only.
V-233540 Medium The PostgreSQL software installation account must be restricted to authorized users.
V-233541 Medium Database software, including PostgreSQL configuration files, must be stored in dedicated directories separate from the host OS and other applications.
V-233546 Medium PostgreSQL must isolate security functions from non-security functions.
V-233547 Medium PostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s).
V-233544 Medium When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.
V-233545 Medium PostgreSQL must utilize centralized management of the content captured in audit records generated by all components of PostgreSQL.
V-233548 Medium PostgreSQL must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.
V-233549 Medium The audit information produced by PostgreSQL must be protected from unauthorized read access.
V-233621 Medium PostgreSQL must generate audit records when successful accesses to objects occur.
V-233620 Medium Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted.
V-233555 Medium PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur.
V-233554 Medium PostgreSQL must generate audit records showing starting and ending time for user access to the database(s).
V-233557 Medium PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.
V-233556 Medium PostgreSQL must generate audit records when privileges/permissions are added.
V-233551 Medium PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed.
V-233550 Medium When updates are applied to PostgreSQL software, any software components that have been replaced or made unnecessary must be removed.
V-233553 Medium PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur.
V-233552 Medium PostgreSQL must generate audit records when unsuccessful attempts to access security objects occur.
V-233559 Medium PostgreSQL must generate audit records when security objects are deleted.
V-233558 Medium PostgreSQL must generate audit records when successful logons or connections occur.
V-233520 Medium PostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
V-233521 Medium PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission.
V-233522 Medium PostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
V-233523 Medium The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (functions, trigger procedures, links to software external to PostgreSQL, etc.) must be restricted to authorized users.
V-233524 Medium PostgreSQL must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
V-233525 Medium PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in storage.
V-233526 Medium PostgreSQL must check the validity of all data inputs except those specifically identified by the organization.
V-233527 Medium PostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it.
V-233528 Medium 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.
V-233529 Medium PostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
V-233533 Medium PostgreSQL must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.
V-233532 Medium PostgreSQL must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
V-233531 Medium The audit information produced by PostgreSQL must be protected from unauthorized deletion.
V-233530 Medium PostgreSQL must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.
V-233537 Medium 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.
V-233535 Medium PostgreSQL must provide an immediate alert to appropriate support staff of all audit log failures.
V-233534 Medium PostgreSQL must allow only the Information System Security Manager (ISSM), or individuals or roles appointed by the ISSM, to select which auditable events are to be audited.
V-233539 Medium Database objects (including but not limited to tables, indexes, storage, trigger procedures, functions, links to software external to PostgreSQL, etc.) must be owned by database/DBMS principals authorized for ownership.
V-233538 Medium PostgreSQL must maintain the confidentiality and integrity of information during reception.
V-233536 Low 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.