Your practice (or your client)
You chose the firewall, access points, and any network hardware, and you decide when it’s time to replace something.
Network administration Administration réseau
We administer the network your client already bought.
This page isn’t about network design. It names day-to-day changes — firewall rules, VPN accounts, Wi-Fi networks — as their own delivered line, while explicitly keeping hardware and the vendor relationship with your practice, consistent with the site’s rule that you keep every commercial decision.
Delivery team
We make the day-to-day changes on what’s already installed — rules, VPN accounts, Wi-Fi networks — and watch for the kind of configuration drift that quietly opens a door nobody meant to leave open.
Firewall, VPN, and Wi-Fi changes
For a client whose firewall, VPN, and Wi-Fi are already in place and need regular, careful administration rather than a new network design.
What we need first
Administrative access to the existing firewall and wireless controller, the rule or network map you want maintained, and who approves a new rule or VPN account.
What’s included
- Firewall rule and VPN account changes you’ve approved
- Wi-Fi network changes on existing hardware
- Drift checks against the configuration baseline you set
Handled separately
- Choosing, purchasing, or licensing network hardware
- A full network redesign or a new site build — that’s project work
- Opening a rule or VPN account without the named approver’s sign-off
What you get: Network changes that happen on request, get checked against a baseline, and come back with a note — not a black box only one person understands.
What we hand back: A change note listing what moved, why, and who asked for it.
What stays your call before you sell this line
Hardware and vendor stay yours
Network hardware, firmware, and warranty support remain your (or your client’s) relationship with the vendor. We work inside it; we don’t replace it.
What counts as a change versus a project
A new rule is a change; a new site or a hardware swap is quoted separately, as the project and rollout capacity page names it.
Emergency changes
Define what counts as urgent enough to bypass the normal approval queue — and who can make that call — before the first incident forces the question.
Multi-site or multi-firewall accounts
A client with several sites or several firewalls needs named ownership per site or per device before month one, not after.
What this line doesn’t include
- Designing a new network from scratch
- A guaranteed uptime commitment for the underlying internet circuit
- Vendor warranty or hardware RMA handling
Straight answers on network administration
Do we need to already use a specific firewall brand?+
No — this line is administered on whatever network hardware your client already has in place. Choosing and purchasing the hardware stays your decision, before and after launch.
What if a rule change needs to happen outside business hours?+
That’s a scope conversation, not an assumed default. Name upfront what counts as urgent enough to bypass the normal approval queue, and who gets to make that call.