Integration hub
Connect the tools you already run to your compliance record
Connectors for cloud, identity, endpoint and monitoring tools bring evidence in beside the controls it supports. When a control fails, you can open a Jira ticket where your engineers already work.
In short
Certifyi connects to the tools that hold compliance evidence and the tools your engineers use to fix things. Evidence from a connected system lands beside the controls it supports, and because a control can be mapped to several frameworks, that evidence serves each of them. You can create a Jira ticket from a failing control. Tell us your stack and we will confirm which connectors fit before you plan around one.
Cloud and infrastructure
Connect AWS, Azure, Cloudflare and Kubernetes to bring configuration and security evidence into the platform, beside the assets and controls it supports.
Identity and access
Connectors for Auth0 and Duo bring identity and sign-in evidence into the record, so access controls can be reviewed against the data your identity tools hold.
DevOps and monitoring
Connect Bitbucket for repository evidence, such as whether code review is enforced, and Datadog and Grafana for evidence that your systems are monitored.
Endpoint and security tools
Connect CrowdStrike, Microsoft Defender and Jamf to bring endpoint protection and device evidence in beside the controls that require it.
Ticketing: Jira
Create Jira tickets from failing controls, so the fix is tracked where your engineers already work. If your engineers work in ServiceNow, keep the work there and attach the resulting evidence to the control it supports.
Tools without a connector
Where a tool has no connector, upload its evidence by hand and keep it on the control it supports. The tamper-evident activity log records who added it and when. If your plans depend on programmatic access, tell us what you need and we will say what is available before you rely on it.
Before you connect a tool
Three questions worth answering first.
-
Which controls need it?
Start from the controls that lack evidence, then choose the connector that supplies it.
-
What access does it need?
Check the permissions each connector asks for and grant the narrowest set that works.
-
Who looks after it?
Name someone who will notice when a connection stops working.
Related modules
Connected tools supply evidence to these modules, and you can create Jira tickets from failing controls in them.
How Certifyi helps
How Certifyi connects your tools
Evidence comes in, remediation goes out to your ticketing tool, and the record stays in one place.
-
Cloud and infrastructure
AWS, Azure, Cloudflare and Kubernetes evidence.
-
Identity and endpoint
Auth0, Duo, CrowdStrike, Microsoft Defender and Jamf evidence.
-
Jira tickets
Create Jira tickets from failing controls.
Questions
Integration questions
Which integrations does Certifyi support?
Connectors include AWS, Azure, Cloudflare, Kubernetes, Auth0, Duo, Bitbucket, Datadog, Grafana, CrowdStrike, Microsoft Defender, Jamf and Jira. Coverage changes, so tell us your stack and we will confirm the status of each tool before you rely on it. Evidence from a tool without a connector can be uploaded by hand.
What does the Jira integration do?
When a control fails, you can create a Jira ticket from it, so the fix is tracked in the tool your engineers already use.
Can we build our own integrations?
Ask us first. We only describe integrations we have confirmed, so tell us what you want to connect and we will say what is available. Evidence from any tool can be uploaded by hand and kept on the control it supports.
Bring evidence in from the tools you already run
Book a walkthrough and send us the tools your team runs beforehand. On the call we will go through which connectors fit, and where you would still upload evidence by hand.
- Each customer workspace has its own database
- Every change written to a tamper-evident activity log
- Auditors get scoped, read-only access
- AI suggestions wait for a person to accept them