When the available firewalls weren't good enough, we built our own. That stubbornness turned into three decades of custom security infrastructure with zero breaches. The Moose holds the line.
The first MooseWall was built in 1996 out of necessity and mild irritation. The alternatives were disappointing. So we stopped using them.
Not a commodity appliance. Not a box with a vendor's name on it. Every MooseWall is built to spec for the environment it protects — configured from the ground up, not from a wizard.
We don't do "good enough." MooseWall is built to the highest standards we know — and after 30 years, we know quite a few. The rules are tight, the logging is thorough, and nothing gets through that isn't supposed to.
MooseWall has been protecting networks at the Lake of the Ozarks since 1996. The threat landscape has changed dramatically. The Moose has kept up with every bit of it.
In nearly thirty years of MooseWall deployments, we have not had a breach attributable to the firewall. We're not going to jinx it by saying more than that. But we said it.
Security through obscurity is not security. Security through committee is not security either. MooseWall exists because one person who understood the problem deeply decided to solve it properly, and has been refining that solution for three decades.
Every network is different. Every MooseWall is configured for the specific environment it guards — not cloned from a template, not auto-generated by a wizard. That's the difference between a lock and a vault.
