Jenkins
Collect Jenkins job, node, controller, and plugin evidence through read-only JSON API endpoints.
Code, CI & delivery
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.
- Job inventory
- Agent/node inventory
- Controller metadata
- Plugin/version inventory
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
Jenkins 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 Jenkins evidence
Get a guided demo, or start by scanning any domain for free.