5stars217

Keybase proof

I hereby claim:

• I am 5stars217 on github.
• I am threlfall (https://keybase.io/threlfall) on keybase.
• I have a public key ASBno_Or2efff3CYxFE8IKmGmnNzZ1ETrW21mMfQMB2bIAo

To claim this, I am signing this object:

5stars217

Purpose

*Most pentesting and gcp privilege escalation stuff out there for GCP assumes what I'm finding to be an absurd level of access handed to you.(i.e Human 2fa protected accounts, organization-wide read only IAM perms, etc that is not suitable for use in black box testing of mature environments.
There's a lot of data you need to use the gcp api only available behind mandatory 2fa protected human accounts that service accounts and low tier project accounts simply do not have access to enumerating if you find yourself having popped an application or shelled a instance somehow and have console-only access.

Intent of this is to break down various categories of escalation that will be available to service accounts, as well as point out various showstoppers.

• 0.1. References
• 0.2. Other cheatsheets
• 0.3. Manage multiple gcloud config configurations
• [0.3.1. Switch gcloud context with gcloud config](#031