Skip to content

Ensure the pgcrypto extension is installed and configured correctly


PostgreSQL must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.

The PostgreSQL pgcrypto extension provides cryptographic functions for PostgreSQL and is intended to address the confidentiality and integrity of user and system information at rest in non-mobile devices.


PostgreSQL handling data that requires "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to PostgreSQL or implemented via additional software or operating system/file system settings, as appropriate to the situation.

Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e. full disk encryption) or encrypt specific data structures (e.g. files, records, or fields). Organizations may also optionally choose to implement both to implement layered security.

The decision whether, and what, to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. If the confidentiality and integrity of application data is not protected, the data will be open to compromise and unauthorized modification.

Applies To

  • Databases


This rule is applied when the following tags are present:

Tag With Value
secureclouddb/provider aws
secureclouddb/service rds
secureclouddb/engine postgres

Default Rule

const { getServerExtension, isEmpty } = module

 * @param {Object} databaseSettings - database settings object
 * @returns {boolean} true if the pgAudit extension is installed and enabled
function validate(databaseSettings) {
    const expectedExtension = 'pgcrypto'
    const expectedStatus = 'available'

    // check if the extension is available
    const pgcryptoExtension = getServerExtension(databaseSettings, expectedExtension);

    const success = pgcryptoExtension && 
        !isEmpty(pgcryptoExtension.status) && 
        pgcryptoExtension.status.toLowerCase() === expectedStatus;

    return {
        success: !!success,

// invoke