OpenCTI
Collect indicator, report, malware, and attack pattern evidence from OpenCTI via read-only GraphQL API queries.
Security operations
Evidence coverage
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Threat intelligence reports status and metadata
- Indicators of compromise (IOC) inventory and patterns
- Malware profiles and signature definitions
- Attack patterns and threat actor techniques mapping
Least privilege
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- API base URL
- Auth header value(secret credential)
- Auth header name
- Evidence endpoints (JSON)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
OpenCTI evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in OpenCTI evidence
Get a guided demo, or start by scanning any domain for free.