☑️ Prevent exposed BitBucket secrets in objects
Kubernetes objects may need to use secret data in their configs such as passwords/tokens/etc. Providing such sensitive data in plain-text is risky and highly unrecommended, as it can be stolen and used maliciously.
Different tools have different secrets, each with its own convention and format.
The gitleaks project aggregates such tools and stays up-to-date with their secret data format.
Targeted objects by this rule (types of kind): All
Complexity: medium (
)Policy as code identifier: ALL_EXPOSED_SECRET_BITBUCKET
This rule will fail
If a BitBucket client ID and/or client secret are present anywhere in the config:
CLIENT_ID: bitbucketr=>yf8gf86gcdz1e4df2efnbtmcpzwivk1a
SECRET: bitbucketnv-sl8p.rdr70z=>='`-y53xqehjw62a1z3wmh9-np9zkbl54_pf9isl0rvinzy3w2qwls0im2u=i08_6-5
Rule output in the CLI
$ datree test *.yaml
>> File: failExample.yaml
❌ Prevent exposed BitBucket secrets in objects [1 occurrence]
💡 Secret data found in config - keep your sensitive data elsewhere to prevent it from being stolen
How to fix this failure
Do not put sensitive data in any config. Kubernetes offers the handy Secret object to handle this.
If you do not wish to use Secrets, take a look at these available alternatives.