> 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-openstack-1.md).

# OpenStack hard coded password, token, or application\_credential\_secret exists in provider misconfigu

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_OPENSTACK\_1                       |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | OTHER                                      |
| Severity               | LOW                                        |
| Framework              | Terraform, Terraform Plan                  |

## Impact

This rule is designed to flag any instances where OpenStack passwords, tokens, or application\_credential\_secrets are hardcoded directly into the provider. The primary concern here is a matter of security. When sensitive credentials such as passwords or tokens are hardcoded, they can potentially be exposed to unauthorized users. If this occurs, the unauthorized user can have access to sensitive data in the OpenStack environment. Therefore, this rule helps to prevent security breaches by ensuring that credentials are not hardcoded and are instead managed securely.

## How to Fix

*Resource:* TBD

* *Arguments:* TBD

To fix the issue, remove any hard-coded secrets, tokens, or application\_credential\_secrets in your OpenStack provider. Instead, use environment variables or supply these credentials through a secure mechanism.

## The above code is secure because no sensitive data (like a password) is hard-coded into the OpenStack Provider configuration. Instead, the password is referenced as a variable `var.password`, which would typically be set using an environment variable or secure vault storage, limiting exposure of sensitive data. \[source,go]

## provider "openstack" { user\_name = "admin" tenant\_name = "admin" password = var.password // Set your password as a variable auth\_url = "<https://my-openstack.org:5000/v3/>" region = "RegionOne" }


---

# 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-openstack-1.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.