Skip to content
Notifications
Clear all

Moved from Symantec Endpoint Protection to Microsoft Defender for Endpoint - real experience

2 Posts
2 Users
0 Reactions
25 Views
(@alexf)
Reputable Member
Joined: 3 months ago
Posts: 233
Topic starter   [#11957]

We ran SEP for years. The management overhead was killing us. Moved 500 endpoints to Defender for Endpoint over the last quarter. Here's the raw take.

**The Good:**
* Integration with Intune and Azure AD is seamless. Deployment was fast.
* The security center portal is actually good. Real-time actions (isolate device, run AV scan) work without lag.
* Attack surface reduction rules are powerful. We've locked down a lot of scripting abuse.
* Cost-effective at our scale. No per-endpoint license juggling.

**The Bad (and the fixes):**
* Initial false positives were high. Had to spend two weeks tuning detection rules for our legacy LOB apps.
* Reporting isn't as granular as I'd like for digging into user behavior flows. You get the security incident, not the conversion funnel view.
* The EDR component needs a dedicated security ops person to get full value. We're not there yet.

Bottom line: If you're already in the Microsoft ecosystem, it's a no-brainer for protection and management. Be prepared to adjust policies out of the gate.

af


Optimize or die.


   
Quote
(@jenniferg)
Estimable Member
Joined: 3 months ago
Posts: 76
 

Thanks for sharing that real world timeline. The two week tuning period for legacy apps is something I've heard from others, and it's a crucial detail for teams planning a switch. That initial overhead often gets overlooked in sales pitches.

> The EDR component needs a dedicated security ops person

This is the hidden cost for many. You get incredible depth, but it's not a set-and-forget tool. For organizations without a dedicated SecOps role, do you think the built-in automated investigation and remediation features are enough to bridge the gap, or does it just create a false sense of security?


Let's keep it real.


   
ReplyQuote