Closed LLMA-dot closed 1 year ago
Notes for "Atul Raizada: Defender for Identity Part 1 - Offering, Architecture & Deployment"
Links:
For onPrem AD (but not only).
Cloud Product, Sensors installed on onPrem Servers.
Not a new product.
"The key here, my friends, is real-time detection.""
- Detection based of learning network and anomolies
- Behavioral detections
- CVE based detections
- Tool and signature-based detection
Network Traffic Analysis: Inspect network traffic, NTLM, Kerberos, LDAP, RDP, DNS, SMB. Security Events and event tracing: Inspect events and event tracing, and profile AD entities. User behavior analytics: Profile users and entities behavior, identify behavior anomalies. Cloud-based real-time detections: Data enrichment and correlation in Azure for real-time detection.
Sensor could also be deployed on a stand-alone server which is much more work. Sensor does not add a lot of compute on DCs.
Should be integrated with Microsoft 365 Defender (hollistic view of your environment)
Requirements Licensing: Enterprise Mobility + Security E5 (EMS E5/A5), Microsoft 365 E5 (M365 E5/A5/G5) or Microsoft 365 E5/A5/G5 Security.
Prerequisites for Deployment Plan Capacity for Microsoft Defender for Identity
The following detections will be shown in the demo!
GMSA Account = Group-managed Service Account
The video next shows the configuration & setup of the GMSA for MDI.
What are entitiy tags? Sensitive Accounts: You could specifically add your Domain Admins to this list. Honeytoken Accounts: Traps for malicious actors. Any authN associated with these accounts triggers an alert. Exchange Server: Self-explanatory.
Groups or Devices work too for these tags, not just accounts! Cool!
You can configure the Syslog Service to enable notications (for SIEM implementation)
Done!
Link to YouTube Video: Microsoft Defender for Identity Part 1 - Offering, Architecture & Deployment
PowerPoint Slides