> 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/appsec2-oci-1.md).

# OCI tenancy administrator users are associated with API keys misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_OCI\_1           |
| Category - Subcategory | IAM - Credential Exposure |
| Provider               | ORACLE                    |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is checking to ensure that administrator users are not associated with API keys. This is important because, if an administrator's API key is compromised, it can give the attacker extensive privileges that can potentially lead to critical consequences. Access via API keys should be given to services and applications, not to users, in order to maintain proper access control and minimize risk.

## How to Fix

*Resource:* oci\_identity\_group, oci\_identity\_user

## To fix this issue, do not associate API keys with administrator users. Instead, use instance principals or dynamic groups. Also, keep a regular rotation of API keys and deprecate old ones to maintain better security. \[source,go]

resource "oci\_identity\_user" "user1" { #Required compartment\_id = "var.tenancy\_ocid" description = "var.user\_description" name = "user1"

\#Optional defined\_tags = {"Operations.CostCenter"= "42"} email = "var.user\_email" freeform\_tags = {"Department"= "Finance"} }

* resource "oci\_identity\_api\_key" "user1\_api\_key" {
* \#Required
* key\_value = "var.api\_key\_key\_value"
* user\_id = oci\_identity\_user.user1.id
* }

## resource "oci\_identity\_user\_group\_membership" "user1\_in\_admin\_group" { #Required group\_id = oci\_identity\_group.admin\_group.id user\_id = oci\_identity\_user.user1.id }


---

# 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/iam/appsec2-oci-1.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.