blocks|key|1117525|text|使用此修改后的版本https://github.com/ICTU/zap2docker-auth-weekly|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1117526|stages:
-+scan
dast:+
++stage:+scan
++image:
++++name:+ictu/zap2docker-weekly+
++before_script:
++++-+mkdir+-p+/zap/wrk
++script:
++++-+pwd
++++-+ls
++++-+zap-full-scan.py+-t+"http://testphp.vulnweb.com"+-I+-r+testreport.html+--hook=/zap/auth_hook.py+-z+"auth.loginurl=http://example.com/login.php+auth.username_field="uname"+auth.password_field="pass"+auth.username="username"+auth.password="pass""
++++-+cp+/zap/wrk/testreport.html+testreport.html
++artifacts:
++++when:+always
++++paths:
++++++-+testreport.html|code-block|syntax|javascript|1117527|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ICTU/zap2docker-auth-weekly^0|9|1A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

using this modified version <a href="https://github.com/ICTU/zap2docker-auth-weekly" rel="nofollow noreferrer">https://github.com/ICTU/zap2docker-auth-weekly</a>
<pre><code>stages:
- scan
dast: 
 stage: scan
 image:
 name: ictu/zap2docker-weekly 
 before_script:
 - mkdir -p /zap/wrk
 script:
 - pwd
 - ls
 - zap-full-scan.py -t &quot;http://testphp.vulnweb.com&quot; -I -r testreport.html --hook=/zap/auth_hook.py -z &quot;auth.loginurl=http://example.com/login.php auth.username_field=&quot;uname&quot; auth.password_field=&quot;pass&quot; auth.username=&quot;username&quot; auth.password=&quot;pass&quot;&quot;
 - cp /zap/wrk/testreport.html testreport.html
 artifacts:
 when: always
 paths:
 - testreport.html
</code></pre>

blocks|key|1117560|text|在本地运行ZAP并按照https://www.zaproxy.org/docs/authentication/进行身份验证|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1117561|然后导出上下文文件并指定该文件以及您希望按照https://www.zaproxy.org/docs/docker/full-scan/使用的用户。|1117562|entityMap|0|LINK|mutability|MUTABLE|url|https://www.zaproxy.org/docs/authentication/|1|https://www.zaproxy.org/docs/docker/full-scan/^0|B|18|0|0|M|1A|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Run ZAP locally and get authentication working as per <a href="https://www.zaproxy.org/docs/authentication/" rel="nofollow noreferrer">https://www.zaproxy.org/docs/authentication/</a>
Then export your context file and specify that and the user you want to use as per <a href="https://www.zaproxy.org/docs/docker/full-scan/" rel="nofollow noreferrer">https://www.zaproxy.org/docs/docker/full-scan/</a>

blocks|key|1117577|text|还可以在执行DAST检查之前对用户进行身份验证：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1117578|dast:
++image:+registry.gitlab.com/gitlab-org/security-products/zaproxy
++variables:
++++website:+"https://example.com"
++++login_url:+"https://example.com/sign-in"
++script:
++++-+mkdir+/zap/wrk/
++++-+/zap/zap-baseline.py+-J+gl-dast-report.json+-t+$website+\
++++++++--auth-url+$login_url+\
++++++++--auth-username+"john.doe@example.com"+\
++++++++--auth-password+"john-doe-password"+%7C%7C+true
++++-+cp+/zap/wrk/gl-dast-report.json+.
++artifacts:
++++paths:+[gl-dast-report.json]|code-block|syntax|javascript|1117579|有关身份验证设置的更多信息，请参见zaproxy文档。|offset|length|1117580|entityMap|0|LINK|mutability|MUTABLE|url|https://gitlab.com/gitlab-org/security-products/zaproxy^0|0|0|H|9|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

It's also possible to authenticate the user before performing DAST checks:
<pre><code>dast:
 image: registry.gitlab.com/gitlab-org/security-products/zaproxy
 variables:
 website: &quot;https://example.com&quot;
 login_url: &quot;https://example.com/sign-in&quot;
 script:
 - mkdir /zap/wrk/
 - /zap/zap-baseline.py -J gl-dast-report.json -t $website \
 --auth-url $login_url \
 --auth-username &quot;john.doe@example.com&quot; \
 --auth-password &quot;john-doe-password&quot; || true
 - cp /zap/wrk/gl-dast-report.json .
 artifacts:
 paths: [gl-dast-report.json]
</code></pre>
See <a href="https://gitlab.com/gitlab-org/security-products/zaproxy" rel="nofollow noreferrer">zaproxy documentation</a> to learn more about authentication settings.

I want to do a zap full scan on gitlab cicd with authentication to the website i want to run it (without the DAST module from gitlab)
i can run the zap-full-scan.py properly but dont know how to add authentication credentials for the site
<pre><code>stages:
 - scan
dast: 
 stage: scan
 image:
 name: owasp/zap2docker-weekly
 before_script:
 - mkdir -p /zap/wrk
 script:
 - pwd
 - ls
 - zap-full-scan.py -t &quot;http://example.com&quot; -m 1 -d -I -r testreport.html 
 - cp /zap/wrk/testreport.html testreport.html
 artifacts:
 when: always
 paths:
 - testreport.html
</code></pre>

OWASP ZAP Full Scan Authenticated on Gitlab CICD

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想在gitlab cicd上做一个zap全面扫描，并对我想运行的网站进行身份验证(没有来自gitlab的DAST模块)我可以正确地运行zap全扫描. to，但不知道如何为站点添加身份验证凭据。stages:  - scandast:   stage: scan  image:    name: owasp/zap2d...

问OWASP全扫描在Gitlab CICD上认证
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OWASP全扫描在Gitlab CICD上认证EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OWASP全扫描在Gitlab CICD上认证
EN