Security research wasn't a decision — it was a consequence. When you've been building and running private data centers since 1996, you either get serious about security or you get serious about apologizing to clients. Cdoc chose the former.
Thirty years of infrastructure means thirty years of watching how things fail — and building solutions when the vendor options weren't good enough.
That path led from hardening our own infrastructure to researching threats on behalf of clients, and eventually to building our own tools. The lab is where that work happens — quietly, continuously, and without a press release.
MooseWall is a Cdoc-built firewall platform that has been protecting client networks since 1996. These two units are typical of what ships — compact, purpose-built, Cdoc-badged, and running software that didn't come from any vendor catalog.
Active development continues. The threat landscape keeps moving and so does MooseWall. See the MooseWall service page for what it does for clients today.
This is what MooseWall looked like at the beginning. The hardware has changed considerably. The philosophy hasn't — purpose-built, locally controlled, no vendor dependency for the security decisions that matter most.
Building our own data centers meant we had to solve our own security problems. Those solutions eventually became a service. That's how most Cdoc services start.
Security research is ongoing. Some of it we can talk about — threat research, architecture decisions, the evolution from early packet filtering to modern stateful inspection and threat intelligence. Some of it we can't talk about yet. The full story lands here when it's ready to be told.