Share the workspace Project ID with the SRE team. Assign the SRE team the
Monitoring Viewer IAM role in the workspace project.

Share the workspace Project ID with the SRE team. Assign the SRE team the
Dashboard Viewer IAM role in the workspace project.

Click "Share chart by URL" and provide the URL to the SRE team. Assign the SRE team
the Monitoring Viewer IAM role in the workspace project.

Click "Share chart by URL" and provide the URL to the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Set up Container Analysis to scan and report Common Vulnerabilities and Exposures.

Configure the containers in the build pipeline to always update themselves before
release.

Reconfigure the existing operating system vulnerability software to exist inside the container.

Implement static code analysis tooling against the Docker files used to create the containers.

Link Stackdriver Logging as a source in Google Data Studio. Filler (he logs on the cache misses.

Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.

Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.

Configure BigOuery as a sink for Stackdriver Logging. Create a scheduled query to filter
the cache miss logs and write them to a separate table

Before merging new code, require 2 different peers to review the code changes.

Adopt the blue/green deployment strategy when releasing new code via a CD server.

Integrate a code linting tool to validate coding standards before any code is accepted
into the repository.

Require developers to run automated integration tests on their local development
environments before release.

Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.

Use a partitioned rolling update.

Use Node taints with NoExecute.

Use a replica set in the deployment specification.

Use a stateful set with parallel pod management policy.

Store the Terraform code in a version-control system. Establish procedures for pushing new versions and merging with the master.

Store the Terraform code in a network shared folder with child folders for each version release. Ensure that everyone works on different files.

Store the Terraform code in a Cloud Storage bucket using object versioning. Give
access to the bucket to every team member so they can download the files.

Store the Terraform code in a shared Google Drive folder so it syncs automatically to every team member’s computer. Organize files with a naming convention that identifies each new version.

Call individual stakeholders lo explain what happened.

Develop a post-mortem to be distributed to stakeholders.

Send the Incident State Document to all the stakeholders.

Require the engineer responsible to write an apology email to all stakeholders.

Prompt developers for secrets at build time. Instruct developers to not store secrets at rest.

Store secrets in a separate configuration file on Git. Provide select developers with access to the configuration file.

Store secrets in Cloud Storage encrypted with a key from Cloud KMS. Provide the CI/CD pipeline with access to Cloud KMS via IAM.

Encrypt the secrets and store them in the source code repository. Store a decryption key in a separate repository and grant your pipeline access to it