Censys Entity Enrichment - Certificate

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

↑ Back to Content Index

This playbook is triggered automatically when a FileHash entity is detected in a Microsoft Sentinel incident, based on an automation rule. Upon triggering, it extracts the FileHash (certificate fingerprint) from the entity and queries the Censys API (v3) to retrieve detailed certificate information including location, autonomous system, WHOIS data, and associated services. The playbook retrieves the Censys API token securely from Azure Key Vault, performs the API call with retry logic and compre

Attribute Value
Type Playbook
Solution Censys
Source View on GitHub

Logic App Connectors

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

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

azureloganalyticsdatacollector (Managed)

Action Method Endpoint Other
Ingest_Censys_Cert_Data post /api/logs —

azuresentinel (Managed)

Action Method Endpoint Other
Get_incident post /Incidents —

keyvault (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_Cert_Data GET @{variables('base_url')}/@{variables('api_version')}/global/asset/certificate/@{variables('EntityData')} —

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: CensysEntityEnrichmentCertificate/readme.md

Summary

This playbook is triggered automatically when a FileHash entity is detected in a Microsoft Sentinel incident, based on an automation rule. Upon triggering, it extracts the FileHash (certificate fingerprint) from the entity and queries the Censys API (v3) to retrieve detailed certificate information including location, autonomous system, WHOIS data, and associated services. The playbook retrieves the Censys API token securely from Azure Key Vault, performs the API call with retry logic and comprehensive error handling for HTTP status codes (200, 401, 403, 404, 422). Upon successful data retrieval, the certificate data is ingested into Azure Log Analytics (CensysCert_CL table) for historical analysis and reporting. The playbook then retrieves the associated incident and invokes the CensysIncidentEnrichment sub-playbook to add the enrichment data as a comment to the incident. If no incident is associated, the playbook terminates successfully after data ingestion.

Prerequisites

  1. Deploy the CensysIncidentEnrichment playbook before deploying this playbook.
  2. Create an Azure Key Vault and store your Censys API token as a secret named 'Censys-Access-Token'.
  3. Obtain your Censys Organization ID from the Censys platform account settings.
  4. Configure an automation rule in Microsoft Sentinel to trigger this playbook when FileHash entities are detected.

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: CensysEntityEnrichmentCertificate).
    • OrganizationID: Your Censys Organization ID from the Censys platform account settings.
    • IncidentEnrichmentPlaybookName: Name of the deployed CensysAddIncidentComment playbook.
    • 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 keyvault connection resource.
  2. Go to General → Edit API connection.
  3. Click Authorize.
  4. Sign in.
  5. Click Save.
  6. Repeat steps for Microsoft Sentinel and Log Analytics Data Collector connections.

b. Add Access policy in Key Vault

Grant the playbook's managed identity 'Key Vault Secrets User' role on the Azure Key Vault.

  1. Go to Logic App → your Logic App → Identity → System assigned Managed identity and copy Object (principal) ID.
  2. Go to Key Vaults → your Key Vault → 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. Create automation rule in Microsoft Sentinel

Create an automation rule in Microsoft Sentinel to trigger this playbook for FileHash entities.

  1. Go to Microsoft Sentinel → your workspace → Automation.
  2. Click Create → Automation rule.
  3. Configure the rule to trigger when FileHash entities are detected.
  4. Add action to run this playbook.
  5. Click Apply.

d. Ensure CensysIncidentEnrichment playbook is deployed

Ensure the CensysIncidentEnrichment (or CensysAddIncidentComment) playbook is deployed and accessible.

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

↑ Back to Playbooks · Back to Censys