EP11-00-005800 - The EDB Postgres Advanced Server must isolate security functions from non-security functions.

Information

An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions.

Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based.

Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles.

Database Management Systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security functionality should not be commingled with objects or code implementing application logic. When security and non-security functionality are commingled, users who have access to non-security functionality may be able to access security functionality.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Remove all application-specific packages that were added to the sys, pg_catalog, information_schema, and dbo schemas.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_EDB_PGS_Advanced_Server_v11_Windows_V2R4_STIG.zip

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-3, CAT|II, CCI|CCI-001084, Rule-ID|SV-224179r961131_rule, STIG-ID|EP11-00-005800, STIG-Legacy|SV-109485, STIG-Legacy|V-100381, Vuln-ID|V-224179

Plugin: PostgreSQLDB

Control ID: 0413463f2a271e645185634af89d642437fcf116ffc7b787dbdeee1485b3e8b6