> 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/compute/appsec-aws-272.md).

# AWS Lambda function is not configured to validate code-signing misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_272                      |
| Category - Subcategory | Compute - Default Credentials Or Auth |
| Provider               | AWS                                   |
| Severity               | HIGH                                  |
| Framework              | Terraform, Terraform Plan             |

## Impact

This rule ensures that an AWS Lambda function has been properly configured to validate code-signing. If not correctly set up, it could mean that your AWS Lambda function is running code that has not been authenticated. This lack of validation raises a significant security concern, as your service could be running code that has been tampered with or injected with malicious code. This could lead to unauthorized access, data leaks, or compromise of the service. Therefore, it is vital to check and ensure that Lambda functions are enforced to validate code-signing for security.

## How to Fix

*Resource:* aws\_lambda\_function

* *Arguments:* code\_signing\_config\_arn

To address the issue, you need to enable the code-signing configuration for your AWS Lambda function. Code-signing adds an extra layer of security to your application by ensuring that the deployed code is not tampered with.

Example:

## In the above code, `aws_lambda_function` is configured with the `code_signing_config_arn` attribute. \[source,go]

resource "aws\_lambda\_function" "example" { function\_name = "example" s3\_bucket = aws\_signer\_signing\_job.job.signed\_object\[0].s3\[0].bucket s3\_key = aws\_signer\_signing\_job.this.signed\_object\[0].s3\[0].key handler = "exports.test" runtime = "nodejs12.x"

* code\_signing\_config\_arn = aws\_lambda\_code\_signing\_config.example.arn }

resource "aws\_lambda\_code\_signing\_config" "example" { allowed\_publishers { signing\_profile\_version\_arns = \[aws\_signer\_signing\_profile.example.version\_arn] }

## policies { untrusted\_artifact\_on\_deployment = "Enforce" } }


---

# 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/compute/appsec-aws-272.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.