iam-audit

Audit, design, and migrate IAM across cloud and identity provider environments.

345|47|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/briiirussell/cybersecurity-skills --skill iam-audit-briiirussell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iam-audit
Source: https://github.com/briiirussell/cybersecurity-skills/tree/main/skills/iam-audit
Command: npx skills add https://github.com/briiirussell/cybersecurity-skills --skill iam-audit-briiirussell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IAM gaps cause privilege creep, insecure federation, and broken least-privilege controls across cloud providers and identity systems, leading to audit failures and real compromise risk.

Core Features & Use Cases

  • End-to-end IAM review across AWS, GCP, and Azure plus common IdPs, identifying insecure patterns like overbroad roles, stale access, and risky trust relationships.
  • IAM design for greenfield that codifies least-privilege, group-based access, workload identity (no long-lived keys), and logged authorization decisions.
  • IAM migration playbooks to consolidate providers and move to SSO/JIT access using phased cutovers with rollback guardrails.

Quick Start

Use the iam-audit skill to generate an IAM Audit Report for your AWS and Entra ID setup with a recommended prioritized 90-day remediation roadmap.

Frequently Asked Questions about iam-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit IAM for privilege creep and insecure federation across cloud providers?

IAM design for greenfield environments codifies least-privilege by implementing group-based access, workload identity without long-lived keys, and logged authorization decisions using RBAC, ABAC/ReBAC, and JIT access patterns.

Does the IAM audit process support cross-provider consolidation and SSO migration?

Cross-provider consolidation and SSO migration are supported through IAM migration playbooks that execute phased cutovers to move identity providers while maintaining rollback guardrails for safe transitions.

What is the safest way to enforce least-privilege outcomes during an IAM posture review?

Safe IAM posture reviews use read-only audit mode boundary handling to identify insecure patterns like overbroad roles and risky trust relationships, producing evidence-based findings and a remediation roadmap without modifying live environments.

Can I use this approach to design greenfield authorization models for workload identity?

Designing greenfield authorization models codifies least-privilege by implementing group-based access, workload identity without long-lived keys, and logged authorization decisions using RBAC, ABAC/ReBAC, and JIT access patterns.