> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/secrets-security/appsec-secret-355.md).

# IBM COS HMAC credentials detected in code

## Rule Details

|                       |                     |
| --------------------- | ------------------- |
| Cortex AppSec Rule ID | APPSEC\_SECRET\_355 |
| Category              | Secrets             |
| Severity              | LOW                 |
| Framework             | Git                 |

## Impact

The IBM Cloud Object Storage (COS) HMAC credential provides S3-compatible access.

Exposure is a Critical Risk allowing an attacker to interact with storage buckets, reading sensitive files, deleting backups, or hosting malware using standard S3 tools.

## How to Fix

To remediate exposed Cloud & Infrastructure credentials:

1. Log in to your cloud provider's console.
2. Locate the identity or service account associated with the compromised credentials.
3. Revoke or deactivate the compromised keys immediately.
4. Generate a new set of credentials.
5. Update your environment variables, secrets manager, or pipelines with the new values.

Next, remove the secret from your codebase:

1. Locate the exposed secret in your codebase.
2. Replace the hardcoded value with a secure variable or reference.

Finally, clean your version control history:

1. Permanently remove the sensitive data from your version control history to ensure it cannot be retrieved.

Warning: Revoking infrastructure keys may cause immediate downtime. Ensure you have identified all dependent services before revoking.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/secrets-security/appsec-secret-355.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.