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

This document offers informal guidance on how you can respond to findings of suspicious
activities in your Cloud Run resources. The recommended steps might not be appropriate for all
findings and might impact your operations. Before you take any action, you should investigate the
findings; assess the information that you gather; and decide how to respond.

> [!IMPORTANT]
> **Note:** The techniques that Security Command Center provides aren't guaranteed to be effective against any previous, current, or future threats that you face. For information about why Security Command Center does not provide official remediation guidance for threats, see [Approach to threat finding remediation](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats.md.txt#remediating_threats).

## Before you begin

1. [Review the
   finding](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings). Note the affected container and the detected binaries, processes, or libraries.
2. To learn more about the finding that you're investigating, search for the finding in the [Threat findings
   index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index).

## General recommendations

- Contact the owner of the affected resource.
- [View the logs](https://docs.cloud.google.com/run/docs/logging.md.txt#viewing-logs) for the potentially compromised Cloud Run service, job, or worker pool.
- For forensic analysis, collect and back up the logs from the affected Cloud Run resource.
- For further investigation, consider using incident response services like [Mandiant](https://docs.cloud.google.com/security/consulting/mandiant-incident-response-services).
- Consider deleting any of the following affected Cloud Run resources:

  - Delete the affected [service](https://docs.cloud.google.com/run/docs/managing/services.md.txt#delete).
  - [Roll back to a previous service revision](https://docs.cloud.google.com/run/docs/rollouts-rollbacks-traffic-migration.md.txt#rollback), or deploy a new, more secure revision, and then [delete the affected revision](https://docs.cloud.google.com/run/docs/managing/revisions.md.txt#delete).
  - Delete the affected [job](https://docs.cloud.google.com/run/docs/managing/jobs.md.txt#delete).
  - Delete the affected [worker pool](https://docs.cloud.google.com/run/docs/managing/workerpools.md.txt#delete).
  - [Roll back to a previous worker pool revision](https://docs.cloud.google.com/run/docs/managing/workerpool-instance-splits-rollbacks.md.txt), or deploy a new, more secure revision, and then [delete the affected revision](https://docs.cloud.google.com/run/docs/managing/workerpool-revisions.md.txt#delete).

## Malicious script or Python code executed

If the script or Python code was making intended changes to the container,
[deploy a revision](https://docs.cloud.google.com/run/docs/deploying.md.txt#revision) to the service that has all
the intended changes. Don't rely on a script to make changes after the container
is deployed.

## What's next

- Learn [how to work with threat
  findings in Security Command Center](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats).
- Refer to the [Threat findings index](https://docs.cloud.google.com/security-command-center/docs/threat-findings-index.md.txt).
- Learn how to [review a
  finding](https://docs.cloud.google.com/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.
- Learn about the [services that
  generate threat findings](https://docs.cloud.google.com/security-command-center/docs/concepts-security-sources#threats).