Generally speaking, this milestone covers a lot of things it might not. Since the release is so big, some features may be moved to v4 or a minor v3.x release.

Update structure and codebase

The biggest change is to make the codebase async. It won't probably affect all components since it may not satisfy our needs. For example, the Worker will still have to launch the modules in a separate Process to get more out of the CPU.

• Async codebase for all components (may need to replace Django due to the lack of async support)?
• Stages and triggers update
• Implementation of APScheduler v4
• Use linters and formatters (PyLint, etc.)

testing

• Rewrite tests in Pytest
• Better code coverage

New features

There will be a lot of new features when it comes to MSF and other codebase updates.

However, these are some specific features we could want:

• MITRE would be nice, but that may be part of the first major release
• Advanced decision logic in the attack scenario (better output sharing and parsing, more options for the execution tree, even stages)

User-friendliness

All components should return only the information the user needs and wants. The debug mode should be verbose but not annoyingly with unnecessary information (Step outputs).