Managed security
That rule says TEMP.
It’s from 2019.
Firewalls configured, intrusion detection and prevention tuned, VPN tunnels kept tight. Every rule gets a reason and an owner, and the network gets split up so one bad laptop stays one bad laptop.
- Firewall configurationWhat network security coversWatching
- Rule review and change controlWhat network security coversWatching
- Intrusion detection and preventionWhat network security coversWatching
- Segmentation, testedWhat network security coversWatching
- Secure VPN tunnelsWhat network security coversWatching
- Hands on the hardwareWhat network security coversWatching
Foothills Digital—Sentrello Premier Partner
- AWS
- Azure
- Google Cloud
- DigitalOcean
- On-premises Linux
- On-premises Windows
Every one of our people holds active certifications on the platforms they work on.
Sentrello is our only partnership. On the clouds, it's our people who hold the certifications. We don't claim a partner tier, and we'll keep saying so until that changes.
Where this usually starts
Your rule base is a fossil record
Somebody set it up carefully once, then left. Since then, rules have been added in a hurry and removed never.
- The rule list is so long that nobody dares delete anything, in case something breaks.
- Intrusion prevention is licensed, switched on and set to alert only. It hasn’t stopped a single thing.
- A laptop on the guest Wi-Fi can ping the finance server, and nobody’s checked what else it can do.
- Remote desktop is open to a supplier, and nobody can find the email that asked for it.
- The VPN was getting replaced last year. It still is.
What we do instead
Every rule has to justify itself
A firewall is a list of decisions, and a decision without an owner is a hole. We go through yours line by line and attach a reason and a person to each rule. Anything with neither gets disabled, watched, then removed. From then on, every change goes through a request and a review, and the intrusion prevention actually prevents. Segmentation does the rest. Your finance server sits on its own network, so an infected laptop has to get past a firewall to reach it, not just a switch.
How it works
How network security runs
It starts with a cleanup, because everything after it depends on one.
Read every rule
What it allows, who asked for it, and whether anything has matched it since the logs began. Unused rules get disabled with a note. If nothing complains, they go.
Put a process in front of change
A rule change is a request with a reason, a reviewer and an expiry date. “Temporary” means it switches itself off on that date. Each change is a commit, so the firewall’s history is a diff, not somebody’s memory.
Turn detection into prevention
Intrusion signatures start in alert mode, get tuned to your traffic until the noise is gone, then move to block. An IPS that only alerts is a subscription, not a control.
Segment what matters
Finance, servers, building systems, guest Wi-Fi and staff laptops each on their own network, with a firewall between. Ransomware on one machine makes for a bad afternoon. On a flat network, it’s the whole company.
Lock down the VPN tunnels
MFA on every connection, an appliance patched the week the advisory lands, and access scoped to what each person needs. Site-to-site tunnels get the same treatment. If the VPN should be retired, we’ll say so and put a date on it.
What network security covers
Firewall configuration
Rule base, NAT, routing and the object groups behind them, kept in version control on infrastructure you own. Any engineer can read why a rule exists, and if we ever part ways the configuration stays exactly where it is.
Rule review and change control
Each rule has a reason and an owner. Each change has a request, a reviewer and a log entry. Temporary rules carry an expiry, because the ones that never expire are the ones that get used against you.
Intrusion detection and prevention
IDS/IPS signatures tuned to your traffic so alerts mean something, then switched to block. Whatever fires joins the same queue as every other security alert, with the packet capture attached.
Segmentation, tested
Servers, workstations, guests, building systems and printers on separate networks, with the rules between them written down. We prove an infected laptop can’t reach the finance server by trying it.
Secure VPN tunnels
Remote access and site-to-site, with MFA enforced and access scoped per person rather than per network. Where something identity-based would serve you better, we’ll plan the move.
Hands on the hardware
Our engineers hold active certifications on the platforms they configure. Most of the work is remote. When a box needs racking or a site needs a visit, we’re out routinely across Denver Metro to Colorado Springs, and anywhere else by arrangement, with travel in the quote.
Related
Network Management
Your LAN, your WAN and your Wi-Fi, watched and configured as one system, right down to the circuit into the building. So when the office shouts that the internet’s gone, we already know which port it really was.
Managed Detection & Response (MDR)
Active threat hunting through your endpoint data for the intruder no alert caught, and a fast response the moment we find one. The SOC watches what fires. MDR goes looking, with your written permission to act.
Identity & Access Management (IAM)
Multi-factor authentication, single sign-on and privileged accounts, managed so a stolen password isn’t enough on its own. Admin rights get borrowed for an hour instead of kept for a career.
What sits at the edge, and what’s behind it?
Your firewall make and model, how many sites you run, and where the servers people rely on live.
That’s enough for us to explain how we’d review your rules, where we’d segment first, and whether the VPN is really the problem you think it is.
- What we arePlan, create, launch, maintain
- What we areSentrello Premier Partner
- What we areEvery quote written for you