# GCP - Security Post Exploitation {% hint style="success" %} Learn & practice AWS Hacking:[**HackTricks Training AWS Red Team Expert (ARTE)**](https://training.hacktricks.xyz/courses/arte)\ Learn & practice GCP Hacking: [**HackTricks Training GCP Red Team Expert (GRTE)**](https://training.hacktricks.xyz/courses/grte)
Support HackTricks * Check the [**subscription plans**](https://github.com/sponsors/carlospolop)! * **Join the** 💬 [**Discord group**](https://discord.gg/hRep4RUj7f) or the [**telegram group**](https://t.me/peass) or **follow** us on **Twitter** 🐦 [**@hacktricks\_live**](https://twitter.com/hacktricks_live)**.** * **Share hacking tricks by submitting PRs to the** [**HackTricks**](https://github.com/carlospolop/hacktricks) and [**HackTricks Cloud**](https://github.com/carlospolop/hacktricks-cloud) github repos.
{% endhint %} ## Security For more information check: {% content-ref url="../gcp-services/gcp-security-enum.md" %} [gcp-security-enum.md](../gcp-services/gcp-security-enum.md) {% endcontent-ref %} ### `securitycenter.muteconfigs.create` Prevent generation of findings that could detect an attacker by creating a `muteconfig`: {% code overflow="wrap" %} ```bash # Create Muteconfig gcloud scc muteconfigs create my-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\"" ``` {% endcode %} ### `securitycenter.muteconfigs.update` Prevent generation of findings that could detect an attacker by updating a `muteconfig`: {% code overflow="wrap" %} ```bash # Update Muteconfig gcloud scc muteconfigs update my-test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\"" ``` {% endcode %} ### `securitycenter.findings.bulkMuteUpdate` Mute findings based on a filer: {% code overflow="wrap" %} ```bash # Mute based on a filter gcloud scc findings bulk-mute --organization=929851756715 --filter="category=\"XSS_SCRIPTING\"" ``` {% endcode %} A muted finding won't appear in the SCC dashboard and reports. ### `securitycenter.findings.setMute` Mute findings based on source, findings... {% code overflow="wrap" %} ```bash gcloud scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED ``` {% endcode %} ### `securitycenter.findings.update` Update a finding to indicate erroneous information: {% code overflow="wrap" %} ```bash gcloud scc findings update `myFinding` --organization=123456 --source=5678 --state=INACTIVE ``` {% endcode %} {% hint style="success" %} Learn & practice AWS Hacking:[**HackTricks Training AWS Red Team Expert (ARTE)**](https://training.hacktricks.xyz/courses/arte)\ Learn & practice GCP Hacking: [**HackTricks Training GCP Red Team Expert (GRTE)**](https://training.hacktricks.xyz/courses/grte)
Support HackTricks * Check the [**subscription plans**](https://github.com/sponsors/carlospolop)! * **Join the** 💬 [**Discord group**](https://discord.gg/hRep4RUj7f) or the [**telegram group**](https://t.me/peass) or **follow** us on **Twitter** 🐦 [**@hacktricks\_live**](https://twitter.com/hacktricks_live)**.** * **Share hacking tricks by submitting PRs to the** [**HackTricks**](https://github.com/carlospolop/hacktricks) and [**HackTricks Cloud**](https://github.com/carlospolop/hacktricks-cloud) github repos.
{% endhint %}