mukul975/configuring-tls-1-3-for-secure-communications
skills/configuring-tls-1-3-for-secure-communications/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mukul975/cyber-skills configuring-tls-1-3-for-secure-communicationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 6, 2026, 2:58 AM265.1s7 files scanned
SKILL.md
- name:
- configuring-tls-1-3-for-secure-communications
- description:
- Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and
- domain:
- cybersecurity
- subdomain:
- cryptography
- version:
- 1.0
- author:
- mahipal
- license:
- Apache-2.0
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 Suite | Key Exchange | Authentication | Encryption | Hash | |-------------|-------------|----------------|------------|------| | TLS_AES_256_GCM_SHA384 | ECDHE/DHE | Certificate | AES-256-GCM | SHA-384 | | TLS_AES_128_GCM_SHA256 | ECDHE/DHE | Certificate | AES-128-GCM | SHA-256 | | TLS_CHACHA20_POLY1305_SHA256 | ECDHE/DHE | Certificate | ChaCha20-Poly1305 | SHA-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
- Verify OpenSSL version supports TLS 1.3 (1.1.1+)
- Generate or obtain TLS certificate and private key
- Configure server to use TLS 1.3 cipher suites
- Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)
- Set preferred key exchange groups
- Enable OCSP stapling for certificate validation
- Test configuration with openssl s_client and testssl.sh
- 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
Related Skills
mukul975/detecting-pass-the-hash-attacks
development
VerifiedTrustedCommunity
Detect Pass-the-Hash (T1550.002) attacks by analyzing NTLM authentication patterns, flagging Type 3 logons using NTLM where Kerberos would be expected, and correlating with credential-dumping indicators. Use when threat hunting for lateral movement via stolen NTLM hashes, triaging EDR/SIEM alerts on suspicious NTLM logons, scoping compromise during incident response, or validating detection coverage in a purple team exercise.
31,851SKILL.mdUpdated Sep 1, 2026
mukul975/detecting-oauth-token-theft
testing
VerifiedTrustedCommunity
Detect and respond to OAuth token theft and replay in Microsoft Entra ID (Azure AD), covering access token theft, refresh token replay, Primary Refresh Token (PRT) abuse, pass-the-cookie attacks, and Token Protection conditional access policies. Use for impossible-travel or anomalous token-usage alerts, suspected session hijacking, sign-in log analysis, or configuring token-binding defenses in Azure/M365.
31,851SKILL.mdUpdated Sep 1, 2026
mukul975/detecting-ntlm-relay-with-event-correlation
development
VerifiedTrustedCommunity
Detect NTLM relay attacks (T1557.001) by correlating Windows Event 4624 LogonType 3 for IP-to-hostname mismatches, identifying Responder/LLMNR poisoning artifacts, auditing SMB/LDAP signing, and flagging NTLMv2-to-NTLMv1 downgrades. Use for hunting credential relay in NTLM-enabled AD, investigating auth-source anomalies, building SIEM correlation rules, or responding to PetitPotam/DFSCoerce/PrinterBug alerts.
31,851SKILL.mdUpdated Sep 1, 2026
mukul975/detecting-network-scanning-with-ids-signatures
data-ai
VerifiedTrustedCommunity
Detect network reconnaissance and port scanning using Suricata and Snort IDS signatures, threshold-based detection rules, and traffic anomaly analysis to identify Nmap, Masscan, and custom scanning activity.
31,851SKILL.mdUpdated Sep 1, 2026