Every system Cremit Platform touches
Scan sources, permission analyzers, alarm channels, SSO, and SCIM directory sync. One catalog for every integration Cremit Platform connects to.
Sources Cremit Platform scans for exposed secrets
Connect code repositories, document stores, and communication platforms. Cremit Platform scans content across them for credentials, API keys, and tokens.
GitHub
Setup: 5 min
Scan repositories, commit history, issues, and GHCR container images for exposed secrets across your GitHub organization.
GitLab
Setup: 7 min
Scan self-hosted or SaaS GitLab projects, commit history, and issues for credential exposure.
AWS S3
Setup: 10 min
Scan S3 buckets for credentials, API keys, and tokens stored in object storage.
Bitbucket
Setup: 5 min
Scan the commit history of every repository in a Bitbucket Cloud workspace for exposed credentials.
Google Drive
Setup: 5 min
Scan documents, spreadsheets, and shared drives for pasted credentials, API keys, and tokens.
Jira
Setup: 7 min
Scan Jira issue descriptions, comments, and attachments for pasted credentials.
Confluence
Setup: 7 min
Scan Confluence pages, templates, and attachments for credentials stored in documentation.
Notion
Setup: 5 min
Scan Notion workspace pages and databases for pasted API keys, tokens, and credentials.
Slack (Messages)
Setup: 5 min
Scan Slack channels and DMs for pasted credentials, API keys, and tokens.
Analyzers for cloud permissions on discovered credentials
When Cremit Platform finds an AWS access key or a GCP API key, the analyzer maps what it can actually reach — IAM policies on AWS, API restrictions on GCP — so you can assess over-privilege and blast radius.
AWS (CloudFormation)
Setup: 10 min
Deploy a read-only analyzer via CloudFormation to map IAM permissions attached to discovered AWS credentials.
GCP (Service Account)
Setup: 10 min
Connect a read-only service account to map IAM bindings and roles on discovered GCP credentials.
Where alerts land
Route detections and admin confirmation requests to the channel your team already watches. Slack, generic webhook, Telegram, or email.
Slack
Setup: 3 min
Send detection alerts to a Slack channel via OAuth-installed Cremit Platform.
Webhook
Setup: 5 min
POST JSON payloads to any HTTPS endpoint: your SOAR, Discord, or a relay into PagerDuty and Teams.
Telegram
Setup: 3 min
Deliver alerts to a Telegram channel or group via bot token.
SAML 2.0 and OIDC authentication for Cremit Platform
Authenticate Cremit Platform users through any SAML 2.0 or OIDC IdP, including Okta, Microsoft Entra ID, Google Workspace and Ping.
Directory sync over SCIM 2.0 and Google Workspace
Sync users and groups from your IdP over SCIM 2.0 or the Google Workspace API. When someone is suspended or removed upstream, Cremit Platform flags the credentials they own as Ghost Keys and routes them to a person to rotate or revoke.
Okta SCIM
Setup: 15 min
Auto-provision and de-provision Cremit Platform users from Okta groups. Handles onboarding and offboarding.
Google Workspace SCIM
Setup: 15 min
Sync Google Workspace users and groups to Cremit Platform. Automatic access removal when accounts are suspended.
Need an integration we do not have?
Tell us about the source, channel, or identity provider you need. We prioritize roadmap items based on real requests.
Request an integration