What you can do to protect your SQL Server and why it matters
summary
CIS Benchmark for SQL Server (about 103 pages) maps each recommendation to T‑SQL checks and remediation, and emphasizes concrete steps: disable ad hoc distributed queries, remove or secure xp_cmdshell, set database TRUSTWORTHY off, enforce a random 64‑char SA password (note: renaming SA once broke Azure VM backups), limit DAC to a specific admin host, increase error log files and use Extended Events for login auditing. A PowerShell scan using DBAchecks/DBAtools produces a Power BI compliance report across many servers.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:46What is the CIS Benchmark for SQL Server
- 4:15Why do we need the CIS benchmark?
- 7:28Section 1 Installation, Updates and Patches
- 8:40Section 2 Surface Area Reduction
- 10:27Surface Area Reduction pt 2
- 12:55Authentication and Authorization
- 15:48Auditing and Logging
- 17:434 Password Policies
- 18:39What's Missing?
related talks
21mWhat you can do to protect your SQL Server and why it matters
54m10 Deadly Sins of SQL Server Configuration
48mProtecting the confidentiality and integrity of your high value data with Azure SQL and SQL Server 2
19mPushing Your Power BI Potential: A Comprehensive Health Check for Improved Performance and Security
52mDetecting Malicious Activity: Unveiling the Secrets of MS-SQL Logging
18mPushing Your Power BI Potential: A Comprehensive Health Check for Improved Performance and Security
19mMicrosoft Defender for SQL: Advanced Threat Protection
40mHow To Get the Auditors Off Your Butt with dbachecks