> 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-364.md).

# Permissions delegated to AWS services for AWS Lambda functions are not limited by SourceArn or Sourc

## Rule Details

|                        |                                           |
| ---------------------- | ----------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_364                          |
| Category - Subcategory | IAM - Overly Permissive                   |
| Provider               | AWS                                       |
| Severity               | HIGH                                      |
| Framework              | CloudFormation, Terraform, Terraform Plan |

## Impact

This rule ensures that AWS Lambda function permissions delegated to AWS services are restricted by `SourceArn` or `SourceAccount`. This helps prevent unauthorized access and limits the scope of permissions granted to Lambda functions.

## How to Fix

To mitigate this issue, ensure that the `AWS::Lambda::Permission` resource includes the `SourceArn` or `SourceAccount` property to limit the permissions delegated to AWS services.

## Example: \[source,go]

{ "Resources": { "MyLambdaPermission": { "Type": "AWS::Lambda::Permission", "Properties": { "Action": "lambda:InvokeFunction", "FunctionName": "MyFunction", "Principal": "sns.amazonaws.com",

* "SourceArn": "arn:aws:sns:us-east-1:123456789012:MyTopic" } } } }

***

Resources: MyLambdaPermission: Type: AWS::Lambda::Permission Properties: Action: lambda:InvokeFunction FunctionName: MyFunction Principal: sns.amazonaws.com

* SourceArn: arn:aws:sns:us-east-1:123456789012:MyTopic

***


---

# 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-364.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.