Stay organized with collections
Save and categorize content based on your preferences.
Complete Security Command Center partner onboarding by creating a Google Cloud Marketplace
solution and completing pre-setup steps. The guide covers the following use
cases:
Onboarding using a customer's service account: your customer owns the service
account and you write data for your customer.
Onboarding for self-service customers: your customer owns the service account
and writes their own data using an app you provide.
Before you begin
Before you create a Cloud Marketplace solution, you need to sign up for
the technology partner program:
If you aren't already signed up as a partner, sign up to
list your products on Cloud Marketplace, and complete the corresponding business and
service agreements.
If you're already signed up as a partner, use the
Partner Support Desk to get started with a
Security Command Center listing, and include the word "Marketplace" in your
description. For more information about Partner Support Desk, including steps
to resolve any issues with accessing Partner Support Desk, visit
Request assistance with Cloud Marketplace.
Your project is added to the access control list that lets you create a
Managed Listing - Billed by Partner (also known as Standalone SaaS).
Onboarding using a customer's service account
This section describes how to complete onboarding in the following scenario:
You want to write Security Command Center data on behalf of your customer;
You're using a service account key from the customer.
To set up the Cloud Marketplace product using the customer's service
account, follow these steps:
In the Google Cloud console, go to the Producer Portal Overview page and
select a project where the Cloud Commerce Producer API is enabled.
PARTNER_ID: the ID assigned to you when you enrolled as a
Cloud Marketplace partner.
SOLUTION_ID: the ID assigned to the solution you created in the
previous steps.
For Product overview, add details about tasks that your
customer must complete after they register. This section supports
hyperlinks to external websites. Include the following
information:
After your customer uses the signup URL to provide their
sourceId and service account key, you can use them to write
Security Command Center data. When your customer adds your security tool
as a new security source, your security findings will
be displayed on the Security Command Center console.
Onboarding for self-service customers
This solution describes how to complete onboarding in the following scenario:
You don't want to write Security Command Center data on behalf of a customer;
You want your customer to write Security Command Center data on their own,
using an app you provide;
Your customer will use their own service account.
To set up the Cloud Marketplace product for a self-service customer,
follow these steps:
In the Google Cloud console, go to the Producer Portal Overview page and
select a project where the Cloud Commerce Producer API is enabled.
[PARTNER_ID] is the ID assigned to you when you enrolled as a
Cloud Marketplace partner.
[SOLUTION_ID] is the ID assigned to the solution you created in the
previous steps.
In the Product overview box, add details about tasks that your
customer should complete after they register. This section supports
hyperlinks to external websites. You should include the following
information:
Where to download your app to write Security Command Center data.
How to set up, sign in and authenticate, and run your app.
Where to paste the sourceId.
How to use the Security Command Center service account credentials in
your app. For example, you might have the customer start a VM as the
service account and run the app inside the VM.
On the Category ID drop-down list, select Security Command Center
Services
Select the Product metadata tab. Under Search metadata, enter
"Security Command Center".
After you've finished setting up your solution, click Submit and contact
cloud-partners@google.com to approve the solution.
Use the Security Command Center API to enable your
customers to write data to Security Command Center using your app.
After your customer sets up the app, they'll be able to use your app to write
their Security Command Center data.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Onboarding as a Security Command Center partner\n\nComplete Security Command Center partner onboarding by creating a Google Cloud Marketplace\nsolution and completing pre-setup steps. The guide covers the following use\ncases:\n\n- Onboarding using a customer's service account: your customer owns the service account and you write data for your customer.\n- Onboarding for self-service customers: your customer owns the service account and writes their own data using an app you provide.\n\nBefore you begin\n----------------\n\nBefore you create a Cloud Marketplace solution, you need to sign up for\nthe technology partner program:\n\n- If you aren't already signed up as a partner, sign up to [list your products on Cloud Marketplace](/marketplace/docs/partners), and complete the corresponding business and service agreements.\n- If you're already signed up as a partner, use the [Partner Support Desk](https://g.co/cloud/psd-partner) to get started with a Security Command Center listing, and include the word \"Marketplace\" in your description. For more information about Partner Support Desk, including steps to resolve any issues with accessing Partner Support Desk, visit [Request assistance with Cloud Marketplace](/marketplace/docs/partners/get-support). Your project is added to the access control list that lets you create a Managed Listing - Billed by Partner (also known as Standalone SaaS).\n\nOnboarding using a customer's service account\n---------------------------------------------\n\nThis section describes how to complete onboarding in the following scenario:\n\n- You want to write Security Command Center data on behalf of your customer;\n- You're using a service account key from the customer.\n\nTo set up the Cloud Marketplace product using the customer's service\naccount, follow these steps:\n\n1. In the Google Cloud console, go to the **Producer Portal Overview** page and\n select a project where the Cloud Commerce Producer API is enabled.\n\n [Go to Overview](https://console.cloud.google.com/projectselector2/producer-portal?supportedpurview=project)\n2. To create a new product, click **Add Product**.\n\n3. On the **Add product** page, complete the\n following steps:\n\n 1. Select **Standalone Listing**.\n 2. For **Product name**, enter the name of the product. The product name\n can't have more than 64 characters.\n\n Take note of the product ID.\n 3. Click **Create**.\n\n4. To view the product details, click **Product details**.\n\n5. In the **Product info** pane, add\n signup instructions for your customer:\n\n 1. For **Signup URL**, enter the signup URL in the following format:\n\n https://console.cloud.google.com/security/command-center/source-registration;partnerId=\u003cvar translate=\"no\"\u003ePARTNER_ID\u003c/var\u003e;solutionId=\u003cvar translate=\"no\"\u003eSOLUTION_ID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePARTNER_ID\u003c/var\u003e: the ID assigned to you when you enrolled as a Cloud Marketplace partner.\n - \u003cvar translate=\"no\"\u003eSOLUTION_ID\u003c/var\u003e: the ID assigned to the solution you created in the previous steps.\n 2. For **Product overview**, add details about tasks that your\n customer must complete after they register. This section supports\n hyperlinks to external websites. Include the following\n information:\n\n - How to generate a service account key for the service account by using the guide to [creating and managing service account keys](/iam/docs/creating-managing-service-account-keys).\n - How to sign in to your website and provide you with the sourceId and service account key.\n 3. In the **Category ID** drop-down list, select **Security Command Center\n Services**.\n\n6. Select the **Product metadata** tab.\n\n7. For **Search metadata**, enter\n \"Security Command Center\".\n\n8. After you finish setting up your solution, click **Submit**.\n\n9. Contact\n [cloud-partners@google.com](mailto:cloud-partners@google.com) to request approval of your solution.\n\n10. Use the [Security Command Center API](/security-command-center/docs/reference/rest) to write data to\n Security Command Center.\n\nAfter your customer uses the signup URL to provide their\n`sourceId` and service account key, you can use them to write\nSecurity Command Center data. When your customer adds your security tool\nas a new [security source](/security-command-center/docs/how-to-security-sources), your security findings will\nbe displayed on the Security Command Center console.\n\nOnboarding for self-service customers\n-------------------------------------\n\nThis solution describes how to complete onboarding in the following scenario:\n\n- You don't want to write Security Command Center data on behalf of a customer;\n- You want your customer to write Security Command Center data on their own, using an app you provide;\n- Your customer will use their own service account.\n\nTo set up the Cloud Marketplace product for a self-service customer,\nfollow these steps:\n\n1. In the Google Cloud console, go to the **Producer Portal Overview** page and\n select a project where the Cloud Commerce Producer API is enabled.\n\n [Go to Overview](https://console.cloud.google.com/projectselector2/producer-portal?supportedpurview=project)\n2. To create a new solution, click **Add Product**.\n\n3. In the **Add product** window that appears, complete the\n following:\n\n 1. Select **Standalone Listing**.\n 2. Add a **Product name** and make note of the **Product ID**. The product name cannot be more than 64 characters.\n 3. Click **Create**.\n4. To view the product details, click **Product details** on the left menu.\n\n5. In the **Product info** panel that appears, add\n signup instructions for your customer:\n\n 1. Under **Signup URL**, enter the signup URL in the following format:\n\n https://console.cloud.google.com/security/command-center/source-registration;partnerId=[PARTNER_ID];solutionId=[SOLUTION_ID]\n\n Where the variables correspond to the following:\n - `[PARTNER_ID]` is the ID assigned to you when you enrolled as a Cloud Marketplace partner.\n - `[SOLUTION_ID]` is the ID assigned to the solution you created in the previous steps.\n 2. In the **Product overview** box, add details about tasks that your\n customer should complete after they register. This section supports\n hyperlinks to external websites. You should include the following\n information:\n\n - Where to download your app to write Security Command Center data.\n - How to set up, sign in and authenticate, and run your app.\n - Where to paste the sourceId.\n - How to use the Security Command Center service account credentials in your app. For example, you might have the customer start a VM as the service account and run the app inside the VM.\n 3. On the **Category ID** drop-down list, select **Security Command Center\n Services**\n\n6. Select the **Product metadata** tab. Under **Search metadata**, enter\n \"Security Command Center\".\n\n7. After you've finished setting up your solution, click **Submit** and contact\n [cloud-partners@google.com](mailto:cloud-partners@google.com) to approve the solution.\n\n8. Use the [Security Command Center API](/security-command-center/docs/reference/rest) to enable your\n customers to write data to Security Command Center using your app.\n\nAfter your customer sets up the app, they'll be able to use your app to write\ntheir Security Command Center data.\n\nWhat's next\n-----------\n\n- Learn how to [access Security Command Center with client libraries](/security-command-center/docs/reference/libraries)."]]
