研究检索敏感数据github未标认证来源可访问许可证需确认审计通过

cryptography-as-a-service-pattern（密码学即服务模式）

Agent Skill

cryptography-as-a-service-pattern 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

188

周安装

GitHub Stars

下载量

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：cryptography-as-a-service-pattern（密码学即服务模式）
来源仓库：https://github.com/igbuend/grimbard
仓库路径：skills/cryptography-as-a-service-pattern
安装命令：
npx skills add https://github.com/igbuend/grimbard --skill cryptography-as-a-service-pattern
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/igbuend/grimbard --skill cryptography-as-a-service-pattern

简介

介绍密码学即服务（Cryptography as a Service）的安全架构模式及其适用场景。

强调将密钥管理委托给执行加解密操作的同一实体，以降低密钥泄露风险。
适用于需要减少密钥持有量、避免错误配置且能接受更高信任依赖的系统设计。
安装需通过 npx 添加指定仓库，建议评估服务可用性与第三方依赖带来的影响。
cryptography-as-a-service-pattern 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Cryptography as a Service Security Pattern

In this pattern, the management of cryptographic keys is delegated to the same entity that performs the cryptographic actions. Consequently, the system under design never possesses the used cryptographic keys.

Benefits and Trade-offs

Benefits:

Limits risk of leaking cryptographic keys
Reduces risk of incorrectly configuring and/or using a cipher
System only handles key identifiers, not key material

Trade-offs:

Requires greater trust in the entity providing cryptographic operations
Dependency on external service availability

Common Implementations

Type	Examples
Cloud-based KMS	Google Cloud KMS, Amazon KMS, Azure Key Vault
Mobile Platform	Android Keystore, iOS KeyChain
Hardware	Hardware Security Modules (HSM)

Core Components

Role	Type	Responsibility
System	Entity	Wants to perform cryptographic operations
Cryptography Service	Entity	Handles cryptographic operations, key storage, and key management

Note: The Cryptography Service inherits the Cryptographer role from the parent Cryptographic Key Management pattern.

Data Elements

keyConf: Configuration for key generation (e.g., symmetric/asymmetric, key length) - optional
keyId: Identifier returned by the service to reference the generated key
input: Plaintext input for cryptographic action
output: Result of cryptographic action (e.g., ciphertext, signature)
config: Configuration for the cryptographic operation (e.g., cipher mode) - optional
masterKey: Credential used to authenticate the System to the Cryptography Service

Actions

generate_key: Generate new cryptographic key according to configuration
crypto_action: Perform cryptographic operation using the identified key

Pattern Flow

Key Generation

System → [generate_key(keyConf)] → Cryptography Service
Cryptography Service → [keyId] → System

The System requests key generation with optional configuration. The Cryptography Service generates the key internally and returns only an identifier (not the key material) for future operations.

Cryptographic Action

System → [crypto_action(input, keyId, config)] → Cryptography Service
Cryptography Service → [output] → System

To use a previously generated key, the System provides the keyId received during generation. The key material never leaves the Cryptography Service.

Key Difference from Self-Managed Cryptography

Aspect	Cryptography as a Service	Self-Managed Cryptography
Key possession	System holds only key identifiers	System holds actual key material
Key storage	Managed by service	Managed by application
Key exposure risk	Lower (keys never exposed)	Higher (keys in application memory)
Trust requirement	Trust the service provider	Trust your own implementation

Security Considerations

The Cryptography Service as Uncontrolled Entity

The Cryptography Service should be considered an uncontrolled entity, requiring additional measures to secure interactions.

Cloud-based Services (Google Cloud KMS, Amazon KMS)

When using cloud-based cryptographic services:

All interactions travel via the public Internet
Confidentiality and integrity of exchanged messages must be ensured
Authentication is critical—verify you're interacting with the actual service, not an attacker spoofing it
Use TLS/HTTPS for all communications
Implement proper service authentication (API keys, certificates, IAM)

Mobile Platform Services (Android Keystore, iOS KeyChain)

When using platform-provided services:

Service is a local entity provided by the underlying platform
Communication channel is typically more controlled
Still verify platform-specific security guarantees
Consider device compromise scenarios

Communication Channel Security

As the Cryptography Service is an uncontrolled entity, at least part of the communication channel will also be uncontrolled.

Required protections:

Confidentiality of requests (especially for encryption/decryption operations)
Integrity of requests and responses
Authentication of the service endpoint

Master Key Handling

The master key is used as a credential to authenticate the System to the Cryptography Service.

Critical: The master key should be treated as a credential:

Store securely (environment variables, secrets manager)
Never hardcode in source code
Rotate periodically
Limit access to minimal required principals

Key Identifier (keyId) Protection

While keyId is not the key material itself:

Protect against unauthorized tampering during storage
An attacker who can modify keyId might redirect operations to a different key
Consider encrypting or signing stored key identifiers

Implementation Checklist

Selected appropriate Cryptography Service for your use case
Reviewed service documentation for security guarantees
Secured communication channel (TLS, certificate validation)
Master key stored and managed as a credential
Key identifiers protected from tampering
Service authentication properly configured
Considered service availability and failure modes
Implemented proper error handling for service failures
Documented which keys are used for which purposes

Service Selection Considerations

Consideration	Cloud KMS	Platform Keystore	HSM
Network dependency	Required	No	Varies
Audit logging	Built-in	Limited	Built-in
Regulatory compliance	Varies by provider	Platform-dependent	Often required
Key ceremony	Managed	N/A	Often required
Multi-cloud support	Provider-specific	Platform-specific	Usually portable

Consult Service Documentation

Always consult the documentation of candidate Cryptography Service(s) to assess:

Security guarantees for interactions between your system and the service
Key protection mechanisms (hardware backing, encryption at rest)
Audit and compliance capabilities
Service Level Agreements (SLAs)
Key backup and disaster recovery procedures

Related Patterns

Cryptographic Key Management (parent pattern)
Self-Managed Cryptography (alternative implementation)
Cryptographic Action (uses keys managed by this pattern)
Encryption (specific cryptographic action)
Digital Signature (specific cryptographic action)

References

Source: https://securitypatterns.distrinet-research.be/patterns/99_02_002__crypto_as_a_service/
E. Barker, 'Recommendation for Key Management: Part 1 – General', NIST SP 800-57 Part 1, May 2020
Google Cloud KMS Documentation: https://cloud.google.com/kms/docs
AWS KMS Documentation: https://docs.aws.amazon.com/kms/
Android Keystore System: https://developer.android.com/training/articles/keystore
iOS Keychain Services: https://developer.apple.com/documentation/security/keychain_services

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.75%

按下载量换算26

Claude

30.6%

按下载量换算20

Cursor

18.87%

按下载量换算12

Gemini CLI

8.76%

按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置，应进入高风险复核队列，默认不自动发布。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/igbuend/grimbard

SKILL.md 来源

github.com

/igbuend/grimbard/tree/main/skills/cryptography-as-a-service-pattern

skills-sh

skills.sh

/igbuend/grimbard/cryptography-as-a-service-pattern

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

cryptography（cryptography 开发）

cryptography 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

cryptolint（cryptolint 搜索）

cryptolint 用于查找、检索和筛选相关信息，适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。