// SYS.ONLINE — 2501.AI COMMAND INTERFACE
[STATUS: ACTIVE]
2501/Agent specialties/FortiOS Manager/Setting up a site-to-site VPN on a FortiGate

SOLUTION //

FortiOS Manager

Setting up a site-to-site VPN on a FortiGate

A site-to-site VPN needs matching security settings at both ends. How 2501 configures the FortiGate end from your ticket and reports what is missing instead of guessing.

A site-to-site VPN request with no shared key ends with 2501 configuring the FortiGate end of the tunnel, its route and policies, verifying each change and leaving the key for your team rather than guessing it

ServiceNow or another ITSM

Your rules, confirmation and blacklists

Investigate only, with a person, or on its own

On-prem, cloud or hybrid

SOLUTION_BRIEFING

// HOW 2501 HANDLES IT

A site-to-site VPN comes up only when both ends agree on their security settings, so filling a gap in the request with a guess gives you a tunnel that looks configured and carries nothing. 2501 configures the FortiGate end from your ticket and reports anything missing rather than inventing it, all within limits you set.

Beyond the remote address and the networks on each side, a tunnel needs security settings that match the far end exactly, a route, policies that let the traffic through and a shared key the ticket often leaves out. One wrong or missing piece leaves it down, or up with the traffic blocked.

What 2501 does

The FortiOS specialty takes the request from your ticketing system and checks what already exists on the FortiGate against the ticket. It reuses objects rather than duplicating them, follows your naming conventions, and goes back to the requester when what is there contradicts the ticket. It configures this end of the tunnel, with the route and policies the traffic needs, and verifies each change once made. Without the shared key, it configures everything else and leaves the key for your team to enter. It reports what it found and what it changed.

How 2501 handles a site-to-site VPN request on a FortiGate: signal, check what already exists against the ticket, configure this end of the tunnel with its route and policies within your rules, report what it changed and anything missing rather than guessing it

You stay in control

  • You choose the level: investigate only, act after a person confirms, or act on its own within your rules. The level is set per specialty, not per ticket.
  • Nothing is guessed: a missing address, network or setting goes back to the requester rather than being filled in.
  • Existing policies stay as they are: they change only when a ticket explicitly asks, and a duplicate is reported to the requester rather than created.
  • Your rules apply: which FortiGates it may change unattended and which changes need a person first, and blacklisted commands stay out of reach.

Frequently asked

Why is the tunnel up but no traffic passes? Traffic also needs a route and a policy on each side, and both ends must agree on which networks they exchange.

Can it check an existing tunnel instead? Yes. It investigates tunnels that are down, and in investigate-only mode it reports what it found and changes nothing.

Related

> READY_TO_DEPLOY

SEE IT ON YOUR OWN INFRASTRUCTURE

Book a technical demo and walk through your own environment with the 2501 team.

REQUEST DEMO

CONTACT SALES