-
Notifications
You must be signed in to change notification settings - Fork 27
Hardening_the_app
This section of the wiki details the effort underway to ensure the Aeolus suite is secure and does not expose any data or access to un-authorized users. The end goal is to be confident enough in the state of the security of the application to be able to deploy a live instance, at first for limited use and then for the general public.
The end-user will completely interact with Aeolus Conductor, through use of the api, web, and cli interfaces. Commands to all other components will be dispatched to and invoked via Conductor. These components will run in their own isolated sandboxes in production and provided no arbitrary code is executed or invalid parameters specified they provide less of a potential attack vector than Conductor.
Conductor is being analysed in terms of sanity of data operations and storage. Since cloud credentials will be stored in the DB which Conductor needs access to, we are methodically going through the application, ensuring Conductor does not provide access to data to unauthorized users.
This effort is being chronicled on this wiki and being implemented through various rounds of security work allocated in each sprint. Once we reached a point which we are sufficiently pleased with the security of the application, we will tag a release as being the extent of our security audit and then move onto attaining the infrastructure needs required to host the application and configuring them, initially for a limited private invite-only preview.
A story has been created to track the progress of the tasks remaining on the backlog from the first conductor security audit: