Azure SQL Database Auditing Not Enabled
Database access is not recorded, so a question about who read which data cannot be answered.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable auditing on the SQL database.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- SQL Databases on Azure
- The fix, by hand
- SQL Server (or database) → Security → Auditing.
- Enable Auditing at the server level so child databases inherit it.
- Pick a destination: Log Analytics workspace (preferred for KQL + Defender for SQL correlation), Event Hub, or Storage Account.
- Set retention per compliance (e.g. 90 days for HIPAA / PCI baselines).
- Save; audit records start within minutes. Validate by running an obvious DDL and confirming the SQLSecurityAuditEvents table receives it.
- Add a Monitor alert on high-risk audit actions (DROP DATABASE, ALTER ROLE).
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1331- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.