Skip to content
cccskills
FreePublished on GitHub

configuring-tls-1-3-for-secure-communications

Configure TLS 1.3, a protocol for encrypted connections, on nginx, Apache, and Python applications. Select encryption settings and key exchange groups, disable outdated protocols, and use openssl s_client and testssl.sh to check connections and configuration weaknesses.

OriginalShow the original description

Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and key-exchange group selection, and validates the resulting configuration with openssl s_client and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications, or when testing a server for common TLS misconfigurations and vulnerabilities.

Run score Not tested

See how to install

Good for

  • Enabling TLS 1.3 on nginx or Apache
  • Configuring encrypted connections in a Python application
  • Disabling outdated TLS versions and weak encryption
  • Checking server TLS settings and certificate chains

Files included (8)

  • SKILL.md4.2 KB
  • assets/template.md2.1 KB
  • LICENSE11.0 KB
  • references/api-reference.md1.4 KB
  • references/standards.md2.5 KB
  • references/workflows.md2.3 KB
  • scripts/agent.py5.4 KB
  • scripts/process.py14.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Configuring TLS 1.3 for Secure Communications

Overview

TLS 1.3 (RFC 8446) is the latest version of the Transport Layer Security protocol, providing significant improvements over TLS 1.2 in both security and performance. It reduces handshake latency to 1-RTT (and 0-RTT for resumed sessions), removes obsolete cipher suites, and mandates perfect forward secrecy. This skill covers configuring TLS 1.3 on servers, validating configurations, and testing for common misconfigurations.

When to Use

  • When deploying or configuring configuring tls 1 3 for secure communications 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

  • Configure TLS 1.3 on nginx and Apache web servers
  • Implement TLS 1.3 in Python applications using the ssl module
  • Validate TLS configurations with openssl and testssl.sh
  • Understand TLS 1.3 cipher suites and key exchange mechanisms
  • Configure 0-RTT early data with appropriate protections
  • Disable legacy TLS versions (1.0, 1.1) and weak cipher suites

Key Concepts

TLS 1.3 Cipher Suites

Cipher SuiteKey ExchangeAuthenticationEncryptionHash
TLS_AES_256_GCM_SHA384ECDHE/DHECertificateAES-256-GCMSHA-384
TLS_AES_128_GCM_SHA256ECDHE/DHECertificateAES-128-GCMSHA-256
TLS_CHACHA20_POLY1305_SHA256ECDHE/DHECertificateChaCha20-Poly1305SHA-256

TLS 1.3 vs 1.2 Improvements

  • 1-RTT Handshake: Full handshake completes in one round trip (vs 2 in TLS 1.2)
  • 0-RTT Resumption: Resumed connections can send data immediately
  • No RSA Key Exchange: Only ephemeral Diffie-Hellman (mandatory PFS)
  • Simplified Cipher Suites: Removed CBC, RC4, 3DES, static RSA, SHA-1
  • Encrypted Handshake: Server certificate is encrypted after ServerHello

Key Exchange Groups

  • x25519: Curve25519 ECDH (preferred, fast)
  • secp256r1: NIST P-256 ECDH (widely supported)
  • secp384r1: NIST P-384 ECDH (higher security margin)
  • x448: Curve448 ECDH (highest security)

Workflow

  1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)
  2. Generate or obtain TLS certificate and private key
  3. Configure server to use TLS 1.3 cipher suites
  4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)
  5. Set preferred key exchange groups
  6. Enable OCSP stapling for certificate validation
  7. Test configuration with openssl s_client and testssl.sh
  8. Configure HSTS header for HTTP Strict Transport Security

Security Considerations

  • 0-RTT data is vulnerable to replay attacks; limit to idempotent requests
  • Always include TLS 1.2 fallback if legacy client support is required
  • Use ECDSA certificates for better performance (vs RSA)
  • Enable OCSP stapling to improve client certificate validation
  • Set HSTS header with long max-age and includeSubDomains
  • Monitor for certificate transparency logs

Validation Criteria

  • TLS 1.3 handshake completes successfully
  • Only approved cipher suites are offered
  • Perfect forward secrecy is enforced
  • TLS 1.0 and 1.1 are rejected
  • OCSP stapling is functional
  • Certificate chain is valid and complete
  • testssl.sh reports no vulnerabilities

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

  • Assessing saved credential exposure in authorized tests
  • Examining collected DPAPI files offline
  • Reviewing protected browser and RDP credentials
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

  • Assessing risky permissions identified in BloodHound
  • Validating account takeover without resetting a password
  • Generating directory change records during security exercises
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

  • Define the assessment scope for systems handling controlled information
  • Calculate an SPRS score and prioritize unmet security requirements
  • Prepare security plans, remediation milestones, and assessment evidence
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

  • Preserving a suspect drive before investigation
  • Creating evidence copies of USB devices or memory cards
  • Verifying that a disk image matches its source
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

  • Auditing excessive Active Directory permissions
  • Investigating privilege escalation paths from ordinary accounts
  • Reporting affected objects and permission remediation recommendations
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

  • Triage suspicious APK files without running them
  • Inspect dangerous permission combinations and suspicious API calls
  • Extract network indicators for malware detection rules
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

See all skills by mukul975

Report a problem with this skill