From MS SQL Server 2016 Database Security Technical Implementation Guide
Part of SRG-APP-000380-DB-000360
Associated with: CCI-001813
Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system.
Obtain a list of users who have privileged role memberships in the database. Execute the following query to obtain a list of users and roles and their respective role memberships. SELECT p.name AS Principal, p.type_desc AS Type, r.name AS Role FROM sys.database_principals p INNER JOIN sys.database_role_members rm ON p.principal_id = rm.member_principal_id INNER JOIN sys.database_principals r ON rm.role_principal_id = r.principal_id WHERE r.name = 'db_owner' UNION ALL SELECT l.name AS Principal, l.type_desc AS Type, 'dbo' AS Role FROM sys.databases d INNER JOIN sys.server_principals l ON d.owner_sid = l.sid WHERE d.name = DB_NAME() Review the server documentation to verify the users and roles returned are authorized. If any users and/or roles are not documented and authorized, this is a finding.
Remove unauthorized users from roles: ALTER ROLE DROP MEMBER user; https://msdn.microsoft.com/en-us/library/ms189775.aspx Set the owner of the database to an authorized login: ALTER AUTHORIZATION ON database::DatabaseName TO login; https://msdn.microsoft.com/en-us/library/ms187359.aspx
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer