Title

Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership. (Cat II impact)

Discussion

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 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.

Check Content

Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s). If any database objects are found to be owned by users not authorized to own database objects, this is a finding.

Fix Text

Assign ownership of authorized objects to authorized object owner accounts.

Additional Identifiers

Rule ID: SV-206547r879586_rule

Vulnerability ID: V-206547

Group Title: SRG-APP-000133

Expert Comments

CCIs tied to check.

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