Non-Microsoft plugins for Microsoft Security Copilot: AbuselPDB

By Ashwin Venugopal -

 







Introduction

Microsoft Security Copilot is compatible with various plugins, both from Microsoft and third parties. This blog outlines a number of examples of third-party plugins that can be utilized with Security Copilot. Each plugin serves a particular purpose. While some require authentication for integration with Security Copilot, not all do. 

Find & Use Other Plugins

  1. Sign in to Microsoft Security Copilot.
  2. Access Manage Plugins by selecting the Sources button from the prompt bar.
  3. Scroll down to Non-Microsoft, and choose the plugin you want to use. One of the examples is described below-

AbuselPDB

Marathon Studios Inc. is the project manager for AbuselPDB. By offering a central location for webmasters, system administrators, and other interested parties to report and identify IP addresses linked to harmful activity online, they hope to contribute to the safety of the Web. The AbuselPDB plugin is compatible with Microsoft Security Copilot. 

Know Before You Begin

Integration with Security Copilot works with an API key. Take following steps before using the plugin:
  • Get your AbuselPDB API key with the help of steps given below-
    • Go to the AbuselPDB website.
    • Select on the Sign-Up button, located at the top right corner of the page.
    • Fill in the required information, such as your email address, username, and password.
    • Complete any other steps for verification, if necessary.
    • Once registered, sign-in to your AbuselPDB account. 

  • Access the API key-
    • After logging-in, go to the AbuselPDB Homepage page.
    • Navigate to the API tab and select Create key.
    • After clicking on Create key, a model appears. Then, input any name for your key.
    • The newly generated API key should populate on the same API tab.  

  • Sign-in to Microsoft Security Copilot.
  • Access Manage Plugins by selecting the Sources button from the prompt bar.
  • Next to AbuselPDB, select Set up.
  • In the AbuselPDB plugin settings pane, in the Value field, paste your API Key, and then Save. 

Provide Feedback

Your feedback facilitates growth. Offer feedback and help in the improvement of the plugins.

















































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