SQ34254
Detected presence of inactive web service API keys.
| 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. Web service users can provide a unique key that identifies the caller or confirms the access rights. API keys for supported web services are automatically validated via the least privilege APIs the service exposes. Detected API keys have been refused by their associated service as either inactive or expired. API keys could be considered secret. Keys that can be safely included in a software release package should only be used to identify the caller. For authentication, users should generate their own access keys instead.
How to resolve the issue
- You should securely store web service access keys, and fully automate their management and periodic rotation.
- If keys were published unintentionally and the software has been made public, you should revoke exposed keys and file a security incident.
Incidence statistics
Not relevant for this type of sensitive information.
Recommended reading
Why and when to use API keys (External resource - Google Cloud)
REST Security Cheat Sheet (External resource - OWASP)