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

Scan target discovery #225

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

Scan target discovery #225

v1r7u opened this issue May 5, 2020 · 0 comments
Labels
kind/question Discussion item 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

Probably, could be done in two ways:

  • a separate service, which could connect to a given cloud, traverses available resources there and list what types of Joseki scanners could be used for that environment;
  • runs as part of backend service and analyzes only data received through available scanners to point which parts of the infrastructure are not scanned yet, while Joseki can do that.
@v1r7u v1r7u added kind/question Discussion item lifecycle/backlog General backlog pile. Any idea, which could be taken into work size/L 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.
Labels
kind/question Discussion item lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/L
Projects
None yet
Development

No branches or pull requests

1 participant