TestingOps.ai

Private networks · Private network

IPsec site-to-site and TestingOps: a tunnel for test runs, on request

If your network team connects outside services with IPsec site-to-site tunnels instead of VPN user accounts, ask the TestingOps team for an IPsec setup. It is available on request and is not self-service yet.

  • Private network
  • On request
Request a demo
Connection
Private network
Writes back
Test traffic only
Last checked
8 Nov 2026

In short

IPsec (site-to-site) and TestingOps in short

IPsec site-to-site connects two gateways with a pre-shared key or a certificate, so no person signs in: there is no SSO, password or one-time code on the tunnel.

In TestingOps the private network form already takes the remote gateway address, an optional remote ID, the IKE version (IKEv2 or IKEv1), optional proposals and a pre-shared key or certificate, but the gateway machine does not bring an IPsec tunnel up by itself yet. That is why IPsec is available on request.

For VPNs with user accounts, the GlobalProtect, Cisco Secure Client, FortiClient, Ivanti Connect Secure, Check Point, OpenVPN and WireGuard connections are self-service, and a RunningOps host inside your network runs the tests without a tunnel.

What it does

What it does for your testing

  1. 1

    Tunnel parameters kept with the connection

    Input
    Remote gateway address, IKE version, proposals and a pre-shared key or certificate
    TestingOps
    Saved as a private network connection; the key or certificate is stored encrypted
    Output
    The parameters your network team agreed, ready for the setup on request
  2. 2

    A way in without VPN user accounts

    Input
    A network that accepts outside services only over site-to-site tunnels
    TestingOps
    Set up on request with the TestingOps team
    Output
    A route to the test environment that does not depend on a person's VPN account

Step by step

How it works

  1. Ask for IPsecTell the TestingOps team that your test environment is reachable over an IPsec site-to-site tunnel, for example when you request a demo.
  2. Agree the tunnel parametersYour network team provides the remote gateway address, an optional remote ID, the IKE version, any proposals and a pre-shared key or certificate, plus the internal ranges the runs need.
  3. Start runs after the confirmationPlan runs over the tunnel once the TestingOps team confirms it is up. Until then a saved IPsec connection does not connect.

The IPsec option under Integrations → Private networks (VPN) saves these parameters but does not connect by itself yet.

Connect

Setup

  1. Ask the TestingOps team for an IPsec site-to-site setup.
  2. Collect from your network team the remote gateway address, an optional remote ID, the IKE version, any proposals and a pre-shared key or certificate.
  3. Plan runs over the tunnel after the TestingOps team confirms that it is up.
Where you connect it in TestingOps: Integrations → Private networks (VPN) → IPsec (site-to-site)

Use cases

Use cases

No VPN accounts for outside services

Trigger
The network team connects partners only with site-to-site tunnels
Uses
An IPsec tunnel agreed with the network team
Agent activity
Set up on request with the TestingOps team
Result
Test runs reach the environment without a personal VPN account
Condition
On request; not self-service yet

Night runs without a sign-in prompt

Trigger
VPN user sign-ins ask for SMS codes that nobody types at night
Uses
A gateway-to-gateway tunnel authenticated with a key or certificate
Agent activity
No person has to sign in for the tunnel
Result
Scheduled runs do not wait for a code
Condition
Once the tunnel is set up on request

Start now with another way in

Trigger
Runs are needed before an IPsec setup is agreed
Uses
A self-service VPN connection or a RunningOps host in your network
Agent activity
The gateway machine signs in as a VPN user, or the host inside your network runs the tests
Result
Runs start now; IPsec can follow later

Capabilities

Capabilities and limits

What is read

Hosts in the internal ranges agreed for the tunnel, once it is set up.

What is produced

On request: an IPsec site-to-site tunnel for the project's test runs. The self-service form saves the parameters but does not bring a tunnel up yet.

Where it can write

Test traffic only. The pre-shared key or certificate is stored encrypted in TestingOps.

How it connects

Gateway to gateway with IKEv2 or IKEv1 and a pre-shared key or certificate; no user sign-in

Account and permissions

  • The public address of your IPsec gateway and, if it uses one, its remote ID
  • The IKE version and proposals agreed with your network team
  • A pre-shared key, or a certificate in PEM format

Limits

  • Not self-service yet: a saved IPsec connection does not connect by itself
  • No SSO or MFA: a site-to-site tunnel authenticates gateways, not people
  • Set up on request with the TestingOps team

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A partner portal's test environment accepts outside services only over IPsec site-to-site. The network team sends the remote gateway address, IKEv2 proposals and a pre-shared key, and the QA team asks the TestingOps team for an IPsec setup.

While the setup is agreed, the team runs the cases that do not need the internal network. Runs over the tunnel start once the TestingOps team confirms it is up.

Frequently asked questions

Can we set up IPsec ourselves?

Not yet. The IPsec option under Integrations → Private networks (VPN) saves the parameters, but the gateway machine does not bring an IPsec tunnel up by itself. Ask the TestingOps team for a setup on request.

Is there SSO or MFA for IPsec?

No. A site-to-site tunnel authenticates the two gateways with a pre-shared key or a certificate, so no person signs in. For VPNs with SSO or SMS codes, see GlobalProtect, Cisco Secure Client, FortiClient, Ivanti Connect Secure and Check Point.

Which IKE settings does the form take?

IKEv2 or IKEv1, optional proposals such as aes256-sha256-modp2048 and an optional remote ID, with a pre-shared key or a PEM certificate.

What can we use until IPsec is set up?

A VPN user account on one of the self-service VPN connections, or a RunningOps host inside your network.

Next step

Ask in a demo whether an IPsec site-to-site tunnel or a host inside your network fits your test environment.

Request a demoMore private networks integrations