Detections
Analytics
SQLD-22-001300 - Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to SQL Server, etc.) must be owned by database/DBMS principals authorized for ownership.
Information
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 uses 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 in SQL Server rely on unauthorized owner accounts, these objects may be lost when an account is removed.
NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.
Solution
Document and obtain approval for any account(s) authorized for object ownership. If necessary, use the ALTER AUTHORIZATION command to change object ownership to an authorized account.Example provided below.
ALTER AUTHORIZATION ON OBJECT::test.table TO AuthorizedUser;
https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-authorization-transact-sql
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_SQL_Server_2022_Y26M04_STIG.zip
Item Details
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-5(6), CAT|II, CCI|CCI-001499, Rule-ID|SV-271146r1109183_rule, STIG-ID|SQLD-22-001300, Vuln-ID|V-271146
Plugin: MS_SQLDB
Control ID: 146e853781f0b47152ff2aee276b81acc8bf91781203287e3b6be205ac1fd19b