Censys Incident Enrichment

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

↑ Back to Content Index

This playbook will be triggered when any automation rule is attached or manually invoked. This will fetch associated IPs, Host(Domains) and SHAs from incident and make associated API calls to retrieve Censys data and enrich incident with additional information as Incident comment.

Attribute Value
Type Playbook
Solution Censys
Source View on GitHub

Tables Used

This content item queries data from the following tables:

Table Transformations Ingestion API Lake-Only
CensysCertificate_CL 🔶 ? ✓ ?
CensysHost_CL 🔶 ? ✓ ?
CensysWebProperty_CL 🔶 ? ✓ ?

Logic App Connectors

This playbook uses 6 Logic App connectors / built-in actions:

Connector / Action Type Connections Actions
azureloganalyticsdatacollector Managed 1 3
azuresentinel Managed 1 0
keyvault Managed 1 0
keyvault-1 Managed 0 1
http Built-in 0 3
workflow Built-in 0 1
Action parameters (URLs, paths, function IDs)

azureloganalyticsdatacollector (Managed)

Action Method Endpoint Other
Ingest_Censys_Host_Data post /api/logs —
Ingest_Censys_Certificate_Data post /api/logs —
Ingest_Censys_Web_Property_Data post /api/logs —

keyvault-1 (Managed)

Action Method Endpoint Other
Get_Censys_API_Token get /secrets/@{encodeURIComponent('Censys-Access-Token')}/value —

http (Built-in)

Action Method Endpoint Other
HTTP_Call_to_Fetch_Host_Data POST @{variables('base_url')}/@{variables('api_version')}/global/asset/host —
HTTP_Call_to_Fetch_Certificates_Data POST @{variables('base_url')}/@{variables('api_version')}/global/asset/certificate —
HTTP_Call_to_Fetch_WebProperty_Data POST @{variables('base_url')}/@{variables('api_version')}/global/asset/webproperty —

workflow (Built-in)

Action Method Endpoint Other
CensysIncidentEnrichment — — workflowId=[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/',resourceGroup().name,'/providers/Microsoft.Logic/workflows/',trim(parameters('IncidentEnrichmentPlaybookName')))]
triggerName=When_an_HTTP_request_is_received

Additional Documentation

📄 Source: CensysIncidentEnrichment/readme.md

Summary

This playbook will be triggered when any automation rule is attached or manually invoked. This will fetch associated IPs, Host(Domains) and SHAs from incident and make associated API calls to retrieve Censys data and enrich incident with additional information as Incident comment.

Prerequisites

  1. Deploy the CensysAddIncidentComment playbook before deploying this playbook.
  2. Obtain a Censys API token and store it in Azure Key Vault as a secret named 'Censys-Access-Token'.
  3. Obtain the Censys Organization ID from your Censys platform account.
  4. Create or identify an Azure Key Vault and note its name and Tenant ID.
  5. Ensure you have a Log Analytics Workspace configured for Microsoft Sentinel.

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:
    • PlaybookName: Enter the playbook name here (default: CensysIncidentEnrichment).
    • OrganizationID: Your Censys Organization ID from the Censys platform account settings.
    • IncidentEnrichmentPlaybookName: Name of the deployed CensysAddIncidentComment playbook.
    • WorkspaceName: Name of the Log Analytics Workspace where Microsoft Sentinel is deployed.
    • KeyVaultName: Name of the Azure Key Vault where the Censys API token is stored.
    • TenantId: Azure AD Tenant ID where the Key Vault is located.

Deploy to Azure Deploy to Azure Gov

Post-Deployment Instructions

a. Authorize connections

Once deployment is complete, authorize each connection.

  1. Go to your logic app → API connections → Select Microsoft Sentinel connection resource.
  2. Go to General → edit API connection.
  3. Click Authorize.
  4. Sign in.
  5. Click Save.
  6. Repeat steps for Key Vault and Log Analytics Data Collector connections.

b. Add Access policy in Keyvault

Add access policy for the playbook's managed identity to read secrets from Key Vault.

  1. Go to logic app → your logic app → identity → System assigned Managed identity and copy Object (principal) ID.
  2. Go to keyvaults → your keyvault → Access policies → create.
  3. Select Get and List permissions for Secrets. Click next.
  4. In the principal section, search by copied object ID. Click next.
  5. Click review + create.

c. Assign Microsoft Sentinel Responder role

Assign Microsoft Sentinel Responder role to the playbook's managed identity.

  1. Go to Log Analytics workspace → Access control (IAM) → Add role assignment.
  2. Select Microsoft Sentinel Responder role.
  3. Select Managed identity and choose the playbook's identity.
  4. Click Save.

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

↑ Back to Playbooks · Back to Censys