| Checked | Name | Title |
|---|
| ☐ | SV-214048r508027_rule | 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. |
| ☐ | SV-214049r508027_rule | PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. |
| ☐ | SV-214050r508027_rule | 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). |
| ☐ | SV-214051r508027_rule | The audit information produced by PostgreSQL must be protected from unauthorized modification. |
| ☐ | SV-214052r508027_rule | PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-214053r508027_rule | 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. |
| ☐ | SV-214054r508027_rule | Privileges to change PostgreSQL software modules must be limited. |
| ☐ | SV-214055r508027_rule | PostgreSQL must limit privileges to change functions and triggers, and links to software external to PostgreSQL. |
| ☐ | SV-214056r508027_rule | If passwords are used for authentication, PostgreSQL must transmit only encrypted representations of passwords. |
| ☐ | SV-214057r508027_rule | PostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-214058r508027_rule | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-214059r508027_rule | PostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. |
| ☐ | SV-214060r508027_rule | 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. |
| ☐ | SV-214061r508027_rule | PostgreSQL must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-214062r508027_rule | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-214063r508027_rule | PostgreSQL must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-214064r508027_rule | PostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-214065r508027_rule | 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. |
| ☐ | SV-214066r508027_rule | PostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-214067r508027_rule | PostgreSQL must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-214068r508027_rule | The audit information produced by PostgreSQL must be protected from unauthorized deletion. |
| ☐ | SV-214069r508027_rule | PostgreSQL must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). |
| ☐ | SV-214070r548749_rule | PostgreSQL must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. |
| ☐ | SV-214071r508027_rule | PostgreSQL must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-214072r508027_rule | PostgreSQL must provide an immediate real-time alert to appropriate support staff of all audit log failures. |
| ☐ | SV-214073r548754_rule | PostgreSQL must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-214074r508027_rule | 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. |
| ☐ | SV-214075r508027_rule | The PostgreSQL software installation account must be restricted to authorized users. |
| ☐ | SV-214076r508027_rule | Database software, including PostgreSQL configuration files, must be stored in dedicated directories separate from the host OS and other applications. |
| ☐ | SV-214077r508027_rule | PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. |
| ☐ | SV-214078r508027_rule | Execution of software modules (to include functions and trigger procedures) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-214079r508027_rule | When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-214080r508027_rule | PostgreSQL must utilize centralized management of the content captured in audit records generated by all components of PostgreSQL. |
| ☐ | SV-214081r508027_rule | PostgreSQL must isolate security functions from non-security functions. |
| ☐ | SV-214082r508027_rule | PostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s). |
| ☐ | SV-214083r508027_rule | The audit information produced by PostgreSQL must be protected from unauthorized read access. |
| ☐ | SV-214084r508027_rule | When updates are applied to PostgreSQL software, any software components that have been replaced or made unnecessary must be removed. |
| ☐ | SV-214085r508027_rule | PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed. |
| ☐ | SV-214086r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-214087r508027_rule | PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-214088r508027_rule | PostgreSQL must generate audit records showing starting and ending time for user access to the database(s). |
| ☐ | SV-214089r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-214090r508027_rule | PostgreSQL must generate audit records when privileges/permissions are added. |
| ☐ | SV-214091r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-214092r508027_rule | PostgreSQL must generate audit records when successful logons or connections occur. |
| ☐ | SV-214093r508027_rule | PostgreSQL must generate audit records when security objects are deleted. |
| ☐ | SV-214094r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. |
| ☐ | SV-214095r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-214096r508027_rule | PostgreSQL must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-214097r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-214098r508027_rule | PostgreSQL must generate audit records when unsuccessful accesses to objects occur. |
| ☐ | SV-214099r508027_rule | PostgreSQL must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-214100r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-214101r508027_rule | PostgreSQL must be able to generate audit records when security objects are accessed. |
| ☐ | SV-214102r508027_rule | PostgreSQL must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-214103r508027_rule | PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur. |
| ☐ | SV-214104r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-214105r508027_rule | PostgreSQL must generate audit records when privileges/permissions are modified. |
| ☐ | SV-214106r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-214107r508027_rule | PostgreSQL must generate audit records when security objects are modified. |
| ☐ | SV-214108r508027_rule | PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is modified. |
| ☐ | SV-214109r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-214110r508027_rule | PostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-214111r508027_rule | PostgreSQL, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-214112r508027_rule | PostgreSQL must produce audit records containing sufficient information to establish where the events occurred. |
| ☐ | SV-214113r548752_rule | PostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-214114r508027_rule | PostgreSQL must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-214115r508027_rule | PostgreSQL must generate time stamps, for audit records and application data, with a minimum granularity of one second. |
| ☐ | SV-214116r508027_rule | PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. |
| ☐ | SV-214117r508027_rule | PostgreSQL must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-214119r508027_rule | PostgreSQL must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements. |
| ☐ | SV-214120r508027_rule | PostgreSQL must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-214121r508027_rule | PostgreSQL must prohibit user installation of logic modules (functions, trigger procedures, views, etc.) without explicit privileged status. |
| ☐ | SV-214122r508027_rule | PostgreSQL must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-214123r508027_rule | PostgreSQL must initiate session auditing upon startup. |
| ☐ | SV-214124r508027_rule | 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. |
| ☐ | SV-214125r508027_rule | PostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events. |
| ☐ | SV-214126r508027_rule | Unused database components, PostgreSQL software, and database objects must be removed. |
| ☐ | SV-214127r508027_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-214128r508027_rule | Unused database components which are integrated in PostgreSQL and cannot be uninstalled must be disabled. |
| ☐ | SV-214129r508027_rule | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-214130r508027_rule | If passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords. |
| ☐ | SV-214131r508027_rule | PostgreSQL must enforce access restrictions associated with changes to the configuration of PostgreSQL or database(s). |
| ☐ | SV-214132r508027_rule | PostgreSQL must protect against a user falsely repudiating having performed organization-defined actions. |
| ☐ | SV-214133r508027_rule | The system must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. |
| ☐ | SV-214134r508027_rule | 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. |
| ☐ | SV-214135r508027_rule | PostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-214136r508027_rule | PostgreSQL must enforce authorized access to all PKI private keys stored/utilized by PostgreSQL. |
| ☐ | SV-214137r508027_rule | 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. |
| ☐ | SV-214138r508027_rule | PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-214139r508027_rule | PostgreSQL must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-214140r508027_rule | PostgreSQL must invalidate session identifiers upon user logout or other session termination. |
| ☐ | SV-214141r508027_rule | PostgreSQL must protect its audit features from unauthorized access. |
| ☐ | SV-214142r508027_rule | PostgreSQL must produce audit records containing time stamps to establish when the events occurred. |
| ☐ | SV-214143r508027_rule | PostgreSQL must protect its audit features from unauthorized removal. |
| ☐ | SV-214144r508027_rule | 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. |
| ☐ | SV-214145r508027_rule | PostgreSQL must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-214146r508027_rule | PostgreSQL must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-214147r508027_rule | PostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. |
| ☐ | SV-214148r508027_rule | PostgreSQL must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-214149r508027_rule | PostgreSQL must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-214150r508027_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-214151r508027_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-214152r508027_rule | PostgreSQL must protect its audit configuration from unauthorized modification. |
| ☐ | SV-214153r508027_rule | PostgreSQL must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-214154r508027_rule | Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted. |
| ☐ | SV-214155r508027_rule | PostgreSQL must generate audit records when successful accesses to objects occur. |
| ☐ | SV-214156r508027_rule | PostgreSQL must generate audit records for all direct access to the database(s). |
| ☐ | SV-214157r508027_rule | The DBMS must be configured on a platform that has a NIST certified FIPS 140-2 installation of OpenSSL. |
| ☐ | SV-220321r508027_rule | PostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements. |
STIGQter: STIG Summary: