auditing-kms-key-policy-and-envelope-encryption SKILL.md skillA
auditing-kms-key-policy-and-envelope-encryption from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/auditing-kms-key-policy-and-envelope-encryption@git:20260827.b5f41a4Pins git:20260827.b5f41a4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/auditing-kms-key-policy-and-envelope-encryption/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260827.b5f41a4, committed Aug 27, 2026
- Size
- 9,023 bytes
- Repository stars
- 26
- License
- MIT
Audit key-management policies and envelope-encryption design for a decrypt path broader than intended: a key policy or grant that admits a principal who should never decrypt, a wildcard key resource in an identity policy that covers unrelated keys, an encryption context that is not enforced so a data key decrypts outside its intended scope, and a cross-account key grant that widens the decrypt set. Covers cloud key-management services, key policies and grants, and envelope encryption where a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Auditing KMS key policy and envelope encryption: who can actually decrypt Envelope encryption protects data with a data key and protects the data key with a managed master key, so the real access boundary is the master key's policy plus whatever encryption context constrains the data key. That indirection hides over-broad access. A key policy or grant can admit a principal who should never decrypt this data; a wildcard key resource in an identity policy can cover keys the author never considered; and an encryption context, meant to bind a data key to a specific scope, does nothing if the decrypt path does not enforce it. Cross-account grants widen the set further. The payload can be perfectly encrypted while the decrypt set quietly includes the wrong principals. You audit these by computing who can decrypt and comparing that to who should read the data. ## When to use - Data is protected by a managed key through envelope encryption, with a data key under a master key. - Decrypt access is governed by a key policy, key grants, and identity policies that may use wildcards. - An encryption context is used to scope a data key, and you need to confirm it is enforced on decrypt. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-kms-key-policy-and-envelope-encryption@sha256:7a4347b7f8473ac4The line at the top of this page pins the label git:20260827.b5f41a4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vsauqztockbdtonn)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 27, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9023 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vsauqztockbdtonn GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-kms-key-policy-and-envelope-encryption GET https://markdownregistry.com/api/v1/blob/7a4347b7f8473ac4ba4136bb1155994a7afcb16675dd70dd86a9354ffe8d2f4a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.