[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7344ZMHE75TDP5098KD2YCE":3,"skill-same:01M7344ZMHE75TDP5098KD2YCE":105},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7344ZMHE75TDP5098KD2YCE","implementing-envelope-encryption-with-aws-kms",null,"Envelope 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","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-envelope-encryption-with-aws-kms\ndescription: Envelope encryption is a strategy where data is encrypted with a data\n  encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed\n  by AWS KMS. This approach allows encrypting\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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\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":25,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":26,"description":7,"mitre_attack":40,"source_commit":46},[26,27,28,29,30,31],"cryptography","encryption","aws","kms","envelope-encryption","key-management","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[37,38,39],"PR.DS-01","PR.DS-02","PR.DS-10",[41,42,43,44,45],"T1600","T1573","T1553","T1078.004","T1530","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-envelope-encryption-with-aws-kms",{"tool":63,"command":64},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-envelope-encryption-with-aws-kms",{"tool":66,"command":67},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-envelope-encryption-with-aws-kms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002FSKILL.md",true,[71,77,81,87,91,95,101],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"assets\u002Ftemplate.md","ASSET","资产文件",2258,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fassets\u002Ftemplate.md",{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",1916,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fstandards.md",1943,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fstandards.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fworkflows.md",1515,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Freferences\u002Fworkflows.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fagent.py","SCRIPT","脚本",6078,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fscripts\u002Fagent.py",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fprocess.py",10876,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-envelope-encryption-with-aws-kms\u002Fscripts\u002Fprocess.py",[106,114,121,129,137,145],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"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":120,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]