# GCP - Security Post Exploitation

{{#include ../../../banners/hacktricks-training.md}}

## Security

For more information check:

{{#ref}}
../gcp-services/gcp-security-enum.md
{{#endref}}

### `securitycenter.muteconfigs.create`

Prevent generation of findings that could detect an attacker by creating a `muteconfig`:

<details>

<summary>Create Muteconfig</summary>

```bash
# Create Muteconfig
gcloud scc muteconfigs create my-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""
```

</details>

### `securitycenter.muteconfigs.update`

Prevent generation of findings that could detect an attacker by updating a `muteconfig`:

<details>

<summary>Update Muteconfig</summary>

```bash
# Update Muteconfig
gcloud scc muteconfigs update my-test-mute-config --organization=123 --description="This is a test mute config" --filter="category=\"XSS_SCRIPTING\""
```

</details>

### `securitycenter.findings.bulkMuteUpdate`

Mute findings based on a filer:

<details>

<summary>Bulk mute based on filter</summary>

```bash
# Mute based on a filter
gcloud scc findings bulk-mute --organization=929851756715 --filter="category=\"XSS_SCRIPTING\""
```

</details>

A muted finding won't appear in the SCC dashboard and reports.

### `securitycenter.findings.setMute`

Mute findings based on source, findings...

<details>

<summary>Set finding as muted</summary>

```bash
gcloud scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED
```

</details>

### `securitycenter.findings.update`

Update a finding to indicate erroneous information:

<details>

<summary>Update finding state</summary>

```bash
gcloud scc findings update `myFinding` --organization=123456 --source=5678 --state=INACTIVE
```

</details>

{{#include ../../../banners/hacktricks-training.md}}



