# Ensure Production Databases Are on a Private Network

- Source: https://support.icompaas.com/support/solutions/articles/a_1791826032073548-ensure-production-databases-are-on-a-private-network
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [OVH Cloud](https://support.icompaas.com/support/solutions/c_1791819364512367) › [checks](https://support.icompaas.com/support/solutions/folders/f_1791819376721251)
- Last updated: 2026-10-12
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description**

Ensure production Public Cloud Database services are connected to a private network (vRack), so that applications reach them over private addresses instead of the public internet.

**Rationale**

Databases with only a public endpoint must be reached over the internet, which exposes them to scanning and attacks. A private network keeps database traffic isolated from the internet and allows access only from resources on that network.

**Impact**

-   Database traffic stays on the private network
    
-   Removes public exposure of the database
    
-   Applications must be on the same private network
    

**Default Value**

By default, database services use public networking unless a private network is selected.

**Pre-Requisites**

-   Permission to manage the database service
    
-   A vRack, a private network, and a subnet in the same region
    

**Test Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, select Databases (under Databases & Analytics), then click the database service to open it.
    
4.  On the Dashboard tab, check the network type (public or private).
    
5.  If a production database uses public networking, follow the implementation steps.
    

**Implementation Steps**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, select Databases (under Databases & Analytics), then click the database service to open it.
    
4.  Update the network configuration of the service to use the private network and subnet, if the engine supports it; otherwise create a new service on the private network and migrate the data.
    
5.  Update the applications to use the private connection details.
    
6.  Confirm that applications can connect.
    

**Backout Plan**

1.  Log in to the OVHcloud Control Panel at [https://www.ovh.com/manager/](https://www.ovh.com/manager/).
    
2.  In the left-hand menu, select Public Cloud and choose your project.
    
3.  In the left-hand menu, select Databases (under Databases & Analytics), then click the database service to open it.
    
4.  Switch the applications back to the previous connection details, or revert the network configuration.
    

**Reference**

-   [https://docs.ovhcloud.com/en/guides/public-cloud/databases/getting-started](https://docs.ovhcloud.com/en/guides/public-cloud/databases/getting-started)
    
-   [https://docs.ovhcloud.com/en/guides/public-cloud/databases/faq](https://docs.ovhcloud.com/en/guides/public-cloud/databases/faq)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.