| V-233511 | | 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. | To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within d... |
| V-233512 | | PostgreSQL must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. | Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel... |
| V-233513 | | 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). | Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching t... |
| V-233514 | | The audit information produced by PostgreSQL must be protected from unauthorized modification. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-233516 | | 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. | Any PostgreSQL or associated application providing too much information in error messages on the screen or printout risks compromising the data and se... |
| V-233517 | | Privileges to change PostgreSQL software modules must be limited. | If the system were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate test... |
| V-233518 | | PostgreSQL must limit privileges to change functions and triggers, and links to software external to PostgreSQL. | If the system were to allow any user to make changes to software libraries, those changes might be implemented without undergoing the appropriate test... |
| V-233521 | | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in transmission. | Without the association of security labels to information, there is no basis for PostgreSQL to make security-related access-control decisions.
Securi... |
| V-233522 | | PostgreSQL must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. | Database management includes the ability to control the number of users and user sessions utilizing PostgreSQL. Unlimited concurrent connections to Po... |
| V-233523 | | 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. | If PostgreSQL were to allow any user to make changes to database structure or logic, those changes might be implemented without undergoing the appropr... |
| V-233524 | | PostgreSQL must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). | Non-organizational users include all information system users other than organizational users, which includes organizational employees or individuals ... |
| V-233525 | | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in storage. | Without the association of security labels to information, there is no basis for PostgreSQL to make security-related access-control decisions.
Securi... |
| V-233526 | | PostgreSQL must check the validity of all data inputs except those specifically identified by the organization. | Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process ... |
| V-233527 | | PostgreSQL and associated applications must reserve the use of dynamic code execution for situations that require it. | With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of t... |
| V-233528 | | 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. | With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of t... |
| V-233529 | | PostgreSQL must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. | To ensure sufficient storage capacity for the audit logs, PostgreSQL must be able to allocate audit record storage capacity. Although another requirem... |
| V-233530 | | PostgreSQL must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. | Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should ... |
| V-233531 | | The audit information produced by PostgreSQL must be protected from unauthorized deletion. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-233532 | | PostgreSQL must record time stamps, in audit records and application data that can be mapped to Coordinated Universal Time (UTC, formerly GMT). | If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.
Time stamps generate... |
| V-233533 | | PostgreSQL must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA. | If PostgreSQL provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and ... |
| V-233534 | | 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. | Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or i... |
| V-233535 | | PostgreSQL must provide an immediate alert to appropriate support staff of all audit log failures. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time aler... |
| V-233537 | | 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. | It is critical that when PostgreSQL is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing ... |
| V-233538 | | PostgreSQL must maintain the confidentiality and integrity of information during reception. | Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protoc... |
| V-233539 | | 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. | Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to ot... |
| V-233541 | | Database software, including PostgreSQL configuration files, must be stored in dedicated directories separate from the host OS and other applications. | When dealing with change control issues, it should be noted, any changes to the hardware, software, and/or firmware components of the information syst... |
| V-233542 | | PostgreSQL must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. | Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possib... |
| V-233543 | | Execution of software modules (to include functions and trigger procedures) with elevated privileges must be restricted to necessary cases only. | In certain situations, to provide required functionality, PostgreSQL needs to execute internal logic (stored procedures, functions, triggers, etc.) an... |
| V-233544 | | When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives. | A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior c... |
| V-233546 | | PostgreSQL must isolate security functions from non-security functions. | An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.
Sec... |
| V-233547 | | PostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s). | Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an a... |
| V-233548 | | 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. | Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.... |
| V-233549 | | The audit information produced by PostgreSQL must be protected from unauthorized read access. | If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity i... |
| V-233550 | | When updates are applied to PostgreSQL software, any software components that have been replaced or made unnecessary must be removed. | Previous versions of PostgreSQL components that are not removed from the information system after updates have been installed may be exploited by adve... |
| V-233551 | | PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed... |
| V-233552 | | PostgreSQL must generate audit records when unsuccessful attempts to access security objects occur. | Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data m... |
| V-233553 | | PostgreSQL must generate audit records when unsuccessful logons or connection attempts occur. | For completeness of forensic analysis, it is necessary to track failed attempts to log on to PostgreSQL. While positive identification may not be poss... |
| V-233554 | | PostgreSQL must generate audit records showing starting and ending time for user access to the database(s). | For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to PostgreSQL lasts. This can be ac... |
| V-233555 | | PostgreSQL must generate audit records when unsuccessful attempts to modify security objects occur. | Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and... |
| V-233556 | | PostgreSQL must generate audit records when privileges/permissions are added. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-233557 | | PostgreSQL must generate audit records when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur. | Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in diag... |
| V-233558 | | PostgreSQL must generate audit records when successful logons or connections occur. | For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to PostgreSQL.... |
| V-233559 | | PostgreSQL must generate audit records when security objects are deleted. | The removal of security objects from the database/PostgreSQL would seriously degrade a system's information assurance posture. If such an event occurs... |
| V-233560 | | PostgreSQL must generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to con... |
| V-233561 | | PostgreSQL must generate audit records when unsuccessful attempts to delete privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-233562 | | PostgreSQL must be able to generate audit records when privileges/permissions are retrieved. | Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to con... |
| V-233563 | | PostgreSQL must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur. | Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in diag... |
| V-233564 | | PostgreSQL must generate audit records when unsuccessful accesses to objects occur. | Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to est... |
| V-233565 | | PostgreSQL must generate audit records for all privileged activities or other system-level access. | Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify th... |
| V-233566 | | PostgreSQL must generate audit records when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
To aid in di... |
| V-233567 | | PostgreSQL must be able to generate audit records when security objects are accessed. | Changes to the security configuration must be tracked.
This requirement applies to situations where security data is retrieved or modified via data m... |
| V-233568 | | PostgreSQL must generate audit records when privileges/permissions are deleted. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-233569 | | PostgreSQL must generate audit records when concurrent logons/connections by the same user from different workstations occur. | For completeness of forensic analysis, it is necessary to track who logs on to PostgreSQL.
Concurrent connections by the same user from multiple work... |
| V-233570 | | PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur. | The removal of security objects from the database/PostgreSQL would seriously degrade a system's information assurance posture. If such an action is at... |
| V-233571 | | PostgreSQL must generate audit records when privileges/permissions are modified. | Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restri... |
| V-233572 | | PostgreSQL must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. | Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify th... |
| V-233573 | | PostgreSQL must generate audit records when security objects are modified. | Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and... |
| V-233574 | | PostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) is modified. | Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed... |
| V-233575 | | PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-233576 | | PostgreSQL must generate audit records when unsuccessful attempts to add privileges/permissions occur. | Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized atte... |
| V-233577 | | PostgreSQL, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. | The DoD standard for authentication is DoD-approved PKI certificates.
A certificate's certification path is the path from the end entity certificate ... |
| V-233578 | | PostgreSQL must produce audit records containing sufficient information to establish where the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to est... |
| V-233579 | | PostgreSQL must maintain the confidentiality and integrity of information during preparation for transmission. | Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during agg... |
| V-233580 | | PostgreSQL must be configured to provide audit record generation for DoD-defined auditable events within all DBMS/database components. | Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or... |
| V-233581 | | PostgreSQL must generate time stamps, for audit records and application data, with a minimum granularity of one second. | Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records.
Time stamps generated ... |
| V-233582 | | PostgreSQL must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. | Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (... |
| V-233587 | | PostgreSQL must prohibit user installation of logic modules (functions, trigger procedures, views, etc.) without explicit privileged status. | Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be inst... |
| V-233588 | | PostgreSQL must separate user functionality (including user interface services) from database management functionality. | Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typ... |
| V-233589 | | PostgreSQL must initiate session auditing upon startup. | Session auditing is for use when a user's activities are under investigation. To ensure the capture of all activity during those periods when session ... |
| V-233590 | | 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. | PostgreSQLs handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification ... |
| V-233591 | | PostgreSQL must produce audit records containing sufficient information to establish the sources (origins) of the events. | Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to e... |
| V-233592 | | Unused database components, PostgreSQL software, and database objects must be removed. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-233593 | | Access to external executables must be disabled or restricted. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-233594 | | Unused database components that are integrated in PostgreSQL and cannot be uninstalled must be disabled. | Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may no... |
| V-233595 | | PostgreSQL must associate organization-defined types of security labels having organization-defined security label values with information in process. | Without the association of security labels to information, there is no basis for PostgreSQL to make security-related access-control decisions.
Securi... |
| V-233597 | | PostgreSQL must enforce access restrictions associated with changes to the configuration of PostgreSQL or database(s). | Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the sy... |
| V-233598 | | PostgreSQL must protect against a user falsely repudiating having performed organization-defined actions. | Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating... |
| V-233599 | | 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. | Organizations are required to use a central log management system, so under normal conditions, the audit space allocated to PostgreSQL on its own serv... |
| V-233600 | | 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. | If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not... |
| V-233601 | | PostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. | The DOD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, ... |
| V-233603 | | 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. | Only DoD-approved external PKIs have been evaluated to ensure security controls and identity vetting procedures are in place that are sufficient for D... |
| V-233604 | | PostgreSQL must produce audit records containing sufficient information to establish what type of events occurred. | Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be diffi... |
| V-233605 | | PostgreSQL must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. | PostgreSQLs handling data requiring data-at-rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification ... |
| V-233606 | | PostgreSQL must invalidate session identifiers upon user logout or other session termination. | Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and continue to employ previously v... |
| V-233607 | | PostgreSQL must protect its audit features from unauthorized access. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.
Depending upon the log format and app... |
| V-233608 | | PostgreSQL must produce audit records containing time stamps to establish when the events occurred. | Information system auditing capability is critical for accurate forensic analysis. Without establishing when events occurred, it is impossible to esta... |
| V-233609 | | PostgreSQL must protect its audit features from unauthorized removal. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-233610 | | 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. | Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Off-loading is a common process in information s... |
| V-233611 | | PostgreSQL must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. | One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identif... |
| V-233612 | | PostgreSQL must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | To ensure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and... |
| V-233613 | | PostgreSQL must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. | This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with commu... |
| V-233615 | | PostgreSQL must map the PKI-authenticated identity to an associated user account. | The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to PostgreSQL user ... |
| V-233616 | | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. | Applications, including PostgreSQL, must prevent unauthorized and unintended information transfer via shared system resources.
Data used for the deve... |
| V-233617 | | Access to database files must be limited to relevant processes and to authorized, administrative users. | Applications, including PostgreSQL, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only DBMS pr... |
| V-233618 | | PostgreSQL must protect its audit configuration from unauthorized modification. | Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is ne... |
| V-233620 | | Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted. | Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.
For detailed i... |
| V-233621 | | PostgreSQL must generate audit records when successful accesses to objects occur. | Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to est... |
| V-233622 | | PostgreSQL must generate audit records for all direct access to the database(s). | In this context, direct access is any query, command, or call to the DBMS that comes from any source other than the application(s) that it supports. E... |
| V-233536 | | 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. | It is critical that when PostgreSQL is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing ... |
| V-233515 | | PostgreSQL must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. | Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functi... |
| V-233519 | | If passwords are used for authentication, PostgreSQL must transmit only encrypted representations of passwords. | The DoD standard for authentication is DoD-approved PKI certificates.
Authentication based on User ID and Password may be used only when it is not po... |
| V-233520 | | PostgreSQL must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. | Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access PostgreSQL. To mitigate the risk of unauthorized... |
| V-233540 | | The PostgreSQL software installation account must be restricted to authorized users. | When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information syste... |
| V-233583 | | PostgreSQL must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-233584 | | PostgreSQL must use NSA-approved cryptography to protect classified information in accordance with the data owner’s requirements. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-233585 | | PostgreSQL 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 owner’s requirements. | Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptogr... |
| V-233586 | | PostgreSQL must protect the confidentiality and integrity of all information at rest. | This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and sys... |
| V-233596 | | If passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords. | The DOD standard for authentication is DOD-approved PKI certificates.
Authentication based on User ID and Password may be used only when it is not po... |
| V-233602 | | PostgreSQL must enforce authorized access to all PKI private keys stored/utilized by PostgreSQL. | The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate h... |
| V-233614 | | PostgreSQL must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. | Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary... |
| V-233619 | | PostgreSQL must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations. | Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak alg... |
| V-233623 | | The DBMS must be configured on a platform that has a NIST certified FIPS 140-2 or 140-3 installation of OpenSSL. | PostgreSQL uses OpenSSL for the underlying encryption layer. It must be installed on an operating system that contains a certified FIPS 140-2 or 140-3... |
| V-265871 | | PostgreSQL products must be a version supported by the vendor. | Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack ... |
