Attack Vectors execute simulation events — the offensive actions. They are deployed on your information system to carry out the events within the campaign scope and per the configured settings. To install one, see Deploy an Attack Vector .
The list shows, for each Attack Vector: its alias, identifier, the campaign using it, creation date, IP address, version, and status. You can order by identifier or creation date, filter (type, in use or not within a campaign), and search.
If an Attack Vector's system clock is not synchronized, the platform calculates a against the reference clock (requires Attack Vector version 1.4.0 or above). It appears in the Attack Vector's details.
On and connected to the BlackNoise platform; ready to run a simulation.
Cannot run a simulation. Check that the Attack Vector is started (host machine, and Docker for the software version) and that the required flows to the platform are open — see Deploy an Attack Vector . Currently used in a simulation, running that campaign's events; it cannot be used by another campaign at the same time.
Setup in progress; ready in a few minutes.
Updating its main code and modules.
A red star next to the version number indicates an available update.
Create and install an Attack Vector, then update it when a new version is available, from (the Create attack vector button, and the Update version button in an Attack Vector's details). The full procedure — prerequisites, installation, updating and troubleshooting — is in Deploy an Attack Vector .