[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF4FWW9A55D1CNHERAFSEW":3,"skill-same:01M6AF4FWW9A55D1CNHERAFSEW":113},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6AF4FWW9A55D1CNHERAFSEW","implementing-envelope-encryption-with-aws-kms",null,"Implements envelope encryption with AWS KMS, encrypting data locally with a data encryption key (DEK) and protecting that DEK with a KMS-managed key (KEK), covering the encrypt\u002Fdecrypt flow, KMS key types, and security validation criteria. Use when designing key management for encrypting large or numerous data objects on AWS, or when reducing direct KMS API call volume.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36146,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"encryption","aws","KMS","implementing envelope encryption with aws kms","security","cybersecurity","pr","validation","data encryption","encrypt","flow","data","cryptography","key-management","t1078","envelope-encryption","2026-11-10 10:12:30",false,"---\nname: implementing-envelope-encryption-with-aws-kms\ndescription: Implements envelope encryption with AWS KMS, encrypting data locally with a data encryption key (DEK) and protecting that DEK with a KMS-managed key (KEK), covering the encrypt\u002Fdecrypt flow, KMS key types, and security validation criteria. Use when designing key management for encrypting large or numerous data objects on AWS, or when reducing direct KMS API call volume.\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- encryption\n- aws\n- kms\n- envelope-encryption\n- key-management\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1600\n- T1573\n- T1553\n- T1078.004\n- T1530\n---\n# Implementing Envelope Encryption with AWS KMS\n\n## Overview\n\nEnvelope encryption is a strategy where data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed by AWS KMS. This approach allows encrypting large volumes of data locally while keeping the master key secure in a hardware security module (HSM) managed by AWS. This skill covers implementing envelope encryption using AWS KMS GenerateDataKey API.\n\n\n## When to Use\n\n- When deploying or configuring implementing envelope encryption with aws kms capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Understand the envelope encryption pattern and its advantages\n- Generate data encryption keys using AWS KMS GenerateDataKey\n- Encrypt\u002Fdecrypt data locally using DEKs\n- Store encrypted DEK alongside ciphertext\n- Implement key caching to reduce KMS API calls\n- Handle key rotation with automatic re-encryption\n- Implement multi-region encryption for disaster recovery\n\n## Key Concepts\n\n### Envelope Encryption Flow\n\n1. Call `kms:GenerateDataKey` to get plaintext DEK + encrypted DEK\n2. Use plaintext DEK to encrypt data locally (AES-256-GCM)\n3. Store encrypted DEK alongside ciphertext\n4. Discard plaintext DEK from memory\n5. For decryption: call `kms:Decrypt` on encrypted DEK, then decrypt data\n\n### Advantages Over Direct KMS Encryption\n\n| Aspect | Direct KMS | Envelope Encryption |\n|--------|-----------|-------------------|\n| Max data size | 4 KB | Unlimited |\n| Latency | Network round-trip per operation | Local encryption |\n| Cost | $0.03\u002F10,000 requests | Fewer KMS requests |\n| Offline | Not possible | Yes (with cached DEKs) |\n\n### KMS Key Types\n\n- **AWS Managed**: AWS creates and manages (`aws\u002Fs3`, `aws\u002Febs`)\n- **Customer Managed**: You create and manage policies\n- **Custom Key Store**: Backed by CloudHSM cluster\n\n## Security Considerations\n\n- Never store plaintext DEK; only keep encrypted DEK\n- Use key policies to restrict who can call GenerateDataKey and Decrypt\n- Enable AWS CloudTrail logging for all KMS API calls\n- Implement key rotation (automatic annual rotation for CMKs)\n- Use encryption context for authenticated encryption metadata\n- Handle KMS throttling with exponential backoff\n\n## Validation Criteria\n\n- [ ] GenerateDataKey returns plaintext and encrypted DEK\n- [ ] Data encrypts correctly with plaintext DEK using AES-256-GCM\n- [ ] Encrypted DEK can be decrypted via KMS Decrypt API\n- [ ] Decrypted DEK recovers the original data\n- [ ] Plaintext DEK is wiped from memory after use\n- [ ] Encryption context is validated during decryption\n- [ ] Key rotation re-encrypts DEKs with new master key\n","# Implementing Envelope Encryption with AWS KMS\n\n## Overview\n\nEnvelope encryption is a strategy where data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed by AWS KMS. This approach allows encrypting large volumes of data locally while keeping the master key secure in a hardware security module (HSM) managed by AWS. This skill covers implementing envelope encryption using AWS KMS GenerateDataKey API.\n\n\n## When to Use\n\n- When deploying or configuring implementing envelope encryption with aws kms capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Understand the envelope encryption pattern and its advantages\n- Generate data encryption keys using AWS KMS GenerateDataKey\n- Encrypt\u002Fdecrypt data locally using DEKs\n- Store encrypted DEK alongside ciphertext\n- Implement key caching to reduce KMS API calls\n- Handle key rotation with automatic re-encryption\n- Implement multi-region encryption for disaster recovery\n\n## Key Concepts\n\n### Envelope Encryption Flow\n\n1. Call `kms:GenerateDataKey` to get plaintext DEK + encrypted DEK\n2. Use plaintext DEK to encrypt data locally (AES-256-GCM)\n3. Store encrypted DEK alongside ciphertext\n4. Discard plaintext DEK from memory\n5. For decryption: call `kms:Decrypt` on encrypted DEK, then decrypt data\n\n### Advantages Over Direct KMS Encryption\n\n| Aspect | Direct KMS | Envelope Encryption |\n|--------|-----------|-------------------|\n| Max data size | 4 KB | Unlimited |\n| Latency | Network round-trip per operation | Local encryption |\n| Cost | $0.03\u002F10,000 requests | Fewer KMS requests |\n| Offline | Not possible | Yes (with cached DEKs) |\n\n### KMS Key Types\n\n- **AWS Managed**: AWS creates and manages (`aws\u002Fs3`, `aws\u002Febs`)\n- **Customer Managed**: You create and manage policies\n- **Custom Key Store**: Backed by CloudHSM cluster\n\n## Security Considerations\n\n- Never store plaintext DEK; only keep encrypted DEK\n- Use key policies to restrict who can call GenerateDataKey and Decrypt\n- Enable AWS CloudTrail logging for all KMS API calls\n- Implement key rotation (automatic annual rotation for CMKs)\n- Use encryption context for authenticated encryption metadata\n- Handle KMS throttling with exponential backoff\n\n## Validation Criteria\n\n- [ ] GenerateDataKey returns plaintext and encrypted DEK\n- [ ] Data encrypts correctly with plaintext DEK using AES-256-GCM\n- [ ] Encrypted DEK can be decrypted via KMS Decrypt API\n- [ ] Decrypted DEK recovers the original data\n- [ ] Plaintext DEK is wiped from memory after use\n- [ ] Encryption context is validated during decryption\n- [ ] Key rotation re-encrypts DEKs with new master key\n",{"name":5,"tags":40,"author":42,"domain":24,"license":15,"version":43,"nist_csf":44,"subdomain":31,"description":7,"mitre_attack":48},[31,19,20,41,34,32],"kms","mahipal","1.0",[45,46,47],"PR.DS-01","PR.DS-02","PR.DS-10",[49,50,51,52,53],"T1600","T1573","T1553","T1078.004","T1530","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fimplementing-envelope-encryption-with-aws-kms",4425,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-envelope-encryption-with-aws-kms",{"tool":70,"command":71},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-envelope-encryption-with-aws-kms",{"tool":73,"command":74},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill implementing-envelope-encryption-with-aws-kms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FSKILL.md",true,[78,84,89,95,99,103,109],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Ftemplate.md","ASSET","资产文件",2258,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fassets\u002Ftemplate.md",{"path":85,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FLICENSE",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fapi-reference.md","REFERENCE","参考文档",1916,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fapi-reference.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fstandards.md",1943,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fstandards.md",{"path":100,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fworkflows.md",1515,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fworkflows.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fagent.py","SCRIPT","脚本",6078,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fscripts\u002Fagent.py",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fprocess.py",10876,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fscripts\u002Fprocess.py",[114,143,167,193,218,245],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":35},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[126,127,128,129,23,24,130,131,25,132,133,134,135,136,137,138,139,140,141,142],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":35},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[149],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[151,139,152,153,23,154,24,25,155,156,157,158,159,160,161,162,163,164,165,166],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":177,"publishedAt":35},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[161,178,179,180,181,24,182,26,155,183,184,185,186,187,188,33,189,190,191,192],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":200,"publishedAt":35},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[199],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[201,202,203,24,204,205,206,207,208,209,210,30,211,212,213,214,158,215,216,217],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":225,"publishedAt":35},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[224],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[226,227,228,24,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":246,"name":247,"nameZh":6,"description":248,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":249,"categories":250,"keywords":252,"publishedAt":35},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[251],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},[23,253,24,254,255,256,257,258,259,260,261,33,262,189,263,264,265,266,267,268],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]