What's included
- Managed Fortinet FortiGate firewalls
- Switching and wireless design and deployment
- Site-to-site and remote access VPN
- Internet failover and multi-site connectivity
- Firmware and lifecycle management
- Configuration backups and change documentation
- Monitoring and alerting
How it's secured
- Separate networks for business, guest, voice and device traffic
- Deny-by-default firewall policies
- Management interfaces kept off the internet, with MFA for administrators
- Centralized logging with defined retention
- Firmware kept current against vendor security advisories
- Every change documented and backed up
A firewall is only as good as its rules.
Many of the firewalls we inherit have years of rules nobody remembers adding, management pages open to the internet, and firmware several versions behind. Each one is a way in.
We start every network engagement by documenting what exists and cleaning it up. Then we build to a standard: business systems, guest Wi-Fi, phones, cameras and other devices each get their own network segment, traffic between them is denied unless it's needed, and administrators sign in with multi-factor authentication.
Logs go to a central location with a defined retention period, so if something does happen there's a record of it. Because a certified forensic examiner leads our incident response, we design logging with investigations in mind, not just troubleshooting.
Why segmentation matters
Most breaches spread sideways. Segmentation keeps a single compromised device from becoming a company-wide incident.
Limit the blast radius
Cameras, phones and guest devices can't reach your business systems.
Shrink compliance scope
Isolating payment or CUI systems reduces what has to be assessed.
Know what's happening
Logging between segments shows where traffic goes and when something is wrong.
How this maps to compliance
Our standard supports these requirements. Your assessment scope, policies and evidence determine whether a requirement is met.
| Requirement area | What our standard puts in place |
|---|---|
| System and Communications Protection (NIST SP 800-171) | Boundary protection, segmentation and deny-by-default policies |
| Access Control: remote access | VPN with multi-factor authentication |
| Audit and Accountability | Centralized firewall logging with defined retention |
| Configuration Management | Documented configurations, change records and backups |
| PCI DSS: network security controls | Segmentation that keeps the cardholder data environment separate |
Common questions
Do you only work with Fortinet?
Fortinet is our standard because it lets us manage firewalls, switching and wireless consistently across clients. If you have other equipment, we will assess it and recommend whether to keep it, manage it or replace it at end of life.
Can you take over a firewall someone else set up?
Yes. We review the existing configuration, document it, remove unused rules and bring it up to our standard, usually before making any other change.
Do you support remote workers?
Yes. We configure remote access VPN with multi-factor authentication so staff can work securely from anywhere.
How do you keep firmware current?
We track Fortinet security advisories and schedule firmware updates in maintenance windows, with configuration backups taken first.
The rest of the standard
Every service is secured the same way, so they work better together.
Find out where your environment stands.
Tell us what you're working toward and we'll recommend a starting point. No obligation.