Azure SQL Database Threat Detection Not Enabled
Nothing flags SQL injection or unusual access patterns, so an attack in progress goes unreported.
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 threat detection 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 → Security → Microsoft Defender for SQL.
- Enable Microsoft Defender for SQL at the server level (cost is per-server, covers all databases).
- Configure alert email recipients (DBAs + on-call security distribution list).
- Review the initial vulnerability assessment report under Security → Vulnerability assessment.
- Tune alert sensitivity; suppress known-benign findings via Defender for Cloud → Security alerts.
- Set up a weekly review cadence for new alerts.
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-1332- 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.