Non-Microsoft plugins for Microsoft Security Copilot: Whoisfreaks

By Ashwin Venugopal -

 








Introduction

Whoisfreaks enhances your cybersecurity approach through its domain and IP intelligence solutions. Tailored for analysts, researchers, and brand proprietors, the platform delivers exceptional insights and monitoring functions to safeguard your digital assets. Keep ahead of potential threats, maintain brand integrity, and make informed choices with reliable, real-time data. Our platform effortlessly integrates with current systems, boosting workflow efficiency and productivity. 

Before You Begin

  1. Sign-in to Microsoft Security copilot.
  2. Access Manage Plugins by selecting the Plugin button from the prompt bar.
  3. Choose Settings to configure your Whoisfreaks plugins.
  4. Select Save and begin prompting in Security Copilot.

Troubleshoot Whoisfreaks Plugins

  • Errors Occur- Make sure the plugin is activated if you receive errors like "Couldn't complete your request" or "Unknown error occurred." Sign-out of Security Copilot and then back in again if the problem continues.

  • Prompts aren't invoking the correct capabilities- You may have custom plugins or other plugins with functionality comparable to the capability set you wish to employ if prompts aren't triggering the relevant capabilities or are triggering a different capability set. Conflicts may arise, for instance, if you are using several informational sources, such as Whoisfreaks. 

Provide Feedback

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

Conclusion

Whoisfreaks, Aviatrix, AbuselPDB are some of the many examples we explored. 

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