Results Summary

Generated

2019-05-20 15:48:11.984914

Results

Generated on 2019-05-20 15:48:11.984914

STIG # NIST # Description Result
V-72841 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. passed
V-72843 PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. failed
V-72845 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). skipped
V-72847 The audit information produced by PostgreSQL must be protected from unauthorized modification. passed
V-72849 PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. skipped
V-72851 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. passed
V-72853 Privileges to change PostgreSQL software modules must be limited. passed
V-72855 PostgreSQL must limit privileges to change functions and triggers, and links to software external to PostgreSQL. passed
V-72857 If passwords are used for authentication, PostgreSQL must transmit only encrypted representations of passwords. passed
V-72859 PostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. passed
V-72861 PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission. skipped
V-72863 PostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. passed
V-72865 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. passed
V-72867 PostgreSQL must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). passed
V-72869 PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in storage. skipped
V-72871 PostgreSQL must check the validity of all data inputs except those specifically identified by the organization. skipped
V-72873 PostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it. skipped
V-72875 PostgreSQL and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code i njection attack. skipped
V-72877 PostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. skipped
V-72883 PostgreSQL must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. passed
V-72885 The audit information produced by PostgreSQL must be protected from unauthorized deletion. passed
V-72887 PostgreSQL must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). passed
V-72889 PostgreSQL must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. passed
V-72891 PostgreSQL must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. passed
V-72893 PostgreSQL must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. skipped
V-72895 PostgreSQL must maintain the confidentiality and integrity of information during reception. failed
V-72897 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. passed
V-72899 The PostgreSQL software installation account must be restricted to authorized users. skipped
V-72901 Database software, including PostgreSQL configuration files, must be stored in dedicated directories separate from the host OS and other applications. passed
V-72903 PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. skipped
V-72905 Execution of software modules (to include functions and trigger procedures) with elevated privileges must be restricted to necessary cases only. failed
V-72907 When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives. passed
V-72909 PostgreSQL must utilize centralized management of the content captured in audit records generated by all components of PostgreSQL. failed
V-72911 PostgreSQL must isolate security functions from non-security functions. passed
V-72913 PostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s). passed
V-72915 The audit information produced by PostgreSQL must be protected from unauthorized read access. passed
V-72917 When updates are applied to PostgreSQL software, any software components that have been replaced or made unnecessary must be removed. skipped
V-72919 PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed. failed
V-72921 PostgreSQL must generate audit records when unsuccessful attempts to access security objects occur. passed
V-72923 PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur. passed
V-72925 PostgreSQL must generate audit records showing starting and ending time for user access to the database(s). passed
V-72927 PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur. passed
V-72929 PostgreSQL must generate audit records when privileges/permissions are added. passed
V-72931 PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur. failed
V-72933 PostgreSQL must generate audit records when successful logons or connections occur. passed
V-72939 PostgreSQL must generate audit records when security objects are deleted. passed
V-72941 PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. passed
V-72945 PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur. passed
V-72947 PostgreSQL must be able to generate audit records when privileges/permissions are retrieved. failed
V-72949 PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur. failed
V-72951 PostgreSQL must generate audit records when unsuccessful accesses to objects occur. passed
V-72953 PostgreSQL must generate audit records for all privileged activities or other system-level access. failed
V-72955 PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur. failed
V-72957 PostgreSQL must be able to generate audit records when security objects are accessed. failed
V-72959 PostgreSQL must generate audit records when privileges/permissions are deleted. failed
V-72961 PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur. passed
V-72963 PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur. failed
V-72965 PostgreSQL must generate audit records when privileges/permissions are modified. passed
V-72969 PostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. passed
V-72971 PostgreSQL must generate audit records when security objects are modified. failed
V-72973 PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is modified. failed
V-72975 PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur. passed
V-72977 PostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur. passed
V-72979 PostgreSQL, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. failed
V-72981 PostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission. failed
V-72983 PostgreSQL must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. skipped
V-72985 PostgreSQL must generate time stamps, for audit records and application data, with a minimum granularity of one second. passed
V-72987 PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. passed
V-72989 PostgreSQL must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. failed
V-72991 PostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements. failed
V-72993 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. failed
V-72995 PostgreSQL must protect the confidentiality and integrity of all information at rest. passed
V-72997 PostgreSQL must prohibit user installation of logic modules (functions, trigger procedures, views, etc.) without explicit privileged status. passed
V-72999 PostgreSQL must separate user functionality (including user interface services) from database management functionality. failed
V-73001 PostgreSQL must initiate session auditing upon startup. passed
V-73003 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. passed
V-73005 PostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events. passed
V-73007 Unused database components, PostgreSQL software, and database objects must be removed. passed
V-73009 Access to external executables must be disabled or restricted. passed
V-73011 Unused database components which are integrated in PostgreSQL and cannot be uninstalled must be disabled. skipped
V-73013 PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in process. skipped
V-73015 If passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords. passed
V-73017 PostgreSQL must enforce access restrictions associated with changes to the configuration of PostgreSQL or database(s). passed
V-73019 PostgreSQL must protect against a user falsely repudiating having performed organization-defined actions. passed
V-73021 PostgreSQL must provide the capability for authorized users to capture, record, and log all content related to a user session. failed
V-73023 The system must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. skipped
V-73025 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. passed
V-73027 PostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. skipped
V-73029 PostgreSQL must enforce authorized access to all PKI private keys stored/utilized by PostgreSQL. failed
V-73031 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. failed
V-73033 PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred. passed
V-73035 PostgreSQL must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. passed
V-73037 PostgreSQL must invalidate session identifiers upon user logout or other session termination. passed
V-73039 PostgreSQL must protect its audit features from unauthorized access. passed
V-73041 PostgreSQL must produce audit records containing time stamps to establish when the events occurred. passed
V-73043 PostgreSQL must protect its audit features from unauthorized removal. passed
V-73045 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. skipped
V-73047 PostgreSQL must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. failed
V-73049 PostgreSQL must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). passed
V-73051 PostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. skipped
V-73053 PostgreSQL must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. passed
V-73055 PostgreSQL must map the PKI-authenticated identity to an associated user account. skipped
V-73057 Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. skipped
V-73059 Access to database files must be limited to relevant processes and to authorized, administrative users. passed
V-73061 PostgreSQL must protect its audit configuration from unauthorized modification. passed
V-73063 PostgreSQL must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. failed
V-73065 Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted. failed
V-73067 PostgreSQL must generate audit records when successful accesses to objects occur. failed
V-73069 PostgreSQL must generate audit records for all direct access to the database(s). passed
V-73071 The DBMS must be configured on a platform that has a NIST certified FIPS 140-2 installation of OpenSSL. skipped
V-73123 PostgreSQL must produce audit records containing sufficient information to establish where the events occurred. passed