- PERSONA
- TheHive / SOC Engineer
- CATEGORY
- Integration
- ENDPOINTS
- 3 used
- UPDATED
- April 2026
One Cortex analyzer, every source
Per-source analyzers are a maintenance tax
- 8–12 separate API keys and quotas to manage across individual TI vendors.
- One report per analyzer, per observable — analysts manually correlate across multiple tabs in the case view.
- Sequential analyzer runs slow down triage; parallel configs introduce rate-limit headaches.
“8–12 separate API keys and quotas to manage across individual TI vendors.”
The endpoints that solve it
Multi-source enrichment endpoint
Accepts one or many indicators (ip, domain, url, hash). Returns a normalized verdict with per-source breakdown, risk score, and aggregated tags — the shape Cortex expects to render in the case report.
Standard Cortex analyzer package
Ships as a Python script + flavor JSON descriptor with dataTypeList for ip/domain/url/hash. Drops into the Cortex analyzers directory like any other community analyzer.
TheHive-native report summary
Output maps cleanly to Cortex's taxonomies so the case-view summary shows a single `DFIRPlatform:score=<n>` tag instead of a dozen per-source labels.
Cortex analyzer, in one screen
# DFIRPlatform_IOCEnrichment.py — Cortex analyzer entrypoint
from cortexutils.analyzer import Analyzer
import requests
class DFIRPlatformAnalyzer(Analyzer):
def run(self):
api_key = self.get_param("config.api_key", None, "API key missing")
r = requests.post(
"https://api.dfir-lab.ch/v1/enrichment/lookup",
headers={"Authorization": f"Bearer {api_key}"},
json={"indicators": [{"type": self.data_type, "value": self.get_data()}]},
timeout=30,
)
self.report(r.json())
if __name__ == "__main__":
DFIRPlatformAnalyzer().run()- 01Step 01
Drop the analyzer into Cortex
Standard layout: `DFIRPlatform_IOCEnrichment/` containing the Python script and a JSON descriptor with `dataTypeList: [ip, domain, url, hash]`.
- 02Step 02
Configure the API key in Cortex
Cortex UI → Organization → Analyzers. Paste the DFIR Platform API key once; every observable on every case uses it.
Step-by-step walkthrough with configuration, error handling, and deployment notes.
Pricing that tracks your workload
- 01
Small SOC — 5 cases/day × ~6 observables
5 × 6 × 30 × 3 credits = 2,700 credits/monthProfessional ($99, 2,500 credits) with a slight top-up, or Starter if you gate enrichment to higher-severity cases. - 02
Mid-size SOC — 15 cases/day × ~8 observables
15 × 8 × 30 × 3 credits = 10,800 credits/monthEnterprise (custom), or Professional with volume top-ups. - 03
Evaluation — a few cases a day while testing
3 × 5 × 30 × 3 credits = 1,350 credits/monthStarter ($29, 500 credits) covers a couple of weeks; Professional for full-month coverage.
Three ways to evaluate
Frequently asked
- Q / 01
- Yes. The analyzer talks to Cortex, not TheHive directly, so TheHive version is not material — Cortex 3.x is the requirement.
- Q / 02
- No. You can run DFIR Platform alongside VirusTotal_GetReport, AbuseIPDB and friends — Cortex runs each analyzer independently. Most teams phase them out gradually once the consolidated analyzer earns trust.
- Q / 03
- ip, domain, url, and hash. File and email observable types are not enriched by this analyzer — for those, use DFIR Platform's dedicated file and phishing endpoints outside Cortex.
- Q / 04
- One credit charge per observable analyzed — 3 credits per call. If TheHive auto-runs the analyzer on every observable at case creation, budget accordingly (see credit math above).
Other teams solving adjacent problems
Stop triaging by hand.
Create a free account — 100 credits per month, no credit card. Or keep browsing to find the use case that matches your workflow.