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

# Usage of the force parameter disabling signature validation allowed misconfiguration detected in cod

## Rule Details

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

## Impact

This rule detects whether the force parameter is used with the Ansible apt module. The force parameter can override important safety mechanisms in package management. Allowing its usage can potentially result in the installation of packages without signature validation or enable package downgrades, potentially compromising system integrity and stability.

## How to Fix

*Module:* ansible.builtin.apt or apt

* *Attribute:* force

To mitigate this risk, it is crucial to avoid using the force parameter in your apt modules. If absolutely necessary, set the force parameter to false to avoid bypassing essential safety checks.

Secure Code Example:

## Ensuring that the force attribute is set to "no" or is absent in apt tasks is crucial to comply with this rule, safeguarding the system's stability and security. \[source,go]

* name: Example hosts: all gather\_facts: False tasks:
  * name: Avoid using force with apt ansible.builtin.apt: name: nginx state: latest
* ```
    force: yes
  ```
* ```
    force: no
  ```

***


---

# 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-ansible-6.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.