GitGuardian can now scan for secrets throughout all your ServiceNow tables and records. GitGuardian now integrates natively with ServiceNow to help your team find and eliminate more than 450 types of secrets that might have been leaked into your instance of the popular process automation platform.

As the landscape of Non-Human Identities (NHI) continues to expand, managing and securing these identities has become one of the most pressing challenges for organizations today. With automation and the increasing reliance on machine-to-machine communication, the stakes for securing these entities have never been higher. Did you know that over 80% of cloud breaches involve mismanaged or unauthorized machine identities?

We are happy to announce that our new integration empowers Jira Data Center users to synchronize their GitGuardian incidents with Jira Data Center issues. We have previously integrated with Jira Cloud for issue creation and coordination, but now anyone running their own Jira Data Center installation can reap the same benefits of both automatic and manual creation of Jira issues from your GitGuardian incidents using customized templates. With our auto-resolve feature, you can automatically close GitGuardian incidents when the corresponding Jira issue is closed.

We are excited to announce that Jira Data Center users can now leverage GitGuardian to perform real-time scanning for secrets in issues and comments. We have supported Jira Cloud with real-time scanning for some time, but now teams that run their own private versions of the popular project management tool, helping teams plan, track, and release work. You can install GitGuardian on multiple Jira Data Center sites to monitor your projects.

We are proud to announce that BitBucket Cloud users can now leverage the GitGuardian Secrets Detection platform to find hardcoded secrets throughout their existing codebases and actively monitor any code changes for newly leaked credentials. We have supported Bitbucket Data Center and Sever for years, but now, teams managing code on bitbucket.org can reap those same benefits. Integration is very simple and straightforward.

It is now easier than ever to receive GitGuardian incident alerts directly in any Microsoft Teams channel you want. Introducing the new Microsoft Teams GitGuardian app. If your organization relies on MS Teams to coordinate incident response, it makes sense to get alerts for new incidents as soon as they occur in your same communications platform. After setup, whenever a new incident is detected by GitGuardian, you will get the alert directly in MS Teams.

Introducing The GitGuardian Secret Analyzer GitGuardian has always helped you find your leaked secrets, but now GitGuardian can also quickly reveal the permissions of your secrets. One of the first questions any security team needs to ask itself when a secret is leaked is "What exactly could an attacker do with it?" Does it grant read-only access or does it have permissions to write or delete data? At the same time, understanding the correct scope needed for replacing a credential can take a long time, as all too often, the permissions originally granted are poorly documented, if at all.

If you are using ServiceNow for centralized incident management and SecOps, We have some good news. You can now configure ServiceNow issues to synchronize with GitGuardian incidents. Once configured, you will be able to send incident data from GitGuardian and map it to ServiceNow issues triggering your preferred workflows. And, if properly configured, you can update GitGuardian incidents directly from ServiceNow Issues.

Introducing The GitGuardian Secret Analyzer GitGuardian has always helped you find your leaked secrets, but now GitGuardian can also quickly reveal the permissions of your secrets. One of the first questions any security team needs to ask itself when a secret is leaked is "What exactly could an attacker do with it?" Does it grant read-only access or does it have permissions to write or delete data? At the same time, understanding the correct scope needed for replacing a credential can take a long time, as all too often, the permissions originally granted are poorly documented, if at all.

We are proud to announce our new Auto-ignore false positive playbook. We've added this new automated Playbook to the GitGuardian Secret Detection platform to eliminate false positives from your incident queue and help you focus on actionable alerts. In the summer of 2024, we released FP remover, our internal machine learning model, that can significantly reduce false positives by understanding code context and semantics. In our testing it eliminates up to 80% of false positives.