[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADY87SZS11KQARXZMP6KFD":3,"skill-same:01M6ADY87SZS11KQARXZMP6KFD":119},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6ADY87SZS11KQARXZMP6KFD","building-devsecops-pipeline-with-gitlab-ci",null,"Configure a GitLab CI\u002FCD pipeline that embeds SAST (Semgrep, SpotBugs, Gosec, Bandit, NodeJsScan), DAST, container scanning, dependency scanning, and secret detection via GitLab's managed security templates. Use when building a shift-left DevSecOps pipeline in GitLab, adding automated vulnerability scanning stages to .gitlab-ci.yml, or triaging scanner findings with GitLab Duo AI before deployment.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"building devsecops pipeline with gitlab ci","gitlab","ci","devsecops","pipeline","dependency scanning","cicd-security","secret-detection","dependency-scanning","container-scanning","dast","gitlab-ci","vulnerability scanning","deployment","pr","cybersecurity","security","sast","2026-11-10 10:12:30",false,"---\nname: building-devsecops-pipeline-with-gitlab-ci\ndescription: Configure a GitLab CI\u002FCD pipeline that embeds SAST (Semgrep, SpotBugs, Gosec, Bandit, NodeJsScan), DAST, container scanning, dependency scanning, and secret detection via GitLab's managed security templates. Use when building a shift-left DevSecOps pipeline in GitLab, adding automated vulnerability scanning stages to .gitlab-ci.yml, or triaging scanner findings with GitLab Duo AI before deployment.\ndomain: cybersecurity\nsubdomain: devsecops\ntags:\n- gitlab-ci\n- devsecops\n- sast\n- dast\n- container-scanning\n- dependency-scanning\n- secret-detection\n- cicd-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- GV.SC-07\n- ID.IM-04\n- PR.PS-04\nmitre_attack:\n- T1195.001\n- T1195.002\n- T1552.001\n- T1190\n- T1610\n---\n\n# Building DevSecOps Pipeline with GitLab CI\n\n## Overview\n\nGitLab provides an integrated DevSecOps platform that embeds security testing directly into the CI\u002FCD pipeline. By leveraging GitLab's built-in security scanners---SAST, DAST, container scanning, dependency scanning, secret detection, and license compliance---teams can shift security left, catching vulnerabilities during development rather than post-deployment. GitLab Duo AI assists with false positive detection for SAST vulnerabilities, helping security teams focus on genuine issues.\n\n\n## When to Use\n\n- When deploying or configuring building devsecops pipeline with gitlab ci 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- GitLab Ultimate license (required for full security scanner suite)\n- GitLab Runner configured (shared or self-hosted)\n- `.gitlab-ci.yml` pipeline configuration familiarity\n- Docker-in-Docker (DinD) or Kaniko for container builds\n- Application deployed to a staging environment for DAST scanning\n\n## Core Security Scanning Stages\n\n### Static Application Security Testing (SAST)\n\nSAST analyzes source code for vulnerabilities before compilation. GitLab supports 14+ languages using analyzers such as Semgrep, SpotBugs, Gosec, Bandit, and NodeJsScan. The simplest inclusion uses GitLab's managed templates.\n\n### Dynamic Application Security Testing (DAST)\n\nDAST tests running applications by simulating attack payloads against HTTP endpoints. It detects XSS, SQLi, CSRF, and other runtime vulnerabilities that static analysis cannot find. DAST requires a deployed, accessible target URL.\n\n### Container Scanning\n\nUses Trivy to scan Docker images for known CVEs in OS packages and application dependencies. Runs after the Docker build stage to gate images before they reach a registry.\n\n### Dependency Scanning\n\nInspects dependency manifests (package.json, requirements.txt, pom.xml, Gemfile.lock) for known vulnerable versions. Operates at the source code level, complementing container scanning.\n\n### Secret Detection\n\nScans commits for accidentally committed credentials, API keys, tokens, and private keys using pattern matching and entropy analysis. Runs on every commit to prevent secrets from reaching the repository.\n\n## Implementation\n\n### Complete Pipeline Configuration\n\n```yaml\n# .gitlab-ci.yml\n\nstages:\n  - build\n  - test\n  - security\n  - deploy-staging\n  - dast\n  - deploy-production\n\nvariables:\n  DOCKER_IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  SECURE_LOG_LEVEL: \"info\"\n\n# Include GitLab managed security templates\ninclude:\n  - template: Security\u002FSAST.gitlab-ci.yml\n  - template: Security\u002FSecret-Detection.gitlab-ci.yml\n  - template: Security\u002FDependency-Scanning.gitlab-ci.yml\n  - template: Security\u002FContainer-Scanning.gitlab-ci.yml\n  - template: DAST.gitlab-ci.yml\n  - template: Security\u002FLicense-Scanning.gitlab-ci.yml\n\nbuild:\n  stage: build\n  image: docker:24.0\n  services:\n    - docker:24.0-dind\n  variables:\n    DOCKER_TLS_CERTDIR: \"\u002Fcerts\"\n  script:\n    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY\n    - docker build -t $DOCKER_IMAGE .\n    - docker push $DOCKER_IMAGE\n  rules:\n    - if: $CI_COMMIT_BRANCH\n\nunit-tests:\n  stage: test\n  image: $DOCKER_IMAGE\n  script:\n    - npm ci\n    - npm run test:coverage\n  coverage: '\u002FLines\\s*:\\s*(\\d+\\.?\\d*)%\u002F'\n  artifacts:\n    reports:\n      junit: junit-report.xml\n      coverage_report:\n        coverage_format: cobertura\n        path: coverage\u002Fcobertura-coverage.xml\n\n# Override SAST to run in security stage\nsast:\n  stage: security\n  variables:\n    SAST_EXCLUDED_PATHS: \"spec,test,tests,tmp,node_modules\"\n    SEARCH_MAX_DEPTH: 10\n\n# Override container scanning\ncontainer_scanning:\n  stage: security\n  variables:\n    CS_IMAGE: $DOCKER_IMAGE\n    CS_SEVERITY_THRESHOLD: \"HIGH\"\n\n# Override dependency scanning\ndependency_scanning:\n  stage: security\n\n# Override secret detection\nsecret_detection:\n  stage: security\n\n# License compliance scanning\nlicense_scanning:\n  stage: security\n\ndeploy-staging:\n  stage: deploy-staging\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n staging\n    - kubectl rollout status deployment\u002Fapp -n staging --timeout=300s\n  environment:\n    name: staging\n    url: https:\u002F\u002Fstaging.example.com\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\n# DAST runs against deployed staging\ndast:\n  stage: dast\n  variables:\n    DAST_WEBSITE: https:\u002F\u002Fstaging.example.com\n    DAST_FULL_SCAN_ENABLED: \"true\"\n    DAST_BROWSER_SCAN: \"true\"\n  needs:\n    - deploy-staging\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ndeploy-production:\n  stage: deploy-production\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n production\n    - kubectl rollout status deployment\u002Fapp -n production --timeout=300s\n  environment:\n    name: production\n    url: https:\u002F\u002Fapp.example.com\n  when: manual\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n```\n\n### Security Approval Policies\n\nConfigure scan execution policies to enforce mandatory security scans:\n\n1. Navigate to Security & Compliance > Policies\n2. Create a \"Scan Execution Policy\" requiring SAST and secret detection on all branches\n3. Create a \"Merge Request Approval Policy\" requiring security team approval when critical vulnerabilities are detected\n\n### Custom SAST Ruleset Configuration\n\nCreate `.gitlab\u002Fsast-ruleset.toml` to customize analyzer behavior:\n\n```toml\n[semgrep]\n  [[semgrep.ruleset]]\n    dirs = [\"src\"]\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fcustom-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fowasp-top-ten\"\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fjava-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fjava\"\n```\n\n## Security Dashboard and Vulnerability Management\n\n### Vulnerability Report\n\nGitLab consolidates all scanner findings into a single Vulnerability Report accessible at Security & Compliance > Vulnerability Report. Each vulnerability includes:\n- Severity rating (Critical, High, Medium, Low, Info)\n- Scanner source (SAST, DAST, Container, Dependency, Secret)\n- Location in source code or image layer\n- Remediation guidance and suggested fixes\n- Status tracking (Detected, Confirmed, Dismissed, Resolved)\n\n### Merge Request Security Widget\n\nEvery merge request displays a security scanning widget showing:\n- New vulnerabilities introduced by the MR\n- Fixed vulnerabilities resolved by the MR\n- Comparison against the target branch baseline\n\n## Pipeline Optimization\n\n- **Parallel execution**: Security scanners run concurrently in the security stage\n- **Caching**: Use CI cache for dependency downloads to speed up scanning\n- **Incremental scanning**: SAST can scan only changed files using `SAST_INCREMENTAL: \"true\"`\n- **Fail conditions**: Set `allow_failure: false` on critical scanners to enforce quality gates\n\n## Monitoring and Metrics\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Pipeline security coverage | Percentage of projects with all scanners enabled | > 95% |\n| Critical vulnerability MTTR | Time from detection to resolution for critical findings | \u003C 48 hours |\n| False positive rate | Percentage of dismissed-as-false-positive findings | \u003C 15% |\n| Secret detection block rate | Percentage of secret commits blocked by push rules | > 99% |\n\n## References\n\n- [GitLab Security Scanning Documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002F)\n- [GitLab SAST Analyzers](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fsast\u002F)\n- [GitLab DAST Configuration](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fdast\u002F)\n- [GitLab Security Policies](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fpolicies\u002F)\n- [GitLab Vulnerability Management](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fvulnerability_report\u002F)\n","# Building DevSecOps Pipeline with GitLab CI\n\n## Overview\n\nGitLab provides an integrated DevSecOps platform that embeds security testing directly into the CI\u002FCD pipeline. By leveraging GitLab's built-in security scanners---SAST, DAST, container scanning, dependency scanning, secret detection, and license compliance---teams can shift security left, catching vulnerabilities during development rather than post-deployment. GitLab Duo AI assists with false positive detection for SAST vulnerabilities, helping security teams focus on genuine issues.\n\n\n## When to Use\n\n- When deploying or configuring building devsecops pipeline with gitlab ci 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- GitLab Ultimate license (required for full security scanner suite)\n- GitLab Runner configured (shared or self-hosted)\n- `.gitlab-ci.yml` pipeline configuration familiarity\n- Docker-in-Docker (DinD) or Kaniko for container builds\n- Application deployed to a staging environment for DAST scanning\n\n## Core Security Scanning Stages\n\n### Static Application Security Testing (SAST)\n\nSAST analyzes source code for vulnerabilities before compilation. GitLab supports 14+ languages using analyzers such as Semgrep, SpotBugs, Gosec, Bandit, and NodeJsScan. The simplest inclusion uses GitLab's managed templates.\n\n### Dynamic Application Security Testing (DAST)\n\nDAST tests running applications by simulating attack payloads against HTTP endpoints. It detects XSS, SQLi, CSRF, and other runtime vulnerabilities that static analysis cannot find. DAST requires a deployed, accessible target URL.\n\n### Container Scanning\n\nUses Trivy to scan Docker images for known CVEs in OS packages and application dependencies. Runs after the Docker build stage to gate images before they reach a registry.\n\n### Dependency Scanning\n\nInspects dependency manifests (package.json, requirements.txt, pom.xml, Gemfile.lock) for known vulnerable versions. Operates at the source code level, complementing container scanning.\n\n### Secret Detection\n\nScans commits for accidentally committed credentials, API keys, tokens, and private keys using pattern matching and entropy analysis. Runs on every commit to prevent secrets from reaching the repository.\n\n## Implementation\n\n### Complete Pipeline Configuration\n\n```yaml\n# .gitlab-ci.yml\n\nstages:\n  - build\n  - test\n  - security\n  - deploy-staging\n  - dast\n  - deploy-production\n\nvariables:\n  DOCKER_IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA\n  SECURE_LOG_LEVEL: \"info\"\n\n# Include GitLab managed security templates\ninclude:\n  - template: Security\u002FSAST.gitlab-ci.yml\n  - template: Security\u002FSecret-Detection.gitlab-ci.yml\n  - template: Security\u002FDependency-Scanning.gitlab-ci.yml\n  - template: Security\u002FContainer-Scanning.gitlab-ci.yml\n  - template: DAST.gitlab-ci.yml\n  - template: Security\u002FLicense-Scanning.gitlab-ci.yml\n\nbuild:\n  stage: build\n  image: docker:24.0\n  services:\n    - docker:24.0-dind\n  variables:\n    DOCKER_TLS_CERTDIR: \"\u002Fcerts\"\n  script:\n    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY\n    - docker build -t $DOCKER_IMAGE .\n    - docker push $DOCKER_IMAGE\n  rules:\n    - if: $CI_COMMIT_BRANCH\n\nunit-tests:\n  stage: test\n  image: $DOCKER_IMAGE\n  script:\n    - npm ci\n    - npm run test:coverage\n  coverage: '\u002FLines\\s*:\\s*(\\d+\\.?\\d*)%\u002F'\n  artifacts:\n    reports:\n      junit: junit-report.xml\n      coverage_report:\n        coverage_format: cobertura\n        path: coverage\u002Fcobertura-coverage.xml\n\n# Override SAST to run in security stage\nsast:\n  stage: security\n  variables:\n    SAST_EXCLUDED_PATHS: \"spec,test,tests,tmp,node_modules\"\n    SEARCH_MAX_DEPTH: 10\n\n# Override container scanning\ncontainer_scanning:\n  stage: security\n  variables:\n    CS_IMAGE: $DOCKER_IMAGE\n    CS_SEVERITY_THRESHOLD: \"HIGH\"\n\n# Override dependency scanning\ndependency_scanning:\n  stage: security\n\n# Override secret detection\nsecret_detection:\n  stage: security\n\n# License compliance scanning\nlicense_scanning:\n  stage: security\n\ndeploy-staging:\n  stage: deploy-staging\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n staging\n    - kubectl rollout status deployment\u002Fapp -n staging --timeout=300s\n  environment:\n    name: staging\n    url: https:\u002F\u002Fstaging.example.com\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\n# DAST runs against deployed staging\ndast:\n  stage: dast\n  variables:\n    DAST_WEBSITE: https:\u002F\u002Fstaging.example.com\n    DAST_FULL_SCAN_ENABLED: \"true\"\n    DAST_BROWSER_SCAN: \"true\"\n  needs:\n    - deploy-staging\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n\ndeploy-production:\n  stage: deploy-production\n  image: bitnami\u002Fkubectl:latest\n  script:\n    - kubectl set image deployment\u002Fapp app=$DOCKER_IMAGE -n production\n    - kubectl rollout status deployment\u002Fapp -n production --timeout=300s\n  environment:\n    name: production\n    url: https:\u002F\u002Fapp.example.com\n  when: manual\n  rules:\n    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH\n```\n\n### Security Approval Policies\n\nConfigure scan execution policies to enforce mandatory security scans:\n\n1. Navigate to Security & Compliance > Policies\n2. Create a \"Scan Execution Policy\" requiring SAST and secret detection on all branches\n3. Create a \"Merge Request Approval Policy\" requiring security team approval when critical vulnerabilities are detected\n\n### Custom SAST Ruleset Configuration\n\nCreate `.gitlab\u002Fsast-ruleset.toml` to customize analyzer behavior:\n\n```toml\n[semgrep]\n  [[semgrep.ruleset]]\n    dirs = [\"src\"]\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fcustom-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fowasp-top-ten\"\n\n  [[semgrep.passthrough]]\n    type = \"url\"\n    target = \"\u002Fsgrep-rules\u002Fjava-rules.yml\"\n    value = \"https:\u002F\u002Fsemgrep.dev\u002Fp\u002Fjava\"\n```\n\n## Security Dashboard and Vulnerability Management\n\n### Vulnerability Report\n\nGitLab consolidates all scanner findings into a single Vulnerability Report accessible at Security & Compliance > Vulnerability Report. Each vulnerability includes:\n- Severity rating (Critical, High, Medium, Low, Info)\n- Scanner source (SAST, DAST, Container, Dependency, Secret)\n- Location in source code or image layer\n- Remediation guidance and suggested fixes\n- Status tracking (Detected, Confirmed, Dismissed, Resolved)\n\n### Merge Request Security Widget\n\nEvery merge request displays a security scanning widget showing:\n- New vulnerabilities introduced by the MR\n- Fixed vulnerabilities resolved by the MR\n- Comparison against the target branch baseline\n\n## Pipeline Optimization\n\n- **Parallel execution**: Security scanners run concurrently in the security stage\n- **Caching**: Use CI cache for dependency downloads to speed up scanning\n- **Incremental scanning**: SAST can scan only changed files using `SAST_INCREMENTAL: \"true\"`\n- **Fail conditions**: Set `allow_failure: false` on critical scanners to enforce quality gates\n\n## Monitoring and Metrics\n\n| Metric | Description | Target |\n|--------|-------------|--------|\n| Pipeline security coverage | Percentage of projects with all scanners enabled | > 95% |\n| Critical vulnerability MTTR | Time from detection to resolution for critical findings | \u003C 48 hours |\n| False positive rate | Percentage of dismissed-as-false-positive findings | \u003C 15% |\n| Secret detection block rate | Percentage of secret commits blocked by push rules | > 99% |\n\n## References\n\n- [GitLab Security Scanning Documentation](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002F)\n- [GitLab SAST Analyzers](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fsast\u002F)\n- [GitLab DAST Configuration](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fdast\u002F)\n- [GitLab Security Policies](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fpolicies\u002F)\n- [GitLab Vulnerability Management](https:\u002F\u002Fdocs.gitlab.com\u002Fee\u002Fuser\u002Fapplication_security\u002Fvulnerability_report\u002F)\n",{"name":5,"tags":42,"author":43,"domain":34,"license":15,"version":44,"nist_csf":45,"subdomain":22,"description":7,"mitre_attack":50},[30,22,36,29,28,27,26,25],"mahipal","1.0",[46,47,48,49],"PR.PS-01","GV.SC-07","ID.IM-04","PR.PS-04",[51,52,53,54,55],"T1195.001","T1195.002","T1552.001","T1190","T1610","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci",4395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":72,"command":73},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":75,"command":76},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill building-devsecops-pipeline-with-gitlab-ci","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",true,[80,86,91,97,101,105,109,115],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Ftemplate.md","ASSET","资产文件",1423,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fassets\u002Ftemplate.md",{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FLICENSE",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"README.md","REFERENCE","参考文档",5170,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Ffrontend-to-backend-requirements\u002FREADME.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fapi-reference.md",1544,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fapi-reference.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fstandards.md",2662,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fstandards.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fworkflows.md",2327,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fworkflows.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fagent.py","SCRIPT","脚本",4951,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fagent.py",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fprocess.py",6111,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fprocess.py",[120,147,171,199,225,252],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":37},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[132,133,134,135,35,34,136,137,33,138,139,21,140,23,141,142,143,144,145,146],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","supply-chain","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":37},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[153],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[155,143,156,157,35,158,34,33,159,160,161,162,163,164,165,166,167,168,169,170],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":37},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[177,180],{"categoryNo":178,"categoryName":179,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[165,182,183,184,185,34,186,187,159,188,189,190,191,192,193,194,195,196,197,198],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":37},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[205],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[207,208,209,34,210,211,212,213,214,215,216,217,218,219,220,221,162,222,223,224],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":232,"publishedAt":37},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[231],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[233,234,235,34,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":259,"publishedAt":37},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[258],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[35,260,34,261,262,263,264,265,266,267,268,194,269,195,270,271,272,273,274,275],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]