Deployment (Part 2)

By Ashwin Venugopal -

 



To read part 1, please click here
To read part 3, please click here




Microsoft Sentinel Content Hub

Content in Microsoft Sentinel includes any of the following types:
  • Data connectors offer log ingestion from different sources into Microsoft Sentinel.

  • Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios.

  • Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users. 

  • Analytics rules give alerts that point to relevant SOC actions via incidents. 

  • Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel.

  • Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks.

  • Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue. 

  • Playbooks and Azure Logic Apps Custom Connectors provide features for automated investigation, remediation, and response scenarios in Microsoft Sentinel. 

Microsoft Sentinel offers these content types as solution and standalone items. One can either customize out-of-the-box (OOTB) content for their own requirements, or create their own solution with content to share others in the community. 

Discover and Manage Microsoft Sentinel Content

The Microsoft Sentinel Content hub offers in-product discoverability, single-step deployment, and enablement of end-to-end product, domain, and/or vertical OOTB solutions and content in Microsoft Sentinel.
  • In the Content hub, filter by categories and other parameters, or the powerful text search can be used, to find the content that works best for the organization's needs. The Content hub also indicates the support model applied to each piece of content, as some content is maintained by partners or the community.

  • Out-of-the-box content can be customized according to the requirements, or custom content can be created, including analytic rules, hunting queries, notebooks, workbooks, and more. The custom content can be managed directly in the Microsoft Sentinel workspace, via the Microsoft Sentinel API, or in own source control repository, via the Microsoft Sentinel Repositories page. 

Why Content Hub Solutions?

Microsoft Sentinel solutions are packaged integrations that deliver end-to-end product value for one or more domain or vertical scenarios in the content hub. 
  • Packaged content are collections of one or more components of Microsoft Sentinel content, such as data connectors, workbooks, analytics rules, playbooks, hunting queries, watchlists, parsers, and more. 

  • Integrations include services or tools built using Microsoft Sentinel or Azure Log Analytics APIs that support integrations between Azure and existing customer applications, or migrate data, queries, and more, from those applications into Microsoft Sentinel. 

Content hub can be used to centrally discover and deploy solutions and OOTB content in a scenario-driven manner. 

Conclusion

This part discusses about Microsoft Sentinel Content Hub, its components, and its importance. 





To read part 1, please click here
To read part 3, please click here




















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