Observability webhooks
Push monitor, incident, alert, retention, or log-source coverage evidence.
Observability · Logging
Tier 2 generic template — runs on the Inbound webhook connector
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.
- Inbound normalized evidence from the customer system or automation tool
- Per-integration secret webhook URL
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.
Where this evidence goes
Which frameworks this evidence supports
Observability webhooks 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 Observability webhooks evidence
Get a guided demo, or start by scanning any domain for free.