[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M733WJD2650KPFZ2SA6HBJW7":3,"skill-same:01M733WJD2650KPFZ2SA6HBJW7":90},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M733WJD2650KPFZ2SA6HBJW7","implementing-api-security-testing-with-42crunch",null,"Implement comprehensive API security testing using the 42Crunch platform to perform static audit and dynamic conformance scanning of OpenAPI specifications.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-api-security-testing-with-42crunch\ndescription: Implement comprehensive API security testing using the 42Crunch platform\n  to perform static audit and dynamic conformance scanning of OpenAPI specifications.\ndomain: cybersecurity\nsubdomain: api-security\ntags:\n- api-security\n- 42crunch\n- openapi\n- api-audit\n- api-scan\n- conformance-testing\n- shift-left\n- ci-cd-security\n- owasp-api-top-10\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1552.001\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Implementing API Security Testing with 42Crunch\n\n## Overview\n\n42Crunch is an API security platform that combines Shift-Left security testing with Shield-Right runtime protection. It provides API Audit for static security analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability detection, and API Protect for real-time threat prevention. The platform integrates into CI\u002FCD pipelines and IDEs to identify OWASP API Security Top 10 vulnerabilities before and after deployment.\n\n\n## When to Use\n\n- When deploying or configuring implementing api security testing with 42crunch 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- 42Crunch platform account (free tier available for evaluation)\n- OpenAPI Specification (OAS) v2.0, v3.0, or v3.1 definitions for target APIs\n- IDE with 42Crunch extension (VS Code, IntelliJ, or Eclipse)\n- CI\u002FCD pipeline (Jenkins, GitHub Actions, Azure DevOps, or GitLab CI)\n- Running API instance for dynamic scanning (conformance scan)\n- Node.js or Python environment for CLI tooling\n\n## Core Concepts\n\n### API Audit (Static Analysis)\n\nAPI Audit performs static security analysis of OpenAPI definitions without requiring a running API. It evaluates the specification against 300+ security checks organized into categories:\n\n**Security Score Categories:**\n- **Data Validation**: Schema definitions, parameter constraints, response validation\n- **Authentication**: Security scheme definitions, scope requirements\n- **Transport Security**: Server URL schemes, TLS requirements\n- **Error Handling**: Error response definitions, information leakage prevention\n\n**Running API Audit via VS Code Extension:**\n\n1. Install the 42Crunch extension from the VS Code marketplace\n2. Open an OpenAPI specification file (YAML or JSON)\n3. Click the security audit icon in the editor toolbar\n4. Review the security score (0-100) and individual findings\n5. Address issues using the inline remediation guidance\n\n**Example OpenAPI Definition with Security Controls:**\n\n```yaml\nopenapi: 3.0.3\ninfo:\n  title: Secure User API\n  version: 1.0.0\nservers:\n  - url: https:\u002F\u002Fapi.example.com\u002Fv1\n    description: Production server (HTTPS only)\nsecurity:\n  - BearerAuth: []\npaths:\n  \u002Fusers\u002F{userId}:\n    get:\n      operationId: getUserById\n      summary: Retrieve user by ID\n      parameters:\n        - name: userId\n          in: path\n          required: true\n          schema:\n            type: string\n            format: uuid\n            pattern: '^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$'\n            maxLength: 36\n      responses:\n        '200':\n          description: User details\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FUser'\n        '400':\n          description: Invalid request\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FError'\n        '401':\n          description: Unauthorized\n        '404':\n          description: User not found\ncomponents:\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: JWT\n  schemas:\n    User:\n      type: object\n      required:\n        - id\n        - email\n      properties:\n        id:\n          type: string\n          format: uuid\n          readOnly: true\n        email:\n          type: string\n          format: email\n          maxLength: 254\n        name:\n          type: string\n          maxLength: 100\n          pattern: '^[a-zA-Z\\s\\-]+$'\n      additionalProperties: false\n    Error:\n      type: object\n      required:\n        - code\n        - message\n      properties:\n        code:\n          type: integer\n          format: int32\n        message:\n          type: string\n          maxLength: 256\n      additionalProperties: false\n```\n\n### API Conformance Scan (Dynamic Testing)\n\nThe conformance scan dynamically tests a running API against its OpenAPI contract to detect runtime vulnerabilities including OWASP API Security Top 10 issues:\n\n**Scan v2 Configuration:**\n\n```yaml\n# 42c-conf.yaml\nversion: \"2.0\"\nscan:\n  target:\n    url: https:\u002F\u002Fapi.example.com\u002Fv1\n  authentication:\n    - type: bearer\n      token: \"${API_TOKEN}\"\n      in: header\n      name: Authorization\n  settings:\n    maxScanTime: 3600\n    requestsPerSecond: 10\n    followRedirects: false\n  tests:\n    owasp:\n      - bola\n      - bfla\n      - injection\n      - ssrf\n      - massAssignment\n      - excessiveDataExposure\n```\n\n**Running Conformance Scan via CLI:**\n\n```bash\n# Install the 42Crunch CLI\nnpm install -g @42crunch\u002Fcicd-cli\n\n# Run conformance scan\n42crunch-cli scan \\\n  --api-definition .\u002Fopenapi.yaml \\\n  --target-url https:\u002F\u002Fapi.example.com\u002Fv1 \\\n  --token $CRUNCH_TOKEN \\\n  --min-score 70 \\\n  --report-format sarif \\\n  --output scan-report.sarif\n```\n\n### CI\u002FCD Pipeline Integration\n\n**GitHub Actions Integration:**\n\n```yaml\nname: API Security Testing\non:\n  push:\n    paths:\n      - 'api\u002F**'\n      - 'openapi\u002F**'\njobs:\n  api-security:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: 42Crunch API Audit\n        uses: 42Crunch\u002Fapi-security-audit-action@v3\n        with:\n          api-token: ${{ secrets.CRUNCH_API_TOKEN }}\n          collection-name: \"my-api-collection\"\n          min-score: 75\n          upload-to-code-scanning: true\n\n      - name: 42Crunch Conformance Scan\n        if: github.ref == 'refs\u002Fheads\u002Fmain'\n        uses: 42Crunch\u002Fapi-conformance-scan@v1\n        with:\n          api-token: ${{ secrets.CRUNCH_API_TOKEN }}\n          target-url: ${{ secrets.STAGING_API_URL }}\n          scan-config: .\u002F42c-conf.yaml\n```\n\n**Jenkins Pipeline Integration:**\n\n```groovy\npipeline {\n    agent any\n    stages {\n        stage('API Security Audit') {\n            steps {\n                script {\n                    def auditResult = sh(\n                        script: '''\n                            42crunch-cli audit \\\n                              --api-definition openapi.yaml \\\n                              --token ${CRUNCH_TOKEN} \\\n                              --min-score 75 \\\n                              --report-format json \\\n                              --output audit-report.json\n                        ''',\n                        returnStatus: true\n                    )\n                    if (auditResult != 0) {\n                        error(\"API Security Audit failed - score below threshold\")\n                    }\n                }\n            }\n        }\n        stage('Conformance Scan') {\n            when { branch 'main' }\n            steps {\n                sh '''\n                    42crunch-cli scan \\\n                      --api-definition openapi.yaml \\\n                      --target-url ${STAGING_URL} \\\n                      --token ${CRUNCH_TOKEN} \\\n                      --scan-config 42c-conf.yaml\n                '''\n            }\n        }\n    }\n    post {\n        always {\n            archiveArtifacts artifacts: '*-report.*'\n            publishHTML([\n                reportDir: '.',\n                reportFiles: 'audit-report.html',\n                reportName: 'API Security Report'\n            ])\n        }\n    }\n}\n```\n\n### API Protect (Runtime Protection)\n\nAPI Protect deploys as a micro-gateway in front of API endpoints to enforce the OpenAPI contract at runtime:\n\n```yaml\n# api-protect-config.yaml\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  name: api-protect-config\ndata:\n  protection-config.json: |\n    {\n      \"apiDefinition\": \"\u002Fconfig\u002Fopenapi.yaml\",\n      \"enforcement\": {\n        \"validateRequests\": true,\n        \"validateResponses\": true,\n        \"blockOnFailure\": true,\n        \"logLevel\": \"warn\"\n      },\n      \"rateLimit\": {\n        \"enabled\": true,\n        \"requestsPerMinute\": 100,\n        \"burstSize\": 20\n      },\n      \"allowlist\": {\n        \"contentTypes\": [\"application\u002Fjson\"],\n        \"methods\": [\"GET\", \"POST\", \"PUT\", \"DELETE\"]\n      }\n    }\n```\n\n## Remediation Workflow\n\nWhen 42Crunch identifies issues, follow this remediation process:\n\n1. **Triage**: Review findings sorted by severity (Critical, High, Medium, Low)\n2. **Analyze**: Understand the specific security control missing from the OpenAPI definition\n3. **Fix**: Apply the recommended changes to the specification\n4. **Validate**: Re-run audit to confirm the score improvement\n5. **Deploy**: Push the updated specification through the CI\u002FCD pipeline\n\n**Common Audit Findings and Fixes:**\n\n| Finding | Severity | Fix |\n|---------|----------|-----|\n| No authentication defined | Critical | Add securitySchemes and security requirements |\n| Missing input validation | High | Add type, format, pattern, maxLength constraints |\n| Server URL uses HTTP | High | Change server URLs to HTTPS |\n| No error responses defined | Medium | Add 4xx and 5xx response definitions |\n| additionalProperties not restricted | Medium | Set additionalProperties: false on object schemas |\n| Missing rate limiting | Medium | Add x-rateLimit extension or use API Protect |\n\n## Key Security Checks\n\n42Crunch evaluates APIs against these critical security areas:\n\n- **BOLA Prevention**: Validates that object-level authorization patterns are defined\n- **BFLA Prevention**: Checks for function-level access control definitions\n- **Injection Prevention**: Ensures input parameters have proper type\u002Fformat\u002Fpattern constraints\n- **Data Exposure**: Verifies response schemas limit returned properties\n- **Security Misconfiguration**: Checks authentication schemes, transport security, CORS settings\n- **Mass Assignment**: Validates that request bodies use explicit property allowlists\n\n## References\n\n- 42Crunch API Security Platform: https:\u002F\u002F42crunch.com\u002Fapi-security-platform\u002F\n- 42Crunch Documentation: https:\u002F\u002Fdocs.42crunch.com\u002F\n- Microsoft Defender for Cloud 42Crunch Integration: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fdefender-for-cloud\u002Fonboarding-guide-42crunch\n- OWASP API Security Top 10 2023: https:\u002F\u002Fowasp.org\u002FAPI-Security\u002Feditions\u002F2023\u002Fen\u002F0x00-header\u002F\n- Jenkins Plugin for 42Crunch: https:\u002F\u002Fplugins.jenkins.io\u002F42crunch-security-audit\u002F\n","# Implementing API Security Testing with 42Crunch\n\n## Overview\n\n42Crunch is an API security platform that combines Shift-Left security testing with Shield-Right runtime protection. It provides API Audit for static security analysis of OpenAPI definitions, API Conformance Scan for dynamic vulnerability detection, and API Protect for real-time threat prevention. The platform integrates into CI\u002FCD pipelines and IDEs to identify OWASP API Security Top 10 vulnerabilities before and after deployment.\n\n\n## When to Use\n\n- When deploying or configuring implementing api security testing with 42crunch 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- 42Crunch platform account (free tier available for evaluation)\n- OpenAPI Specification (OAS) v2.0, v3.0, or v3.1 definitions for target APIs\n- IDE with 42Crunch extension (VS Code, IntelliJ, or Eclipse)\n- CI\u002FCD pipeline (Jenkins, GitHub Actions, Azure DevOps, or GitLab CI)\n- Running API instance for dynamic scanning (conformance scan)\n- Node.js or Python environment for CLI tooling\n\n## Core Concepts\n\n### API Audit (Static Analysis)\n\nAPI Audit performs static security analysis of OpenAPI definitions without requiring a running API. It evaluates the specification against 300+ security checks organized into categories:\n\n**Security Score Categories:**\n- **Data Validation**: Schema definitions, parameter constraints, response validation\n- **Authentication**: Security scheme definitions, scope requirements\n- **Transport Security**: Server URL schemes, TLS requirements\n- **Error Handling**: Error response definitions, information leakage prevention\n\n**Running API Audit via VS Code Extension:**\n\n1. Install the 42Crunch extension from the VS Code marketplace\n2. Open an OpenAPI specification file (YAML or JSON)\n3. Click the security audit icon in the editor toolbar\n4. Review the security score (0-100) and individual findings\n5. Address issues using the inline remediation guidance\n\n**Example OpenAPI Definition with Security Controls:**\n\n```yaml\nopenapi: 3.0.3\ninfo:\n  title: Secure User API\n  version: 1.0.0\nservers:\n  - url: https:\u002F\u002Fapi.example.com\u002Fv1\n    description: Production server (HTTPS only)\nsecurity:\n  - BearerAuth: []\npaths:\n  \u002Fusers\u002F{userId}:\n    get:\n      operationId: getUserById\n      summary: Retrieve user by ID\n      parameters:\n        - name: userId\n          in: path\n          required: true\n          schema:\n            type: string\n            format: uuid\n            pattern: '^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$'\n            maxLength: 36\n      responses:\n        '200':\n          description: User details\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FUser'\n        '400':\n          description: Invalid request\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FError'\n        '401':\n          description: Unauthorized\n        '404':\n          description: User not found\ncomponents:\n  securitySchemes:\n    BearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: JWT\n  schemas:\n    User:\n      type: object\n      required:\n        - id\n        - email\n      properties:\n        id:\n          type: string\n          format: uuid\n          readOnly: true\n        email:\n          type: string\n          format: email\n          maxLength: 254\n        name:\n          type: string\n          maxLength: 100\n          pattern: '^[a-zA-Z\\s\\-]+$'\n      additionalProperties: false\n    Error:\n      type: object\n      required:\n        - code\n        - message\n      properties:\n        code:\n          type: integer\n          format: int32\n        message:\n          type: string\n          maxLength: 256\n      additionalProperties: false\n```\n\n### API Conformance Scan (Dynamic Testing)\n\nThe conformance scan dynamically tests a running API against its OpenAPI contract to detect runtime vulnerabilities including OWASP API Security Top 10 issues:\n\n**Scan v2 Configuration:**\n\n```yaml\n# 42c-conf.yaml\nversion: \"2.0\"\nscan:\n  target:\n    url: https:\u002F\u002Fapi.example.com\u002Fv1\n  authentication:\n    - type: bearer\n      token: \"${API_TOKEN}\"\n      in: header\n      name: Authorization\n  settings:\n    maxScanTime: 3600\n    requestsPerSecond: 10\n    followRedirects: false\n  tests:\n    owasp:\n      - bola\n      - bfla\n      - injection\n      - ssrf\n      - massAssignment\n      - excessiveDataExposure\n```\n\n**Running Conformance Scan via CLI:**\n\n```bash\n# Install the 42Crunch CLI\nnpm install -g @42crunch\u002Fcicd-cli\n\n# Run conformance scan\n42crunch-cli scan \\\n  --api-definition .\u002Fopenapi.yaml \\\n  --target-url https:\u002F\u002Fapi.example.com\u002Fv1 \\\n  --token $CRUNCH_TOKEN \\\n  --min-score 70 \\\n  --report-format sarif \\\n  --output scan-report.sarif\n```\n\n### CI\u002FCD Pipeline Integration\n\n**GitHub Actions Integration:**\n\n```yaml\nname: API Security Testing\non:\n  push:\n    paths:\n      - 'api\u002F**'\n      - 'openapi\u002F**'\njobs:\n  api-security:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n\n      - name: 42Crunch API Audit\n        uses: 42Crunch\u002Fapi-security-audit-action@v3\n        with:\n          api-token: ${{ secrets.CRUNCH_API_TOKEN }}\n          collection-name: \"my-api-collection\"\n          min-score: 75\n          upload-to-code-scanning: true\n\n      - name: 42Crunch Conformance Scan\n        if: github.ref == 'refs\u002Fheads\u002Fmain'\n        uses: 42Crunch\u002Fapi-conformance-scan@v1\n        with:\n          api-token: ${{ secrets.CRUNCH_API_TOKEN }}\n          target-url: ${{ secrets.STAGING_API_URL }}\n          scan-config: .\u002F42c-conf.yaml\n```\n\n**Jenkins Pipeline Integration:**\n\n```groovy\npipeline {\n    agent any\n    stages {\n        stage('API Security Audit') {\n            steps {\n                script {\n                    def auditResult = sh(\n                        script: '''\n                            42crunch-cli audit \\\n                              --api-definition openapi.yaml \\\n                              --token ${CRUNCH_TOKEN} \\\n                              --min-score 75 \\\n                              --report-format json \\\n                              --output audit-report.json\n                        ''',\n                        returnStatus: true\n                    )\n                    if (auditResult != 0) {\n                        error(\"API Security Audit failed - score below threshold\")\n                    }\n                }\n            }\n        }\n        stage('Conformance Scan') {\n            when { branch 'main' }\n            steps {\n                sh '''\n                    42crunch-cli scan \\\n                      --api-definition openapi.yaml \\\n                      --target-url ${STAGING_URL} \\\n                      --token ${CRUNCH_TOKEN} \\\n                      --scan-config 42c-conf.yaml\n                '''\n            }\n        }\n    }\n    post {\n        always {\n            archiveArtifacts artifacts: '*-report.*'\n            publishHTML([\n                reportDir: '.',\n                reportFiles: 'audit-report.html',\n                reportName: 'API Security Report'\n            ])\n        }\n    }\n}\n```\n\n### API Protect (Runtime Protection)\n\nAPI Protect deploys as a micro-gateway in front of API endpoints to enforce the OpenAPI contract at runtime:\n\n```yaml\n# api-protect-config.yaml\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  name: api-protect-config\ndata:\n  protection-config.json: |\n    {\n      \"apiDefinition\": \"\u002Fconfig\u002Fopenapi.yaml\",\n      \"enforcement\": {\n        \"validateRequests\": true,\n        \"validateResponses\": true,\n        \"blockOnFailure\": true,\n        \"logLevel\": \"warn\"\n      },\n      \"rateLimit\": {\n        \"enabled\": true,\n        \"requestsPerMinute\": 100,\n        \"burstSize\": 20\n      },\n      \"allowlist\": {\n        \"contentTypes\": [\"application\u002Fjson\"],\n        \"methods\": [\"GET\", \"POST\", \"PUT\", \"DELETE\"]\n      }\n    }\n```\n\n## Remediation Workflow\n\nWhen 42Crunch identifies issues, follow this remediation process:\n\n1. **Triage**: Review findings sorted by severity (Critical, High, Medium, Low)\n2. **Analyze**: Understand the specific security control missing from the OpenAPI definition\n3. **Fix**: Apply the recommended changes to the specification\n4. **Validate**: Re-run audit to confirm the score improvement\n5. **Deploy**: Push the updated specification through the CI\u002FCD pipeline\n\n**Common Audit Findings and Fixes:**\n\n| Finding | Severity | Fix |\n|---------|----------|-----|\n| No authentication defined | Critical | Add securitySchemes and security requirements |\n| Missing input validation | High | Add type, format, pattern, maxLength constraints |\n| Server URL uses HTTP | High | Change server URLs to HTTPS |\n| No error responses defined | Medium | Add 4xx and 5xx response definitions |\n| additionalProperties not restricted | Medium | Set additionalProperties: false on object schemas |\n| Missing rate limiting | Medium | Add x-rateLimit extension or use API Protect |\n\n## Key Security Checks\n\n42Crunch evaluates APIs against these critical security areas:\n\n- **BOLA Prevention**: Validates that object-level authorization patterns are defined\n- **BFLA Prevention**: Checks for function-level access control definitions\n- **Injection Prevention**: Ensures input parameters have proper type\u002Fformat\u002Fpattern constraints\n- **Data Exposure**: Verifies response schemas limit returned properties\n- **Security Misconfiguration**: Checks authentication schemes, transport security, CORS settings\n- **Mass Assignment**: Validates that request bodies use explicit property allowlists\n\n## References\n\n- 42Crunch API Security Platform: https:\u002F\u002F42crunch.com\u002Fapi-security-platform\u002F\n- 42Crunch Documentation: https:\u002F\u002Fdocs.42crunch.com\u002F\n- Microsoft Defender for Cloud 42Crunch Integration: https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fdefender-for-cloud\u002Fonboarding-guide-42crunch\n- OWASP API Security Top 10 2023: https:\u002F\u002Fowasp.org\u002FAPI-Security\u002Feditions\u002F2023\u002Fen\u002F0x00-header\u002F\n- Jenkins Plugin for 42Crunch: https:\u002F\u002Fplugins.jenkins.io\u002F42crunch-security-audit\u002F\n",{"name":5,"note":25,"tags":26,"author":36,"domain":37,"source":38,"license":15,"version":39,"nist_csf":40,"subdomain":27,"description":7,"mitre_attack":45,"source_commit":49},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32,33,34,35],"api-security","42crunch","openapi","api-audit","api-scan","conformance-testing","shift-left","ci-cd-security","owasp-api-top-10","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[41,42,43,44],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01",[46,47,48],"T1190","T1059.007","T1552.001","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-security-testing-with-42crunch",{"tool":66,"command":67},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-security-testing-with-42crunch",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-api-security-testing-with-42crunch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch\u002FSKILL.md",true,[74,78,84],{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",1551,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fagent.py","SCRIPT","脚本",5929,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-api-security-testing-with-42crunch\u002Fscripts\u002Fagent.py",[91,99,106,114,122,130],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]