Agent
The 8 checks in the “Agent” category of a SQL Server audit: what each one verifies, its severity and the versions covered.
- Checks in this category
- 8
- Weight in the score
- 10
- Breakdown by severity
- 1 critical · 4 high · 3 medium
Checks in this category
AGENT001Agent Running
CriticalSQL Server Agent must be running
Versions : 2012-2025
AGENT002Failed Jobs
HighRecurring failed jobs indicate a problem
Versions : 2012-2025
AGENT004Operators Configured
HighAt least one operator should be configured for alerts
Versions : 2012-2025
AGENT005Severity 19-25 Alerts
HighAlerts for critical errors should be configured
Versions : 2012-2025
AGENT008Corruption Alerts
HighAlerts for errors 823, 824, 825 should exist
Versions : 2012-2025
AGENT003Jobs Without Notification
MediumJobs should notify on failure
Versions : 2012-2025
AGENT006Failsafe Operator
MediumA failsafe operator should be configured
Versions : 2012-2025
AGENT007Jobs owned by named accounts
MediumCounts the SQL Server Agent jobs whose owner is not the built-in administrator account "sa". A login that owns a job can no longer be dropped (error 15170), and the T-SQL steps of a job run with the rights of its owner as long as that owner is not a sysadmin.
Versions : 2012-2025
Other categories
- Security 103
- Backups 11
- Reliability 64
- Encryption 14
- Configuration 33
- Maintenance 33
- Performance 29
- Database Settings 13
- Files 10
- Wait Statistics 9
- Advanced I/O 5
- Advanced Memory 8
- Blocking & Deadlocks 8
- Query Store 8
- Linked Servers 5
- Capacity 9
- Updates 7
- Hardware 10
- Top Queries 7
- Stored Procedures 4
- Connections 6
- Extended Events 4
- Database Mail 3
- Database Level 7