What is required to setup testing on an internal/private environment?

How to setup an Edgescan jumpbox, what Edgescan needs to successfully test?

Version Number: v1.0.1

Published Date: 29 Mar 2024

____________________________________________________________________________

Edgescan offers continuous Dynamic Application Security Testing (DAST) integrated with business logic penetration testing, in addition to Network Vulnerability Intelligence for non-internet facing infrastructure, such as internal Local Area Networks or Virtual Private Clouds. The combination of automation and manual testing from one platform allow enterprises to meet the ever-increasing demand for accurate and useful Vulnerability and Security intelligence.

You do not need to create any virtual appliances in your environments. The Edgescan deployments team will build, configure, and deliver you the JumpBox in a deployable format.

Screenshot 2024-03-01 at 16.13.19

Testing of internal systems differs from external systems as our scanning and testing traffic must find a way to access internal infrastructure which is protected by layers of security, including firewalls. To facilitate testing, we utilise two key hosts:

Edgescan Cloud Control (Hosted in Amazon AWS)

The Cloud Control host is a virtual machine which runs in Edgescan’s Amazon AWS environment. Each customer is provided with a dedicated Cloud Control which is completely segregated within a private VPC in AWS. This host provides one end-point of a Virtual Private Network (VPN) which utilises OpenVPN to provide a strongly encrypted end-to- end tunnel between itself and the JumpBox.

Edgescan JumpBox (On Premise Appliance)

The JumpBox host is deployed as a virtual machine using your own VM infrastructure (VMWare, Hyper-V etc). This host is typically deployed on your internal network at a suitable location which provides traffic routes to the target network, device, or application infrastructure. Both the Cloud Control and JumpBox will auto-initiate a VPN connection to each other and this allows for a secure tunnel into your network. Our scanning technology is deployed at the Cloud Control host, depending on what infrastructure needs to be assessed and all results are fed into the Edgescan platform for validation by our engineers and later consumption by your organisation.

Edgescan Internal Testing - checklist

Testing on internal systems requires a presence on the network. Edgescan makes this easy with Edgescan cloud control and the Edgescan JumpBox. 

To facilitate this, read below and talk to your Edgescan onboarding team to get the infrastructure setup.

Confirmation of the IP address space (i.e. subnet, gateway).
The appliance works with DHCP. We can also facilitate static IPs. Please let us know.
Where the VM/host will be deployed. Note that this location should be able to route traffic to the target infrastructure.
Egress Rules -The JumpBox needs to send traffic to the cloud control public IP (which will be provided by Edgescan) for TCP port 9801.
The type of virtual server infrastructure and version you use (e.g. VMware, Hyper-V etc.) Min. Spec required for the VM = 1 CPU, 1GB RAM, 10GB HD.

The type of virtual server infrastructure and version you use (e.g VMWare, Hyper-V, AMI, Azure VM) If appliance in the cloud is required (AWS or Azure) – AWS region/ID, Azure shell access required to configure appliance.