Attack vectors

Manage all Attack Vectors of the company


BlackNoise Attack Vectors execute simulation events (offensive actions). They are deployed on your Information System to carry out the technical actions (events) within the defined campaign scope and based on the configured technical settings.


Attack Vectors list


This list provides all information about your Attack Vectors:
  • Alias (the name you provide)
  • Identifier
  • Campaign using the Attack Vector
  • Creation date
  • IP address
  • Version
  • Status: operational, non operational, working or deploying

To facilitate the use of this list, several features are available:
  • Display order by identifier or creation date
  • Application of filters: type, used or not within a campaign
  • Search field


Set up a virtual Attack Vector

Check the Setup section titled "1) Deploy an Attack Vector" in this documentation for more information on what you need and how to install an Attack Vector:
 https://doc.blacknoise.co/p/FtdVpP2Qnl33xq/1-Deploy-an-Attack-Vector 
You can quickly launch a BlackNoise Attack Vector from the Resources > Attack Vectors page. Simply click the Create attack vector button in the top right and provide a name (alias) for this Attack Vector.

Next, copy the docker command from the screen and paste it into the terminal of the host deployed for that purpose (check prerequisites from the Setup section:  https://doc.blacknoise.co/p/FtdVpP2Qnl33xq/1-Deploy-an-Attack-Vector ).

The attack Vector shows up in the web app list. The container image is downloaded and started. Once the authentication between the Docker container and the BlackNoise web app is done, the Attack Vector is ready to use (ie. operational). This is shown by a green dot. It can now be used in an attack campaign.

A red star next to the version number of an Attack Vector indicates an available update. Click the Attack Vector to open the details modal. The update command appears at the top. Run the command from the host system running Docker. The new version will be downloaded and used when the container restarts.

When an Attack Vector is not synchronized via NTP, the platform now calculates the Time offset against the reference clock (requires Attack Vector version 1.4.0). This data is also provided within this details screen.