translate

src/pentesting-cloud/gcp-security/gcp-services/README.md

@@ -4,4 +4,3 @@
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-ai-platform-enum.md

@@ -24,4 +24,3 @@ gcloud ai-platform jobs describe <job>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-api-keys-enum.md

@@ -46,4 +46,3 @@ gcloud services api-keys list --show-deleted
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-app-engine-enum.md

@@ -119,4 +119,3 @@ gcloud app ssl-certificates describe <name>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-artifact-registry-enum.md

@@ -94,4 +94,3 @@ gcloud artifacts docker images list-vulnerabilities projects/<proj-name>/locatio
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-batch-enum.md

@@ -37,4 +37,3 @@ gcloud batch tasks describe projects/<proj-number>/locations/<location>/jobs/<jo
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-bigquery-enum.md

@@ -231,4 +231,3 @@ SELECT catalog_name, schema_name, NULL FROM <project-name>.INFORMATION_SCHEMA.SC
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-bigtable-enum.md

@@ -34,4 +34,3 @@ gcloud bigtable app-profiles describe --instance <INSTANCE> <app-prof>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-build-enum.md

@@ -173,4 +173,3 @@ done
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-functions-enum.md

@@ -110,4 +110,3 @@ In the following page, you can check how to **abuse cloud function permissions t
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-run-enum.md

@@ -113,4 +113,3 @@ In the following page, you can check how to **abuse cloud run permissions to esc
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-scheduler-enum.md

@@ -48,4 +48,3 @@ gcloud scheduler jobs describe --location us-central1 <scheduler-name>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-shell-enum.md

@@ -30,4 +30,3 @@ Note that Cloud Shell can be **easily disabled** for the organization.
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-cloud-sql-enum.md

@@ -91,4 +91,3 @@ gcloud sql backups describe <backup-name> --instance <intance-name>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-composer-enum.md

@@ -45,4 +45,3 @@ In the following page you can check how to **abuse composer permissions to escal
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-compute-instances-enum/README.md

@@ -233,4 +233,3 @@ Check the Compute Instances privilege escalation section.
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-compute-instances-enum/gcp-compute-instance.md

@@ -105,4 +105,3 @@ A Google-managed encryption key is used by default a but a Customer-managed encr
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-compute-instances-enum/gcp-vpc-and-networking.md

@@ -87,4 +87,3 @@ These are the needed permissions:
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-containers-gke-and-composer-enum.md

@@ -106,4 +106,3 @@ Even if the API **doesn't allow to modify resources**, it could be possible to f
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-dns-enum.md

@@ -27,4 +27,3 @@ gcloud dns policies list
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-filestore-enum.md

@@ -76,4 +76,3 @@ There aren't ways to escalate privileges in GCP directly abusing this service, b
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-firebase-enum.md

@@ -79,4 +79,3 @@ You may be able to access some interesting information
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-firestore-enum.md

@@ -19,4 +19,3 @@ gcloud firestore export gs://my-source-project-export/export-20190113_2109 --col
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-iam-and-org-policies-enum.md

@@ -228,4 +228,3 @@ In the following page you can check how to **abuse org policies permissions to e
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-kms-enum.md

@@ -84,4 +84,3 @@ gcloud kms decrypt --ciphertext-file=[INFILE] \
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-logging-enum.md

@@ -148,4 +148,3 @@ There aren't logs of **`testIamPermissions`**:
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-memorystore-enum.md

@@ -23,4 +23,3 @@ gcloud redis instances export gs://my-bucket/my-redis-instance.rdb my-redis-inst
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-monitoring-enum.md

@@ -59,4 +59,3 @@ gcloud alpha monitoring channels describe <channel>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-pub-sub.md

@@ -96,4 +96,3 @@ gcloud pubsub lite-operations describe <topic>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-secrets-manager-enum.md

@@ -55,4 +55,3 @@ An attacker could update the secret to **stop rotations** (so it won't be modifi
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-security-enum.md

@@ -94,4 +94,3 @@ gcp-secrets-manager-enum.md
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-source-repositories-enum.md

@@ -69,4 +69,3 @@ git add, commit, push...
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-spanner-enum.md

@@ -33,4 +33,3 @@ gcloud spanner instance-configs describe <name>
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-stackdriver-enum.md

@@ -35,4 +35,3 @@ gcloud logging buckets list
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-storage-enum.md

@@ -158,4 +158,3 @@ In the following page you can check how to **abuse storage permissions to escala
 
 
 
-

src/pentesting-cloud/gcp-security/gcp-services/gcp-workflows-enum.md

@@ -40,4 +40,3 @@ gcloud workflows executions describe projects/<proj-number>/locations/<location>
 
 
 
-