mirror of https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git synced 2026-08-06 10:50:19 +03:00

Files

T

mukul975 cb8d79e068 Map all 754 skills to MITRE ATT&CK v19.1

- Add validated mitre_attack frontmatter to all 754 skills (286 distinct
  techniques), verified against MITRE ATT&CK v19.1 via the official
  mitreattack-python library: 0 revoked, deprecated, or invalid IDs
- Curate precise per-skill technique IDs for forensics, malware-analysis,
  threat-intel, and red-team skills (e.g. DCSync -> T1003.006,
  Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003)
- Reconcile v19.1 tactic restructuring: Defense Evasion split into
  Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.*
  family and T1070.001/.002 remapped to active equivalents (T1685.*)
- Normalize word-split tags across 35 skills (remove filename-derived
  stopword tags, add semantic cybersecurity tags)
- Add api-reference.md for 3 skills that were missing it
- Update README ATT&CK section with accurate v19.1 tactic distribution

2026-06-01 12:13:29 +02:00

4.1 KiB

Raw Blame History

name, description, domain, subdomain, tags, version, author, license, nist_csf, mitre_attack

name

description

domain

subdomain

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

4.1 KiB Raw Blame History