The internet is working, so the firewall must be fine. It is an easy assumption to make about equipment that sits quietly in a cabinet. But a router, firewall, or remote access gateway can keep passing traffic while its software, management access, or support status needs attention.
These devices sit where your business meets outside networks. A managed firewall conversation should cover how it is configured, maintained, monitored, and eventually replaced. Buying the appliance is the beginning of that work, not evidence that someone is still doing it two years later.
Know the equipment and its support life
Record the model, installed software, owner, subscriptions, and vendor support dates. A device can be physically reliable and still be end of support. If security fixes are no longer available, a replacement plan belongs in the budget. Waiting for the hardware to fail may leave an avoidable exposure in place.
CISA’s edge-device guidance specifically calls attention to unsupported equipment, management interfaces, authentication, configuration, and recovery. Some CISA directives apply to federal agencies; that does not make every associated deadline a requirement for your private business. The technical reasons to review unsupported edge equipment remain relevant.
Source: CISA edge device security
Check who can manage it and from where
An administrative interface should not be casually exposed to the internet. Review the approved management route, named administrator accounts, authentication, and the people who still have access. Former providers and employees should not retain privileges simply because the connection has continued to work.
Keep the rules understandable. A temporary exception for a vendor or a troubleshooting session should have a purpose, an owner, and a review date. Otherwise the configuration gradually becomes a record of requests that nobody remembers. Remove unused access carefully, with an understanding of what depends on it.
- Review firmware and security advisories against the deployed model and version.
- Confirm that required security features and subscriptions are active and configured.
- Separate guest and other appropriate network traffic from sensitive business systems.
- Protect configuration backups and test how equipment would be restored or replaced.
Balance protection with a usable network
A rule that disrupts a business application needs investigation, not an automatic instruction to turn protection off. Understand the traffic and the work being done. It may be possible to make a narrow adjustment rather than opening a broad exception. Document what changed so the next person has the context.
RIKR prefers Cisco Meraki for managed networks while remaining vendor agnostic. We work with environments using Ubiquiti, Arista, Palo Alto, and many more. The right recommendation depends on the equipment you have, your business requirements, and the practical path to supporting it.
Ask what the management agreement covers
Equipment allowances, remote support limits, hardware costs, and subscriptions should be clear. RIKR’s Managed Networks page explains the defined location plan and the separate connectivity consulting work. A network management service and an internet service contract are different things, even when one team helps you coordinate them.
The useful result is knowing who maintains the equipment your team depends on and what happens when it needs attention. That is a better position than discovering the login, subscription, and replacement problem during an outage.
Explore RIKR Managed Networks and connectivity consulting
Related: build a repeatable patch management process
Written by Joshua Price
Back to the blog