Getting Started with Microsoft Sentinel- Connect Your Data

By Ashwin Venugopal -

 






Overview

Data is sent to the Microsoft Sentinel workspace after configuring the provided data connectors, which are generally present in Out-Of-The-Box (OOTB), or built-in Content Hub solutions for Microsoft 365 services, Azure, and third-party specific.

Ingest Log Data with Data Connectors

  • Connect the data sources with Microsoft Sentinel Data Connectors, which are in the Content Hub Solutions provided by Microsoft Sentinel.

  • After installing the Content Hub Solution, the Configuration | Data Connectors menu section will show the installed Data Connectors.

  • Now, select the Open Connector page to view the detailed connector page split in left and right halves.

    • The left half contains all the information regarding the connector, its status, and the last time a log was received when connected. Whereas, the bottom part displays the Data Types with the lists of tables that the connector writes to.

    • The right half has an instructions tab that can vary according to the connector, and generally contains Prerequisites and Configuration. The Configuration tab can connect with the data source, while the Next Step tab offers a quick look through workbooks, query samples, and analytical templates. However, Data Connectors can only be disconnected or deactivated, they cannot be deleted.

Understand Data Connector Providers

Microsoft 365 Defender

It provides alerts, incidents, and raw data from Microsoft 365 Defender products including (but not limited to):
  1. Microsoft Defender for Endpoint
  2. Microsoft Defender for Identity
  3. Microsoft Defender for Office 365
  4. Microsoft Defender for Cloud Apps
Microsoft Azure Services

Its connectors include (but not limited to):
  1. Azure AD
  2. Azure Activity
  3. Azure AD Identity Protection
  4. Azure DDoS Protection
  5. Microsoft Defender for IoT
  6. Azure Information Protection
  7. Azure Firewall
  8. Microsoft Defender for Cloud
  9. Azure Web Application Firewall (WAF) 
  10. Domain name server
  11. Office 365
  12. Windows firewall
  13. Security Events

Vendor Connectors

There is an ever-growing list of vendor-specific data connectors:
  • Custom connectors using the Log Analytics API- Log Analytics Data Connector API can be used to send data to the Microsoft Sentinel Log Analytics workspace.

  • Logstash plugin- Microsoft Sentinel's output plugin for Logstash data collection engine can be used to send any log to the Log Analytics workspace. The logs are written to a custom table defined via the output login. 

Common Event Format and Syslog Connector

The generic Common Event Format (CEF) and Syslog Connector can be used in case of no vendor-provided connector. Syslog, common to Linux, is an event logging protocol where applications send messages that may be either stored on the local machine or Syslog collector. However, Common Event Format (CEF) is an industry-standard format on top of Syslog messages, and is used by many security vendors to allow event interoperability among different platforms. 

CEF has always been the first choice as log data is stored into the predefined fields of the CommonSecurityLog table, whereas, Syslog offers header fields and the raw log messages are stored in SyslogMessage field in the Syslog table. To query a Syslog data, a parser should be written to extract the specific field. 

View Connected Hosts

The Data Connector page shows the installed connectors and to view the connected hosts, following steps should be taken:
  1. Select Settings
  2. Workspace settings transfers to Log Analytics
  3. Now, select Agents in the Log Analytics Settings area
  4. Two tabs will be displayed, one for Windows and another one for Linux.
































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