Istio Authorization Policy Review
Evaluate the combined access decision against an explicit intended access matrix.
Decision and boundary
Does the applicable policy set implement the intended access matrix?
Operate as static-review. Read supplied files only; never collect live evidence, probe, mutate, or inherit ambient credentials. Host-enforced tool permissions remain mandatory.
Required inputs
Require intended behavior/access, rendered resources, exact environment/version/mode scope, and an evidence ledger with capture times and visibility limits. Continue bounded analysis when fields are missing, but mark affected conclusions needs-review.
Workflow
- Obtain the intended source/destination/protocol/identity allow-deny matrix and enumerate relevant namespace/root policies; record incomplete visibility.
- Resolve targets, selectors, targetRefs, revision support and enforcement points; send unresolved ambient attachment to the ambient reviewer.
- Evaluate CUSTOM, DENY and ALLOW together; keep missing/empty rules distinct from an empty matching rule. Include other applicable ALLOW policies.
- Separate transport authentication, JWT validation, identity presence and authorization. Do not infer access requirements from validation resources alone.
- Check protocol-specific missing attributes, path normalization, trusted forwarded addresses and narrow exceptions against actual traffic shape.
- Produce access decisions with assumptions and negative tests; propose bounded remediations but never mutate or self-authorize a live guard.
Reference loading
Read evidence-boundary.md, applicability.md, and output-contract.md first. Load the following only for the active branch.
| Reference |
Load when |
| policy-set-semantics.md |
Evaluate actions, rule shapes, attachment and overlap. |
| authentication-and-identity.md |
Evaluate mTLS identities and JWT requirements. |
| protocol-and-normalization.md |
Review HTTP/TCP, host, path, header and forwarded-identity boundaries. |
| negative-tests.md |
Define access regression tests. |
| official-sources.md |
Verify a version-sensitive rule or source disagreement. |
| review-contract.json |
Produce or validate a portable structured review. |
Deliverable
Expected-versus-derived access matrix, policy-set reasoning, and paired authentication/authorization tests.
Separate observed evidence, derived conclusions, assumptions and unknowns. Include one counterexample for every consequential finding. Never describe unperformed tests as passing or a bounded review as production certification.
1---2name: istio-authorization-policy-review3description: Review Istio AuthorizationPolicy, PeerAuthentication and RequestAuthentication4 together against intended access. Use for default-deny design, overlapping CUSTOM/DENY/ALLOW5 policies, empty rules, JWT requirements, wildcard principals, L7-on-TCP risks, policy6 targetRefs, trust identity or authorization regressions. Review supplied evidence7 only; separate policy semantics from observed enforcement and do not apply changes.8allowed-tools: Read Grep Glob9metadata:10 source: https://skillmd.com/skills/vincentchuwaichow/istio-authorization-policy-review11 author: 'github: VincentChuWaiChow'12 version: 0.1.013 category: security14 lifecycle: beta15 execution_tier: static-review16---1718# Istio Authorization Policy Review19Evaluate the combined access decision against an explicit intended access matrix.20## Decision and boundary21Does the applicable policy set implement the intended access matrix?22Operate as static-review. Read supplied files only; never collect live evidence, probe, mutate, or inherit ambient credentials. Host-enforced tool permissions remain mandatory.23## Required inputs24Require intended behavior/access, rendered resources, exact environment/version/mode scope, and an evidence ledger with capture times and visibility limits. Continue bounded analysis when fields are missing, but mark affected conclusions `needs-review`.25## Workflow261. Obtain the intended source/destination/protocol/identity allow-deny matrix and enumerate relevant namespace/root policies; record incomplete visibility.272. Resolve targets, selectors, targetRefs, revision support and enforcement points; send unresolved ambient attachment to the ambient reviewer.283. Evaluate CUSTOM, DENY and ALLOW together; keep missing/empty rules distinct from an empty matching rule. Include other applicable ALLOW policies.294. Separate transport authentication, JWT validation, identity presence and authorization. Do not infer access requirements from validation resources alone.305. Check protocol-specific missing attributes, path normalization, trusted forwarded addresses and narrow exceptions against actual traffic shape.316. Produce access decisions with assumptions and negative tests; propose bounded remediations but never mutate or self-authorize a live guard.3233## Reference loading34Read [evidence-boundary.md](references/evidence-boundary.md), [applicability.md](references/applicability.md), and [output-contract.md](references/output-contract.md) first. Load the following only for the active branch.35| Reference | Load when |36| --- | --- |37| [policy-set-semantics.md](references/policy-set-semantics.md) | Evaluate actions, rule shapes, attachment and overlap. |38| [authentication-and-identity.md](references/authentication-and-identity.md) | Evaluate mTLS identities and JWT requirements. |39| [protocol-and-normalization.md](references/protocol-and-normalization.md) | Review HTTP/TCP, host, path, header and forwarded-identity boundaries. |40| [negative-tests.md](references/negative-tests.md) | Define access regression tests. |41| [official-sources.md](references/official-sources.md) | Verify a version-sensitive rule or source disagreement. |42| [review-contract.json](references/review-contract.json) | Produce or validate a portable structured review. |4344## Deliverable45Expected-versus-derived access matrix, policy-set reasoning, and paired authentication/authorization tests.46Separate observed evidence, derived conclusions, assumptions and unknowns. Include one counterexample for every consequential finding. Never describe unperformed tests as passing or a bounded review as production certification.