Azure Web Application Firewall Integration in Microsoft Copilot for Security (preview)

By Ashwin Venugopal -

 





About

A cloud-based artificial intelligence platform called Microsoft Copilot for Security offers a Copilot experience in natural language. In a variety of situations, such as incident response, threat hunting, and intelligence collection, it can assist security professionals. 

Deep analysis of Azure Web Application Firewall (WAF) events is made possible by Microsoft Copilot for Security's integration with Azure WAF. In just a few minutes, it can assist in examining WAF logs that were triggered by Azure WAF and offer relevant attack vectors through machine-speed natural language responses. It gives insight into the threat landscape of the surroundings. It enables one to find the most offending IP addresses in an environment and obtain a list of the WAF rules that are most frequently triggered. 

Both Azure WAF on Azure Application Gateway and Azure WAF on Azure Front Door support Microsoft Copilot for Security integration. 

Key Features

The preview standalone experience in Azure WAF can help in:
  1. Providing a list of top Azure WAF rules triggered in the customer environment and generating deep context with related attack vectors. 
  2. providing a list of malicious IP addresses in the customer environment and generating related threats.
  3. Summarizing SQL injection(SQLi) attacks. 
  4. Summarizing Cross-site scripting(XSS) attacks.

Enable the Azure WAF Integration in Copilot for Security

Follow the below steps to enable the integration:
  1. Make sure that you have at least Copilot contributor permissions.
  2. Open https://securitycopilot.microsoft.com/.
  3. Open the Copilot for Security menu.
  4. Open Sources in the prompt bar.
  5. On the plugins page, set the Azure Web Application Firewall toggle to On.
  6. Select the settings on the Azure Web Application Firewall plugin to configure the Log Analytics workspace, Log Analytics subscription ID, and the Log Analytics resource group name for Azure Front Door WAF and/or the Azure Application Gateway WAF. 
  7. To start using the skills, use the prompt bar.

Provide Feedback

Your feedback on the Azure WAF integration with Microsoft Copilot for Security helps with development. 

Limitation

The Application Gateway WAF V2 version's Microsoft Copilot for Security WAF Skills aren't working if you switch to Azure Log Analytics-specific tables. In addition to the resource-specific table, enable Azure Diagnostics as the destination table as a temporary solution. 

Conclusion

Here we learned more about Azure Web Application Firewall Integration in Microsoft Copilot for Security, its key features, and limitation.













































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