Get Started with Microsoft Security Copilot

By Ashwin Venugopal -

 







Introduction

The generative AI security product called Security Copilot enables IT and security professionals to process signals, evaluate risk exposure, and react to cyberthreats at the speed and scale of artificial intelligence. However firstly, one has to understand the requirements needed to get started with it.

Minimum Requirements

  • Subscription- In order to purchase security compute units, one must have an Azure subscription.

  • Security compute units- For Microsoft Copilot to operate reliably and consistently, security compute units are the necessary resource units. Security Copilot is billed on an hourly basis and is offered in a provisioned capacity model. Security Compute Units (SCUs) can be provisioned and scaled up or down at any time. Instead of using 60-minute increments, billing is calculated in hourly blocks with a minimum of one hour. Regardless of start or end times, any usage that occurs within the same hour is billed as a full SCU. 

  • Capacity- In Security Copilot, capacity refers to an Azure resource that holds SCUs. Security Copilot has SCUs available. Increasing or decreasing the number of provisioned SCUs through the Azure or Security Copilot portals makes capacity management simple. Security Copilot gives Copilot owners access to a usage monitoring dashboard so they can keep tabs on usage over time and decide how best to provision capacity. 

Onboarding to Security Copilot

It is a two-step process: 

  • Step 1- Provision Capacity: The following options can be selected- 

    • Option 1 (Recommended): Provision capacity through Security Copilot- After opening the Security Copilot, one is guided through the steps in setting up capacity for your organization. Only an Azure subscription owner or contributor can create capacity.

    1. Sign-in to Security Copilot.
    2. Select Get Started. 
    3. Set up security capacity- select the Azure subscription, associate capacity to a resource group, add a name to the capacity, choose the prompt evaluation location, and specify the number of Security Compute Units (SCUs). 
    4. Acknowledge and agree to the terms and conditions, then select Continue.

After this, it will take a few minutes to deploy the Azure resource on the backend.
    • Option 2: Provision capacity in Azure- This one starts in the Azure portal. After that complete the setup in the Security Copilot portal. 

    1. Sign in to Azure portal.
    2. Search for Security Copilot in the list services, then select Security Copilot.
    3. Select Resource groups.
    4. Under Plan, select Microsoft Security Copilot. Then select Create.
    5. Select a subscription and resource group, add a name to the capacity, select the prompt evaluation location and select the number of Security Compute Units (SCUs). 
    6. Acknowledge and read the terms and conditions, then select Review + create.
    7. Verify all the information, then choose Create. A confirmation page is displayed. 
    8. Select Finish setup in the Security Copilot portal.

  • Step 2: Set up default environment- Requires at least a Security Administrator role to accomplish this task. Also, an Azure Owner or a Contributor for the capacity resource can associate capacity to Security Copilot. 
  1. Associate capacity to the Security Copilot environment if the capacity was created in the Azure portal. 
  2. Select Continue after getting information about the stored customer data.
  3. Continue after getting informed about accessing data from Microsoft 365 services. 
  4. If it's required for the Security Copilot to capture and store admin actions, user actions, and system responses, choose Continue. 
  5. Select among the data sharing options and Continue.
  6. Select the roles that can access Security Copilot and Continue. 
  7. After the display of the confirmation page, Finish. 

Offboarding

To offboard from Security Copilot, delete the provisioned capacity and one must at least be a Security Administrator to accomplish this task.

Conclusion

Now we are all set to join the Microsoft Security Copilot and have access to all its latest products. 




































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 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

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