We determine which systems employee, vendor and branch connections need to reach. We plan authentication and permission scope for remote users, and tunnel and routing requirements for inter-branch connections, separately.
We address MFA and group-based permissions for remote user access, and encryption, endpoint authentication and routing for inter-branch tunnels. We also decide where connection logs are kept.
01
Does MFA require an additional license?
It depends on the platform you use. We evaluate the capabilities of Entra ID, the firewall vendor’s token solution or your current identity provider and recommend the option with the least additional cost.
02
Is split tunneling secure?
It can be risky when used without control. The decision is made by looking together at when internet traffic should go out locally, the state of endpoint protection and the need for web filtering.
03
Do vendors need a separate solution?
In most cases the existing infrastructure is sufficient with a separate group, time-limited accounts and restrictions on target systems. For critical OT or administrative access, PAM solutions that record sessions can be considered.
04
Should we move to ZTNA instead of VPN right away?
Not necessarily. First VPN policies are narrowed and MFA is completed. A ZTNA migration is planned in phases once the application inventory is ready.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Current state
VPN users, tunnels, authentication and the systems accessed are mapped.
02 / PLAN
Access matrix
Group-based target systems, the MFA model and the vendor process are designed.
03 / EXECUTION
Pilot and migration
It’s tested with a pilot user group, then migrated in phases.
04 / HANDOVER
Monitoring and handover
Log and alarm rules, a user guide and administration documentation are delivered.