> 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/public-exposure/appsec-gcp-16.md).

# GCP Cloud DNS has DNSSEC disabled misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_16                            |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | GCP                                        |
| Severity               | MEDIUM                                     |
| Framework              | Terraform, Terraform Plan                  |
| Mapped CSPM/KSPM Rule  | 72a4b096-a34b-4a22-a77c-3f38cdbcf986       |

## Impact

DNSSEC is a feature of the Domain Name System that authenticates responses to domain name lookups. DNSSEC prevents attackers from manipulating or poisoning the responses to DNS requests. We recommend you ensure DNSSEC is enabled in: any public DNS zone, the top level domain registry, and in the local DNS resolvers.

NOTE: If *visibility* is set to *private*, then DNSSEC cannot be set, and this rule will pass.

## How to Fix

*Resource:* google\_dns\_managed\_zone

* *Arguments:* dnssec\_config (Optional) DNSSEC configuration Structure is documented below. \[source,go]

***

resource "google\_dns\_managed\_zone" "example" { description = "Company Domain name" dns\_name = "example.com."

* dnssec\_config { # forces replacement
* kind = "dns#managedZoneDnsSecConfig" # forces replacement
* non\_existence = "nsec3" # forces replacement
* state = "on" # forces replacement", }

***


---

# 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/public-exposure/appsec-gcp-16.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.