Add vulnerability context without building an intel pipeline
Most vulnerability scanners output CVSS scores and CVE IDs. They can't tell you what's being actively exploited right now. Adding that context normally requires a full threat intelligence team. attestd is the API shortcut.
the request
bash
curl "https://api.attestd.io/v1/check?product=log4j&version=2.14.1" \
-H "Authorization: Bearer attestd_demo_key"integration
enrich.py
from attestd import check
def enrich_finding(product: str, version: str, cve_id: str) -> dict:
"""Enrich a scanner finding with real-world exploitation data."""
risk = check(product, version)
return {
"cve": cve_id,
"product": product,
"version": version,
"cvss_score": get_cvss(cve_id), # your existing data
"actively_exploited": risk.actively_exploited,
"remote_exploitable": risk.remote_exploitable,
"patch_available": risk.patch_available,
"fixed_version": risk.fixed_version,
"attestd_risk_state": risk.risk_state, # enriched signal
"priority": "P0" if risk.risk_state == "critical" else "P2",
}operational outcome
▸
Findings are prioritized by what's actually being exploited.
Instead of presenting a list of hundreds of CVSS scores, your tool can surface a short list of things that matter right now — vulnerabilities with confirmed active exploitation. No threat intel team required.