Self-Hosted Deployment

AttackForge Enterprise Server installs and operates completely air-gapped on your hosted infrastructure.

Applying Application Update

Step 1: Perform a backup of your AttackForge environment

This may include performing a full VM snapshot of your AttackForge server, and any other associated infrastructure and components based on your deployment configuration.

Step 2: Download the latest application update and copy it to your AttackForge Server

1. Open your AttackForge SharePoint project (or other agreed upon file transfer system) and download the following file:

afe-server_202X-XX-XXTXX-XX.zip

NOTE: The X's will be replaced with the new version information

1. Copy this file to your AttackForge application folder on your AttackForge server e.g. <PATH-TO-ATTACKFORGE>/afe/app

2. Decrypt and extract the file using the previously supplied decryption key. You should see the following files after the ZIP extraction:

• afe-server_202X-XX-XXTXX-XX.run

• config.json

1. Replace the new config.json with the existing version in <PATH-TO-ATTACKFORGE>/afe/app/custom

Step 3: Apply latest application update, build new images and launch new containers

1. Open a terminal on your AttackForge Server.

2. Navigate to the AttackForge application directory e.g. <PATH-TO-ATTACKFORGE>/afe/app

3. Make afe-server_202X-XX-XXTXX-XX.run executable:

chmod u+x afe-server_202X-XX-XXTXX-XX.run

1. Run afe-server_202X-XX-XXTXX-XX.run to build the new application source files:

./afe-server_202X-XX-XXTXX-XX.run

1. Run rebuild.run to build the new application images and launch new application containers:

./rebuild.run

1. App should now be updated to the latest version. You can confirm this by logging in and going to Administration > About and check the build date:

Updating NodeJS

Step 1: Perform a backup of your AttackForge environment

This may include performing a full VM snapshot of your AttackForge server, and any other associated infrastructure and components based on your deployment configuration.

Step 2: Download the latest NodeJS image and copy it to your AttackForge Server

1. Open your AttackForge SharePoint project (or other agreed upon file transfer system) and download the following file:

node_XX.XX.X-XXX.tar

NOTE: The X's will be replaced with the new version information - for example node_24.21.0-bookworm.tar

1. Copy this file to your AttackForge application folder on your AttackForge server e.g. <PATH-TO-ATTACKFORGE>/afe/app

Step 3: Load and configure the new NodeJS image

1. Open a terminal on your AttackForge Server.

2. Navigate to the AttackForge application directory e.g. <PATH-TO-ATTACKFORGE>/afe/app

3. Load the new image, ensuring to replace the X's with the new image version details:

docker load -i node_XX.XX.X-XXX

EXAMPLE: docker load -i node_24.21.0-bookworm

1. Confirm the new image has loaded correctly in Docker. You should see the image showing:

docker images | grep node

1. Open the file afe-server.Dockerfile in a text editor. The file is located in <PATH-TO-ATTACKFORGE>/afe/app/custom.

2. Update the following entry at the top/start of the file, ensuring to replace the X's with the new image version details, then save the file:

FROM node:XX.XX.X-XXX

EXAMPLE: FROM node:24.21.0-bookworm

Step 4: Load and configure the new NodeJS image

1. Open a terminal on your AttackForge Server.

2. Navigate to the AttackForge application directory e.g. <PATH-TO-ATTACKFORGE>/afe/app

3. Run afe-server_202X-XX-XXTXX-XX.run to build the new application source files with the new Docker config, ensuring to replace the X's with the latest AttackForge version details in your app directory:

./afe-server_202X-XX-XXTXX-XX.run

1. Run rebuild.run to build the new application images and launch new application containers:

./rebuild.run

1. App should now be updated to the latest NodeJS version.

Updating NGINX

Step 1: Perform a backup of your AttackForge environment

This may include performing a full VM snapshot of your AttackForge server, and any other associated infrastructure and components based on your deployment configuration.

Step 2: Download the latest NGINX image and copy it to your AttackForge Server

1. Open your AttackForge SharePoint project (or other agreed upon file transfer system) and download the following file:

nginx_X.XX.X-XXX.tar

NOTE: The X's will be replaced with the new version information - for example nginx_1.31.5-trixie.tar

1. Copy this file to your AttackForge application folder on your AttackForge server e.g. <PATH-TO-ATTACKFORGE>/afe/app

Step 3: Load and configure the new NGINX image

1. Open a terminal on your AttackForge Server.

2. Navigate to the AttackForge application directory e.g. <PATH-TO-ATTACKFORGE>/afe/app

3. Load the new image, ensuring to replace the X's with the new image version details:

docker load -i nginx_X.XX.X-XXX

EXAMPLE: docker load -i nginx_1.31.5-trixie

1. Confirm the new image has loaded correctly in Docker. You should see the image showing:

docker images | grep nginx

1. Open the file afe-client.Dockerfile in a text editor. The file is located in <PATH-TO-ATTACKFORGE>/afe/app/custom.

2. Update the following entry at the top/start of the file, ensuring to replace the X's with the new image version details, then save the file:

FROM nginx:X.XX.X-XXX

EXAMPLE: FROM nginx:1.31.5-trixie

Step 4: Load and configure the new NGINX image

1. Open a terminal on your AttackForge Server.

2. Navigate to the AttackForge application directory e.g. <PATH-TO-ATTACKFORGE>/afe/app

3. Run afe-server_202X-XX-XXTXX-XX.run to build the new application source files with the new Docker config, ensuring to replace the X's with the latest AttackForge version details in your app directory:

./afe-server_202X-XX-XXTXX-XX.run

1. Run rebuild.run to build the new application images and launch new application containers:

./rebuild.run

1. App should now be updated to the latest NGINX version.