Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

[New Scanner] ZAProxy #220

Open
v1r7u opened this issue May 5, 2020 · 0 comments
Open

[New Scanner] ZAProxy #220

v1r7u opened this issue May 5, 2020 · 0 comments
Labels
area/backend Issue relates to Backend service area/scanner Issue relates to Scanners services kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/L

Comments

@v1r7u
Copy link
Contributor

v1r7u commented May 5, 2020

Support https://github.com/zaproxy/zaproxy
Potentially, it could work in two ways:

  • scan given URLs according to a defined schedule
  • like a trivy-scanner - triggered by message in the queue. In this case, this message could be composed by backend application for each discovered service object in k8s
@v1r7u v1r7u added kind/enhancement New feature or request area/scanner Issue relates to Scanners services lifecycle/backlog General backlog pile. Any idea, which could be taken into work size/L area/backend Issue relates to Backend service priority/low Low priority issues labels May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/backend Issue relates to Backend service area/scanner Issue relates to Scanners services kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/L
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@v1r7u