A flexible, easy to use, automation framework allowing users to integrate their capabilities and devices to cut through the repetitive, tedious tasks slowing them down. #nsacyber
This update includes a rewrite of the API Gateway from Flask to FastAPI to leverage Python Asyncio functionality. Server-Sent Events used for streaming data to the UI was also replaced by Socket.IO which should be easier to maintain and be more robust. UI improvements for interacting with JSON data were also included.
We would have liked to go for a full 1.0.0 release within the month, but due to factors outside of our control, the development team will be pausing work on WALKOFF. We hope to be back within the next couple weeks.
This update includes a number of bugfixes, particularly to role-based permissions and the workflow scheduler.
Minio data from the WALKOFF application editor is now persistent after bringing WALKOFF down.
Personal user settings have been added to the drop-down menu under a user profile. This new feature allows for all users to change their own username and password.
mitre_attack
and adversary_hunting
applications have been added to WALKOFF’s default applications. These two apps have pre-configured actions that run Powershell scripts that may be useful to blue teams/threat hunting.
Added subcommand to bootloader for rebuilding and updating specific services.
Added a three-tier level role permissions system for Global Variable and Workflow creation. A user can choose between “only-me,” “everyone,” and “role-based” options for their access restriction level.
Added a close button to Action Settings menu during workflow creation.
Added sample_report_data
action to basics
application. This app generates sample CSV data to be imported into the Reports
tab.
Added Unsaved Changes warning on Workflow and Application editor pages.
Added ability to create/edit Global Variables from the workflow editor.
Top bar navigation has been reworked to include a “Settings” drop-down menu. Global variable creation, user settings, workflow scheduler creation, and link to Portainer have been moved to this menu.
Changed Workflow Variables
to Local Variables
and always display them in the workflow editor.
Renamed hello_world
application tobasics
Workflow abortion in the execution tab is now functional and properly ends the workflow stream.
The unpacking zipped apps on startup was reimplemented with bootloader changes.
The execution tab now returns started_at
time for each NodeStatusMessage
for a WorkflowStatusMessage
. Likewise, current_app
and current_action
are now live updated during Workflow processing.
Workflow scheduler’s tasks can now be updated with new variables, descriptions, and titles. Interval scheduled tasks no longer become stuck in PENDING
.
Fixed the ability undo/redo the deletion of an action on the workflow editor.
This update introduces a number of new features, including an App Editor in the UI, more granular role-based permissions, and a "bootloader" for automating deployment of WALKOFF.
Included are the massive re-architecture changes from 1.0.0-alpha.1 and 1.0.0-alpha.2 for which we did not make a GitHub release (changelogs below).
This update includes numerous bugfixes and a number of reintroduced features. This release wasn't tagged, so the changelog is included here.
This update includes a near-complete rewrite of the workflow execution logic, and a considerable refactor of the server in preparation for a future move to an asynchronous framework. The following changes are not exhaustive.
pip install --upgrade -r requirements.txt
to make sure all dependencies are met. This is also good practice to do after every new release.This is a minor release to fix missing front-end resources. A number of documentation changes have also been made, particularly regarding installing WALKOFF on Windows, as running WALKOFF directly on Windows has no longer supported since 0.9.0.
python -m walkoff local update
to updatePlease Note: From version 0.9.0 forwards, WALKOFF requires a Redis cache to operate. You can run Redis natively on most Linux distributions (see the Redis quickstart guide: https://redis.io/topics/quickstart or search for a packagein your OS's package manager). On Windows, you will need to use Docker to run Redis in a container or expose Redis from a VM.