Перейти к основному содержимому
Версия: 0.4 · текущая

Проверки безопасности SQL Server

СправочникПроверено 11 октября 2026 г.
Область применения:Excubius 0.4Роли: Оператор, Редактор, Администратор сущности
ПланыPro · EnterpriseРазвертываниеСамостоятельное размещение

Модуль sqlserver_security содержит 9 проверок. Состояние безопасности SQL Server (в соответствии с CIS, только для чтения). Замечания учитываются в области Database security оценки безопасности. Рекомендуемые действия — это текст, по которому администратор баз данных действует в окне изменений; платформа никогда их не выполняет.

Эта страница создается из каталога проверок продукта при сборке документации, поэтому правила, интервалы и уровни серьезности по умолчанию всегда соответствуют версии, которую вы читаете. Пороговые значения указаны по умолчанию; сущности и ресурсы могут их переопределить.

ПроверкаИнтервалСерьезность по умолчаниюПравило
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

Проверки​

sqlserver_security.sa_enabled

sa login enabled

Метрика
sa_enabled · каждые 3600s · tsql
Правило
is_disabled = 1 · Серьезность по умолчанию: critical
Действие
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.
Базовый уровень
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. · источник

sqlserver_security.command_execution

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

Метрика
feature_enabled · каждые 3600s · tsql
Правило
value_in_use = 0 · Серьезность по умолчанию: critical
Действие
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.
Базовый уровень
CIS: xp_cmdshell and Ole Automation Procedures must be 0 unless a documented exception exists. · источник

sqlserver_security.surface_area

Surface-area features enabled

Метрика
feature_enabled · каждые 3600s · tsql
Правило
value_in_use = 0 · Серьезность по умолчанию: warning
Действие
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.
Базовый уровень
CIS 2.1–2.8: each should be 0 unless documented. Command execution (xp_cmdshell, OLE Automation) is checked separately as critical. · источник

sqlserver_security.linked_server_credentials

Linked servers using sa or self credentials

Метрика
risky_linked_logins (count) · каждые 3600s · tsql
Правило
warning >= 1 count / critical >= 1 count · Серьезность по умолчанию: critical
Действие
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.
Базовый уровень
Linked-server mappings must use a least-privilege remote login, never sa or a catch-all self credential. · источник

sqlserver_security.sysadmin_members

Members of sysadmin / securityadmin

Метрика
privileged_members · каждые 300s · tsql
Правило
any change · Серьезность по умолчанию: critical
Действие
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.
Базовый уровень
Any change in membership raises an event (the first run only records the baseline); review quarterly. · источник

sqlserver_security.failed_logins

Failed logins per minute

Метрика
failed_logins_per_min (per_minute) · каждые 60s · tsql
Правило
warning >= 10 per_minute / critical >= 50 per_minute · Серьезность по умолчанию: warning
Действие
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.
Базовый уровень
Bursts of failed logins from one client indicate brute force or a broken service credential. · источник

sqlserver_security.audit_enabled

Server audit enabled and running

Метрика
audit_state · каждые 3600s · tsql
Правило
is_state_enabled = 1 · Серьезность по умолчанию: warning
Действие
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.
Базовый уровень
CIS 5.x: at least one server audit capturing login and role changes, enabled and running. · источник

sqlserver_security.encryption

TDE and backup encryption

Метрика
encryption_state · каждые 3600s · tsql
Правило
backup_encrypted = true · Серьезность по умолчанию: warning
Действие
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.
Базовый уровень
Production backups should be encrypted; TDE recommended for regulated data (https://learn.microsoft.com/sql/relational-databases/security/encryption/transparent-data-encryption). · источник

sqlserver_security.orphaned_users

Orphaned database users

Метрика
orphaned_users (count) · каждые 86400s · tsql
Правило
warning >= 1 count · Серьезность по умолчанию: info
Действие
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.
Базовый уровень
Orphaned users are a sign of restores without login sync; clean up or remap. · источник