> 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-ansible-5.md).

# Usage of packages with unauthenticated or missing signatures allowed misconfiguration detected in co

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ANSIBLE\_5                    |
| Category - Subcategory | Compute - Default Credentials Or Auth |
| Provider               | OTHER                                 |
| Severity               | LOW                                   |
| Framework              | Ansible                               |

## Impact

This rule detects whether Ansible apt modules install packages without authenticating their signatures, including those with missing signatures. Unauthenticated packages can result in the installation of modified or malicious packages through several mechanisms such as Man-in -the-Middle\_Attacks. Malicious attackers could potentially manipulate packages during download, inserting malicious code or substituting them with entirely malicious versions.

## How to Fix

*Module:* ansible.builtin.apt or apt

* *Attribute:* allow\_unauthenticated

To mitigate this risk, set the allow\_unauthenticated attribute in your apt module to either 'false' or 'omitted'. When you set allow\_unauthenticated to 'false', Ansible strictly enforces package authentication. This enforces the authentication of package signatures, thereby safeguarding your systems against potentially harmful packages. If you omit the allow\_unauthenticated attribute from your apt module, Ansible defaults to the system's behavior regarding package authentication. Typically, this behavior requires package signatures to be authenticated before installation.

Secure Code Example:

## Setting allow\_unauthenticated to false in this example ensures that only authenticated packages are installed via your apt module. \[source,go]

* name: Example hosts: all gather\_facts: False tasks:
  * name: Do not allow unauthenticated packages ansible.builtin.apt: name: nginx state: latest
* ```
    allow_unauthenticated: true
  ```
* ```
    allow_unauthenticated: false
  ```

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-ansible-5.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.