[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GVGJWPJCPN72BQDF6P86B":3,"skill-same:01M71GVGJWPJCPN72BQDF6P86B":106},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":79,"commitSha":80,"skillDirectory":81,"forksCount":14,"repositoryHtmlUrl":82,"repositoryHomepageUrl":6,"ownerHtmlUrl":83,"ownerBlogUrl":6,"ownerDescription":84,"updatedAt":85,"install":86,"resources":99},"01M71GVGJWPJCPN72BQDF6P86B","framework-owasp-audit",null,"This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI\u002FCD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab CI.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fweb-application\u002Fframework\u002Fowasp\u002Faudit\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"owasp","framework owasp audit","audit","framework","gitlab","secure","cybersecurity","actions","ci","github actions","testing","tuning","owasp-zap","api","Bash","gitlab ci","read","zed","CI\u002FCD","application security","2026-11-10 10:12:30",false,"---\nname: framework-owasp-audit\ndescription: This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI\u002FCD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab CI.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- devsecops\n- cicd\n- dast\n- owasp-zap\n- dynamic-testing\n- secure-sdlc\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1046\n- T1189\n- T1190\ncwe:\n- CWE-200\n- CWE-352\n- CWE-79\n- CWE-89\ncapec: []\n---\n\n# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: framework-owasp-audit\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n","# Integrating DAST with OWASP ZAP in Pipeline\n\n## When to Use\n\n- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations\n- When SAST alone is insufficient and runtime behavior testing is required\n- When compliance mandates dynamic security testing of web applications before production\n- When testing APIs (REST\u002FGraphQL) for authentication, authorization, and injection flaws\n- When establishing continuous DAST scanning in staging environments before production deployment\n\n**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).\n\n## Prerequisites\n\n- OWASP ZAP Docker image or installed locally (zaproxy\u002Fzap-stable or zaproxy\u002Faction-*)\n- Running target application accessible from the CI\u002FCD runner (staging URL or Docker service)\n- ZAP scan rules configuration (optional, for tuning)\n- OpenAPI\u002FSwagger specification for API scanning (optional)\n\n## Workflow\n\n### Step 1: Configure ZAP Baseline Scan in GitHub Actions\n\n```yaml\n# .github\u002Fworkflows\u002Fdast-scan.yml\nname: framework-owasp-audit\n\non:\n  deployment_status:\n  workflow_dispatch:\n    inputs:\n      target_url:\n        description: 'Target URL to scan'\n        required: true\n\njobs:\n  zap-baseline:\n    name: ZAP Baseline Scan\n    runs-on: ubuntu-latest\n    services:\n      webapp:\n        image: ${{ github.repository }}:${{ github.sha }}\n        ports:\n          - 8080:8080\n        options: --health-cmd=\"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth\" --health-interval=10s --health-timeout=5s --health-retries=5\n\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Baseline Scan\n        uses: zaproxy\u002Faction-baseline@v0.12.0\n        with:\n          target: 'http:\u002F\u002Fwebapp:8080'\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j'\n          allow_issue_writing: false\n\n      - name: Upload ZAP Report\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-baseline-report\n          path: report_html.html\n```\n\n### Step 2: Configure ZAP Full Scan for Comprehensive Testing\n\n```yaml\n  zap-full-scan:\n    name: ZAP Full Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP Full Scan\n        uses: zaproxy\u002Faction-full-scan@v0.12.0\n        with:\n          target: ${{ github.event.inputs.target_url || 'https:\u002F\u002Fstaging.example.com' }}\n          rules_file_name: '.zap\u002Frules.tsv'\n          cmd_options: '-a -j -T 60'\n\n      - name: Upload Reports\n        if: always()\n        uses: actions\u002Fupload-artifact@v4\n        with:\n          name: zap-full-report\n          path: |\n            report_html.html\n            report_json.json\n```\n\n### Step 3: Configure API Scan with OpenAPI Specification\n\n```yaml\n  zap-api-scan:\n    name: ZAP API Scan\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: ZAP API Scan\n        uses: zaproxy\u002Faction-api-scan@v0.12.0\n        with:\n          target: 'https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fopenapi.json'\n          format: openapi\n          rules_file_name: '.zap\u002Fapi-rules.tsv'\n          cmd_options: '-a -j'\n```\n\n### Step 4: Configure ZAP Scan Rules\n\n```tsv\n# .zap\u002Frules.tsv\n# Rule ID\tAction (IGNORE\u002FWARN\u002FFAIL)\tDescription\n10003\tIGNORE\t# Vulnerable JS Library (handled by SCA)\n10015\tWARN\t# Incomplete or No Cache-control Header\n10021\tFAIL\t# X-Content-Type-Options Missing\n10035\tFAIL\t# Strict-Transport-Security Missing\n10038\tFAIL\t# Content Security Policy Missing\n10098\tIGNORE\t# Cross-Domain Misconfiguration (CDN)\n40012\tFAIL\t# Cross Site Scripting (Reflected)\n40014\tFAIL\t# Cross Site Scripting (Persistent)\n40018\tFAIL\t# SQL Injection\n40019\tFAIL\t# SQL Injection (MySQL)\n40032\tFAIL\t# .htaccess Information Leak\n90033\tFAIL\t# Loosely Scoped Cookie\n```\n\n### Step 5: Run ZAP with Docker Compose for Local Testing\n\n```yaml\n# docker-compose.zap.yml\nservices:\n  webapp:\n    build: .\n    ports:\n      - \"8080:8080\"\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 10s\n      retries: 5\n\n  zap:\n    image: zaproxy\u002Fzap-stable:latest\n    depends_on:\n      webapp:\n        condition: service_healthy\n    command: >\n      zap-baseline.py\n        -t http:\u002F\u002Fwebapp:8080\n        -r \u002Fzap\u002Fwrk\u002Freport.html\n        -J \u002Fzap\u002Fwrk\u002Freport.json\n        -c \u002Fzap\u002Fwrk\u002Frules.tsv\n        -I\n    volumes:\n      - .\u002Fzap-reports:\u002Fzap\u002Fwrk\n      - .\u002F.zap\u002Frules.tsv:\u002Fzap\u002Fwrk\u002Frules.tsv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| DAST | Dynamic Application Security Testing — tests running applications by sending requests and analyzing responses |\n| Baseline Scan | Quick passive scan that spiders the application without active attacks, suitable for CI\u002FCD |\n| Full Scan | Active scan including attack payloads for XSS, SQLi, and other injection vulnerabilities |\n| API Scan | Targeted scan using OpenAPI\u002FSwagger specs to test all documented API endpoints |\n| Spider | ZAP's crawler that discovers application pages and endpoints by following links |\n| Active Scan | Phase where ZAP sends attack payloads to discovered endpoints to find exploitable vulnerabilities |\n| Passive Scan | Analysis of HTTP responses for security headers, cookies, and information disclosure without sending attacks |\n| Scan Policy | Configuration defining which attack types to enable and their intensity levels |\n\n## Tools & Systems\n\n- **OWASP ZAP**: Open-source web application security scanner for DAST testing\n- **zaproxy\u002Faction-baseline**: GitHub Action for ZAP passive baseline scanning\n- **zaproxy\u002Faction-full-scan**: GitHub Action for ZAP active full scanning\n- **zaproxy\u002Faction-api-scan**: GitHub Action for API-focused scanning with OpenAPI support\n- **Nuclei**: Alternative vulnerability scanner with template-based detection for CI\u002FCD integration\n\n## Common Scenarios\n\n### Scenario: Integrating DAST into a Staging Deployment Pipeline\n\n**Context**: A team deploys to staging before production and needs automated DAST scanning between stages to catch runtime vulnerabilities.\n\n**Approach**:\n1. Add a DAST job in the pipeline that triggers after successful staging deployment\n2. Run ZAP baseline scan first for quick passive feedback (2-5 minutes)\n3. Follow with a targeted API scan using the application's OpenAPI specification\n4. Configure rules.tsv to FAIL on critical findings (XSS, SQLi) and WARN on headers\u002Fcookies\n5. Upload ZAP reports as pipeline artifacts for review\n6. Block production deployment if any FAIL-level findings are detected\n7. Schedule weekly full scans against staging for deeper coverage\n\n**Pitfalls**: ZAP full scans can take 30+ minutes and may overwhelm staging servers with attack traffic. Use baseline scans in CI and full scans on schedule. Running DAST against production without coordination can trigger WAF blocks and incident alerts.\n\n## Output Format\n\n```\nZAP DAST Scan Report\n======================\nTarget: https:\u002F\u002Fstaging.example.com\nScan Type: Baseline + API\nDate: 2026-02-23\nDuration: 4m 32s\n\nFINDINGS:\n  FAIL: 3\n  WARN: 7\n  INFO: 12\n  PASS: 45\n\nFAILING ALERTS:\n  [HIGH] 40012 - Cross Site Scripting (Reflected)\n    URL: https:\u002F\u002Fstaging.example.com\u002Fsearch?q=\u003Cscript>\n    Method: GET\n    Evidence: \u003Cscript>alert(1)\u003C\u002Fscript>\n\n  [MEDIUM] 10021 - X-Content-Type-Options Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002Fapi\u002Fv1\u002F*\n    Evidence: Response header missing\n\n  [MEDIUM] 10035 - Strict-Transport-Security Missing\n    URL: https:\u002F\u002Fstaging.example.com\u002F\n    Evidence: HSTS header not present\n\nQUALITY GATE: FAILED (1 HIGH, 2 MEDIUM findings)\n```\n",{"cwe":52,"name":5,"tags":57,"capec":63,"model":64,"tools":65,"domain":33,"maxTurns":69,"nist_csf":70,"subdomain":58,"description":7,"mitre_attack":75},[53,54,55,56],"CWE-200","CWE-352","CWE-79","CWE-89",[58,59,60,39,61,62],"devsecops","cicd","dast","dynamic-testing","secure-sdlc",[],"sonnet",[66,41,67,68],"Read","Glob","Grep",20,[71,72,73,74],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[76,77,78],"T1046","T1189","T1190","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fweb-application\u002Fframework\u002Fowasp\u002Faudit","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":87,"prompt":97,"zipAvailable":98},[88,91,94],{"tool":89,"command":90},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill framework-owasp-audit",{"tool":92,"command":93},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill framework-owasp-audit",{"tool":95,"command":96},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill framework-owasp-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fweb-application\u002Fframework\u002Fowasp\u002Faudit\u002FSKILL.md",true,[100],{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"index.json","REFERENCE","参考文档",694,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fweb-application\u002Fframework\u002Fowasp\u002Faudit\u002Findex.json",[107,132,153,174,196,211],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":47},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,33,131],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":47},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[139,114,140,117,141,142,143,33,41,144,145,146,147,148,119,149,150,43,151,152],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":47},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[160,161,162,163,164,165,33,41,166,144,167,168,119,43,169,170,171,172,173,64],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":47},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[115,181,182,183,184,185,186,120,187,33,131,188,189,190,191,192,193,194,195,119],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":47},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[203,204,115,205,183,185,206,120,207,187,33,131,144,40,208,209,210,195,119,121],"thread","processes thread injection detect","injection","memory","process-injection","apc-injection","thread-injection","nt-api",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":47},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[218,115,183,219,206,120,220,221,33,131,222,223,224,225,226,227,119,121,228,229],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]