Security Copilot with Microsoft Sentinel

By Ashwin Venugopal -

 







Introduction

Microsoft Security Copilot is a platform that assists in in protecting an organization at scale and machine speed. The extensive security data from Microsoft Sentinel is a great resource for Copilot to use when analyzing incidents and creating hunting queries. 

Microsoft Sentinel incidents and data, when combined with other Security Copilot sources, gives a broader understanding of threats as well as context. 

Security Copilot Integration with Microsoft Sentinel

This integration primarily supports standalone experience accessed via https://securitycopilot.microsoft.com, where interaction is done in a chat-like experience to summarize incidents and get other answers about security data. 

Key Features

Microsoft Sentinel data integrates with Security in following two ways:
  • In Microsoft's unified security operations platform, Copilot in Microsoft Defender XDR benefits from unified incidents integrated with Microsoft Sentinel.

  • In the standalone experience, Microsoft Sentinel offers Microsoft Sentinel (Preview) and Natural language to KQL for Microsoft Sentinel (Preview) to integrate with Security Copilot. 

Enable Security Copilot Integration with Microsoft Sentinel

To maximize Security Copilot integration with Microsoft Sentinel:

  • Configure a default Microsoft Sentinel workspace

    • Navigate to Security Copilot at https://securitycopilot.microsoft.com/.
    • Open Sources in the prompt bar.
    • On the Manage plugins page, set the toggle On.
    • Select the gear icon on the Microsoft Sentinel (preview) plugin.
    • Configure the default workspace name.

  • Integrate Microsoft Sentinel with Copilot in Defender- use the Microsoft Defender portal with Microsoft Sentinel data for an embedded Security Copilot experience. Microsoft Sentinel's unique data sources flowing into Microsoft Defender XDR unified incidents allow Copilot in Defender to maximize its capabilities. 

Provide Feedback

Feedback is vital to guide the current and planned development of the product. The best way to provide feedback is directly in the product. 

Conclusion

All the main information about Security Copilot integration with Microsoft Sentinel is discussed above.











































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

Deployment (Part 2)

By Ashwin Venugopal -
Image
  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 featu...
Read more