
Auditing Gcp Iam Permissions
Audit Google Cloud IAM bindings and over-privileged roles before production or after org changes.
Overview
Auditing GCP IAM permissions is an agent skill for the Ship phase that guides systematic review of Google Cloud IAM roles and bindings to reduce over-privileged access.
Install
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill auditing-gcp-iam-permissionsWhat is this skill?
- Maps GCP IAM roles, bindings, and service accounts to least-privilege findings
- Supports systematic review of project, folder, and organization-level policies
- Aligns with cloud identity audit workflows for indie SaaS on Google Cloud
- Produces actionable gaps for overly broad admin or custom role assignments
Adoption & trust: 1 installs on skills.sh; 14.9k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are on GCP but cannot confidently say who can admin your project or whether inherited org roles violate least privilege.
Who is it for?
Indie SaaS or side projects on GCP that need a first-pass IAM review before production or SOC-style questions.
Skip if: Teams without Google Cloud assets or builders who only need generic OWASP app scanning with no IAM surface.
When should I use this skill?
User asks to review, audit, or harden Google Cloud IAM roles, bindings, or service account permissions.
What do I get? / Deliverables
You get a structured IAM audit narrative with prioritized permission risks to remediate before launch or during access reviews.
- IAM finding list with severity-oriented permission gaps
- Remediation-oriented notes for role binding changes
Recommended Skills
Journey fit
How it compares
Use for GCP identity posture review, not as a substitute for runtime vulnerability scanning or MCP market-data tools.
Common Questions / FAQ
Who is auditing-gcp-iam-permissions for?
Solo and indie builders shipping on Google Cloud who must validate IAM without a full-time cloud security team.
When should I use auditing-gcp-iam-permissions?
During ship security hardening, before granting production access, after org restructuring, or when preparing compliance evidence about access control.
Is auditing-gcp-iam-permissions safe to install?
Review the Security Audits panel on this Prism page for published audit results; treat any cloud-related skill as requiring careful scoping of credentials and agent permissions.
SKILL.md
READMESKILL.md - Auditing Gcp Iam Permissions
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of