> 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/appsec2-azure-26.md).

# Azure PostgreSQL database flexible server configured with overly permissive network access misconfig

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_26                   |
| Category - Subcategory | Public Exposure - Ingress Controls   |
| Provider               | AZURE                                |
| Severity               | MEDIUM                               |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | 840a792d-f8a3-4331-b183-3eea67f519b8 |

## Impact

This rule is verifying that Azure PostgreSQL Flexible server is not set up with excessively permissive network access. The rule is important because overly permissive network access can potentially expose the database server to a wider range of threats. It offers an increased attack surface for unauthorized individuals or programs to exploit. If network access isn't restricted, it can lead to data breaches or unauthorized alterations to the database, compromising the privacy, security and integrity of the data hosted on the server. Hence, it is recommended to provide only necessary access permissions to maintain the lowest level of risk and exposure.

## How to Fix

*Resource:* azurerm\_postgresql\_flexible\_server\_firewall\_rule

* *Arguments:* start\_ip\_address, end\_ip\_address

Your Terraform configuration should define azurerm\_postgresql\_flexible\_server\_firewall\_rule resources with start\_ip\_address and end\_ip\_address values that do not allow access from any IP address (0.0.0.0 to 255.255.255.255). Here's how you might configure it:

## Remember to replace the example IP addresses with the actual IP ranges that should be allowed to access your server. \[source,go]

resource "azurerm\_postgresql\_flexible\_server\_firewall\_rule" "example" { name = "example-firewall-rule" resource\_group\_name = azurerm\_resource\_group.example.name server\_name = azurerm\_postgresql\_flexible\_server.example.name

* start\_ip\_address = "10.0.0.4" // Specific IP or range, not 0.0.0.0
* end\_ip\_address = "10.0.0.20" // Specific IP or range, not 255.255.255.255 }

***


---

# 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/public-exposure/appsec2-azure-26.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.