Skip to content
English
  • There are no suggestions because the search field is empty.

Can We Deploy a Microsoft Azure or Bespoke Jumpbox Build?

Preparing for an Edgescan Jumpbox in a Microsoft Azure or bespoke environment.

Version Number: v1.0.0

Published Date: 19 Mar 2026

____________________________________________________________________________

While we traditionally provide prebuilt VM images, we support the deployment of bespoke jumpboxes which require the jumpbox to be built in place, such as within Microsoft Azure environments. 

Setup process for deployment in Microsoft Azure.

The setup process typically follows these steps:

  1. Provision a Virtual Machine

    1. Create a Debian-based virtual machine (Debian 13 recommended) in Azure

    2. Ensure the VM meets the minimum specifications:
      • 1 GB RAM
      • 1 CPU core
      • 10 GB disk space
    3. Provide SSH access to the VM
  2. Jumpbox Configuration

    We will access the VM via SSH, configure it as a jumpbox and establish a secure VPN tunnel to a dedicated, hardened VM on our network.
    Alternatively, if you don't want to give us ssh access, we can also send a provisioning script which has to be run as root on the VM (note that this might require doing a call/screenshare to debug if there are any issues).

  3. Networking Configuration (Post setup)

    1. Remove general public internet access to the jumpbox (recommended)

    2. Allow the following outbound connectivity:

      • TCP egress on port 9801 to a public IP address (provided by us)

      • Ensure the jumpbox has appropriate internal network access to the systems you want scanner

      • Note that it is your responsibility to ensure the jumpbox can reach all intended scan targets internally. We do not enforce internal network restrictions on the VM.

  4. Validation & Transition

    We will confirm successful connectivity between the jumpbox and our infrastructure and migrate any existing assets if needed.

Minimum specs:

  • 1 GB RAM

  • 1 core

  • 10 GB Harddrive

Networking Requirements

  1. Access to Scan Targets
    1. The jumpbox must be able to reach all systems you want to scan.
    2. If networks cannot be connected, multiple jumpboxes may be required.
  2. Port Access
    1. If you want us to do Network Scanning, providing us access to all ports on target systems is recommended.
    2. If you want us to do Application Scanning, you only need to provide us access to the application on whatever port it is exposed on.
  3. External Connectivity

            The jumpbox must allow outbound (egress) access:

    • Protocol: TCP
    • Port: 9801
    • Destination: Public IP address (provided by us)