Configure Your Azure Sentinel Environment

By Ashwin Venugopal -

 



Introduction to Azure Sentinel

What is the Security Incident & Event Management (SIEM)?

A tool that can be used by an organization to collect, analyze, and perform security operations on its computer systems is widely known as an SIEM and in its simplest form, it can enable you to:
  • Collect and query logs.
  • Do some form of correlation or anomaly detection.
  • Create alerts and incidents based on your findings.

An SIEM system might offer functionality such as:

  • Log management- The ability to collect, store, and query the log data from resources within your environment.
  • Alerting- A proactive look inside the log data for potential security incidents and anomalies.
  • Visualization- Graphs and dashboards that provides visual insights into your log data.
  • Incident management- The ability to create, update, assign, and investigate incidents that have been identified.
  • Querying data- A rich query language, similar to that for log management, that you can use to query and understand your data. 

What is Azure Sentinel?

Azure Sentinel is cloud-native SIEM system that a security operations team can use to:
  • Get security insights across the enterprise by collecting data from virtually any source.
  • Detect and investigate threats quickly by using built-in machine learning and Microsoft threat intelligence.
  • Automate threat responses by using playbooks and by integrating Azure Logic Apps.

In contrast to the traditional SIEM solutions, to run Azure Sentinel, it is not required to install any servers either on-premises or in the cloud but can be deployed in Azure itself. You can easily start with Sentinel in just a few minutes in the Azure portal that can help you to enable end-to-end security operations including collection, detection, investigation, and response. 

How Azure Sentinel works?

Data Connectors

Data Connectors enables you to ingest your data into Azure Sentinel along with some additional services, such as Azure activity logs, just by selecting a button. There are data connectors that covers all the scenarios and sources, including but not limited to:

  • syslog
  • Common Event Format (CEF)
  • Trusted Automated eXchange of Indicator Information (TAXII) (for threat intelligence)
  • Azure
  • AWS services

Log Retention

After it's been ingested into Azure Sentinel, your data is stored by using Log Analytics whose benefits  includes the ability to use the Kusto Query Language (KQL) to query your data which is a rich query language that gives you the power to dive into and gain insights from our data.

Workbooks

You can easily use the workbooks to visualize your data within Azure Sentinel, edit them to meet your own needs, or create your own workbooks from scratch. This feature is similar to  Azure Monitor workbooks due to it's Sentinel's implementation of Monitor workbooks. 

Analytics Alerts

Built-in analytics alerts can be enabled within your Sentinel workspace. There are various types of alerts, some of which you can edit to your own needs while the others are built on machine-learning models that are proprietary to Microsoft. You can also create custom, scheduled alerts from scratch.

Threat Hunting

There are some built-in hunting queries available for SOC analysts to hunt for any suspicious activity while also creating their own queries. Sentinel also integrates with Azure Notebooks to provide example notebooks for advanced hunters who wants to use the full power of a programming language to hunt through their data. 

Incidents & Investigations

An incident is created when an alert that you've enabled is triggered and in Azure Sentinel, you can do standard incident management tasks like changing status or assigning incidents to individuals for investigation. Azure Sentinel also has investigation functionality allowing you to visually investigate incidents by mapping entities across log data along a timeline. 

Automation Playbooks

Azure Sentinel integrates with Azure Logic Apps, enabling you to create automated workflows, or playbooks, in response to events which could be used for incident management, enrichment, investigation, or remediation. These capabilities are also referred to as Security Orchestration, Automation, and Response (SOAR).

When to use Azure Sentinel?

Azure Sentinel is a solution for performing security operations on your cloud and on-premises environments. You can use Azure Sentinel if you want to:

  • Collect event data from various sources.
  • Perform security operations on that data to identify suspicious activity.     

Security operations could include:

  • Visualization of log data
  • Anomaly detection
  • Threat hunting
  • Security incident investigation
  • Automated response to alerts and incidents

It is proven that Azure Sentinel could be a good fit as it offers data connectors for syslog, Amazon Web Service (AWS), and other sources, and the ability to scale effortlessly without provisioning servers.You can also ingest Security Center alerts as a data connector for Azure Sentinel.




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