QualysVM-GetAssets-ByOpenPort

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Content Index

When a new sentinel incident is created, this playbook gets triggered and performs the following actions: 1. Gets Port from incident. (Only one port) 2. Search the Qualys platform and get the asset count with open port. 3. Search the Qualys platform and get the asset details as well. (Asset details limited to 50 assets, since incident comment has limitaion of 30000 characters.) 4. Combine both the results. 5. Add the info as comment to the incident.

Attribute Value
Type Playbook
Solution QualysVM
Source View on GitHub

Additional Documentation

📄 Source: QualysVMPlaybooks/QualysVM-GetAssets-ByOpenPort/readme.md

Summary

When a new sentinel incident is created, this playbook gets triggered and performs the following actions:

  1. Gets Port from incident. (Only one port)
  2. Search the Qualys platform and get the asset count with open port.
  3. Search the Qualys platform and get the asset details as well. (Asset details limited to 50 assets, since incident comment has limitaion of 30000 characters.)
  4. Combine both the results.
  5. Add the info as comment to the incident.



Prerequisites

  1. Prior to the deployment of this playbook, Qualys Logic App Custom Connector needs to be deployed under the same subscription.
  2. Refer to Qualys Logic App Custom Connector documentation for deployment instructions.

Deployment instructions

  1. To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
  2. Fill in the required parameters:
    • Playbook Name
    • Custom Connector Name

Deploy to Azure Deploy to Azure

Post-Deployment instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Select the Microsoft Sentinel connection resource
  2. Click Edit API connection blade
  3. Click Authorize/Provide credentianls
  4. Click Save
  5. Repeat these steps for other connections

b. Configurations in Sentinel

  1. In Microsoft sentinel, analytical rules should be configured to trigger an incident that contains Netowrk Port. Since there is no entity for Ports for now, Network Ports need to be passed as key value pair in Custom details section. [Important] In the Custom details section of the analytics rule creation workflow, Assign NetworkPort as key and choose appropriate column as value.

    Check the documentation to know more about custom details in alerts.

    Check the documentation to learn more about mapping entities. 2. Configure the automation rules to trigger the playbook. Check the documentation to learn more about automation rules.

c. Assign Playbook Microsoft Sentinel Responder Role

  1. Select the Playbook (Logic App) resource
  2. Click on Identity Blade
  3. Choose Systen assigned tab
  4. Click on Azure role assignments
  5. Click on Add role assignments
  6. Select Scope - Resource group
  7. Select Subscription - where Playbook has been created
  8. Select Resource group - where Playbook has been created
  9. Select Role - Microsoft Sentinel Responder
  10. Click Save (It takes 3-5 minutes to show the added role.)

References

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Playbooks · Back to QualysVM