Tip 1: Enable Cloud Protection, Sample Submission, and cloud block timeout period for getting all MDE features enabled. Always use one of the options for sending samples to Microsoft. Never use "Do not send" which is disabling the complete feature.
Tip 2: Enable Network Protection in block mode for block custom indicators and block C2 infrastructure attacks. Did you know Windows Servers require additional configuration for getting NP enabled?
Tip 3: - Configure the correct signature updating settings. Use a quick update interval (1 hour) and avoid WSUS/ MECM. Don't use slow frequencies for “skipping” bad updates. Microsoft is really quick in deploying fixes; how quicker the signature frequency how better it is.
Tip 4: - Disable Local Admin Merge for preventing local admins to manage exclusions locally. Always manage exclusion from centralized systems (Intune/ GPO/ MECM), and yes it is not completely blocking the local admin exclusions permissions.
Tip 5: - Only a quick scan is fine in combination with all cloud protection and AIR features. Use only the full scan in case of incidents or the first scan on the machine after onboarding.
Tip 6: - Enable always Tamper Protection. There are no excuses anymore; we need to do some troubleshooting. The new troubleshooting mode is available which disables Tamper Protection for a short time. More information: jeffreyappel.nl/microsoft-defe…
Tip 7: - Enable Windows Firewall for all zones and enable additional auditing events for more in-depth network details in MDE.
Audit events:
Audit Filtering Platform Packet Drop
Audit Filtering Platform Connection
More in part 4B of the series.
Tip 8: - New to Defender for Endpoint and Defender AV? Really recommended watching the Virtual Ninja Episodes by @HeikeRitter. Episode 2 starts tomorrow with some brand-new content.
Tip 3 - Network Protection is important for Defender for Endpoint. With the use of Network Protection malicious sites and added indicators can be blocked. There are some important points which are commonly forgotten/ misconfigured for Windows.
Network Protection in itself is independent of MDE. The relationship between NP and MDE is the Custom Indicators features,C2-detection capability, WCF reporting, and some additional events. For Network Protection it is required to have Defender AV in active mode.
2/6
Configuration is possible with the use of Intune, GPO, PowerShell and other supported methods. Accepted configurations; Audit/ Block/ Disabled. Only block mode blocks the connection. For NP AV must be enabled with CP/RTP.
New Tenant Creation setting in AzureAD User Settings?
Yes, allows default users to create Azure AD tenants. No, allows only users with global administrator or tenant creator roles to create Azure AD tenants.
The default seems configured on Yes in all tenants. (1/2)
7 AzureAD identity-related protection tips for protecting against new identity attacks like OAuth theft, MFA prompt spamming, AiTM, and MFA Phishing. #azureAD#MicrosoftSecurity
Links included for more information to earlier posted blogs.
A thread🛡️
Tip 1: MFA fatigue / MFA spamming is growing. To protect against MFA spamming enable:
- Azure MFA number matching (preview)
- Show additional context in notifications (preview)