Getting Started with Microsoft Sentinel- Use Overview Dashboard and Workbooks To Get Visibility Across Enterprise

By Ashwin Venugopal -

 








Get Visualization

The overview dashboard gives an idea of the security posture of an organization. Incidents are a group of related alerts that are used to create an actionable incident to investigate and resolve. In Microsoft Sentinel a desired workspace can be selected to monitor. 

View Incident Data


  1. There are various types of incident data under Incidents.
  2. The top left contains the number of new, active, and closed incidents of the last 24 hours.
  3. The right left contains the incidents according to severity, and closed incidents by closing classification.
  4. There is a graph at the bottom left that breaks up the incident status by creation time in 4 hour intervals.
  5. The bottom right consists of the mean time that acknowledges an incident and mean time to close with a link to the SOC efficiency workbook. 

View Automation Data

  1. There are various types of automation data under Automation.
  2. At the top, there is a summary of the automation rules activity, like- Incidents closed by automation, the time the automation saved, and related playbooks health. 
  3. Under the summary, there is a graph that summarizes the numbers of actions done by automation, by type of action. 
  4. At the bottom, the active number of automation rules are available with automation blade. 

View Status of Data Records, Data Collectors, and Threat Intelligence 




  1. There are various types of data on data records, data collectors, and threat intelligence under Data.
  2. The graph on the left showcase the number of records collected in the last 24 hours as compared to the previous 24 hours along with the anomalies detected in that time period.
  3. The top right depicts the summary of the data connector status, divided by unhealthy and active connectors. Unhealthy connectors indicates the number of connectors with errors, while Active connectors contains Microsoft Sentinel's data streaming, as measured by a query included in the connector. 
  4. The bottom right contains threat intelligence records in Microsoft Sentinel, by indicator of compromise. 

View Analytics Data



There are various analytics rules under Analytics in Microsoft Sentinel by enabled, disabled, or auto-disabled status.

Use Workbooks Templates

They offers integrated data from the connector data sources and allows to learn more about the events generated in those services. There is a wide variety of workbook templates like Azure AD, Azure activity events, etc. They rely on Azure Monitor Workbooks to provide enhanced customizability and flexibility in designing a workbook. 
  1. Go to Settings and choose Workbooks. My Workbooks contains all the saved workbooks and Templates contains all the installed workbook templates. You can also go to Content hub to look for more workbook templates.
  2. Search for the required workbook and read the whole list and description.
  3. However, it is recommended to install Azure AD solution for Microsoft Sentinel and use following workbooks:
  • Azure AD- Use either or both of the following-
    • Azure AD sign-ins, which analyzes the sign-ins to look for any anomalies. They provide failed sign-ins by applications, devices, and locations to catch anything unusual with more focus on the multiple failed sign-ins. 
    • Azure AD Audit Logs, analyzes admin activities like changes in number of users, group creation, and modifications. 
  • An appropriate solution can be installed to add a workbook for your firewall. Workbooks analyzes the firewall traffic and offer details about the correlation between the firewall data and threat events while also throwing light on the suspicious activities. They can also provide information about traffic trends, to know more and filter results. 
The workbooks cam be customized by editing the main query. 





















Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more