Pular para o conteúdo principal
Versão: 0.4 · atual

Verificações de segurança do SQL Server

ReferênciaRevisado em 11 de outubro de 2026
Aplica-se a:Excubius 0.4Funções: Operador, Editor, Administrador de entidade
PlanosPro · EnterpriseImplantaçãoAuto-hospedado

O módulo sqlserver_security tem 9 verificações. Postura de segurança do SQL Server (alinhada ao CIS, somente leitura). As descobertas alimentam a área Database security da pontuação de segurança. As ações sugeridas são textos para um DBA seguir em uma janela de mudança; a plataforma nunca as executa.

Esta página é gerada a partir do catálogo de verificações do produto quando a documentação é compilada, portanto as regras, os intervalos e as severidades padrão sempre correspondem à versão que você está lendo. Os limites são valores padrão; entidades e recursos podem substituí-los.

VerificaçãoIntervaloGravidade padrãoRegra
sqlserver_security.sa_enabled
sa login enabled
3600scriticalis_disabled = 1
sqlserver_security.command_execution
Operating-system command execution enabled (xp_cmdshell, OLE Automation)
3600scriticalvalue_in_use = 0
sqlserver_security.surface_area
Surface-area features enabled
3600swarningvalue_in_use = 0
sqlserver_security.linked_server_credentials
Linked servers using sa or self credentials
3600scriticalwarning >= 1 count / critical >= 1 count
sqlserver_security.sysadmin_members
Members of sysadmin / securityadmin
300scriticalany change
sqlserver_security.failed_logins
Failed logins per minute
60swarningwarning >= 10 per_minute / critical >= 50 per_minute
sqlserver_security.audit_enabled
Server audit enabled and running
3600swarningis_state_enabled = 1
sqlserver_security.encryption
TDE and backup encryption
3600swarningbackup_encrypted = true
sqlserver_security.orphaned_users
Orphaned database users
86400sinfowarning >= 1 count

Verificações​

sqlserver_security.sa_enabled

sa login enabled

Métrica
sa_enabled · a cada 3600s · tsql
Regra
is_disabled = 1 · Gravidade padrão: critical
Ação
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.
Linha de base
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. · fonte

sqlserver_security.command_execution

Operating-system command execution enabled (xp_cmdshell, OLE Automation)

Métrica
feature_enabled · a cada 3600s · tsql
Regra
value_in_use = 0 · Gravidade padrão: critical
Ação
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.
Linha de base
CIS: xp_cmdshell and Ole Automation Procedures must be 0 unless a documented exception exists. · fonte

sqlserver_security.surface_area

Surface-area features enabled

Métrica
feature_enabled · a cada 3600s · tsql
Regra
value_in_use = 0 · Gravidade padrão: warning
Ação
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.
Linha de base
CIS 2.1–2.8: each should be 0 unless documented. Command execution (xp_cmdshell, OLE Automation) is checked separately as critical. · fonte

sqlserver_security.linked_server_credentials

Linked servers using sa or self credentials

Métrica
risky_linked_logins (count) · a cada 3600s · tsql
Regra
warning >= 1 count / critical >= 1 count · Gravidade padrão: critical
Ação
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.
Linha de base
Linked-server mappings must use a least-privilege remote login, never sa or a catch-all self credential. · fonte

sqlserver_security.sysadmin_members

Members of sysadmin / securityadmin

Métrica
privileged_members · a cada 300s · tsql
Regra
any change · Gravidade padrão: critical
Ação
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.
Linha de base
Any change in membership raises an event (the first run only records the baseline); review quarterly. · fonte

sqlserver_security.failed_logins

Failed logins per minute

Métrica
failed_logins_per_min (per_minute) · a cada 60s · tsql
Regra
warning >= 10 per_minute / critical >= 50 per_minute · Gravidade padrão: warning
Ação
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.
Linha de base
Bursts of failed logins from one client indicate brute force or a broken service credential. · fonte

sqlserver_security.audit_enabled

Server audit enabled and running

Métrica
audit_state · a cada 3600s · tsql
Regra
is_state_enabled = 1 · Gravidade padrão: warning
Ação
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.
Linha de base
CIS 5.x: at least one server audit capturing login and role changes, enabled and running. · fonte

sqlserver_security.encryption

TDE and backup encryption

Métrica
encryption_state · a cada 3600s · tsql
Regra
backup_encrypted = true · Gravidade padrão: warning
Ação
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.
Linha de base
Production backups should be encrypted; TDE recommended for regulated data (https://learn.microsoft.com/sql/relational-databases/security/encryption/transparent-data-encryption). · fonte

sqlserver_security.orphaned_users

Orphaned database users

Métrica
orphaned_users (count) · a cada 86400s · tsql
Regra
warning >= 1 count · Gravidade padrão: info
Ação
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.
Linha de base
Orphaned users are a sign of restores without login sync; clean up or remap. · fonte