OpenParable
Skip to content
← Back to skills

Cis Azure Database 6.4

DevOps & Security
cis-azure-database-6.4

Cis Azure Database 6.4 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure Private Endpoints Are Used for Azure Database for PostgreSQL

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Database_Services_Benchmark_v2.0.0/cis-azure-database-6.4/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-database-6-4, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

6.4 Ensure Private Endpoints Are Used for Azure Database for PostgreSQL (Automated)

Profile Applicability

  • Level 2

Description

Private links make resources available via a private endpoint to a network you select. Tunneling between subscriptions, resource groups, without the need for traditional network routing.

Rationale

For sensitive data, private endpoints allow granular control of which services can communicate with PostgreSQL Servers and ensure that this network traffic is private. This can be set this up on a case by case basis for each service to be connected.

Impact

A private endpoint will expose your PostgreSQL database to the network selected, where it can be accessed by either IP or FQDN.

Audit Procedure

Audit from Azure Portal

  1. From Azure Database for PostgreSQL servers select a server to audit.
  2. In the column expand > Settings.
  3. Select Networking.
  4. Scroll down to the bottom to determine if there are any private endpoints attached to the server.

Audit from Azure Policy

Policy ID: 5375a5bb-22c6-46d7-8a43-83417cfb4460 Name: 'Private endpoint should be enabled for PostgreSQL flexible servers'

Expected Result

At least one private endpoint should be attached to the PostgreSQL server.

Remediation

Remediate from Azure Portal

  1. From Azure Database for PostgreSQL flexible servers select a server to audit.
  2. In the column expand > Settings.
  3. Select Networking.
  4. Scroll down to the bottom, and select + Create private endpoint.
  5. Select a subscription and resource group.
  6. Enter an instance name, network interface name, and select the same region that your PostgreSQL server is in.
  7. Verify that the information on Resource is correct. Then select Next.
  8. Select the virtual network, and subnet and select Next.
  9. Choose whether to use a dynamic or static IP address and select Next.
  10. Choose Yes or No on Integreate with private DNS zone.
  11. If Yes then select the subscription and resource group, then select Next.
  12. Enter any desired tags, then select Next.
  13. Verify the information, then select Create.

Default Value

Unless specified at resource creation, by default Azure Database for PostgreSQL does not have a private endpoint attached.

References

  1. https://learn.microsoft.com/en-us/azure/postgresql/network/concepts-networking-private-link

Profile

  • Level 2