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

> [!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.

## Get a Google support package

Google Cloud offers different support packages to meet different needs, such as
24/7 coverage, phone support, and access to a technical support manager. For
more information, see [Cloud Customer Care](https://docs.cloud.google.com/support).

> [!NOTE]
> **Note:** Cloud Support staff can't see your Security Command Center pages in the [Google Cloud console](https://docs.cloud.google.com/security-command-center/docs/how-to-use-security-command-center#console_access). Consequently, they can't help debug or remediate specific threats, vulnerabilities, or compliance findings. They also can't view your assets.

Security Command Center detects and reports vulnerabilities through a web-based interface
and API. The findings in Security Command Center are only a first step in identifying and
remediating vulnerabilities and threats. Every organization has unique risks.
It's up to you to understand and evaluate the attack surface of your
organization, properly configure Security Command Center to protect your resources,
and determine whether fixes should be applied to vulnerabilities and threats
detected by Security Command Center.

Security Command Center's user interface provides suggestions for remediating common
vulnerabilities. Security Command Center product documentation also provides guidance
on remediating common findings for
[Security Health Analytics](https://docs.cloud.google.com/security-command-center/docs/how-to-remediate-security-health-analytics-findings)
and
[Web Security Scanner](https://docs.cloud.google.com/security-command-center/docs/how-to-remediate-web-security-scanner-findings).

## Discuss Security Command Center

You can visit the Google Cloud
[Slack community](https://googlecloud-community.slack.com/) to discuss
Security Command Center and other Google Cloud products. If you haven't
already joined,
[use this form to sign up](https://join.slack.com/t/googlecloud-community/shared_invite/zt-3icuwfdvq-eq_58LqmOoCNc16mpZcaNA).


## File feature requests and bug reports

If you want to request a new feature for Security Command Center, or if you
encounter a reproducible bug, you can report it through the
[issue tracker](https://docs.cloud.google.com/support/docs/issue-trackers). You can
[review the open issues](https://issuetracker.google.com/savedsearches/6123493)
to see if your bug or request has already been reported, and
[star](https://developers.google.com/issue-tracker/guides/subscribe#subscribing_by_starring_an_issue)
an existing thread to subscribe to updates. If there are no existing threads, you can
[request a new feature](https://issuetracker.google.com/issues/new?component=709980&template=1322893)
or [report a new bug](https://issuetracker.google.com/issues/new?component=709980&template=1322867).

## Event Threat Detection

Visit the Google Cloud
[Slack community](https://googlecloud-community.slack.com/) to discuss
Event Threat Detection and other Google Cloud products. If you haven't
already joined,
[use this form to sign up](https://join.slack.com/t/googlecloud-community/shared_invite/zt-3icuwfdvq-eq_58LqmOoCNc16mpZcaNA).

## Anomaly Detection

Anomaly Detection identifies security anomalies for your projects and Virtual
Machine (VM) instances, including compromised credentials and abuse of
resources. We are unable to provide full details on the methods or logic used to
detect resource abuses because they are proprietary.

## Web Security Scanner

To file bugs or a feature request, use the [Google Issue Tracker](https://issuetracker.google.com/issues/new?component=187215) for the
Web Security Scanner component.

We value your feedback about Web Security Scanner. Example feedback topics
are:

- **Noise:** Finding false positives? Let us know. We have a goal for zero false positives.
- **Coverage:** Is our crawling system having problems navigating your site?
- **Effectiveness:** Did we miss a bug you think we should have caught?
- **Authentication:** Are you having problems with our custom login support?
- **Usability:** We want an easy to use scanner, how can we make it more intuitive?
- **General:** Do you love it? Do you hate it? Was it worth your time to set up and use?

To send feedback about a specific scan:

1. Sign in to the test account that you used to create the scan.
2. Go to the [Web Security Scanner](https://console.cloud.google.com/projectselector2/security/web-scanner/) page in the Google Cloud console.  
   [Go to the Web Security Scanner page](https://console.cloud.google.com/projectselector2/security/web-scanner/)
3. Click **Select**, and then select the project that contains the scan that you want to edit.
4. Under **Scan configs**, click the name of the scan that you want to edit.
5. On the scan details page that appears, click **Send feedback**.
6. Click **Send feedback** and enter the feedback you want to share.
7. When you're finished entering feedback, click **Send**.