algorithm-selection

Evaluate cryptographic algorithms and protocols for security compliance and post-quantum readiness.

47|5|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill algorithm-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: algorithm-selection
Source: https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/algorithm-selection
Command: npx skills add https://github.com/RedHatProductSecurity/prodsec-skills --skill algorithm-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides secure cryptographic algorithm selection and configuration, preventing the use of weak or deprecated algorithms and preparing for post-quantum cryptography.

Core Features & Use Cases

  • Recommendation: Identifies approved and forbidden cryptographic algorithms to enforce security standards.
  • Guidance: Assists in implementing secure protocol versions like TLS 1.3 and enforcing key management best practices.
  • Use Case: A security engineer uses this Skill to audit an application's cryptographic configurations and update them to meet latest standards and PQC readiness.

Quick Start

Use the algorithm-selection skill to review the cryptographic settings of your server configuration.

Frequently Asked Questions about algorithm-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate cryptographic algorithms for post-quantum readiness?

Evaluating cryptographic algorithms for post-quantum readiness involves checking current configurations against approved standards and identifying deprecated key exchange mechanisms. This process ensures security compliance and prepares systems for PQC migration.

What are the best practices for secure TLS 1.3 configuration and key management?

Secure TLS 1.3 configuration requires enforcing approved protocol versions and implementing key management best practices. Following cryptographic standards ensures applications prevent weak algorithms and maintain robust security compliance across systems.

How do I audit my application's cryptographic settings for deprecated protocols?

Auditing cryptographic settings involves reviewing server configurations to identify forbidden algorithms and weak protocols. This validates your setup against current security standards, highlighting necessary updates for deprecated mechanisms.

Does OpenSSL support post-quantum cryptography and secure algorithm selection?

OpenSSL implementations require validation against current cryptographic standards to ensure secure algorithm selection. Reviewing library documentation confirms whether specific configurations support post-quantum cryptography and approved key exchange mechanisms.

When should I migrate from deprecated cryptographic algorithms to recommended standards?

Migrating from deprecated cryptographic algorithms is necessary when configurations fail security compliance checks. Enforcing recommended algorithms and secure protocol versions ensures scalability and addresses vulnerabilities before system deployment.

What libraries and documentation do I need to validate cryptographic protocol configurations?

Validating cryptographic protocol configurations requires libraries and standards documentation for best practices. These references provide the necessary approved algorithm lists and configuration validation rules to ensure security compliance.