> 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/networking/appsec-oci-23.md).

# OCI Data Catalog configured with overly permissive network access misconfiguration detected in code

## Rule Details

|                       |                           |
| --------------------- | ------------------------- |
| Cortex AppSec Rule ID | APPSEC\_OCI\_23           |
| Category              | Networking                |
| Provider              | ORACLE                    |
| Severity              | HIGH                      |
| Framework             | Terraform, Terraform Plan |

## Impact

This rule identifies Data Catalogs configured with overly permissive network access.

The OCI Data Catalog service provides a centralized repository to manage and govern data assets, including their metadata. When network access settings are too permissive, it can expose sensitive metadata to unauthorized users or malicious actors, potentially leading to data breaches and compliance issues.

As a best practice, it is recommended to configure the Data catalog with private endpoints; so that the Data catalog is accessible only to restricted entities.

## How to Fix

Ensure that your OCI Data Catalog is configured with a private endpoint to restrict network access. This will help prevent overly permissive access to the data catalog service.

## In this example, you should configure a private endpoint for the `oci_data_catalog` resource using Terraform. \[source,go]

resource "oci\_datacatalog\_catalog" "example" { ...

* attached\_catalog\_private\_endpoints = \[oci\_datacatalog\_catalog\_private\_endpoint.example\_private\_endpoint.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 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/networking/appsec-oci-23.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.