• Prerequisites: You need Google Workspace administrator privileges.

1. Access Google Admin Console

  • Log in to your Google Admin console at admin.google.com.
  • From the sidebar menu, navigate to Apps > Web and mobile apps.
  • Click Add app and select Add custom SAML app.

2. Define App Details

  • Enter an App name for the Cremit integration (e.g., Cremit Security).
  • (Optional) Add an App icon and description.
  • Click Continue.

3. Provide Google Identity Provider (IdP) Details

  • On this screen, Google provides its IdP details. You will need to copy these values into your Cremit SAML configuration settings (refer to Cremit's specific SAML setup guide for where to input these). The key details are:
    • SSO URL
    • Entity ID
    • Certificate (Download the certificate file).
  • Keep this browser tab open or securely store these values. Click Continue.

4. Configure Service Provider (SP) Details

  • Now, you need to enter the details provided by Cremit (the Service Provider). Refer to Cremit's SAML configuration section to get these values:
    • ACS URL (Assertion Consumer Service URL): Enter the URL provided by Cremit.
    • Entity ID: Enter the unique identifier for Cremit provided by Cremit.
  • Ensure Name ID format is set to EMAIL.
  • Ensure Name ID is set to Basic Information > Primary email.
  • Click Continue.

5. Configure Attribute Mapping

  • Cremit may require specific attributes to be sent in the SAML assertion. The primary email is usually required.
  • Click Add mapping.
  • Map the Google Directory attribute Basic Information > Primary email to the application attribute email (or as specified by Cremit's requirements, though email is standard).
  • Add any other required attribute mappings as specified by Cremit (e.g., first name, last name).
  • Click Finish.

6. Enable User Access

  • After the custom SAML app is created, it will appear in your list of Web and mobile apps. By default, it is OFF for everyone.
  • Click on the newly created Cremit SAML app.
  • Find the User access section.
  • Click on it and choose the Organizational Units (OUs) or Groups that should have access to Cremit via SSO.
  • Set the service status to ON for these selected groups/OUs.
  • Click Save.

Your Google Workspace SAML configuration for Cremit is now complete. Users in the enabled OUs/Groups should be able to log in to Cremit using their Google credentials.

Need help with this integration? Please Contact Us, and we'll be happy to assist.

essential

Essential

Startups & Small Teams – Manage risk early by securing non-human identities from day one.

Best for scaling businesses
+800 Types NHI Verification
Git & SaaS Integration
No False Positive Alerts

enterprise

Enterprise

Custom Solutions – Secure non-human identities at scale, across complex environments.

Custom solutions for large organizations
SIEM Integration
Dedicated Region & On-Premise
24/7 Support

FAQ

We're Here to Help

Aenean lobortis, massa a imperdiet iaculis, lorem odio lacinia elit, non hendrerit ligula justo tempor lorem.

How frequently does Cremit update its detection engine?

We continuously update our detection engine to include new non-human identity types and improve accuracy. Updates are automatically applied for cloud users. Subscribe to our newsletter to stay up to date with updates or check our changelog.

What support options are available?

We provide detailed documentation for the integration processes, and dedicated customer support to assist with integrations, troubleshooting, and remediation strategies on paid versions. For more information or to get started, visit our website or contact our support team.

How does Cremit compare to other non-human identities detection tools?

Cremit differentiates itself with a highly accurate detection engine, broad coverage, seamless integration into developer workflows, and the most cost effective tool available.

What is the difference between Cremit’s free and paid versions?

The free version offers core non-human identities detection, while the paid versions include advanced features such as real-time alerts, more integrations, and others. For more information please visit our pricing page.

How can I test Cremit’s detection capabilities?

You can test Cremit using sample repositories with intentionally embedded credentials.

Does Cremit offer on-premise deployments?

Cremit is primarily a cloud-based solution, but Enterprise plan customers can request on-premise deployments to meet specific security requirements.

Is there an API available for automation?

Yes, Cremit offers a robust API for integrating NHI leak detection into your automation pipelines, ensuring security across your development process.

Does Cremit scan public repositories?

Yes, Cremit proactively scans public repositories. If a leak of confidential information is detected, we notify the repository owner and provide guidance on remediation. For more information please visit our Vigilant Ally page.

Can I integrate Cremit with my existing development workflow?

Absolutely. Cremit integrates with CI/CD workflows. Our API and CLI options allow seamless incorporation into development workflows.

How secure is the scanning process?

Cremit prioritizes security and confidentiality. We scan repositories in a secure environment without permanently storing your code. Our protocols ensure privacy throughout the process.

What happens when a NHI is detected?

When a leak is flagged, Cremit provides a detailed alert that includes the file location, type of secret, and risk assessment. This helps teams quickly remediate issues and secure their environment.

How does Cremit detect non-human identities?

Our scanning engine employs advanced pattern matching to identify a wide range of sensitive data, including API keys, private keys, and database credentials.

What types of credentials does Cremit detect?

Cremit is designed to identify over 800+ types of non-human identities and other credential types.

How does Cremit handle false positives?

Our detection engine continuously improves with machine learning to ensure no false positives.

What is Cremit’s Non-Human Identity (NHI) detection solution?

Cremit provides an automated, SaaS-based detection solution that scans your code repositories for non-human identities (NHI) such as API keys, tokens, passwords, certificates, and others to help prevent data breaches and security incidents.

Why is secret detection important for my code security?

Vulnerable NHIs can expose your systems to unauthorized access, data leaks, and compliance violations. By using Cremit, you can continuously monitor and detect leaks early in the development cycle, reducing the risk of security breaches and ensuring your codebase remains secure.

Trusted by hundered of companies globally