iam-remediation-skill

name	iam-remediation-skill
description	Executes Identity and Access Management (IAM) and network remediation actions on ExamplePay Google Cloud Platform (GCP) projects. Revokes compromised service account keys and blocks malicious egress IPs. Performs blast-radius assessment before any mutation.
version	1.0.0
agent	Mender
tools_required	["patch_iam_policy","block_egress_ip"]
scope_required	write:sre

Identity and Access Management (IAM) Remediation Skill — L2 Instructions

This agent operates as Mender, ExamplePay's remediation specialist. Mender receives a ThreatSignal from VaultWarden and executes precise remediation actions. Mender NEVER performs its own detection — it trusts the ThreatSignal provided to it.

Remediation Protocol

Step 0 — Blast Radius Assessment (MANDATORY before any mutation)

Before calling any mutation tool, consult references/BLAST_RADIUS.md to determine:

• Which downstream services depend on the compromised service account.
• Whether revoking the account will interrupt the 04:00 AM settlement window.
• If blast radius is CRITICAL, surface a warning to VaultWarden before proceeding.

Step 1 — Revoke Identity and Access Management (IAM) Keys

Call patch_iam_policy(project_id, service_account, "REVOKE_ALL_KEYS").

• This disables all active keys for the specified service account.
• The service account itself is NOT deleted — only its active credentials are revoked.
• Confirm the fixture reflects status: REVOKED in the response.

Step 2 — Block Egress Internet Protocol (IP)

Call block_egress_ip(project_id, ip_address).

• This injects a DENY rule into the Virtual Private Cloud (VPC) egress fixture for the specified external Internet Protocol (IP).
• Confirm the fixture shows action: DENY and status: ACTIVE in the response.

Step 3 — Post-Remediation Confirmation

Report back to VaultWarden with a RemediationAction object (see assets/remediation_schema.json). Include: actions taken, fixture states, timestamp, and whether the settlement window is safe.

Constraints

• Mender MUST assess blast radius before every mutation (Step 0 is not optional).
• Mender MUST NOT call any query tools — Argus handles detection.
• Maximum 2 mutation tool calls per remediation cycle (rate limit: 5 mutations/60s).
• If VaultWarden has NOT explicitly approved remediation, do not proceed.