IBM Cloud Docs
Using private endpoints to connect to Security and Compliance Center

Using private endpoints to connect to Security and Compliance Center

You can use private routes to IBM Cloud service endpoints to ensure that you have enhanced control and security over your data when you use IBM Cloud® Security and Compliance Center. Private routes are not accessible or reachable over the internet. By using the IBM Cloud private service endpoints, you can protect your data from threats from the public network, and logically extend your private network.

Before you begin

First, you must enable virtual routing and forwarding in your account before you can enable the use of IBM Cloud private service endpoints. For more information about setting up your account to support the private connectivity option, see Enabling VRF and service endpoints.

Setting up private endpoints

You must set up Security and Compliance Center instances to accept API requests from both public and private endpoints. You don't have the option to set up a Security and Compliance Center instance to be accessible through only private endpoints.

Viewing your endpoint URLs

The service endpoint URLs are different for private and public network connections. You can find your service endpoint URLs in the Endpoints page of the Security and Compliance Center UI. For more information about your service endpoint URLs, see Regions and endpoints.