[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE62KYYEC3ZCMXPRS234HD":3,"skill-same:01M6AE62KYYEC3ZCMXPRS234HD":120},{"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":26,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AE62KYYEC3ZCMXPRS234HD","configuring-tls-1-3-for-secure-communications",null,"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.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"secure","configuring tls 1 3 for secure communications","testing","security","cybersecurity","vulnerabilities","pr","server","ssl","network","network-security","hardening","cryptography","openssl","tls","transport-security","2026-11-10 10:12:30",false,"---\nname: configuring-tls-1-3-for-secure-communications\ndescription: Configures TLS 1.3 (RFC 8446) on servers, covering cipher suite and\n  key-exchange group selection, and validates the resulting configuration with openssl\n  s_client and testssl.sh. Use when deploying or hardening TLS 1.3 for secure communications,\n  or when testing a server for common TLS misconfigurations and vulnerabilities.\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- tls\n- ssl\n- transport-security\n- network-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1557\n- T1040\n- T1573.002\n- T1539\n- T1556.004\n---\n# Configuring TLS 1.3 for Secure Communications\n\n## Overview\n\nTLS 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.\n\n\n## When to Use\n\n- When deploying or configuring configuring tls 1 3 for secure communications capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure TLS 1.3 on nginx and Apache web servers\n- Implement TLS 1.3 in Python applications using the ssl module\n- Validate TLS configurations with openssl and testssl.sh\n- Understand TLS 1.3 cipher suites and key exchange mechanisms\n- Configure 0-RTT early data with appropriate protections\n- Disable legacy TLS versions (1.0, 1.1) and weak cipher suites\n\n## Key Concepts\n\n### TLS 1.3 Cipher Suites\n\n| Cipher Suite | Key Exchange | Authentication | Encryption | Hash |\n|-------------|-------------|----------------|------------|------|\n| TLS_AES_256_GCM_SHA384 | ECDHE\u002FDHE | Certificate | AES-256-GCM | SHA-384 |\n| TLS_AES_128_GCM_SHA256 | ECDHE\u002FDHE | Certificate | AES-128-GCM | SHA-256 |\n| TLS_CHACHA20_POLY1305_SHA256 | ECDHE\u002FDHE | Certificate | ChaCha20-Poly1305 | SHA-256 |\n\n### TLS 1.3 vs 1.2 Improvements\n\n- **1-RTT Handshake**: Full handshake completes in one round trip (vs 2 in TLS 1.2)\n- **0-RTT Resumption**: Resumed connections can send data immediately\n- **No RSA Key Exchange**: Only ephemeral Diffie-Hellman (mandatory PFS)\n- **Simplified Cipher Suites**: Removed CBC, RC4, 3DES, static RSA, SHA-1\n- **Encrypted Handshake**: Server certificate is encrypted after ServerHello\n\n### Key Exchange Groups\n\n- **x25519**: Curve25519 ECDH (preferred, fast)\n- **secp256r1**: NIST P-256 ECDH (widely supported)\n- **secp384r1**: NIST P-384 ECDH (higher security margin)\n- **x448**: Curve448 ECDH (highest security)\n\n## Workflow\n\n1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)\n2. Generate or obtain TLS certificate and private key\n3. Configure server to use TLS 1.3 cipher suites\n4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)\n5. Set preferred key exchange groups\n6. Enable OCSP stapling for certificate validation\n7. Test configuration with openssl s_client and testssl.sh\n8. Configure HSTS header for HTTP Strict Transport Security\n\n## Security Considerations\n\n- 0-RTT data is vulnerable to replay attacks; limit to idempotent requests\n- Always include TLS 1.2 fallback if legacy client support is required\n- Use ECDSA certificates for better performance (vs RSA)\n- Enable OCSP stapling to improve client certificate validation\n- Set HSTS header with long max-age and includeSubDomains\n- Monitor for certificate transparency logs\n\n## Validation Criteria\n\n- [ ] TLS 1.3 handshake completes successfully\n- [ ] Only approved cipher suites are offered\n- [ ] Perfect forward secrecy is enforced\n- [ ] TLS 1.0 and 1.1 are rejected\n- [ ] OCSP stapling is functional\n- [ ] Certificate chain is valid and complete\n- [ ] testssl.sh reports no vulnerabilities\n","# Configuring TLS 1.3 for Secure Communications\n\n## Overview\n\nTLS 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.\n\n\n## When to Use\n\n- When deploying or configuring configuring tls 1 3 for secure communications capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Configure TLS 1.3 on nginx and Apache web servers\n- Implement TLS 1.3 in Python applications using the ssl module\n- Validate TLS configurations with openssl and testssl.sh\n- Understand TLS 1.3 cipher suites and key exchange mechanisms\n- Configure 0-RTT early data with appropriate protections\n- Disable legacy TLS versions (1.0, 1.1) and weak cipher suites\n\n## Key Concepts\n\n### TLS 1.3 Cipher Suites\n\n| Cipher Suite | Key Exchange | Authentication | Encryption | Hash |\n|-------------|-------------|----------------|------------|------|\n| TLS_AES_256_GCM_SHA384 | ECDHE\u002FDHE | Certificate | AES-256-GCM | SHA-384 |\n| TLS_AES_128_GCM_SHA256 | ECDHE\u002FDHE | Certificate | AES-128-GCM | SHA-256 |\n| TLS_CHACHA20_POLY1305_SHA256 | ECDHE\u002FDHE | Certificate | ChaCha20-Poly1305 | SHA-256 |\n\n### TLS 1.3 vs 1.2 Improvements\n\n- **1-RTT Handshake**: Full handshake completes in one round trip (vs 2 in TLS 1.2)\n- **0-RTT Resumption**: Resumed connections can send data immediately\n- **No RSA Key Exchange**: Only ephemeral Diffie-Hellman (mandatory PFS)\n- **Simplified Cipher Suites**: Removed CBC, RC4, 3DES, static RSA, SHA-1\n- **Encrypted Handshake**: Server certificate is encrypted after ServerHello\n\n### Key Exchange Groups\n\n- **x25519**: Curve25519 ECDH (preferred, fast)\n- **secp256r1**: NIST P-256 ECDH (widely supported)\n- **secp384r1**: NIST P-384 ECDH (higher security margin)\n- **x448**: Curve448 ECDH (highest security)\n\n## Workflow\n\n1. Verify OpenSSL version supports TLS 1.3 (1.1.1+)\n2. Generate or obtain TLS certificate and private key\n3. Configure server to use TLS 1.3 cipher suites\n4. Disable TLS 1.0 and 1.1 (optionally keep 1.2 for compatibility)\n5. Set preferred key exchange groups\n6. Enable OCSP stapling for certificate validation\n7. Test configuration with openssl s_client and testssl.sh\n8. Configure HSTS header for HTTP Strict Transport Security\n\n## Security Considerations\n\n- 0-RTT data is vulnerable to replay attacks; limit to idempotent requests\n- Always include TLS 1.2 fallback if legacy client support is required\n- Use ECDSA certificates for better performance (vs RSA)\n- Enable OCSP stapling to improve client certificate validation\n- Set HSTS header with long max-age and includeSubDomains\n- Monitor for certificate transparency logs\n\n## Validation Criteria\n\n- [ ] TLS 1.3 handshake completes successfully\n- [ ] Only approved cipher suites are offered\n- [ ] Perfect forward secrecy is enforced\n- [ ] TLS 1.0 and 1.1 are rejected\n- [ ] OCSP stapling is functional\n- [ ] Certificate chain is valid and complete\n- [ ] testssl.sh reports no vulnerabilities\n",{"name":5,"tags":48,"author":49,"domain":31,"license":15,"version":50,"nist_csf":51,"subdomain":39,"description":7,"mitre_attack":55},[39,41,35,42,37],"mahipal","1.0",[52,53,54],"PR.DS-01","PR.DS-02","PR.DS-10",[56,57,58,59,60],"T1557","T1040","T1573.002","T1539","T1556.004","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fconfiguring-tls-1-3-for-secure-communications",4395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications",{"tool":77,"command":78},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications",{"tool":80,"command":81},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill configuring-tls-1-3-for-secure-communications","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FSKILL.md",true,[85,91,96,102,106,110,116],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate.md","ASSET","资产文件",2127,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fassets\u002Ftemplate.md",{"path":92,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002FLICENSE",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fapi-reference.md","REFERENCE","参考文档",1481,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fapi-reference.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstandards.md",2573,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fstandards.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fworkflows.md",2304,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Freferences\u002Fworkflows.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fagent.py","SCRIPT","脚本",5490,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fscripts\u002Fagent.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fprocess.py",14481,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fconfiguring-tls-1-3-for-secure-communications\u002Fscripts\u002Fprocess.py",[121,146,170,195,221,247],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":128,"publishedAt":43},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[127],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[129,130,131,132,30,31,133,134,33,135,136,137,138,139,140,141,142,143,144,145],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":43},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[152],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[154,142,155,156,30,157,31,33,158,159,160,161,162,163,164,165,166,167,168,169],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":178,"publishedAt":43},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[176,177],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[164,179,180,181,29,31,182,183,158,184,185,186,187,188,189,190,191,192,193,194],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":202,"publishedAt":43},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[201],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[203,204,205,31,206,207,208,209,210,211,212,213,214,215,216,217,161,218,219,220],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":228,"publishedAt":43},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[227],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[32,229,230,31,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246],"framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":251,"categories":252,"keywords":254,"publishedAt":43},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[253],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[30,255,31,256,257,258,259,260,261,262,263,190,264,191,265,266,267,268,269,270],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]