Most security problems aren’t clever attacks. They’re doors that were left open by accident: a setting nobody changed, a test that was never switched off, an old route nobody remembered. Here are five we see most, and how to close them.
1. A sign-up form nobody remembered
Many systems have a “register” page that’s switched on by default: websites, code servers, forums, online tools. Bots search the internet for these constantly. In a recent security review of a self-hosted server, we found more than 63,000 fake accounts that bots had created, filling it with spam pages. Nobody had noticed because nobody was looking.
Fix: If a system doesn’t need public sign-ups, switch them off. If it doesn’t need to be public at all, require a login before anyone can see anything.
2. A firewall that can’t see who’s knocking
Many businesses put a service such as Cloudflare in front of their website. That’s a good idea, but it has a catch. Your own security tools may only see the service’s addresses, not the real visitors. Your firewall then can’t tell attackers from customers, and in the worst case it could block the wrong thing.
Fix: Check your access logs once. If every visitor shows up with the same few addresses, the real visitor addresses aren’t being passed through, and a setting needs changing.
3. An old access route that’s still switched on
When you replace one remote access method with another, the old one often stays behind. We found a leftover remote desktop route with no protection at all, open to anyone who found its address.
Fix: List every way into your network and check each one is still needed and still protected. Remove the rest.
4. Access rules that are too generous
A rule like “anyone with an email address ending in these domains can enrol a device” sounds sensible until you realise it includes people you never meant to trust. Rules like this are easy to write too loosely, because each line you add widens who gets in.
Fix: Review who is actually allowed, and make the rules as narrow as you can.
5. Open ports at the router
Hiding your address behind a service doesn’t close the ports on your own connection. Scanners find business internet connections quickly, and anyone who connects directly skips your website protection entirely.
Fix: Either restrict those ports so only your protection service can reach them, or close them completely and connect through a secure tunnel. With a tunnel, there’s nothing listening on your internet connection at all, and attempts to connect directly just time out.
Two good habits
- Add a second lock to anything that controls remote access, with a code from your phone as well as a password.
- When you move a service, check what depended on the old address. Firewall rules, routes and VPN settings are often tied to a specific address and quietly stop working.
And before you delete anything
If you’re ever cleaning up a system, verify your backups first and keep a copy somewhere separate. Deleting is the easy part. Recovering from a mistake is not.
Not sure what’s open on your network? We can review it, close what shouldn’t be open and tell you what we found in plain language. Get in touch for a security check.



