Confirm
133
edits
Changes
no edit summary
==Components==
===Web Interface===
====Overview====
The Web UI is responsible for:
* Generating the web UI (not surprisingly)
* Authenticating and managing users and user sessions
====Notes====
* Log in using Persona (BrowserID) (can be restricted by domain for use on central server by organizations)
* Menu -> New Scan, Running Scans, Completed Scans
** Advanced: Login information, technologies used (customize scan such as SQLmap for SQL)
** Future: Scan type based on plugin (web app, client code, etc)
It should maintain as little data in memory as possible - all data should be retrieved from the Task Engine (and/or db?). This will allow us to run multiple Web UI servers for one service.
====Questions====
* Should this also provide a REST based API, or will we rely on the one implemented by the Task Engine?
* Will it need access to the db or will it get all data from the Task Engine?
===Task Engine===
====Overview====
The task engine is responsible for:
* Managing Minions
* Persisting all info to the db
* Providing a REST API
====Notes====
* Instance started when user clicks start scan
* Collects provided information
* Starts scan based on provided information
* Launches tools (Minions) and awaits responses
It should persist all data to a db and maintain as little data in memory as possible. This will allow us to run multiple Task Engine servers for one service, with all of the synchronization happening via the db (which would probably be clustered).
===Minions (Scanners)===
