8 Security operations and response: Microsoft Sentinel

 

This chapter covers

  • Security information and event management
  • Microsoft Sentinel
  • Data collection
  • Analytics rules
  • Incidents
  • User entity behavior analytics
  • Security orchestration, automation, and response
  • Automation rules

As you learned in chapter 7, enabling threat detection for commonly used resource types in Azure (like your VMs, containers, storage accounts, and others) notifies you about suspicious activities and potential signs of compromise in your Azure environment. Have you ever found yourself wondering how to detect threats across your entire digital estate, not just in Azure? If you have, you’re not alone. Many organizations, in addition to IaaS and PaaS resources, also use SaaS applications (like Microsoft 365 or SAP). Furthermore, to further complicate things, large enterprises typically have many resources on-premises too (and even in other public cloud providers like AWS or GCP). The question then becomes how do you detect threats across your entire digital estate (spanning IaaS, PaaS, SaaS, and on-premises)? Historically, organizations have relied on a system called Security Information and Event Management (SIEM), that provided them with the end-to-end visibility of their entire digital estate in a single dashboard.

8.1 Security information and event management

8.2 Microsoft Sentinel

8.2.1 Enabling Microsoft Sentinel

8.3 Data collection

8.3.1 What data should go in a SIEM?

8.3.2 Data connectors

8.3.3 Data connectors in action

8.3.4 Content hub

8.4 Analytics rules

8.4.1 Microsoft security rules

8.4.2 Microsoft security rules in action

8.4.3 Scheduled rules

8.4.4 Scheduled rules in action

8.5 Incidents

8.6 User and entity behavior analytics

8.6.1 When to use user and entity behavior analytics?

8.6.2 User and entity behavior analytics in action

8.8 Automation rules