Security Copilot in Microsoft Surface Management Portal (Public Preview)

By Ashwin Venugopal -

 





Introduction

Microsoft Security Copilot is an AI-powered, cloud-based platform that offers a natural language user experience to assist with providing information and troubleshooting problems. The Surface Management portal works as a centralized hub for overseeing and managing Surface devices in bulk. The integration of the Surface Management Portal with Microsoft Copilot for Security enhances the efficiency of Surface device administrators, enabling quicker resolution of hardware issues on a larger scale. 

The Copilot for Surface Management Portal gives a clear view of environment's warranty coverage and end-of-service timelines. Furthermore, it provides valuable insights into different areas of device management, such as compliance policies, malware defenses, and other potential threats to minimize risks. 

Key Features

The Copilot for Surface Management Portal integrates the capabilities of Security Copilot into the Microsoft Surface Management Portal admin center, allowing for swift responses to issues and escalations regarding Surface devices. By incorporating AI into the Surface Management Portal, teams can quickly assess the warranty status of their devices fleet and identify necessary remediation actions. An administrator can evaluate the latest Surface for Business devices alongside the surface devices. Additionally, insights can be gained on how to safeguard an organization's devices against malware and other threats, helping to mitigate risks. 

Enable the Security Copilot Integration in Surface Management Portal

Enable integration of Security Copilot:
  1. Sign-in to the Security Copilot portal.
  2. In the prompt bar, select Sources at the right corner.
  3. In Manage Sources, activate the Surface Management Portal plugin.
  4. Close the plugin pane.

Provide Feedback

Your feedback is essential for steering both the ongoing and upcoming development of the product. The most effective way to share your thoughts is by utilizing the feedback buttons located at the bottom of each finished prompt, directly in the product. 










































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