> [!NOTE]
> Standard-legacy, Standard, Premium, and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

> [!CAUTION]
> The Security Command Center Enterprise service tier will shut down on May 21, 2027. If your organization uses the Enterprise service tier, then the organization will automatically move to the Premium service tier on or after May 21, 2027. Contact your account representative or a [Google Cloud sales specialist](https://cloud.google.com/contact) if you have questions.

Two types of services run on Security Command Center:
*built-in services* and *integrated services*. Built-in services are part of
Security Command Center. Integrated services
are Google Cloud or third-party
services that provide findings to Security Command Center.

This page describes how to configure built-in services and integrated services.

If data residency is enabled, some services and features might be unsupported
or provide a modified set of capabilities. For more information, see
[Plan for data residency](https://docs.cloud.google.com/security-command-center/docs/data-residency-support.md.txt).

### Activate Security Command Center

Verify that you have
[activated Security Command Center](https://docs.cloud.google.com/security-command-center/docs/activate-scc-overview.md.txt) at either
the project or the organization level.

Some services might be unsupported or provide a modified set of
capabilities when Security Command Center is activated at the project level.

## Required permissions and roles

To enable or disable a service, you must have the following IAM
permission. You can grant this permission at the organization, folder, or project
level.

`securitycentermanagement.securityCenterServices.update`

Ask your administrator to either grant you one of the following roles that
includes this permission or add the permission to the custom role (if your
organization uses custom roles).

- [Security Center Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycenter.md.txt#securitycenter.admin) (`roles/securitycenter.admin`)
- [Security Center Settings Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycenter.md.txt#securitycenter.settingsAdmin) (`roles/securitycenter.settingsAdmin`)
- [Security Center Settings Editor](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycenter.md.txt#securitycenter.settingsEditor) (`roles/securitycenter.settingsEditor`)
- [Security Center Management Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycentermanagement.md.txt#securitycentermanagement.admin) (`roles/securitycentermanagement.admin`)
- [Security Center Management Services Editor](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycentermanagement.md.txt#securitycentermanagement.securityCenterServicesEditor) (`roles/securitycentermanagement.securityCenterServicesEditor`)
- [Security Center Management Settings Editor](https://docs.cloud.google.com/iam/docs/roles-permissions/securitycentermanagement.md.txt#securitycentermanagement.settingsEditor) (`roles/securitycentermanagement.settingsEditor`)

## Built-in services of Security Command Center

> [!NOTE]
> Standard-legacy, Standard, Premium, and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt)

The following built-in services are part of Security Command Center:

- AI Protection: *Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Artifact guard ([Preview](https://cloud.google.com/products/#product-launch-stages)): *Premium and Enterprise (Deprecated) service tiers only*
- Container Threat Detection: *Premium and Enterprise (Deprecated) service tiers only*
- Cloud Run Threat Detection: *Premium and Enterprise (Deprecated) service tiers only*
- Compliance Manager: *Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Data Security Posture Management (DSPM): *Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Event Threat Detection: *Premium and Enterprise (Deprecated) service tiers only*
- External Exposure ([Preview](https://cloud.google.com/products/#product-launch-stages)): *Premium and Enterprise (Deprecated) service tiers only*
- Notebook Security Scanner ([Preview](https://cloud.google.com/products/#product-launch-stages)): *Premium and Enterprise (Deprecated) service tiers only*
- Security Health Analytics: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Security posture: *Premium and Enterprise (Deprecated) service tiers only*
- Sensitive Actions Service: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Virtual Machine Threat Detection: *Premium and Enterprise (Deprecated) service tiers only*
- Vulnerability Assessment for Amazon Web Services (AWS): *Enterprise (Deprecated) service tier only*
- Vulnerability Assessment for Google Cloud: *Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Web Security Scanner: *Standard-legacy, Premium, and Enterprise (Deprecated) service tiers only*

You can't enable or disable the
Security posture service or Sensitive Actions Service. These services are available
by default when you activate the Security Command Center Premium tier or
Security Command Center Enterprise tier.

You can't disable Compliance Manager after you enable it.

You can't enable DSPM for an organization that doesn't already
use it. If DSPM is already enabled for your organization, you
can't disable it.

Most built-in services can be enabled for your entire organization or just for
selected folders or projects. By default, folders and projects inherit service
enablement settings from their parent organization or folder.

The Vulnerability Assessment for AWS service can be enabled only for a Google Cloud
organization and requires that you establish a connection between
Security Command Center and AWS.

The Container Threat Detection service can be enabled only for clusters. For information
about required permissions for Container Threat Detection, see
[Required IAM permissions](https://docs.cloud.google.com/security-command-center/docs/how-to-use-container-threat-detection.md.txt#required_permissions).

### Enable or disable a built-in service

To enable or disable a Security Command Center service for a resource, do the
following:

1. In the Google Cloud console, go to the **Settings** page of Security Command Center.

   <br />

   [Go to Settings](https://console.cloud.google.com/projectselector2/security/command-center/config/services?supportedpurview=organizationId,project)

   <br />

2. Select the organization or project for which you need to manage
   services.

3. For the service that you want to modify, click **Manage settings**.

4. On the **Service enablement** tab, in the hierarchical view of resources,
   select the organization, folder, project, or container for which you need to
   enable the service.

5. For that resource, set the service to **Enable** , **Disable** , or
   **Inherit**.

   > [!NOTE]
   > **Note:** For Container Threat Detection and Cloud Run Threat Detection, setting the state of a folder or project to **Inherit** is the same as setting it to **Disable**.

Some services, like Security Health Analytics, operate using batch scans. When you
disable such a service, the change might not be reflected immediately. The change
is effective after all ongoing batch scans are complete. This can lead to
a scenario where new vulnerabilities are still detected for a short period after
you disable the service.

### View and edit the modules of a service

For some services (for example, Security Health Analytics), you can enable or disable certain
detectors by enabling or disabling their corresponding modules. To configure the
modules of a service and view their current statuses, do the following:

1. In the Google Cloud console, go to the **Settings** page of Security Command Center.

   <br />

   [Go to Settings](https://console.cloud.google.com/projectselector2/security/command-center/config/services?supportedpurview=organizationId,project)

   <br />

2. Select the organization or project for which you need to manage
   services.

3. For the service that you want to view, click **Manage settings**.

4. Click the **Modules** tab. The service's modules are displayed, along with
   their respective statuses. The **Modules** tab is available only for
   services that have configurable modules.

5. Find the module that you want to modify, and set its status to
   **Enable** or **Disable**.

If you disable a service, the individual modules of that service are also
disabled. For
Virtual Machine Threat Detection for Google Cloud and Event Threat Detection, the modules continue to show
their previous statuses---through the API and the
Google Cloud console---even when the service is disabled. Be aware that
although certain modules appear to be enabled, those modules aren't in operation
if the service is disabled.

## Add integrated Google Cloud services to Security Command Center

> [!NOTE]
> Standard-legacy, Standard, Premium, and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt) (requires [organization-level activation](https://docs.cloud.google.com/security-command-center/docs/activate-scc-overview.md.txt#overview_of_organization-level_activation))

You can add an integrated service to an organization-level activation of
Security Command Center. Project-level activations don't support integrated
Google Cloud services.

Security Command Center provides the following integrated services:

- Assured Open Source Software (Assured OSS): *Premium and Enterprise (Deprecated) service tiers only*
- Mandiant Attack Surface Management: *Enterprise (Deprecated) service tier only*
- Anomaly Detection: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Cloud Armor: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*
- IAM Recommender: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*
- Sensitive Data Protection: *Standard-legacy, Premium, and Enterprise (Deprecated) service tiers only*
- VM Manager ([Preview](https://cloud.google.com/products/#product-launch-stages)): *Premium and Enterprise (Deprecated) service tiers only*
- Model Armor: *Standard-legacy, Standard, Premium, and Enterprise (Deprecated) service tiers only*

For more information about these services, see
[Detection services for vulnerabilities and threats](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources.md.txt).

To enable an integrated service, follow these steps:

1. In the Google Cloud console, go to the Security Command Center page.


   [Go to Security Command Center](https://console.cloud.google.com/security/command-center/config/services)

   <br />

2. Select your organization or project.

3. Click **Settings**.

4. Click the **Integrated services** tab.

5. Next to the integrated source that you want to enable, click the **Status**
   list and select **Enable**.

Findings from the services that you enable are displayed on the **Findings**
page in the Security Command Center dashboard.

Some Google Cloud security services require additional integration steps
that you must complete. See the following:

- To configure the Assured OSS integration, see [Integrate with Assured OSS](https://docs.cloud.google.com/security-command-center/docs/integrate-aoss-with-scc.md.txt).
- To configure the Sensitive Data Protection integration, see [Enable sensitive data discovery](https://docs.cloud.google.com/security-command-center/docs/activate-sensitive-data-discovery.md.txt).

To disable an integrated service, next to its name, click the list and select
**Disable**.

## Add a third-party security service

> [!NOTE]
> Standard-legacy, Standard, Premium, and Enterprise (Deprecated) [service tiers](https://docs.cloud.google.com/security-command-center/docs/service-tiers.md.txt) (requires [organization-level activation](https://docs.cloud.google.com/security-command-center/docs/activate-scc-overview.md.txt#overview_of_organization-level_activation))

Organization-level activations of Security Command Center can display findings from
third-party security services that have registered as Cloud Marketplace
partners.

Project-level activations of Security Command Center don't support third-party
services.

To integrate security services that aren't registered as
Cloud Marketplace partners, ask the providers to complete the guide to
[Onboard as a Security Command Center partner](https://docs.cloud.google.com/security-command-center/docs/how-to-partner-onboard.md.txt).

To add a new third-party security service to Security Command Center, you set up the
security service, and then enable it in the Google Cloud console.

### Before you begin

To add a security service for a registered Cloud Marketplace partner,
you need the following:

- The following Identity and Access Management (IAM) [roles](https://docs.cloud.google.com/iam/docs/understanding-roles):
  - Security Center Admin (`roles/securitycenter.admin`)
  - Service Account Admin (`roles/iam.serviceAccountAdmin`)
- A Google Cloud project that you want to use for the security service.

### Set up a security service

To set up a third-party security service, you need a service account for that
service. When you add the new security service, you can choose from the
following service account options:

- Create a service account.
- Use your own existing service account.
- Use a service account from the service provider.

To set up a new security service that's already registered as a
Cloud Marketplace partner, complete the following:

1. Go to the Security Command Center Services **Marketplace** page in the
   Google Cloud console.


   [Go to Marketplace](https://console.cloud.google.com/marketplace/browse?filter=category:security-command-center-services)

   <br />

2. The **Marketplace** page displays security services that are directly
   associated with Security Command Center.

   - If you don't see the security service that you want to add, search for **Security**, and then select the security service provider.
   - If the security service provider isn't registered in the Cloud Marketplace, ask your provider to complete the guide to [Onboard as a Security Command Center partner](https://docs.cloud.google.com/security-command-center/docs/how-to-partner-onboard.md.txt).
3. On the security service provider page in the Cloud Marketplace,
   follow any provider setup instructions in the **Overview**.

When configured correctly, the security service you added is available in
Security Command Center.

After you set up a new security service, you need to enable it in the
Google Cloud console.

### Enable the security service

Third-party security services use service accounts that might be outside your
organization.

To enable a third-party service, follow these steps:

1. In the Google Cloud console, go to the Security Command Center page.


   [Go to Security Command Center](https://console.cloud.google.com/security/command-center/config/services)

   <br />

2. Select your organization or project.

3. Click **Settings**.

4. Click the **Integrated services** tab.

5. Next to the integrated source that you want to enable, click the **Status**
   list and select **Enable**.

Findings from the services that you enable are displayed on the **Findings**
page in the Security Command Center dashboard.

### Change the service account of a security service

You can change the service account used for a third-party security service, for
example to address service account leakage or rotation. To change the service
account for a security service, you need to update it in the Google Cloud
console. Afterward, follow the service provider's instructions to update the
service account for their service.

1. In the Google Cloud console, go to the Security Command Center page.


   [Go to Security Command Center](https://console.cloud.google.com/security/command-center/config/services)

   <br />

2. Select your organization or project.

3. Click **Settings**.

4. Click the **Integrated services** tab.

5. In the drop-down list next to the integrated service:

   1. Select **Disabled** to temporarily disable the integrated service.
   2. Select **Manage service account**.
6. On the **Edit <var translate="no">provider</var>** panel that appears, enter the new
   service account, then click **Submit**.

7. In the drop-down list next to the integrated service, select **Enabled** to
   enable the security service.

When configured correctly, the service account for the integrated service is
updated in Security Command Center. Follow the service provider's instructions to
update the service account information for their service.

## What's next

- Learn about Google Cloud security services and how to [view the vulnerabilities and threats](https://docs.cloud.google.com/security-command-center/docs/how-to-view-vulnerabilities-threats) they surface.
- Learn how to [optimize Security Command Center](https://docs.cloud.google.com/security-command-center/docs/optimize-security-command-center.md.txt).
- [Export logs to Cloud Logging](https://docs.cloud.google.com/security-command-center/docs/export-cloud-logging.md.txt).
- Configure [attack exposure scores](https://docs.cloud.google.com/security-command-center/docs/attack-exposure-learn.md.txt) to assess risk.