Three locks on the door, none of them locked
Found and closed three SSH brute‑force protections that had never
worked: a ban jail watching port 22 while the daemon listened on
1986, a rate limit shadowed by a broader rule above it, and a ban
action whose binary never resolved, so no ban had ever applied.
August 2026

Situation. A hardening review of the production host in August 2026
asked a question that usually gets a confident answer: are the SSH
brute‑force protections working. All three were configured, all
three appeared in every report anyone looked at, and all three had
been inert since the day the host was built.

Task. The controls had to be checked against what the kernel
actually does with a packet, rather than against the configuration
files that describe what should happen to one.

Action. Reading the configuration would have confirmed the wrong
answer three times, so the review read the running system instead.
The intrusion‑banning jail was watching port 22 while the daemon had
been moved to 1986 during the initial hardening — every ban it wrote
named a port nothing listened on. The firewall's rate limit was
worse in a subtler way: the rule existed, and it sat below a broader
rule that matched first. Firewall user rules are evaluated top down
and the first match wins, so a broad allow above a rate limit makes
the limit dead code that still prints in every status listing. The
third was the quietest of them: the ban action shells out to a
packet‑filter binary that the package system only recommends rather
than requires, so on a host without it the jail starts, counts and
decides, and then fails at the one moment it tries to ban. All three
fixes were small. What came out of it was not the fix but two rules
that now govern the repository: a security control gets an assertion
rather than a comment, and a firewall is verified by rule position
rather than by rule presence.

Result. Three protections that had never once fired now do, and the
class of defect they belong to — a control whose failure mode is
that it keeps reporting healthy — is the class the platform's checks
are now built to catch. All three had been inert from bootstrap. All
three printed healthy in every place anyone looked, which is the
whole reason they lasted.

Categories:
1Infrastructure	/categories/infrastructure/	engineer.company	70
1Monitoring & Observability	/categories/observability/	engineer.company	70
1Networking & VPN	/categories/networking/	engineer.company	70
1Linux & Servers	/categories/linux/	engineer.company	70
1Security	/categories/security/	engineer.company	70
1System Administration	/categories/system-administration/	engineer.company	70

Services:
1Site Reliability & Monitoring	/services/site-reliability/	engineer.company	70
1Networking & VPN Setup	/services/networking-vpn/	engineer.company	70
1Security & Access Management	/services/security-access/	engineer.company	70
1AI Agent Security	/services/ai-security/	engineer.company	70

hThis page on the web	URL:https://engineer.company/portfolio/three-locks-on-the-door-none-of-them-locked/	engineer.company	70
