[New feature] Scan internal networks with the VPN Agent

Author(s)
Ioana Rijnetu Content Marketer

Updated at: July 26, 2022

Article tags

To enhance the way you scan your internal networks, we added a new way to perform this on Pentest-Tools.com. It is a lot easier and does not require any special configuration.

All you need to do is run the VPN Agent and start scanning!

Note: This feature is available for PRO Advanced and Enterprise plans only.

Start by downloading the VPN Agent virtual machine (VMWare format) and run it inside your internal network. The VPN Agent automatically initiates a secure connection (VPN tunnel) between your internal network and our scanning servers.

To learn how easily you can configure the VPN Agent and create a new VPN profile on Pentest-Tools.com, read our step-by-step tutorial from the Support Center.

How to scan AWS cloud networks with the Pentest-Tools.com VPN Agent

Save time and run internal network scans faster with the new VPN Agent!

Get vulnerability research & write-ups

In your inbox. (No fluff. Actionable stuff only.)

How to exploit the DotNetNuke Cookie Deserialization

How to exploit the PHAR deserialization vulnerability

Visualize exploit paths with the Sniper network graph

Whether working in offensive or defensive security, we all see it: high-risk, widespread vulnerabilities cause significant disruptions to already struggling security teams.

Author(s)

Andra Zaharia

Published at: 23 Jun 2022

April updates: Get RCE evidence for 6 critical CVEs

After weeks of working on auto-exploitation for this critical CVE (CVSSv3 9.8), we finally have it! As a Pentest-Tools.com customer, you can run Sniper Auto-Exploiter to get conclusive proof that validates targets vulnerable to this high-risk vulnerability, which bad actors have already shown interest in.

Author(s)

Ioana Rijnetu

Published at: 05 May 2022

March updates: Spring4Shell: find and confirm exploitable targets and more updates

If you instantly thought of Log4Shell when Spring4Shell emerged just a few days ago, you’re not alone. A coolheaded analysis reveals this CVE is not as severe as last year’s Log4j vulnerability. Nevertheless, it remains a priority in terms of detection and patching. Here’s why.

Author(s)