> 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/iac-security/iam/appsec-aws-107.md).

# Credentials exposure actions return credentials in an API response misconfiguration detected in code

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_107                                      |
| Category - Subcategory | IAM - Credential Exposure                             |
| Provider               | AWS                                                   |
| Severity               | LOW                                                   |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |

## Impact

AWS IAM users access AWS resources using different types of credentials, such as passwords or access keys. Credentials Exposure actions return credentials as part of the API response, such as ecr:GetAuthorizationToken, iam:UpdateAccessKey, and others. For more info, visit cloudsplaning documentation <https://cloudsplaining.readthedocs.io/en/latest/glossary/credentials-exposure/>

## How to Fix

*Resource:* AWS::IAM::Policy / AWS::IAM::ManagedPolicy / AWS::IAM::Group / AWS::IAM::Role / AWS::IAM::User

* *Arguments:* Effect + Actions \[source,go]

***

Resources: AdminDeny: Type: 'AWS::IAM::ManagedPolicy' Properties: ... PolicyDocument: ... Statement:

* Effect: Allow Action:
* 'lambda:CreateFunction'
* 'lambda:CreateEventSourceMapping'
* 'dynamodb:CreateTable' Resource: '\*'

***


---

# 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/iac-security/iam/appsec-aws-107.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.