Microsoft Security Copilot in Defender for Cloud (Preview)

By Ashwin Venugopal -

 






Introduction

Both Microsoft Security Copilot and Microsoft Copilot for Azure are included into Microsoft Defender for Cloud. These connections allow you to ask security-related questions, get answers, and immediately activate the skills required to use natural language prompts for analysis, summarization, remediation, and suggestion delegation.

Cloud-based AI technologies that offer a natural language copilot experience are Security Copilot and Copilot for Azure. They help security experts fix or assign jobs, fix code misconfigurations, and comprehend the context and impact of recommendations. 

You may improve your security posture and reduce risks in your environments by integrating Defender for Cloud with Security Copilot and Copilot for Azure on the suggestions page. This integration improves the effectiveness and efficiency of your security management by streamlining the process of comprehending and putting recommendations into practice. 

Key Features

Data Processing Workflow

When you use Security Copilot in Defender for Cloud, the following data processing workflow occurs:
  1. A user enters a prompt in the Copilot interface.
  2. Copilot for Azure receives the prompt.
  3. Copilot for Azure evaluates the prompt and the active page, to determine the skills needed to resolve prompt.
  4. If the prompt is security related and the skill is available, Security Copilot executes the skills and sends back a response to Copilot in Azure for presentation.
  5. If a security-related prompt is received but the skill is unavailable, Azure Copilot searches all of its available skills to find the most relevant skills to resolve the prompt. A response is then sent to the user. 

Enable Security Copilot Integration in Defender for Cloud

Security Copilot in Defender for Cloud is independent of any Defender for Cloud plans. Security Copilot is available for all users when you:
  1. Enable Defender for Cloud on your environment.
  2. Have access to Azure Copilot.
  3. Have Security Compute Units assigned for Security Copilot.

However, we advise turning on the Defender for Cloud Security Posture Management (DCSPM) plan on your environments to take advantage of Security Copilot's entire suite of features. Numerous more security elements, including attack path analysis and risk prioritization, are included in the DCSPM plan. Security Copilot can be used to browse and manage these features. You can use Security Copilot in Defender for Cloud without the DCSPM plan, but only to a limited extent. 

Provide Feedback

Your feedback on the Defender for Cloud Security integration Copilot facilitates growth. In Copilot, choose "How's this response?" to offer feedback. Choose from the options provided at the bottom of each completed prompt. 







































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