Should domain controllers, SQL Server and Hyper-V hosts run antivirus, and what should be excluded?
Servers should use supported antimalware controls, but exclusions must follow role and vendor guidance, with minimum scope, current documentation and performance validation.

Establish a factual baseline with “supportability of server roles” and “vendor-recommended exclusions”, then move to “database and virtualization I/O paths”. Use instance state, logs, storage and application connectivity as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking supportability of server roles, vendor-recommended exclusions and database and virtualization I/O paths independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · supportability of server roles | Checking supportability of server roles helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of supportability of server roles. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
| 02 · vendor-recommended exclusions | Checking vendor-recommended exclusions helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of vendor-recommended exclusions. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
| 03 · database and virtualization I/O paths | Checking database and virtualization I/O paths helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of database and virtualization I/O paths. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
| 04 · real-time scanning performance | Checking real-time scanning performance helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of real-time scanning performance. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
| 05 · antivirus definition update path | Checking antivirus definition update path helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of antivirus definition update path. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
| 06 · minimal exclusions with periodic review | Checking minimal exclusions with periodic review helps establish whether the server role, workload and security controls remain compatible; compare it with a known-good baseline and the incident timeline. | Record the actual state of minimal exclusions with periodic review. Check vendor guidance, version and exclusions while collecting baseline performance and service logs. |
Investigation and change sequence
- Capture a baseline for supportability of server roles and vendor-recommended exclusions and compare it with a known-good system.
- Correlate evidence from database and virtualization I/O paths and real-time scanning performance to distinguish the direct fault from dependent symptoms.
- Only if evidence points to antivirus definition update path, plan a controlled change with backups, a change window and rollback triggers.
- Finally check minimal exclusions with periodic review and the real business workflow. Retest real workload functions, logs and performance; review any security exceptions.
Validation and rollback evidence
- Retest real workload functions, logs and performance; review any security exceptions.
- Recheck antivirus definition update path and minimal exclusions with periodic review against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming supportability of server roles is sufficient while overlooking vendor-recommended exclusions and dependent checks.
- Changing several settings before preserving the original evidence for database and virtualization I/O paths.
- Do not disable necessary protections permanently to resolve a short-term scan issue.
Common questions and acceptance criteria
What should be checked first?
Begin with supportability of server roles and vendor-recommended exclusions. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Retest real workload functions, logs and performance; review any security exceptions.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
