> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/data-security-posture-management/prisma-cloud-dspm-deployment/deploy-prisma-cloud-dspm-on-gcp/offboarding-gcp.md). # Offboarding GCP ## Overview Offboarding involves stopping the monitoring of a cloud account in Prisma Cloud Data Security Posture Management (DSPM) and then deleting it from the DSPM console. This process removes all data associated with the specified project. **Important:** If you want to temporarily disable DSPM without offboarding, please refer to [Monitoring an Account](https://docs.prismacloud.io/en/enterprise-edition/content-collections/data-security-posture-management/how-to-articles/configure-the-scanning-settings-for-supported-services#monitoring-an-account). ### Prerequisites Before proceeding with the offboarding process, make sure that you have the necessary permissions to manage your GCP project and deployment manager resources. ## Offboarding Procedure **WARNING:** Perform the offboarding procedure according to the order described below to avoid causing issues such as resources not being deleted from the project. ### Step 1: Offboarding a Project from the Prisma Cloud Console **WARNING:** The offboarding process is irreversible; once initiated, it cannot be canceled, and all data is permanently deleted. Before initiating the offboarding process, review the project information in the Prisma Cloud DSPM console. **Deleted Data** When you initiate offboarding, the following data is deleted: * Assets * Classification findings * Risk findings * Activity log entries * Dynamic resources used for scans The following resources are not deleted; however, they are deleted in the next steps: * Static resources created by Prisma Cloud DSPM for scanning purposes * Third-party integrations * Prisma Cloud DSPM deployment resources, including: * Roles * Service accounts * Bindings * Sign in to Prisma Cloud Console. * From the DSPM **Preferences** tab, navigate to the **GCP projects** page. ![](/files/UqdZTSh0ZPHLT3qT1HoK) * Navigate to the DSPM project you want to offboard. * Click the gear icon in the column on the far right side of the project table, and select **Offboard Project**. ![](/files/NoIw1mSLmONZxiKRAxxM) * Read the information provided and click **Offboard** Project to confirm. * Read content on the entire **Offboard Project?** screen. If you agree with the warnings and want to proceed with offboarding the project, click **Offboard Project.** ![](/files/cBOIQicA5B3SDzeim3N1) During the offboarding process, the following occurs: * Project monitoring is disabled. * An **Offboarding** tag is applied to the project. * All data associated with the cloud account is deleted within 72 hours. **NOTE:** Data may still appear in the console during this period. **WARNING:** The cloud infrastructure deployed by DSPM is not deleted during the offboarding process. For more details, refer to the specific offboarding documentation. **This process is irreversible, so proceed with caution**. ### Step 2: Wait for Resource Deletion After disabling monitoring, wait for 48 hours. During this time, all resources created in GCP as part of the scanning procedures are scheduled for deletion. **WARNING:** If you proceed with the offboarding process before this period concludes, some resources may remain in your environment and will not be deleted. ### Step 3: Access the CloudShell * Sign in to your GCP account. * Navigate to the CloudShell page. ### Step 4: Delete the Org Resources (Single Account) Locate and delete the Dig Security deployment manager according to your location. Europe * dig-security-logging * dig-security-roles * dig-security-service-accounts (edited) United States * dig-security-logginguse1 * Dig-security-rolesuse1 * dig-security-service-accountsuse1 ### Step 5: Delete Binding of the Deleted Service Accounts 1. Navigate to the IAM (account level or Folder/Org level) page and delete the binding of the deleted service accounts. 2. Delete each binding with the prefix “dig-”. 3. Navigate to the Org roles page and delete all roles with “Dig\_”. **Disclaimer:** The permanent deletion process takes 30 days. During the 30-day window, the role and all associated bindings are permanently removed, and you cannot create a new role with the same role ID. Reference: ​​[Create and manage custom roles | IAM Documentation | Google Cloud](https://cloud.google.com/iam/docs/creating-custom-roles#deleting-custom-role) ### Step 6: DDR Offboarding **Note:** Perform the following steps only when offboarding an Orchestrator project. 1. Go to the GCP console in the orchestrator project you are offboarding. 2. In the search box, type log router and select the Log Router page. 3. Search for the sink mentioned under Log Sink with the prefix “dig-”. 4. Click on the three dots and select Delete sink. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prismacloud.io/content-collections/data-security-posture-management/prisma-cloud-dspm-deployment/deploy-prisma-cloud-dspm-on-gcp/offboarding-gcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.