[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GWYV2QE4FGDAW2DCVMKQAX":3,"skill-same:01M6GWYV2QE4FGDAW2DCVMKQAX":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6GWYV2QE4FGDAW2DCVMKQAX","building-devsecops-pipeline-with-gitlab-ci",null,"Design and implement a comprehensive DevSecOps pipeline in GitLab CI\u002FCD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"devsecops","with","gitlab","ci","pipeline","devsecops pipeline","gitlab ci","building devsecops pipeline with gitlab ci","container scanning","design","CI\u002FCD","dependency","scanning","dependency-scanning","container-scanning","dast","gitlab-ci","cybersecurity","security","sast","2026-11-10 10:12:30",false,"---\nname: building-devsecops-pipeline-with-gitlab-ci\ndescription: Design and implement a comprehensive DevSecOps pipeline in GitLab CI\u002FCD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.\ndomain: cybersecurity\nsubdomain: devsecops\ntags: [gitlab-ci, devsecops, sast, dast, container-scanning, dependency-scanning, secret-detection, cicd-security]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\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":43,"author":46,"domain":35,"license":14,"version":47,"subdomain":18,"description":7},[34,18,37,33,32,31,44,45],"secret-detection","cicd-security","mahipal","1.0","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill building-devsecops-pipeline-with-gitlab-ci",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill building-devsecops-pipeline-with-gitlab-ci","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FSKILL.md",true,[69,75,80,86,90,94,100],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md","ASSET","资产文件",1423,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002FLICENSE",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",1544,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fstandards.md",2662,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fstandards.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fworkflows.md",2327,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Freferences\u002Fworkflows.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fagent.py","SCRIPT","脚本",4951,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fagent.py",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fprocess.py",6111,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-devsecops-pipeline-with-gitlab-ci\u002Fscripts\u002Fprocess.py",[105,143,171,191,211,236],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":122,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[112,117],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":157,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[149,150,153,156],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":151,"categoryName":152,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":154,"categoryName":155,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[158,159,160,161,124,162,163,164,165,21,166,167,132,133,139,168,169,140,28,170],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","github actions","github-actions","as","guides","implementing",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[177],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[179,180,181,36,124,127,132,133,182,183,184,185,186,187,188,140,189,190,170,142],"policy","authoring","apim policy authoring","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[197,198],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[200,36,201,132,185,202,124,158,203,204,205,206,133,207,140,208,209,210,141,142],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[218,219,220,160,221,222,223,224,132,225,226,227,228,229,230,231,232,233,234,235],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[238,243,244,245,246,247,248,183,249,250],"npm","js","calculate","node","math","user","compute","errors"]