SOLUTION //
FortiOS Manager
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.

TICKETS FROM
ServiceNow or another ITSM
SAFEGUARDS
Your rules, confirmation and blacklists
AUTONOMY
Investigate only, with a person, or on its own
DEPLOYMENT
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.
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.

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.
> READY_TO_DEPLOY
Book a technical demo and walk through your own environment with the 2501 team.