QualysVM-LaunchVMScan-GenerateReport
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
When a new sentinel incident is created, this playbook gets triggered and performs the following actions: 1. Get IP Addresses from incident. 2. Scan IP Addresses with Qualys Scanner. 3. Generate the Scan Report. 4. Download the report and store it to a blob storage. 5. Add the link of report as a comment to the incident.
| Attribute | Value |
|---|---|
| Type | Playbook |
| Solution | QualysVM |
| Source | View on GitHub |
Logic App Connectors
This playbook uses 3 Logic App connectors / built-in actions:
| Connector / Action | Type | Connections | Actions |
|---|---|---|---|
azureblob |
Managed | 1 | 2 |
azuresentinel |
Managed | 1 | 2 |
QualysCustomConnector |
Custom | 1 | 13 |
Action parameters (URLs, paths, function IDs)
azureblob (Managed)
| Action | Method | Endpoint | Other |
|---|---|---|---|
| Create_SAS_URI_by_path_(V2) | post | /v2/datasets/@{encodeURIComponent('AccountNameFromSettings')}/CreateSharedLinkByPath |
— |
| Create_blob_(V2) | post | /v2/datasets/@{encodeURIComponent(encodeURIComponent('AccountNameFromSettings'))}/files |
— |
azuresentinel (Managed)
| Action | Method | Endpoint | Other |
|---|---|---|---|
| Add_comment_to_incident_(V3) | post | /Incidents/Comment |
— |
| Entities_-_Get_IPs | post | /entities/ip |
— |
QualysCustomConnector (Custom)
| Action | Method | Endpoint | Other |
|---|---|---|---|
| Check_Scan_Status | post | /api/2.0/fo/scan/ |
— |
| Launch_Scan | post | /api/2.0/fo/scan/ |
— |
| Check_Scan_Status_Again | post | /api/2.0/fo/scan/ |
— |
| Create_Option_Profile_for_Scan | post | /api/2.0/fo/subscription/option_profile/vm/ |
— |
| List_Scanner_Appliances | get | /api/2.0/fo/appliance/ |
— |
| Create_Scan_Report_Template | post | /api/2.0/fo/report/template/scan/ |
— |
| Delete_Option_Profile | post | /api/2.0/fo/subscription/option_profile/vm/ |
— |
| Delete_Scan_Report_Template | post | /api/2.0/fo/report/template/scan/ |
— |
| Download_Scan_Report | post | /api/2.0/fo/report/ |
— |
| Get_Asset_Details_By_IP | post | /api/2.0/fo/asset/host/ |
— |
| Get_Report_Status | post | /api/2.0/fo/report/ |
— |
| Launch_VM_Scan_Report | post | /api/2.0/fo/report/ |
— |
| Get_Report_Status_Again | post | /api/2.0/fo/report/ |
— |
Additional Documentation
📄 Source: QualysVMPlaybooks/QualysVM-LaunchVMScan-GenerateReport/readme.md
Summary
When a new sentinel incident is created, this playbook gets triggered and performs the following actions:
- Get IP Addresses from incident.
- Scan IP Addresses with Qualys Scanner.
- Generate the Scan Report.
- Download the report and store it to a blob storage.
- Add the link of report as a comment to the incident.
Prerequisites
- Prior to the deployment of this playbook, Qualys Logic App Custom Connector needs to be deployed under the same subscription.
- Refer to Qualys Logic App Custom Connector documentation for deployment instructions.
- New or Existing Storage Account deployed under the same subscription.
Deployment instructions
- To deploy the Playbook, click the Deploy to Azure button. This will launch the ARM Template deployment wizard.
- Fill in the required parameters:
- Playbook Name
- Custom Connector Name
- Storage Account Name
Post-Deployment instructions
a. Authorize connections
Once deployment is complete, authorize each connection if required.
- Select the Microsoft Sentinel connection resource
- Click Edit API connection blade
- Click Authorize/Provide credentianls
- Click Save
- Repeat these steps for other connections
- For Qualys connection, provide Qualys Username and Password
b. Configurations in Sentinel
In Microsoft sentinel, analytical rules should be configured to trigger an incident that contains IP Addresses. In the Entity maping section of the analytics rule creation workflow, IP Address should be mapped to Address identitfier of the IP entity type.
Check the documentation to learn more about mapping entities.
Configure the automation rules to trigger the playbook. Check the documentation to learn more about automation rules.
c. Create Container report-blob in Storage Account
- Choose Containers blade in Data storage section
- Click on +Container
- Give name report-blob
- Let the Public access level be deafault Private (no anonymous access)
- Click Create
d. Assign Playbook Microsoft Sentinel Responder Role
- Select the Playbook (Logic App) resource
- Click on Identity Blade
- Choose Systen assigned tab
- Click on Azure role assignments
- Click on Add role assignments
- Select Scope - Resource group
- Select Subscription - where Playbook has been created
- Select Resource group - where Playbook has been created
- Select Role - Microsoft Sentinel Responder
- Click Save (It takes 3-5 minutes to show the added role.)
References
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊