Create a private connection
Assess your internal networks with the Argunis probe through a WireGuard, OpenVPN or IPsec IKEv2 tunnel or your remote access VPN, without installing a local probe.
On this page
A private connection is a tunnel from the Argunis probe to your internal networks. With it, Private connection (tunnel) scopes assess those networks without installing a probe in your network, and only within their time window. Each connection's secret is backed up and encrypted in your company's vault.
Before you start
Administer permission on Vulnerabilities.
Argunis must have enabled its probe for your company and allowed at least one type of private connection. If the probe is enabled only for the perimeter, the screen says so: ask Argunis to allow private connections.
Access to your network's firewall or VPN device.
Choose the connection type
Type | When to use it |
|---|---|
WireGuard | Firewalls with WireGuard (MikroTik, pfSense, OPNsense) or, if the firewall doesn't support it, the ARGUNIS connector |
OpenVPN | Devices without WireGuard: ARGUNIS generates the CA and certificates and provides the .ovpn file for the host on your network |
IPsec IKEv2 | Firewalls with IPsec (FortiGate, MikroTik, pfSense, strongSwan): ARGUNIS generates the pre-shared key or the certificates and provides the templates |
Dial-up VPN | Your remote access VPN (.ovpn, Cisco AnyConnect, Fortinet SSL VPN, Palo Alto GlobalProtect or Pulse/Ivanti): the probe uses it only during the scan window |
Steps
Go to Security (SIEM) → Vulnerabilities → Scopes and scroll down to the Private connection card.
Click New private connection.
Enter the Name and choose the Argunis probe.
Choose the Connection type.
Choose Who initiates the connection:
The probe dials: your device listens on a public IP and the probe connects to it. Enter the endpoint or IPsec device on your side.
The client dials: your device connects to the probe's public IP and UDP port; you don't open any inbound ports.
In Internal networks (one per line), enter only the private networks the probe will be able to assess (10/8, 172.16/12, 192.168/16 or 100.64/10).
For WireGuard, paste the Client host public key (it can be added later). For a dial-up VPN, choose the VPN client and paste or upload its configuration, with the server, username and password.
Save.
If ARGUNIS shows a pre-shared key (PSK), copy it right then: it is shown only once. It stays encrypted in the vault and isn't shown again.
Configure your side of the tunnel
Depending on the type, on the connection's row:
Client-side template: the configuration for your firewall or device.
Download .ovpn (OpenVPN) or Download .conf (IPsec): the full package for your device. Store it in a safe place.
Connector (WireGuard): if your firewall doesn't support WireGuard (for example, FortiGate), install the connector, a lightweight container that runs with Docker on a machine in your network. Click Generate token, paste the command over SSH on the machine and then the token (single-use, expires in 24 hours). The machine must see your internal networks and reach the internet over UDP.
Review and maintain the connection
The table shows the tunnel's Status, the Last handshake, the Traffic and how many Scopes use it.
The pencil button edits the connection.
Rotate keys generates new keys: the tunnel stays down until you configure your device with the new ones (or download the .ovpn or .conf again).
Load new configuration (dial-up VPN) replaces the configuration you provided.
The trash button deletes it. If a scope uses it, delete or change that scope first.
What happens next
When you create a scope with the Private connection (tunnel) vantage point, you choose this connection instead of a probe. Targets must be within its networks and the time window is mandatory. See Create a scope.