Checkov tool omits Azure Pipelines results
@DimaBir 已经在做这个了。
开始于 2026年5月13日。
评估
这个 Issue 还没有评估数据。
描述
When I use the Checkov tool to scan a cloned Azure DevOps Git repo with an azure-pipelines.yml, I can see CKV_AZUREPIPELINES_ results, but when I use MicrosoftSecurityDevOps@1 in a pipeline for that very same repo, scanning the whole repo, I don't get these CKV_AZUREPIPELINES_ errors.
Don't get me wrong but, this seems like a missed easy win?
Thus, I'm not sure if this is a bug with my implementation or a missing feature. As such here are some details on my implementation, please let me know if I'm missing something obvious.
Here's my .gdcnconfig, derived from https://github.com/microsoft/security-devops-azdevops/wiki#checkov-gdnconfig-sample:
{
"tools": [
{
"tool": {
"name": "checkov",
"version": "Latest"
},
"arguments": {
"Directory": "$(Checkov.DefaultTargetDirectory)",
"Help": false,
"Version": false,
"OutputType": "sarif",
"List": false,
"Quiet": false,
"Compact": true,
"RunAllExternalChecks": false,
"Soft": false,
"ShowConfig": false,
"CreateBaseline": false,
"OutputBaselineAsSkipped": false,
"NoFailOnCrash": false,
"EnableSecretScanAllFiles": true
},
"outputExtension": "sarif",
"successfulExitCodes": [
0
],
"errorExitCodes": {
"1": "Checkov tool found issues.",
"2": "An error has occurred running the Checkov tool."
},
"outputPaths": []
}
]
}
And the pipeline task:
- task: MicrosoftSecurityDevOps@1
env:
GDN_RUN_WORKINGDIRECTORY: $(Build.SourcesDirectory)
inputs:
break: true
publish: false
I do get the other results from Checkov, although not always on par with calling standalone Checkov itself.
There seems to be some behind-the-scenes magic at work. For instance, when using MicrosoftSecurityDevOps@1 I found CKV_AZURE_177 downgraded to a warning, where it's an error when I call checkov standalone to perform what I think is the same scan.
Here's how I've been performing a manual scan with Checkov, that seems to look deeper and be more strict than the task's call does:
checkov -d "$(Build.SourcesDirectory)" --repo-root-for-plan-enrichment "$(Build.SourcesDirectory)" --deep-analysis -o cli -o sarif --output-file-path console,$results
- 主要语言
- TypeScript
- 星标
- 86
- 派生
- 22
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/security-devops-azdevops 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
-
area:task area:tools status:waiting-on-author type:docs type:question
microsoft/security-devops-azdevops#169 · 1 条评论 · 已指派 1 人 ·
-
Which Defender CLI binary should be used in CI/CD pipelines — `aka.ms` or the DevOps CDN endpoint? 未关闭
难度 5/5 一周以上 新手友好度 35/100
microsoft/security-devops-azdevops#166 · 2 条评论 · 1 个 reaction ·
-
area:task area:tools status:team-review type:feature
microsoft/security-devops-azdevops#164 · 2 个 reaction · 已指派 2 人 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 35/100
microsoft/security-devops-azdevops#152 · 2 条评论 ·
查看 microsoft/security-devops-azdevops 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
area:tools bug good first issue help wanted priority:P2
难度 2/5 1-3 小时 新手友好度 90/100
TaewoooPark/Motifcode#14 ·
-
bug 🐞
难度 2/5 1-3 小时 新手友好度 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
BasedHardware/omi#15320 ·
-
难度 2/5 半天 新手友好度 78/100
vercel/vercel-plugin#199 ·