Overview
Matproof integrates with the tools your team already uses. Connecting an integration means evidence is collected automatically — no screenshots, no manual uploads, no spreadsheets. Each integration runs on a 24-hour sync cycle. Evidence collected is mapped directly to the relevant controls in your active frameworks.Available Integrations
GitHub
Branch protection, code review records, MFA enforcement, Dependabot alerts, repository access lists.
Google Workspace
User access, MFA enrollment, admin role assignments, inactive accounts, external sharing policy.
AWS
IAM, CloudTrail, S3 encryption, security groups, KMS key rotation, GuardDuty status.
Microsoft Entra ID
Identity, MFA registration, Conditional Access policies, privileged role assignments, risky sign-ins.
Jira
Change management tickets, incident tracking, corrective action linking.
More coming soon
Slack, Okta, GitLab, Notion, and more. Vote for the next integration at support@matproof.com.
How Integrations Work
- Connect — authorize Matproof with read-only access to your tool via OAuth or API key
- Sync — Matproof pulls configuration and activity data on a 24-hour schedule
- Map — collected data is automatically matched to the relevant controls in your active frameworks
- Surface — passing checks move controls toward compliant; failing checks surface as gaps
What Integrations Replace
Without integrations, demonstrating access control compliance means manually exporting user lists, screenshotting MFA settings, and uploading them every quarter. With integrations, this happens automatically.| Manual task replaced | Integration |
|---|---|
| Export user list and MFA status | Google Workspace / Entra ID |
| Screenshot branch protection settings | GitHub |
| Export IAM policy and CloudTrail status | AWS |
| Document change approval records | Jira |
| Capture Dependabot vulnerability status | GitHub |
Custom Integrations
For tools not on the list above, use the Matproof API to push evidence programmatically from any system — CI/CD pipelines, custom scripts, internal dashboards, or third-party tools. Common API use cases:- Upload penetration test results directly from your security scanner
- Push deployment records from your CI/CD pipeline as change management evidence
- Sync vendor data from your procurement system