Install any skill in seconds. Free to start, no credit card required.
Get Started Free →toddkasper/aws-security-specialty
AWS security engineering — threat detection (GuardDuty, Security Hub CSPM, Detective, Security Lake), incident response and containment, IAM policy evaluation and permission boundaries, infrastructure/network security (security groups, NACLs, WAF, Shield, PrivateLink), data protection and KMS encryption strategy, Secrets Manager, Macie, and multi-account governance (SCPs, Control Tower, Config, Firewall Manager).
Passed 17 of 23 test cases with the skill, and 14 of 23 without it.
and 1 more in the full report
3 fixed14 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
An alert came in indicating that IAM temporary credentials assigned to an EC2 application server were detected making API calls from an external IP address. Provide a structured incident response playbook to contain the compromise, isolate the host, preserve evidence for investigation, and audit the activity window. Format your output with an ordered step-by-step operational guide, specific mitigation actions, and verification steps to confirm access is completely blocked.
| Checked | Without skill | With skill |
|---|---|---|
| Directs attaching an unconditional explicit-deny inline policy to the compromised IAM role. | Missed | Passed |
| Directs replacing security groups with a forensic security group allowing SSM endpoint traffic on TCP port 443. | Missed | Passed |
| Directs taking EBS volume snapshots prior to host remediation or termination. | Passed | Passed |
The instructions your model reads when the skill loads.
Operational playbook for AWS security work. Each section states the rule to apply: decision criteria, concrete limits, anti-patterns, and verification steps. Verify against the live account — effective permissions result from combining multiple policy types, and a single missing allow or extra deny changes the outcome. Benchmarked against AWS Security – Specialty (SCS-C03, December 2025).
Load this skill when… designing or reviewing IAM policies, permission boundaries, SCPs, or RCPs; configuring threat detection (GuardDuty, Security Hub CSPM, Detective, Security Lake); implementing KMS encryption strategy or Secrets Manager rotation; auditing network defenses (WAF, Shield, PrivateLink, NACLs) or building IR/containment automation. Not this skill: pipeline/IaC delivery → see
aws-devops-engineer-professional; enterprise architecture trade-offs → seeaws-solutions-architect-professional.
Study resources, SCS-C02→SCS-C03 changes, and credential logistics: references/study-resources.md.
Verify steps — use your project's MCP/automation, the AWS CLI (
aws) or CloudShell, or the Console, in that order.
[volatile — verify live], GuardDuty finding type catalog (new finding families added quarterly) [volatile — verify live], IAM Access Analyzer supported resource types [volatile — verify live], RCP (Resource Control Policy) service coverage (partial list, expanding) [volatile — verify live], and any feature flagged in the blueprint: frontmatter as a recent addition.[volatile — verify live] (changes with AWS service updates) or [opinion — house style] (a defensible default, not the only valid choice).Every authorization decision passes through this stack in order. Explicit Deny at any layer is an immediate, unconditional halt.
[volatile — verify live].AssumeRole / GetFederationToken; caps the session below the role's full permissions.KMS special case: the key policy is the primary access control. Unless it explicitly delegates to IAM ("Principal": {"AWS": "arn:aws:iam::<account>:root"}), IAM policies for kms:Decrypt etc. have no effect. Always verify the key policy first when debugging KMS denials.
test cases passed, vs 14 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.