Title

The EDB Postgres Advanced Server must isolate security functions from nonsecurity functions. (Cat II impact)

Discussion

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 nonsecurity 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 nonsecurity functionality are commingled, users who have access to nonsecurity functionality may be able to access security functionality.

Check Content

All EDB Postgres Advanced Server built-in security packages are in the sys, pg_catalog, information_schema, and dbo schemas. If any application-specific packages have been added to these schemas, this is a finding.

Fix Text

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

Additional Identifiers

Rule ID: SV-259260r938833_rule

Vulnerability ID: V-259260

Group Title: SRG-APP-000233-DB-000124

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.