SQL Server security checks
The sqlserver_security module has 9 checks. SQL Server security posture (CIS-aligned, read-only). Findings feed the Database security area of the security score. Suggested actions are text for a DBA to follow in a change window; the platform never executes them.
This page is generated from the product's check catalog when the documentation is built, so the rules, intervals and default severities always match the version you are reading. Thresholds are defaults; entities and resources can override them.
| Check | Every | Default severity | Rule |
|---|---|---|---|
sqlserver_security.sa_enabledsa login enabled | 3600s | critical | is_disabled = 1 |
sqlserver_security.command_executionOperating-system command execution enabled (xp_cmdshell, OLE Automation) | 3600s | critical | value_in_use = 0 |
sqlserver_security.surface_areaSurface-area features enabled | 3600s | warning | value_in_use = 0 |
sqlserver_security.linked_server_credentialsLinked servers using sa or self credentials | 3600s | critical | warning >= 1 count / critical >= 1 count |
sqlserver_security.sysadmin_membersMembers of sysadmin / securityadmin | 300s | critical | any change |
sqlserver_security.failed_loginsFailed logins per minute | 60s | warning | warning >= 10 per_minute / critical >= 50 per_minute |
sqlserver_security.audit_enabledServer audit enabled and running | 3600s | warning | is_state_enabled = 1 |
sqlserver_security.encryptionTDE and backup encryption | 3600s | warning | backup_encrypted = true |
sqlserver_security.orphaned_usersOrphaned database users | 86400s | info | warning >= 1 count |
Checks
sqlserver_security.sa_enabled
sa login enabled
- Measures
sa_enabled· every3600s·tsql- Rule
is_disabled = 1· Default severity: critical- Action
- Confirm that no application, job or linked server signs in as sa (the error log and a login trace show it), then disable it in a change window (ALTER LOGIN [sa] DISABLE) and rename it if your policy requires it. Use named logins with only the permissions they need.
- Baseline
- CIS Microsoft SQL Server Benchmark: sa must be disabled (and ideally renamed); enforce password policy if it must exist. The well-known sid 0x01 finds it even when renamed. · source
sqlserver_security.command_execution
Operating-system command execution enabled (xp_cmdshell, OLE Automation)
- Measures
feature_enabled· every3600s·tsql- Rule
value_in_use = 0· Default severity: critical- Action
- Find what uses the option (search jobs and procedures for xp_cmdshell / sp_OACreate) with its owner. If nothing needs it, turn it off in a change window (EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'xp_cmdshell', 0; RECONFIGURE;). If it must stay, restrict who can run it and accept the risk with a reason.
- Baseline
- CIS: xp_cmdshell and Ole Automation Procedures must be 0 unless a documented exception exists. · source
sqlserver_security.surface_area
Surface-area features enabled
- Measures
feature_enabled· every3600s·tsql- Rule
value_in_use = 0· Default severity: warning- Action
- Ask the owner of the instance whether the option is needed (Database Mail XPs is needed by Database Mail, clr enabled by CLR assemblies). If not, set it to 0 in a change window (EXEC sp_configure '<option>', 0; RECONFIGURE;); if it is, accept the risk with the reason so the next review knows.
- Baseline
- CIS 2.1–2.8: each should be 0 unless documented. Command execution (xp_cmdshell, OLE Automation) is checked separately as critical. · source
sqlserver_security.linked_server_credentials
Linked servers using sa or self credentials
- Measures
risky_linked_logins(count) · every3600s·tsql- Rule
warning >= 1 count / critical >= 1 count· Default severity: critical- Action
- Create a remote login with only the rights the linked server needs (often read-only), map the local logins that use the linked server to it (sp_addlinkedsrvlogin with @useself = 'FALSE'), then remove the catch-all or sa mapping (sp_droplinkedsrvlogin) in a change window. Test the queries that use the linked server afterwards.
- Baseline
- Linked-server mappings must use a least-privilege remote login, never sa or a catch-all self credential. · source
sqlserver_security.sysadmin_members
Members of sysadmin / securityadmin
- Measures
privileged_members· every300s·tsql- Rule
any change· Default severity: critical- Action
- Confirm the change with the person who made it (the server audit or the default trace shows who) and that an approved request exists. If it was not approved, remove the member in a change window (ALTER SERVER ROLE [sysadmin] DROP MEMBER [<login>]) and review what the login did meanwhile. Resolve the event once reviewed.
- Baseline
- Any change in membership raises an event (the first run only records the baseline); review quarterly. · source
sqlserver_security.failed_logins
Failed logins per minute
- Measures
failed_logins_per_min(per_minute) · every60s·tsql- Rule
warning >= 10 per_minute / critical >= 50 per_minute· Default severity: warning- Action
- Read the error log entries (error 18456; the state number says why) to find the login and the client address. A service with an expired or changed password is fixed by its owner; an unknown client is blocked at the firewall. Keep CHECK_POLICY = ON for SQL logins so the Windows lockout policy applies.
- Baseline
- Bursts of failed logins from one client indicate brute force or a broken service credential. · source
sqlserver_security.audit_enabled
Server audit enabled and running
- Measures
audit_state· every3600s·tsql- Rule
is_state_enabled = 1· Default severity: warning- Action
- Create (or enable) a server audit that writes to a protected location, with a server audit specification for at least FAILED_LOGIN_GROUP, SUCCESSFUL_LOGIN_GROUP, SERVER_ROLE_MEMBER_CHANGE_GROUP and AUDIT_CHANGE_GROUP; turn it on with ALTER SERVER AUDIT [<name>] WITH (STATE = ON). An audit that is defined but disabled on purpose should be dropped or accepted with a reason.
- Baseline
- CIS 5.x: at least one server audit capturing login and role changes, enabled and running. · source
sqlserver_security.encryption
TDE and backup encryption
- Measures
encryption_state· every3600s·tsql- Rule
backup_encrypted = true· Default severity: warning- Action
- Create a certificate (or asymmetric key) in master, back it up with its private key to a safe place outside the server, then change the backup jobs to BACKUP DATABASE … WITH ENCRYPTION (ALGORITHM = AES_256, SERVER CERTIFICATE = <certificate>). Restore one encrypted backup on another server before relying on it. Consider TDE for databases with regulated data.
- Baseline
- Production backups should be encrypted; TDE recommended for regulated data (https://learn.microsoft.com/sql/relational-databases/security/encryption/transparent-data-encryption). · source
sqlserver_security.orphaned_users
Orphaned database users
- Measures
orphaned_users(count) · every86400s·tsql- Rule
warning >= 1 count· Default severity: info- Action
- For each user listed in the evidence, map it to its login when the login exists (ALTER USER [<user>] WITH LOGIN = [<login>]); otherwise confirm with the database owner that it is no longer needed and drop it (DROP USER [<user>]). On availability groups, create logins with the same SID on every replica.
- Baseline
- Orphaned users are a sign of restores without login sync; clean up or remap. · source
Related content
- SQL Server security: prerequisites and how to add resources
- Thresholds and baselines: how a default threshold is overridden