Design a Cisco network around business traffic, physical sites and failure scenarios, with a clear plan for implementation and handover.
Proxar · UK expertise
Secure remote access
People working away from the office need access to their tools, not unrestricted access to everything. We help plan remote connections around the person, the device and the work they need to do.
A cloud application, a private server and an administrator’s tools may each need a different approach.
Technology partnerships
Technology partners you know
We help you choose and look after the technology your team uses every day.
Begin with who needs to reach what
List the applications, information and administration tools involved. Consider employees, contractors and administrators separately, along with device ownership and any restrictions from application suppliers or partners.
A contractor supporting one application may need a limited session, not permanent access to the office network. Administrative permissions deserve particular care because of the wider changes they allow. Make those differences explicit before choosing a connection method.
Make the design usable when life is not routine
Identity, authentication, device checks and permissions need to fit together. So do logging, support and access removal. Check client compatibility, licences and existing infrastructure rather than assuming the chosen product works with every device already in use.
People replace phones, travel and lose their usual authentication method. The access design needs a supportable recovery route for those situations. A control that only works on an ideal day can encourage unsafe workarounds when someone urgently needs to get back to work.
Professional using a laptop and security key for secure remote access · Illustrative image
Pilot complete working tasks
Test the applications people actually need, including access restrictions and removal of permissions. Check that a permitted user can complete their work while a contractor or personal device cannot reach resources outside the agreed access.
The pilot should also exercise the support process. Staff need to know how to report a problem without sharing credentials or bypassing controls. Time-limited supplier access should have an approval and expiry process, not quietly become a permanent connection.
For wider links between offices rather than individual users, explore SD-WAN and business VPNs. The connection technology is only useful once the access requirement is understood.
Client experience
What our clients say
“Proxar’s exceptional responsiveness and seamless collaboration with building management and service providers enabled them to deliver a rapid solution that exceeded our expectations.”
Before you decide
Your questions, answered
Does every remote worker need a VPN?
Not necessarily. It depends on where the required resources run and how they support access. A cloud application and a private network may need different controls. Start with the user’s tasks and the permitted resources, then choose an appropriate method rather than assuming one connection fits everything.
Can staff use personally owned devices?
That needs an assessment of the applications, information involved and controls available. Personal and managed devices should not automatically receive the same access. The design should state what each can use, any restrictions and what happens when the device can no longer meet the agreed requirements.
How should we handle supplier or contractor access?
Give access a purpose, an owner and a review or expiry point. Identify the particular resources needed and how the session or account is authorised. Avoid broad permanent access simply because it is convenient, and include a way to confirm access has been removed when the work ends.
What happens when someone cannot complete the normal sign-in?
Plan a support and recovery process in advance, including how identity is checked and who can authorise an alternative. A lost phone or replacement device should not lead to shared passwords or disabled controls without review. The process needs to be tested alongside the normal connection.
Your next step
Remote access getting in the way—or opening too much?
Tell us who needs to work remotely, which resources they use and how access works today. We will help you find an approach that supports the task without giving more access than it needs.