SQ34253
Detected presence of inactive web service access tokens.
| priority | CI/CD status | severity | effort | RL level | RL assessment |
|---|---|---|---|---|---|
| None | pass | low | low | None | secrets: warning Reason: inactive web service credentials |
About the issue
Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, users provide a unique token that confirms their access rights to the web service. Access tokens for supported web services are automatically validated via the least privilege APIs the service exposes. Detected tokens have been refused by their associated service as either inactive or expired. Web service access tokens are considered secrets. They should never be included in a software release package, even if they are currently inactive or if they are obfuscated by encryption on the client-side.
How to resolve the issue
- You should securely store web service access tokens, and fully automate their management and periodic rotation.
- If tokens were published unintentionally and the software has been made public, you should file a security incident.
- Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.
Incidence statistics
Not relevant for this type of sensitive information.
Recommended reading
It’s not a secret if you publish it on PyPI (ReversingLabs blog)
What Is Token-Based Authentication? (External resource - Okta)