Connecting CIEM GCP to IdentityNow

Once you have configured your GCP account, you can connect it to IdentityNow to display the total effective access users have to your Google Cloud Platform. To display this data, you must use the G Suite identity and CIEM GCP cloud governance connectors.


G Suite identity governance connector	Allows you to manage your GCP accounts, groups, and roles in IdentityNow. If your organization has licensed a SailPoint cloud management solution, it will also gather data on the cloud resources users are granted through your GCP organization, projects, accounts, and role assignments.
CIEM GCP cloud governance connector	Works with your GCP identity governance connector to collect cloud resource data and display the total access an identity has to your cloud systems.

FedRamp Limitations

CIEM FedRamp customers can register a maximum of 650 GCP projects.

You may connect your G Suite identity governance and CIEM GCP cloud governance sources in any order.

After you've connected and aggregated your accounts and entitlements, you will mark the entitlements related to cloud access. This will allow you to view an identity's cloud access granted through entitlements and include those entitlements in certification campaigns.

Connecting GCP Identity Governance

Follow the directions to connect your G Suite source, or edit an existing one.

Select the Manage Cloud Resources toggle and enter your organization ID in the Cloud Resource Management Settings configuration to enable it to gather cloud data.

You must then use the CIEM GCP cloud governance connector to display all access users have to your cloud resources.

Connecting GCP Cloud Governance

The CIEM GCP source pulls data daily about the cloud resources your GCP IaaS users can access.

To register CIEM GCP:

Go to Admin > Connections > Create New.
Find and select the CIEM GCP source type.
Enter a source name.
Enter a description for your source.
In the Source Owner field, begin typing the name of an owner. Matches appear after you type two letters.
(Optional) Select a governance group for source management.
Select Save.
Select Connection Settings in the left panel.
In the Organization ID field, enter the 10-digit organization ID. You can find this in the Google Cloud Platform console by selecting the dropdown menu with your project or organization name. Select the All tab and copy the organization ID.
Enter an email with admin access to the Google Admin Console.

Note

The domain must be the same as the organization name. For example, if the organization name is "testorg.com", then the admin email will need to be formatted like "smith@testorg.com".
Paste the JSON you received when creating the key for the service account.
Select Save.
Select Review and Test.
Review the configuration details and select Test Connection. A successful test is required for CIEM to gather data for this source.

Note

If the test connection fails, you can use the Search query name:“Test_connection Source Failed” for more information.

After a successful test connection, you can set the source scope or move on to marking the entitlement types that grant cloud access.

Setting Source Scope

By default, CIEM reads and automatically discovers changes to your cloud infrastructure, which are displayed in the Cloud Scopes section of your CIEM source configuration. You can choose to exclude scopes to prevent CIEM from including data for those accounts.

To change the scope of your included source data:

In the CIEM GCP source, select Cloud Scopes under Aggregation and Provisioning.
Use the checkboxes to change which accounts are included. Removing a scope disables Auto-Include Scopes.
Select Save.

CIEM will now only read and include data from your selected scopes. When Auto-Include Scopes is disabled, new and deleted accounts in your cloud system will be detected, but they will not be automatically included in your CIEM data until you select them individually or reenable Auto-Include Scopes.

Notes

You can search for scopes as well as filter by selected and unselected scopes.
The Last Refreshed time is when changes to your source inventory were last detected by CIEM. This is separate from aggregation.

Marking GCP Cloud-Enabled Entitlement Types

When entitlements are pulled from your GCP cloud environment, you must mark the Group and Role entitlement types as Cloud Enabled in the G Suite source configuration. This will allow certification campaign reviewers to view the access users have to your GCP cloud infrastructure.

Go to Admin > Connections > Sources.
Select the G Suite identity governance connector you enabled to manage cloud resources.
Select the Import Data tab and choose Entitlement Types.
Edit the Group and Role entitlement types and select the Cloud Enabled checkbox.
Select Update.

You can now view an identity's cloud access granted through entitlements and add cloud-based entitlement types to certification campaigns to allow certifiers to view the effective access an identity has on a GCP resource.

Viewing Effective Access to GCP Resources

After marking your entitlement types, you can include cloud-enabled entitlements in certification campaigns to allow your certifiers to view cloud access details like the last level of access and type of action taken on the resource.

Certifiers can also view the access paths between scoped objects like groups, policies, and projects granting the user access to the selected resource. They can view the direct access granted by the entitlement or all access paths to the resource. The entitlement access path is highlighted.

If a user has multiple of the same type of access at the same scope, such as multiple role assignments that lead to the same management group, your certifiers can select the node to display the access leading to the resource.

Refer your certifiers to Viewing Cloud Access Details in the User Help for guidance on viewing cloud access details.

Excluded GCP Asset Types

SailPoint CIEM displays the effective and last access data for supported GCP asset types except:

anthos.googleapis.com/ConnectedCluster
bigquerymigration.googleapis.com/MigrationWorkflow
compute.googleapis.com/RegionDisk
containerregistry.googleapis.com/Image
dialogflow.googleapis.com/KnowledgeBase
dialogflow.googleapis.com/LocationSettings
dlp.googleapis.com/DlpJob
firebase.googleapis.com/FirebaseAppInfo
firestore.googleapis.com/Database
identity.accesscontextmanager.googleapis.com/AccessLevel
identity.accesscontextmanager.googleapis.com/AccessPolicy
identity.accesscontextmanager.googleapis.com/ServicePerimeter
networkconnectivity.googleapis.com/PolicyBasedRoutes
networkservices.googleapis.com/EdgeCacheKeyset
networkservices.googleapis.com/EdgeCacheOrigin
networkservices.googleapis.com/EdgeCacheService
sqladmin.googleapis.com/Instance