- Traditional antivirus scanners primarily work signature-based and detect only known malware. Modern attacks use fileless techniques that bypass signature scanners.
- Endpoint Detection and Response (EDR) monitors the behavior of processes, network connections and registry changes and detects suspicious patterns — even without a signature.
- Microsoft Defender for Business provides EDR, Threat & Vulnerability Management and automated incident response in a single license affordable for SMEs.
- Setup is done through Microsoft Intune and requires no dedicated server infrastructure. Onboarding, policies and monitoring run entirely cloud-based.
- In the ISMS, Defender for Business can be documented as a TOM for malware protection (A.8.7) and vulnerability management (A.8.8).
Why the Traditional Antivirus Scanner Is No Longer Enough
The traditional antivirus scanner has operated on the same principle for over 30 years: it compares files on the endpoint against a database of known malware signatures. If a match is found, the file is blocked or quarantined. This principle works well against known threats but has a fundamental disadvantage: it only detects what is already known.
Modern attackers have long adapted. The techniques used in today's cyberattacks are designed to evade signature-based detection:
Fileless attacks (fileless malware): The malicious code is executed directly in memory without writing a file to disk. A solid incident response plan helps prepare for these hard-to-detect attacks as well. Since no file scan can take place, the attack remains invisible to traditional antivirus scanners. Typical example: a PowerShell script launched via a phishing email that opens a reverse shell connection directly in memory.
Living off the Land (LotL): Attackers use legitimate system tools such as PowerShell, WMI, certutil or mshta to achieve their objectives. Since these tools are part of the operating system, they do not trigger signature alerts. An antivirus scanner that blocks PowerShell would cripple normal IT operations.
Polymorphic malware: Each instance of the malware slightly modifies its code so that the signature is never identical. The functionality remains the same, but the fingerprint changes with each propagation.
Obfuscation and packing: The malicious code is encrypted, compressed or hidden in legitimate code, making it undetectable during static analysis. Only at runtime is the actual malicious code unpacked and executed.
Against all these techniques, a signature-based antivirus scanner is at best partially effective — at worst, completely blind.
What Is EDR and Why Does It Make the Difference?
Endpoint Detection and Response (EDR) takes a fundamentally different approach than traditional antivirus scanners. Instead of checking files against a signature database, EDR monitors behavior on the endpoint in real time:
- Which processes are started, and by which parent process?
- Which network connections does a process establish?
- Which files are created, modified or deleted?
- Which registry keys are changed?
- Which PowerShell commands are executed?
- Which user accounts access which resources?
This telemetry data is compared against behavioral models, machine learning algorithms and threat intelligence. The system detects suspicious patterns even when no known signature exists. For example, when a Word document launches a PowerShell process that establishes an encrypted connection to an unknown server, that is suspicious behavior — regardless of whether the code used appears in a signature database.
EDR additionally offers capabilities that a traditional antivirus scanner does not have:
Forensic investigation: When a security incident is detected, you can trace the entire attack path: which process initiated the attack? Which files were modified? Which data were exfiltrated? Which other devices are affected?
Automated response: The system can automatically respond to detected threats: terminate processes, quarantine files, disconnect network connections, lock user accounts. This happens in seconds — not the minutes or hours that manual incident response takes.
Threat hunting: Security analysts can proactively search for indicators of compromise before an alert is triggered. With advanced queries, patterns can be analyzed across thousands of endpoints.
Microsoft Defender for Business in Detail
Microsoft Defender for Business is Microsoft's EDR solution for small and medium-sized businesses. It is included in Microsoft 365 Business Premium and available as a standalone license for companies with up to 300 employees. The feature set is oriented toward the enterprise product Defender for Endpoint Plan 2 but is simplified in some areas.
Next-Generation Protection
The foundation is antivirus protection that goes far beyond traditional signatures:
- Cloud-based detection: Suspicious files are checked in milliseconds against Microsoft's cloud intelligence, which aggregates billions of signals from hundreds of millions of endpoints worldwide.
- Behavior-based detection: Process behavior is analyzed in real time and compared against known attack patterns.
- Exploit protection: Protection against common exploit techniques such as buffer overflow, return-oriented programming and DLL injection.
- Network protection: Blocks connections to known command-and-control servers and phishing domains.
- Tamper protection: Prevents malware or attackers from disabling Defender or changing its configuration.
Endpoint Detection and Response
The EDR component monitors the behavior of all endpoints and correlates telemetry data into security incidents:
- Incident-based view: Individual alerts are automatically aggregated into incidents that map the entire attack path. Instead of reviewing 50 individual alerts, you see one incident with a clear attack story.
- Attack story visualization: Graphical representation of the attack path from initial access through lateral movement to objective achievement.
- Device timeline: Chronological display of all relevant events on an endpoint, filtered by the investigation timeframe.
- Response actions: Manual response options such as device isolation (device is disconnected from the network but remains reachable via Defender Cloud), file quarantine, process kill, live response session.
Threat & Vulnerability Management (TVM)
TVM is an integrated vulnerability management system that continuously assesses the security posture of all endpoints:
- Software inventory: Automatic capture of all installed software and their versions.
- Vulnerability detection: Comparison of installed software against known vulnerabilities (CVEs) without requiring a separate vulnerability scanner.
- Risk assessment: Prioritization of vulnerabilities based on actual exploitability in the corporate network, not just by CVSS score.
- Security recommendations: Concrete action recommendations (software updates, configuration changes, disabling insecure services).
- Exposure score: Overall assessment of the attack surface on a scale from 0 to 100.
TVM is particularly valuable because it integrates vulnerability management into the endpoint protection platform. You do not need a separate vulnerability scanner, a separate database or a separate report. Vulnerabilities become visible in the same portal as security incidents, and the relationship between a vulnerability and its exploitation is automatically established.
Automated Investigation and Response (AIR)
Automated Investigation and Response investigates alerts automatically and executes countermeasures without requiring analyst intervention:
- When an alert is triggered, an automated investigation starts that collects related artifacts (files, processes, registry entries, network connections).
- The collected evidence is analyzed and an action recommendation is generated (e.g., quarantine file, terminate process, lock user).
- Depending on configuration, the actions are executed automatically (full automation) or submitted for approval (semi-automation).
For mid-market companies without a dedicated SOC, full automation is recommended: the automated response is in most cases faster and more precise than a manual response that takes hours because no one happens to be watching the portal.
Defender for Business vs. Third-Party Solutions
The question of whether Defender for Business or a third-party solution (CrowdStrike, SentinelOne, Sophos, Bitdefender, ESET) is the better choice cannot be answered universally. But there are clear arguments for both sides.
Advantages of Defender for Business
Integration: Defender for Business is deeply integrated into the Microsoft ecosystem. Telemetry data flows into the Microsoft 365 security stack (Conditional Access, Identity Protection, Defender for Cloud Apps) and enables correlated detection across endpoints, email, identities and cloud apps. This cross-domain correlation is a significant advantage over isolated endpoint solutions.
No additional costs: Defender for Business is already included in Microsoft 365 Business Premium. Since most companies need Business Premium for Conditional Access and Intune anyway, Defender for Business generates no additional costs.
Simplified management: Onboarding, configuration and monitoring run through the Microsoft 365 Defender portal and Intune. No additional management server, no additional console, no additional infrastructure.
TVM included: The integrated vulnerability management is a separate, paid product with most third-party vendors.
Advantages of Third-Party Solutions
Independence: If Microsoft itself is compromised (as in the Midnight Blizzard attack in 2023), an independent security solution is not automatically affected. Diversification reduces concentration risk.
Specialization: Dedicated EDR vendors like CrowdStrike or SentinelOne focus exclusively on endpoint security and invest all their resources in this area. This can be reflected in detection rates and response speed.
Cross-platform: If you need to protect macOS, Linux, iOS and Android in addition to Windows, some third-party vendors offer a more consistent experience across all platforms.
Managed Detection and Response (MDR): Many third-party vendors offer MDR services where an external SOC monitors alerts around the clock and responds to incidents. Microsoft offers a similar service with Defender Experts, but offerings from specialized vendors are often more mature.
Pragmatic Recommendation for SMEs
For most mid-market companies that already have Microsoft 365 Business Premium or E3/E5 licensed, Defender for Business is the pragmatic choice. The integration into the Microsoft 365 stack, the included TVM functionality and the elimination of additional infrastructure and license costs outweigh the theoretical advantages of a third-party solution. If you currently use a traditional third-party antivirus scanner, switching to Defender for Business is a clear security improvement at lower total cost.
The situation is different if you have specific requirements: regulatory mandates requiring an independent vendor, a heterogeneous environment with many non-Windows systems, or the requirement for an external MDR with a 24/7 SOC. In these cases, a comparison with dedicated EDR vendors is worthwhile.
Setup: Step by Step
Setting up Defender for Business is organized into four phases:
Phase 1: Preparation (1-2 Days)
- Check licensing: Ensure all users have a Microsoft 365 Business Premium license (or Defender for Business standalone).
- Document existing antivirus: Which endpoints are protected? Which exclusions are configured? Which policies exist?
- Check Intune enrollment: Defender for Business is managed through Intune. Ensure all devices are enrolled in Intune (Windows 10/11, macOS, iOS, Android).
- Communication: Inform employees about the upcoming transition. In most cases, the switch is invisible to end users, but proactive communication does not hurt.
Phase 2: Onboarding (1-3 Days)
- Open the Microsoft 365 Defender portal (security.microsoft.com) and complete the setup wizard.
- Choose onboarding method: Via Intune (recommended for managed devices), via Group Policy (for domain-joined devices without Intune) or via a local script (for individual devices).
- Onboard pilot group: Start with 5-10 devices from the IT department to validate the process.
- Set existing antivirus to passive mode or uninstall (depending on coexistence configuration). Defender for Business can run in passive mode alongside a third-party scanner, but EDR functionality is limited in this case.
Phase 3: Configuration (2-5 Days)
- Next-generation protection policies: Enable real-time protection, cloud-based detection, tamper protection and PUA protection (potentially unwanted applications).
- Attack Surface Reduction (ASR) rules: Enable rules that block common attack techniques (e.g., "Block Office applications from creating child processes," "Block credential stealing from LSASS"). Initially in audit mode, then gradually switch to block mode.
- Firewall and network protection: Configure web content filtering and network protection.
- Define exclusions: Add industry-specific software that triggers false positives to the exclusion list. Keep the exclusion list as short as possible and document the justification for each exclusion.
- Configure automated response: Full automation recommended; alternatively, semi-automation for the initial phase.
Phase 4: Rollout and Monitoring (1-4 Weeks)
- Gradual rollout: Expand from the pilot group to additional departments, then to all devices.
- Monitoring the first weeks: Check the Defender portal daily, evaluate alerts, identify false positives and adjust exclusions as needed.
- Evaluate TVM: Use the vulnerability reports to prioritize critical software updates.
- Uninstall existing antivirus: Once Defender for Business is active and validated on all devices, remove the old scanner.
Defender for Business in the ISMS
Defender for Business addresses multiple ISO 27001 controls and can be documented as a TOM in various areas of the ISMS:
A.8.7 (Protection Against Malware):
- Next-generation protection as primary malware defense
- Cloud-based detection and behavioral analysis
- Automatic updates via Microsoft Cloud
- Exclusions documented and justified
A.8.8 (Management of Technical Vulnerabilities):
- Threat & Vulnerability Management as continuous vulnerability management
- Software inventory and CVE matching automated
- Risk assessment based on actual exploitability
- Regular evaluation and prioritization of recommendations
A.5.24 (Information Security Incident Management: Planning and Preparation):
- Automated Investigation and Response (AIR)
- Incident-based view for rapid analysis
- Response actions for containment and eradication
- Forensic data for post-incident analysis
A.8.15 (Logging) and A.8.16 (Monitoring Activities):
- Continuous telemetry collection on all endpoints
- Correlation via the Microsoft 365 Defender portal
- Alert policies for critical detections
The ISMS documentation should cover not only the technical configuration but also the operational process. ISMS Lite maps the relevant controls from 11 frameworks and provides practical implementation recommendations for each control. This allows you to document TOMs and logging measures directly within the appropriate controls, and the AI-assisted policy generation helps create the associated policies. The organizational framework is equally important: who reviews the alerts? How quickly is the response to critical incidents? How often is TVM evaluated? Who approves exclusions? These organizational aspects are at least as important to the auditor as the technical setup.
Operations and Monitoring
After setup, Defender for Business needs a structured operational process. Without regular monitoring, even the best EDR solution is worthless because alerts go unread and vulnerabilities remain unpatched.
Daily monitoring (5-10 minutes):
- Review new incidents in the Defender portal
- Evaluate critical and high alerts immediately
- Validate automated responses (did the automation react correctly?)
Weekly review (30 minutes):
- Review all incidents of the week
- Identify false positives and adjust exclusions as needed
- Check TVM dashboard: new critical vulnerabilities?
- Onboarding status: are all devices active and reporting telemetry?
Monthly reporting (1 hour):
- Incident statistics: count, severity, response time
- TVM statistics: exposure score, open vulnerabilities, patch compliance
- Secure Score trend (endpoint category)
- Prepare results for the ISMS dashboard
Quarterly review:
- Check ASR rules and policies for currency
- Review exclusion list (are all exclusions still needed?)
- Evaluate new Defender features (Microsoft regularly expands the feature set)
For companies without dedicated IT security personnel, it makes sense to simplify daily monitoring through email notifications. Defender for Business can automatically send emails to a defined distribution group for critical incidents. This way, you do not need to check the portal every day — you are proactively informed when something happens.
Frequently Asked Questions About the Transition
Can Defender for Business and a third-party scanner run in parallel? Yes, Defender for Business can run in passive mode alongside another scanner. EDR telemetry is collected, but real-time protection is disabled. For full protection, Defender for Business must run in active mode and the third-party scanner must be uninstalled.
What happens to existing antivirus exclusions? The exclusions must be manually transferred to Defender for Business. Use the transition as an opportunity to critically review each exclusion: is it still needed? Is there a better solution?
Do I need a SOC for EDR? No, not necessarily. Defender for Business is designed so that small IT teams can operate the solution. Automated Investigation and Response (AIR) handles much of the work that SOC analysts perform in enterprise environments. But you need at least one person who regularly reviews alerts and responds to critical incidents.
How long does the transition take? For a company with 50-200 endpoints, a timeframe of 2-4 weeks is realistic — from preparation to full rollout. The pure technical setup is faster, but the evaluation phase (false positives, exclusions, ASR rules) takes time.
Does Defender for Business also protect servers? Defender for Business primarily protects client devices (Windows 10/11, macOS, iOS, Android). For servers (Windows Server, Linux Server), you need Defender for Servers, which is licensed through Microsoft Defender for Cloud. For small companies with few servers, the standalone Defender for Servers license may be sufficient.
Further Reading
- Securing Microsoft 365: The 15 Most Important Security Settings
- Building Vulnerability Management: Processes, Tools and Prioritization
- Patch Management for SMEs: Process, Prioritization and Automation
- Intune for Beginners: Device Management Without Enterprise Complexity
- Creating an Incident Response Plan: Structure, Roles and Escalation Paths
