> 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/appsec2-ibm-2.md).

# IBM Cloud Virtual Private Cloud (VPC) classic access is enabled in Terraform misconfiguration detect

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_IBM\_2                |
| Category - Subcategory | Public Exposure - VPC VCN VNet |
| Provider               | IBM                            |
| Severity               | HIGH                           |
| Framework              | Terraform, Terraform Plan      |

## Impact

This rule ensures that VPC classic access is disabled. It checks for configurations in your cloud infrastructure to confirm that virtual private cloud (VPC) instances are not allowing classic access. Classic access can pose several security risks as it may enable connections from legacy environments that lack modern security features and controls. Disabling this access minimizes the potential attack surface and enhances the overall security posture of your infrastructure.

## How to Fix

*Resource:* ibm\_is\_vpc

* *Arguments:* classic\_access

Ensure that the `classic_access` attribute in the ibm\_is\_vpc resource is set to `false`, preventing access from legacy environments.

## In this example, the `classic_access` attribute is set to `false` in the ibm\_is\_lb resource to disable classic access to the VPC. \[source,go]

resource "ibm\_is\_vpc" "secure\_vpc" { ...

* classic\_access = 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 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/appsec2-ibm-2.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.