For every event, create complex, realistic environments that, if successful, will be contaminated and need to be destroyed. Reduce the time and cost necessary to stand up a range.
Create designs for infrastructure, red team, and blue team tools to rapidly create environments. These would be in isolated cloudspaces as needed for proper security. It also allows for quick replacement during an exercise in the event something is rendered useless. Automating the creation frees the team, allowing for a take no prisoners approach during the event.
Rapidly re-validate compliance as changes to baseline (version, bug fix, vulnerability patches) occur. Standing up an environment that faithfully reproduces what is in the field in order to do a re-scan can take lots of time.
Performing security validation inside CONS3RT along the way means when a change comes along it is a quick process to re-run existing test cases, leveraging both the tools in the library (manual) and tools as services (automated). Typical edits to a system design and relaunch can be done in minutes. In fact, by having the security tests already in the library, testing can be done during the development and debug phase, rather than as an afterthought.