mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-03 09:20:18 +03:00
Mahipal
2fb6a9faff
Each rewritten description now states both what the skill does (concrete capability, named tools/artifacts) and an explicit when-to-use trigger, improving agent discovery/activation. Grounded in each skill's own body; changes confined to the `description` field only (bodies and all other frontmatter untouched). Produced by a gated audit->rewrite->recheck loop (548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded). Schema: 817/817 pass. Framework-ID gate: 0 defects.
103 lines
3.6 KiB
Markdown
103 lines
3.6 KiB
Markdown
---
|
|
name: implementing-rsa-key-pair-management
|
|
description: Generates, stores, rotates, and manages RSA key pairs following NIST
|
|
SP 800-57 guidelines, covering serialization formats (PEM, DER, PKCS#8), passphrase
|
|
protection, and key strength validation. Use when creating or rotating RSA keys
|
|
for signatures, key exchange, or encryption, or when auditing existing keys for
|
|
proper storage and NIST-compliant strength.
|
|
domain: cybersecurity
|
|
subdomain: cryptography
|
|
tags:
|
|
- cryptography
|
|
- rsa
|
|
- key-management
|
|
- pki
|
|
- asymmetric-encryption
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.DS-01
|
|
- PR.DS-02
|
|
- PR.DS-10
|
|
mitre_attack:
|
|
- T1600
|
|
- T1573
|
|
- T1553
|
|
- T1486
|
|
---
|
|
# Implementing RSA Key Pair Management
|
|
|
|
## Overview
|
|
|
|
RSA (Rivest-Shamir-Adleman) is the most widely deployed asymmetric cryptographic algorithm, used for digital signatures, key exchange, and encryption. This skill covers generating, storing, rotating, and managing RSA key pairs following NIST SP 800-57 key management guidelines, including key serialization formats (PEM, DER, PKCS#8), passphrase protection, and key strength validation.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing rsa key pair management capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## Prerequisites
|
|
|
|
- Familiarity with cryptography concepts and tools
|
|
- Access to a test or lab environment for safe execution
|
|
- Python 3.8+ with required dependencies installed
|
|
- Appropriate authorization for any testing activities
|
|
|
|
## Objectives
|
|
|
|
- Generate RSA key pairs with appropriate key sizes (2048, 3072, 4096 bits)
|
|
- Serialize keys in PEM and DER formats with PKCS#8
|
|
- Protect private keys with strong passphrase encryption
|
|
- Implement key rotation with versioning
|
|
- Extract public key components and fingerprints
|
|
- Validate key strength and detect weak keys
|
|
- Sign and verify data using RSA-PSS
|
|
|
|
## Key Concepts
|
|
|
|
### RSA Key Sizes and Security Strength
|
|
|
|
| Key Size (bits) | Security Strength (bits) | Recommended Until |
|
|
|-----------------|-------------------------|-------------------|
|
|
| 2048 | 112 | 2030 |
|
|
| 3072 | 128 | Beyond 2030 |
|
|
| 4096 | ~140 | Beyond 2030 |
|
|
|
|
### RSA Padding Schemes
|
|
|
|
| Scheme | Use Case | Standard |
|
|
|--------|----------|----------|
|
|
| OAEP | Encryption | PKCS#1 v2.2 (RFC 8017) |
|
|
| PSS | Signatures | PKCS#1 v2.2 (RFC 8017) |
|
|
| PKCS#1 v1.5 | Legacy only | Deprecated for new systems |
|
|
|
|
### Key Storage Formats
|
|
|
|
- **PEM**: Base64-encoded with headers, human-readable
|
|
- **DER**: Binary ASN.1 encoding, compact
|
|
- **PKCS#8**: Standard for private key encapsulation
|
|
- **PKCS#12/PFX**: Bundled key + certificate, password-protected
|
|
|
|
## Security Considerations
|
|
|
|
- Minimum 3072-bit keys for new deployments (NIST recommendation)
|
|
- Always protect private keys with AES-256-CBC passphrase encryption
|
|
- Use RSA-PSS for signatures (not PKCS#1 v1.5)
|
|
- Use RSA-OAEP for encryption (not PKCS#1 v1.5)
|
|
- Store private keys with restrictive file permissions (0600)
|
|
- Implement key rotation at least annually
|
|
|
|
## Validation Criteria
|
|
|
|
- [ ] Key generation produces valid RSA key pair
|
|
- [ ] Public key can be extracted from private key
|
|
- [ ] Private key is protected with passphrase
|
|
- [ ] RSA-PSS signature verification succeeds
|
|
- [ ] Tampered signature verification fails
|
|
- [ ] Key fingerprint is computed correctly
|
|
- [ ] Key rotation maintains old key access for verification
|