Comprobaciones de seguridad de SQL Server
El módulo sqlserver_security tiene 9 comprobaciones. Postura de seguridad de SQL Server (alineada con CIS, solo lectura). Los hallazgos alimentan el área de seguridad de bases de datos de la puntuación de seguridad. Las acciones sugeridas son texto para que un DBA las aplique en una ventana de cambios; la plataforma nunca las ejecuta.
Esta página se genera a partir del catálogo de comprobaciones del producto al compilar la documentación, así que las reglas, los intervalos y las severidades predeterminadas siempre coinciden con la versión que estás leyendo. Los umbrales son valores predeterminados; las entidades y los recursos pueden reemplazarlos.
| Comprobación | Cada | Severidad predeterminada | Regla |
|---|---|---|---|
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 |
Comprobaciones
sqlserver_security.sa_enabled
sa login enabled
- Mide
sa_enabled· cada3600s·tsql- Regla
is_disabled = 1· Severidad predeterminada: critical- Acción
- 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.
- Línea 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. · origen
sqlserver_security.command_execution
Operating-system command execution enabled (xp_cmdshell, OLE Automation)
- Mide
feature_enabled· cada3600s·tsql- Regla
value_in_use = 0· Severidad predeterminada: critical- Acción
- 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.
- Línea base
- CIS: xp_cmdshell and Ole Automation Procedures must be 0 unless a documented exception exists. · origen
sqlserver_security.surface_area
Surface-area features enabled
- Mide
feature_enabled· cada3600s·tsql- Regla
value_in_use = 0· Severidad predeterminada: warning- Acción
- 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.
- Línea base
- CIS 2.1–2.8: each should be 0 unless documented. Command execution (xp_cmdshell, OLE Automation) is checked separately as critical. · origen
sqlserver_security.linked_server_credentials
Linked servers using sa or self credentials
- Mide
risky_linked_logins(count) · cada3600s·tsql- Regla
warning >= 1 count / critical >= 1 count· Severidad predeterminada: critical- Acción
- 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.
- Línea base
- Linked-server mappings must use a least-privilege remote login, never sa or a catch-all self credential. · origen
sqlserver_security.sysadmin_members
Members of sysadmin / securityadmin
- Mide
privileged_members· cada300s·tsql- Regla
any change· Severidad predeterminada: critical- Acción
- 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.
- Línea base
- Any change in membership raises an event (the first run only records the baseline); review quarterly. · origen
sqlserver_security.failed_logins
Failed logins per minute
- Mide
failed_logins_per_min(per_minute) · cada60s·tsql- Regla
warning >= 10 per_minute / critical >= 50 per_minute· Severidad predeterminada: warning- Acción
- 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.
- Línea base
- Bursts of failed logins from one client indicate brute force or a broken service credential. · origen
sqlserver_security.audit_enabled
Server audit enabled and running
- Mide
audit_state· cada3600s·tsql- Regla
is_state_enabled = 1· Severidad predeterminada: warning- Acción
- 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.
- Línea base
- CIS 5.x: at least one server audit capturing login and role changes, enabled and running. · origen
sqlserver_security.encryption
TDE and backup encryption
- Mide
encryption_state· cada3600s·tsql- Regla
backup_encrypted = true· Severidad predeterminada: warning- Acción
- 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.
- Línea base
- Production backups should be encrypted; TDE recommended for regulated data (https://learn.microsoft.com/sql/relational-databases/security/encryption/transparent-data-encryption). · origen
sqlserver_security.orphaned_users
Orphaned database users
- Mide
orphaned_users(count) · cada86400s·tsql- Regla
warning >= 1 count· Severidad predeterminada: info- Acción
- 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.
- Línea base
- Orphaned users are a sign of restores without login sync; clean up or remap. · origen
Contenido relacionado
- Seguridad de SQL Server: requisitos previos y cómo agregar recursos
- Umbrales y líneas base: cómo se reemplaza un umbral predeterminado