Security/Projects/Minion/Architecture: Difference between revisions
< Security | Projects/Minion
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
=Minion Architecture= | =Minion Architecture= | ||
At a very high level the responsibilities of each component are: | At a very high level the responsibilities of each component are: | ||
| Line 23: | Line 16: | ||
* [[Security/Projects/Minion/Plugins | Plugins]] | * [[Security/Projects/Minion/Plugins | Plugins]] | ||
** Providing a consistent API to other security tools | ** Providing a consistent API to other security tools | ||
[[File:Minon_threat_model.png]] | |||
Latest revision as of 13:46, 19 October 2012
Minion Architecture
At a very high level the responsibilities of each component are:
- Web UI
- Generating the web UI (not surprisingly)
- Authenticating and managing users and user sessions
- Task Engine
- Providing a REST based API
- Handling requests from trusted components (eg the Web UI)
- Scheduling work across the available resources (ie plugins)
- Persisting data
- Plugin Service
- Providing a REST based API
- Handling requests from trusted components (eg the Task Engine)
- Communication with the Plugins
- Plugins
- Providing a consistent API to other security tools
