[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HNDA0RMX9SP4JBMS0CXVNV":3,"skill-same:01M6HNDA0RMX9SP4JBMS0CXVNV":97},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6HNDA0RMX9SP4JBMS0CXVNV","performing-post-quantum-cryptography-migration",null,"Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS...","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-post-quantum-cryptography-migration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"performing","cryptography","post","quantum","migration","performing post quantum cryptography migration","CRYSTALS-Kyber","scanning","hybrid-TLS","FIPS-204","FIPS-203","cybersecurity","PQC","inventory","crypto-agility","ml-dsa","ml-kem","post-quantum","tls","NIST","2026-11-10 10:12:30",false,"---\nname: performing-post-quantum-cryptography-migration\ndescription: Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS...\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- post-quantum\n- PQC\n- CRYSTALS-Kyber\n- ML-KEM\n- ML-DSA\n- FIPS-203\n- FIPS-204\n- hybrid-TLS\n- crypto-agility\nversion: '1.0'\nauthor: mukul975\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- T1040\ncategory: performing-post-quantum-cryptography-migration\n---\n# Performing-Post-Quantum-Cryptography-Migration\n\n## Overview\nAssesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure.\n\n\n\n# Performing Post-Quantum Cryptography Migration\n\n## When to Use\n\n- When assessing organizational readiness for the NIST post-quantum cryptography transition\n- When building a cryptographic inventory to identify quantum-vulnerable algorithms across infrastructure\n- When evaluating hybrid TLS 1.3 configurations using X25519MLKEM768 key exchange\n- When testing CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) algorithm support\n- When implementing crypto-agility to support both classical and post-quantum algorithms\n- When preparing migration roadmaps aligned with NIST IR 8547 deprecation timelines\n- When configuring oqs-provider with OpenSSL 3.x for post-quantum algorithm support\n\n## Prerequisites\n\n- Python 3.8+ with `cryptography`, `requests`, `pyOpenSSL` libraries\n- OpenSSL 3.0+ (3.5+ recommended for native ML-KEM\u002FML-DSA support)\n- oqs-provider for OpenSSL (for hybrid TLS testing with older OpenSSL)\n- Network access to target servers for TLS assessment\n- Administrative access for infrastructure scanning\n- Familiarity with PKI, TLS, and cryptographic protocols\n\n## Core Concepts\n\n### NIST Post-Quantum Cryptography Standards\n\nNIST published three finalized PQC standards on August 13, 2024:\n\n| Standard | Algorithm | Renamed To | Purpose | Based On |\n|----------|-----------|------------|---------|----------|\n| FIPS 203 | CRYSTALS-Kyber | ML-KEM | Key Encapsulation Mechanism | Module lattice |\n| FIPS 204 | CRYSTALS-Dilithium | ML-DSA | Digital Signatures | Module lattice |\n| FIPS 205 | SPHINCS+ | SLH-DSA | Digital Signatures (backup) | Stateless hash |\n\n**ML-KEM (FIPS 203)** -- Primary standard for key exchange and encryption. Replaces\nRSA and ECDH for key establishment. Three security levels: ML-KEM-512, ML-KEM-768,\nML-KEM-1024.\n\n**ML-DSA (FIPS 204)** -- Primary standard for digital signatures. Replaces RSA and\nECDSA for signing. Three security levels: ML-DSA-44, ML-DSA-65, ML-DSA-87.\n\n**SLH-DSA (FIPS 205)** -- Backup signature standard using hash-based approach. Intended\nas fallback if lattice-based ML-DSA is found vulnerable. Larger signatures but\nconservative security assumptions.\n\n### Quantum-Vulnerable Algorithms\n\nThese classical algorithms are vulnerable to quantum attack via Shor's algorithm:\n\n| Algorithm | Usage | Quantum Threat | Migration Priority |\n|-----------|-------|---------------|-------------------|\n| RSA-2048\u002F4096 | Key exchange, signatures, encryption | Shor's algorithm breaks factoring | Critical |\n| ECDH (P-256, P-384) | TLS key exchange | Shor's algorithm breaks ECDLP | Critical |\n| ECDSA | Code signing, TLS certificates | Shor's algorithm breaks ECDLP | Critical |\n| DSA | Legacy signatures | Shor's algorithm breaks DLP | Critical |\n| DH (Diffie-Hellman) | Key exchange | Shor's algorithm breaks DLP | Critical |\n| AES-128 | Symmetric encryption | Grover's halves key strength | Medium (upgrade to AES-256) |\n| SHA-256 | Hashing | Grover's reduces to 128-bit | Low (still adequate) |\n\n### NIST Migration Timeline (IR 8547)\n\n- **2024**: Standards published, migration planning should begin\n- **2030**: Deprecation of quantum-vulnerable algorithms for most federal systems\n- **2035**: Complete removal of quantum-vulnerable algorithms from NIST standards\n- **Now**: \"Harvest now, decrypt later\" attacks make early migration essential for\n  long-lived secrets and data requiring long-term confidentiality\n\n### Hybrid TLS Key Exchange\n\nDuring the transition period, hybrid key exchange combines a classical algorithm with\na post-quantum algorithm. If either algorithm is secure, the connection remains protected.\n\n```\nHybrid Key Exchange: X25519MLKEM768\n  = X25519 (classical ECDH) + ML-KEM-768 (post-quantum)\n\nClient Hello:\n  supported_groups: X25519MLKEM768, X25519, secp256r1\n  key_share: X25519MLKEM768\n\nServer Hello:\n  selected_group: X25519MLKEM768\n  key_share: X25519MLKEM768\n\nShared Secret = KDF(X25519_shared || MLKEM768_shared)\n```\n\n## Instructions\n\n### Phase 1: Cryptographic Inventory Scanning\n\nThe first step in PQC migration is discovering all cryptographic algorithm usage\nacross the enterprise. This includes TLS configurations, certificates, code libraries,\nkey stores, and protocol configurations.\n\n```python\n# Scan TLS endpoints for quantum-vulnerable algorithms\npython scripts\u002Fagent.py --action scan_tls \\\n    --targets targets.txt \\\n    --output tls_inventory.json\n```\n\nThe scanner identifies:\n- TLS protocol versions in use\n- Key exchange algorithms (RSA, ECDH, DH -- all quantum-vulnerable)\n- Certificate signature algorithms (RSA, ECDSA)\n- Cipher suite configurations\n- Certificate key sizes and expiration dates\n\n### Phase 2: Crypto-Agility Assessment\n\nEvaluate the organization's ability to swap cryptographic algorithms without\nmajor infrastructure changes:\n\n```python\n# Assess crypto-agility readiness\npython scripts\u002Fagent.py --action assess_agility \\\n    --scan-results tls_inventory.json \\\n    --output agility_report.json\n```\n\nKey assessment areas:\n1. **Protocol flexibility**: Can TLS configurations be updated without downtime?\n2. **Library versions**: Do deployed crypto libraries support PQC algorithms?\n3. **Certificate infrastructure**: Can CA issue PQC certificates?\n4. **Key management**: Can KMS handle larger PQC key sizes?\n5. **Hardware constraints**: Can HSMs support PQC operations?\n\n### Phase 3: Hybrid TLS Readiness Testing\n\nTest whether infrastructure supports hybrid key exchange with X25519MLKEM768:\n\n```python\n# Test hybrid TLS support on target servers\npython scripts\u002Fagent.py --action test_hybrid_tls \\\n    --target server.example.com:443 \\\n    --output hybrid_tls_report.json\n```\n\n**OpenSSL 3.5+ (native ML-KEM support):**\n```bash\n# Test with native PQC support\nopenssl s_client -connect server.example.com:443 \\\n    -groups X25519MLKEM768\n```\n\n**OpenSSL 3.0-3.4 with oqs-provider:**\n```bash\n# Configure oqs-provider\n# \u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf\n[openssl_init]\nproviders = provider_sect\n\n[provider_sect]\ndefault = default_sect\noqsprovider = oqsprovider_sect\n\n[default_sect]\nactivate = 1\n\n[oqsprovider_sect]\nactivate = 1\nmodule = \u002Fusr\u002Flib\u002Foqs-provider\u002Foqsprovider.so\n\n# Test hybrid TLS\nOPENSSL_CONF=\u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf \\\nopenssl s_client -connect server.example.com:443 \\\n    -groups x25519_mlkem768\n```\n\n**Web Server Configuration for Hybrid TLS:**\n\nApache httpd:\n```apache\nSSLEngine on\nSSLCertificateFile \u002Fetc\u002Fssl\u002Fcerts\u002Fserver.crt\nSSLCertificateKeyFile \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\nSSLOpenSSLConfCmd Curves X25519MLKEM768:X25519:prime256v1\nSSLProtocol -all +TLSv1.2 +TLSv1.3\n```\n\nNGINX:\n```nginx\nssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;\nssl_protocols TLSv1.2 TLSv1.3;\nssl_prefer_server_ciphers on;\n```\n\n### Phase 4: ML-KEM Key Encapsulation Validation\n\nValidate that ML-KEM (CRYSTALS-Kyber) key encapsulation works correctly in your\nenvironment:\n\n```python\n# Test ML-KEM key encapsulation at all security levels\npython scripts\u002Fagent.py --action test_mlkem \\\n    --output mlkem_validation.json\n```\n\nML-KEM parameter comparison:\n\n| Parameter | ML-KEM-512 | ML-KEM-768 | ML-KEM-1024 |\n|-----------|-----------|-----------|------------|\n| Security Level | NIST Level 1 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 800 bytes | 1,184 bytes | 1,568 bytes |\n| Ciphertext Size | 768 bytes | 1,088 bytes | 1,568 bytes |\n| Shared Secret | 32 bytes | 32 bytes | 32 bytes |\n| Comparable To | AES-128 | AES-192 | AES-256 |\n\n### Phase 5: ML-DSA Digital Signature Validation\n\nValidate ML-DSA (CRYSTALS-Dilithium) signature operations:\n\n```python\n# Test ML-DSA digital signatures\npython scripts\u002Fagent.py --action test_mldsa \\\n    --output mldsa_validation.json\n```\n\nML-DSA parameter comparison:\n\n| Parameter | ML-DSA-44 | ML-DSA-65 | ML-DSA-87 |\n|-----------|----------|----------|----------|\n| Security Level | NIST Level 2 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 1,312 bytes | 1,952 bytes | 2,592 bytes |\n| Signature Size | 2,420 bytes | 3,293 bytes | 4,595 bytes |\n| Secret Key Size | 2,560 bytes | 4,032 bytes | 4,896 bytes |\n\n### Phase 6: Migration Roadmap Generation\n\nGenerate a prioritized migration roadmap based on inventory and assessment results:\n\n```python\n# Generate complete migration roadmap\npython scripts\u002Fagent.py --action roadmap \\\n    --scan-results tls_inventory.json \\\n    --agility-results agility_report.json \\\n    --output migration_roadmap.json\n```\n\nThe roadmap prioritizes systems by:\n1. **Data sensitivity**: Systems handling long-lived secrets migrate first\n2. **Exposure level**: Internet-facing services before internal\n3. **Crypto-agility**: Systems that can easily swap algorithms first\n4. **Compliance requirements**: Federal\u002Fregulated systems per NIST IR 8547 timeline\n5. **Dependency chains**: Libraries and frameworks before applications\n\n## Examples\n\n### Full Assessment Pipeline\n\n```bash\n# Step 1: Scan all TLS endpoints\npython scripts\u002Fagent.py --action scan_tls --targets hosts.txt --output scan.json\n\n# Step 2: Assess crypto-agility\npython scripts\u002Fagent.py --action assess_agility --scan-results scan.json --output agility.json\n\n# Step 3: Test hybrid TLS on critical servers\npython scripts\u002Fagent.py --action test_hybrid_tls --target critical.example.com:443\n\n# Step 4: Validate ML-KEM support\npython scripts\u002Fagent.py --action test_mlkem --output mlkem.json\n\n# Step 5: Validate ML-DSA support\npython scripts\u002Fagent.py --action test_mldsa --output mldsa.json\n\n# Step 6: Generate migration roadmap\npython scripts\u002Fagent.py --action roadmap --scan-results scan.json --agility-results agility.json --output roadmap.json\n```\n\n### Quick Server Assessment\n\n```bash\n# Single server PQC readiness check\npython scripts\u002Fagent.py --action scan_tls --target server.example.com:443\n```\n\n## Validation Checklist\n\n- [ ] Cryptographic inventory covers all TLS endpoints, certificates, and key stores\n- [ ] All quantum-vulnerable algorithms (RSA, ECDH, ECDSA, DH, DSA) are identified\n- [ ] Crypto-agility assessment documents library versions and upgrade paths\n- [ ] Hybrid TLS (X25519MLKEM768) tested on representative server configurations\n- [ ] ML-KEM key encapsulation validated at target security level (768 recommended)\n- [ ] ML-DSA signature verification validated for certificate chain use\n- [ ] SLH-DSA (FIPS 205) evaluated as backup signature algorithm\n- [ ] Migration roadmap prioritizes by data sensitivity and compliance timeline\n- [ ] OpenSSL version and oqs-provider compatibility confirmed\n- [ ] Key size increases accounted for in network and storage capacity planning\n- [ ] HSM\u002FKMS compatibility with PQC algorithms verified\n- [ ] Performance impact of PQC algorithms benchmarked under production load\n- [ ] \"Harvest now, decrypt later\" risk assessed for sensitive data channels\n- [ ] Certificate Authority PQC readiness confirmed for certificate issuance\n\n## References\n\n- NIST PQC Standards: https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fpost-quantum-cryptography\n- FIPS 203 (ML-KEM): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal\n- FIPS 204 (ML-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F204\u002Ffinal\n- FIPS 205 (SLH-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F205\u002Ffinal\n- NIST SP 1800-38 Migration Guide: https:\u002F\u002Fwww.nccoe.nist.gov\u002Fcrypto-agility-considerations-migrating-post-quantum-cryptographic-algorithms\n- NIST IR 8547 Transition Timeline: https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fir\u002F8547\u002Fipd\n- Open Quantum Safe Project: https:\u002F\u002Fopenquantumsafe.org\u002F\n- oqs-provider for OpenSSL: https:\u002F\u002Fgithub.com\u002Fopen-quantum-safe\u002Foqs-provider\n- OQS TLS Integration: https:\u002F\u002Fopenquantumsafe.org\u002Fapplications\u002Ftls.html\n- CISA PQC Migration Strategy: https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002F2024-09\u002FStrategy-for-Migrating-to-Automated-PQC-Discovery-and-Inventory-Tools.pdf\n- IETF Hybrid Key Exchange Draft: https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-tls-hybrid-design\u002F\n- CycloneDX Crypto BOM: https:\u002F\u002Fcyclonedx.org\u002Fuse-cases\u002Fcryptographic-key\u002F\n","# Performing-Post-Quantum-Cryptography-Migration\n\n## Overview\nAssesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203\u002F204\u002F205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use when planning or executing the transition from classical to post-quantum cryptographic algorithms across enterprise infrastructure.\n\n\n\n# Performing Post-Quantum Cryptography Migration\n\n## When to Use\n\n- When assessing organizational readiness for the NIST post-quantum cryptography transition\n- When building a cryptographic inventory to identify quantum-vulnerable algorithms across infrastructure\n- When evaluating hybrid TLS 1.3 configurations using X25519MLKEM768 key exchange\n- When testing CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) algorithm support\n- When implementing crypto-agility to support both classical and post-quantum algorithms\n- When preparing migration roadmaps aligned with NIST IR 8547 deprecation timelines\n- When configuring oqs-provider with OpenSSL 3.x for post-quantum algorithm support\n\n## Prerequisites\n\n- Python 3.8+ with `cryptography`, `requests`, `pyOpenSSL` libraries\n- OpenSSL 3.0+ (3.5+ recommended for native ML-KEM\u002FML-DSA support)\n- oqs-provider for OpenSSL (for hybrid TLS testing with older OpenSSL)\n- Network access to target servers for TLS assessment\n- Administrative access for infrastructure scanning\n- Familiarity with PKI, TLS, and cryptographic protocols\n\n## Core Concepts\n\n### NIST Post-Quantum Cryptography Standards\n\nNIST published three finalized PQC standards on August 13, 2024:\n\n| Standard | Algorithm | Renamed To | Purpose | Based On |\n|----------|-----------|------------|---------|----------|\n| FIPS 203 | CRYSTALS-Kyber | ML-KEM | Key Encapsulation Mechanism | Module lattice |\n| FIPS 204 | CRYSTALS-Dilithium | ML-DSA | Digital Signatures | Module lattice |\n| FIPS 205 | SPHINCS+ | SLH-DSA | Digital Signatures (backup) | Stateless hash |\n\n**ML-KEM (FIPS 203)** -- Primary standard for key exchange and encryption. Replaces\nRSA and ECDH for key establishment. Three security levels: ML-KEM-512, ML-KEM-768,\nML-KEM-1024.\n\n**ML-DSA (FIPS 204)** -- Primary standard for digital signatures. Replaces RSA and\nECDSA for signing. Three security levels: ML-DSA-44, ML-DSA-65, ML-DSA-87.\n\n**SLH-DSA (FIPS 205)** -- Backup signature standard using hash-based approach. Intended\nas fallback if lattice-based ML-DSA is found vulnerable. Larger signatures but\nconservative security assumptions.\n\n### Quantum-Vulnerable Algorithms\n\nThese classical algorithms are vulnerable to quantum attack via Shor's algorithm:\n\n| Algorithm | Usage | Quantum Threat | Migration Priority |\n|-----------|-------|---------------|-------------------|\n| RSA-2048\u002F4096 | Key exchange, signatures, encryption | Shor's algorithm breaks factoring | Critical |\n| ECDH (P-256, P-384) | TLS key exchange | Shor's algorithm breaks ECDLP | Critical |\n| ECDSA | Code signing, TLS certificates | Shor's algorithm breaks ECDLP | Critical |\n| DSA | Legacy signatures | Shor's algorithm breaks DLP | Critical |\n| DH (Diffie-Hellman) | Key exchange | Shor's algorithm breaks DLP | Critical |\n| AES-128 | Symmetric encryption | Grover's halves key strength | Medium (upgrade to AES-256) |\n| SHA-256 | Hashing | Grover's reduces to 128-bit | Low (still adequate) |\n\n### NIST Migration Timeline (IR 8547)\n\n- **2024**: Standards published, migration planning should begin\n- **2030**: Deprecation of quantum-vulnerable algorithms for most federal systems\n- **2035**: Complete removal of quantum-vulnerable algorithms from NIST standards\n- **Now**: \"Harvest now, decrypt later\" attacks make early migration essential for\n  long-lived secrets and data requiring long-term confidentiality\n\n### Hybrid TLS Key Exchange\n\nDuring the transition period, hybrid key exchange combines a classical algorithm with\na post-quantum algorithm. If either algorithm is secure, the connection remains protected.\n\n```\nHybrid Key Exchange: X25519MLKEM768\n  = X25519 (classical ECDH) + ML-KEM-768 (post-quantum)\n\nClient Hello:\n  supported_groups: X25519MLKEM768, X25519, secp256r1\n  key_share: X25519MLKEM768\n\nServer Hello:\n  selected_group: X25519MLKEM768\n  key_share: X25519MLKEM768\n\nShared Secret = KDF(X25519_shared || MLKEM768_shared)\n```\n\n## Instructions\n\n### Phase 1: Cryptographic Inventory Scanning\n\nThe first step in PQC migration is discovering all cryptographic algorithm usage\nacross the enterprise. This includes TLS configurations, certificates, code libraries,\nkey stores, and protocol configurations.\n\n```python\n# Scan TLS endpoints for quantum-vulnerable algorithms\npython scripts\u002Fagent.py --action scan_tls \\\n    --targets targets.txt \\\n    --output tls_inventory.json\n```\n\nThe scanner identifies:\n- TLS protocol versions in use\n- Key exchange algorithms (RSA, ECDH, DH -- all quantum-vulnerable)\n- Certificate signature algorithms (RSA, ECDSA)\n- Cipher suite configurations\n- Certificate key sizes and expiration dates\n\n### Phase 2: Crypto-Agility Assessment\n\nEvaluate the organization's ability to swap cryptographic algorithms without\nmajor infrastructure changes:\n\n```python\n# Assess crypto-agility readiness\npython scripts\u002Fagent.py --action assess_agility \\\n    --scan-results tls_inventory.json \\\n    --output agility_report.json\n```\n\nKey assessment areas:\n1. **Protocol flexibility**: Can TLS configurations be updated without downtime?\n2. **Library versions**: Do deployed crypto libraries support PQC algorithms?\n3. **Certificate infrastructure**: Can CA issue PQC certificates?\n4. **Key management**: Can KMS handle larger PQC key sizes?\n5. **Hardware constraints**: Can HSMs support PQC operations?\n\n### Phase 3: Hybrid TLS Readiness Testing\n\nTest whether infrastructure supports hybrid key exchange with X25519MLKEM768:\n\n```python\n# Test hybrid TLS support on target servers\npython scripts\u002Fagent.py --action test_hybrid_tls \\\n    --target server.example.com:443 \\\n    --output hybrid_tls_report.json\n```\n\n**OpenSSL 3.5+ (native ML-KEM support):**\n```bash\n# Test with native PQC support\nopenssl s_client -connect server.example.com:443 \\\n    -groups X25519MLKEM768\n```\n\n**OpenSSL 3.0-3.4 with oqs-provider:**\n```bash\n# Configure oqs-provider\n# \u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf\n[openssl_init]\nproviders = provider_sect\n\n[provider_sect]\ndefault = default_sect\noqsprovider = oqsprovider_sect\n\n[default_sect]\nactivate = 1\n\n[oqsprovider_sect]\nactivate = 1\nmodule = \u002Fusr\u002Flib\u002Foqs-provider\u002Foqsprovider.so\n\n# Test hybrid TLS\nOPENSSL_CONF=\u002Fetc\u002Fssl\u002Fopenssl-oqs.cnf \\\nopenssl s_client -connect server.example.com:443 \\\n    -groups x25519_mlkem768\n```\n\n**Web Server Configuration for Hybrid TLS:**\n\nApache httpd:\n```apache\nSSLEngine on\nSSLCertificateFile \u002Fetc\u002Fssl\u002Fcerts\u002Fserver.crt\nSSLCertificateKeyFile \u002Fetc\u002Fssl\u002Fprivate\u002Fserver.key\nSSLOpenSSLConfCmd Curves X25519MLKEM768:X25519:prime256v1\nSSLProtocol -all +TLSv1.2 +TLSv1.3\n```\n\nNGINX:\n```nginx\nssl_ecdh_curve X25519MLKEM768:X25519:prime256v1;\nssl_protocols TLSv1.2 TLSv1.3;\nssl_prefer_server_ciphers on;\n```\n\n### Phase 4: ML-KEM Key Encapsulation Validation\n\nValidate that ML-KEM (CRYSTALS-Kyber) key encapsulation works correctly in your\nenvironment:\n\n```python\n# Test ML-KEM key encapsulation at all security levels\npython scripts\u002Fagent.py --action test_mlkem \\\n    --output mlkem_validation.json\n```\n\nML-KEM parameter comparison:\n\n| Parameter | ML-KEM-512 | ML-KEM-768 | ML-KEM-1024 |\n|-----------|-----------|-----------|------------|\n| Security Level | NIST Level 1 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 800 bytes | 1,184 bytes | 1,568 bytes |\n| Ciphertext Size | 768 bytes | 1,088 bytes | 1,568 bytes |\n| Shared Secret | 32 bytes | 32 bytes | 32 bytes |\n| Comparable To | AES-128 | AES-192 | AES-256 |\n\n### Phase 5: ML-DSA Digital Signature Validation\n\nValidate ML-DSA (CRYSTALS-Dilithium) signature operations:\n\n```python\n# Test ML-DSA digital signatures\npython scripts\u002Fagent.py --action test_mldsa \\\n    --output mldsa_validation.json\n```\n\nML-DSA parameter comparison:\n\n| Parameter | ML-DSA-44 | ML-DSA-65 | ML-DSA-87 |\n|-----------|----------|----------|----------|\n| Security Level | NIST Level 2 | NIST Level 3 | NIST Level 5 |\n| Public Key Size | 1,312 bytes | 1,952 bytes | 2,592 bytes |\n| Signature Size | 2,420 bytes | 3,293 bytes | 4,595 bytes |\n| Secret Key Size | 2,560 bytes | 4,032 bytes | 4,896 bytes |\n\n### Phase 6: Migration Roadmap Generation\n\nGenerate a prioritized migration roadmap based on inventory and assessment results:\n\n```python\n# Generate complete migration roadmap\npython scripts\u002Fagent.py --action roadmap \\\n    --scan-results tls_inventory.json \\\n    --agility-results agility_report.json \\\n    --output migration_roadmap.json\n```\n\nThe roadmap prioritizes systems by:\n1. **Data sensitivity**: Systems handling long-lived secrets migrate first\n2. **Exposure level**: Internet-facing services before internal\n3. **Crypto-agility**: Systems that can easily swap algorithms first\n4. **Compliance requirements**: Federal\u002Fregulated systems per NIST IR 8547 timeline\n5. **Dependency chains**: Libraries and frameworks before applications\n\n## Examples\n\n### Full Assessment Pipeline\n\n```bash\n# Step 1: Scan all TLS endpoints\npython scripts\u002Fagent.py --action scan_tls --targets hosts.txt --output scan.json\n\n# Step 2: Assess crypto-agility\npython scripts\u002Fagent.py --action assess_agility --scan-results scan.json --output agility.json\n\n# Step 3: Test hybrid TLS on critical servers\npython scripts\u002Fagent.py --action test_hybrid_tls --target critical.example.com:443\n\n# Step 4: Validate ML-KEM support\npython scripts\u002Fagent.py --action test_mlkem --output mlkem.json\n\n# Step 5: Validate ML-DSA support\npython scripts\u002Fagent.py --action test_mldsa --output mldsa.json\n\n# Step 6: Generate migration roadmap\npython scripts\u002Fagent.py --action roadmap --scan-results scan.json --agility-results agility.json --output roadmap.json\n```\n\n### Quick Server Assessment\n\n```bash\n# Single server PQC readiness check\npython scripts\u002Fagent.py --action scan_tls --target server.example.com:443\n```\n\n## Validation Checklist\n\n- [ ] Cryptographic inventory covers all TLS endpoints, certificates, and key stores\n- [ ] All quantum-vulnerable algorithms (RSA, ECDH, ECDSA, DH, DSA) are identified\n- [ ] Crypto-agility assessment documents library versions and upgrade paths\n- [ ] Hybrid TLS (X25519MLKEM768) tested on representative server configurations\n- [ ] ML-KEM key encapsulation validated at target security level (768 recommended)\n- [ ] ML-DSA signature verification validated for certificate chain use\n- [ ] SLH-DSA (FIPS 205) evaluated as backup signature algorithm\n- [ ] Migration roadmap prioritizes by data sensitivity and compliance timeline\n- [ ] OpenSSL version and oqs-provider compatibility confirmed\n- [ ] Key size increases accounted for in network and storage capacity planning\n- [ ] HSM\u002FKMS compatibility with PQC algorithms verified\n- [ ] Performance impact of PQC algorithms benchmarked under production load\n- [ ] \"Harvest now, decrypt later\" risk assessed for sensitive data channels\n- [ ] Certificate Authority PQC readiness confirmed for certificate issuance\n\n## References\n\n- NIST PQC Standards: https:\u002F\u002Fcsrc.nist.gov\u002Fprojects\u002Fpost-quantum-cryptography\n- FIPS 203 (ML-KEM): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal\n- FIPS 204 (ML-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F204\u002Ffinal\n- FIPS 205 (SLH-DSA): https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F205\u002Ffinal\n- NIST SP 1800-38 Migration Guide: https:\u002F\u002Fwww.nccoe.nist.gov\u002Fcrypto-agility-considerations-migrating-post-quantum-cryptographic-algorithms\n- NIST IR 8547 Transition Timeline: https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fir\u002F8547\u002Fipd\n- Open Quantum Safe Project: https:\u002F\u002Fopenquantumsafe.org\u002F\n- oqs-provider for OpenSSL: https:\u002F\u002Fgithub.com\u002Fopen-quantum-safe\u002Foqs-provider\n- OQS TLS Integration: https:\u002F\u002Fopenquantumsafe.org\u002Fapplications\u002Ftls.html\n- CISA PQC Migration Strategy: https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002F2024-09\u002FStrategy-for-Migrating-to-Automated-PQC-Discovery-and-Inventory-Tools.pdf\n- IETF Hybrid Key Exchange Draft: https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-tls-hybrid-design\u002F\n- CycloneDX Crypto BOM: https:\u002F\u002Fcyclonedx.org\u002Fuse-cases\u002Fcryptographic-key\u002F\n",{"name":5,"tags":44,"author":47,"domain":30,"license":15,"version":48,"category":5,"nist_csf":49,"subdomain":20,"description":7,"mitre_attack":53},[36,31,25,45,46,29,28,27,33],"ML-KEM","ML-DSA","mukul975","1.0",[50,51,52],"PR.DS-01","PR.DS-02","PR.DS-10",[54,55,56,57],"T1600","T1573","T1553","T1040","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fperforming-post-quantum-cryptography-migration",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill performing-post-quantum-cryptography-migration",{"tool":72,"command":73},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill performing-post-quantum-cryptography-migration",{"tool":75,"command":76},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill performing-post-quantum-cryptography-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-post-quantum-cryptography-migration\u002FSKILL.md",true,[80,85,91],{"path":81,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-post-quantum-cryptography-migration\u002FLICENSE",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fapi-reference.md","REFERENCE","参考文档",8824,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-post-quantum-cryptography-migration\u002Freferences\u002Fapi-reference.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fagent.py","SCRIPT","脚本",56599,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fperforming-post-quantum-cryptography-migration\u002Fscripts\u002Fagent.py",[98,129,155,177,193,214],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[110,111,112,113,114,115,30,116,117,118,119,120,121,122,123,124,125,126,127,128],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"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":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[136,137,138,139,140,30,141,142,143,144,145,146,147,148,149,150,151,152,153,154],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[162,163,126,30,164,165,38,122,123,166,167,168,169,170,171,172,173,174,175,176],"security","triaging security incident","actions","soc","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[162,184,185,163,126,140,30,186,165,119,187,188,122,123,189,167,150,190,191,192],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"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":199,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[162,200,201,202,203,204,30,205,206,207,165,208,122,209,210,211,170,212,126,213],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[221,222,223,224,30,225,226,227,228,229,230,209,231,232,212,233,213,234,235,236],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]