Database objects must be owned by database/EDB Postgres Advanced Server principals authorized for ownership.
An XCCDF Rule
Description
<VulnDiscussion>Database objects include but are not limited to tables, indexes, storage, stored procedures, functions, triggers, and links to software external to the EDB Postgres Advanced Server, etc. Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions as if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals. Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-259238r960960_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Assign ownership of authorized objects to authorized object owner accounts by running the following SQL command for each object to be changed:
ALTER <type> <object name> OWNER TO <new owner>;
For example: ALTER TABLE my_table OWNER TO APP_USER;