what are secrets?
Secrets are any sensitive or private information residing in your code that when exposed, will compromise a company's security.
Secrets consist of:
- Passwords
- API keys
- Encryption keys
- Tokens
- Database credentials
SECRETS DETECTION AT THE SOURCE
is your source code
Clean of Secrets?
Secrets in your source code, when leaked, expose you to a security vulnerability due to illicit access to your private data. Sonar can find secrets in source code in your IDE using SonarLint and also detect them in your CI/CD pipeline using SonarQube and SonarCloud.
Secrets are any sensitive or private information residing in your code that when exposed, will compromise a company's security.
Secrets consist of:
Leaked secrets are a severe security exposure when they end up in the hands of cybercriminals, granting unauthorized access to secure systems and data.
Secrets in your code repository:
Sonar uses a powerful combination of Regular Expressions and Semantic Analysis to detect secrets in source code. We scan as you code in your IDE with SonarLint in a true shift left approach, unlike other secrets detection tools, which only detect secrets in Git repo. Because Sonar can detect secrets in code while you write, secrets never enter your repository, eliminating leakage. Additionally, SonarQube and SonarCloud catch secrets that unintentionally enter your repo or your CI/CD pipeline for a complete solution.
Sonar leverages the power of both RegEx and Semantic Analysis
Publicly known secrets cover most of your secrets, but a good portion are company-specific secrets with a structure or format only your company knows. Create custom rules with SonarQube Enterprise Edition and Data Center Edition to detect your company’s private secret patterns and deliver the best secrets detection coverage, up to 100% of all your secrets.
Sonar goes above and beyond by educating developers on which code contains secrets. Each secrets detection rule includes content explaining why the found code segment is a secret and the impact details of why the secret poses a security risk. Now developers know how not to include secrets in their code. How cool is that?