Services · Security
Security as operating practice.
We harden systems and keep the public surface small. This page does not publish internal tooling, addresses, or control-plane architecture.
What we implement
- Server hardening and a defined patch/update path.
- Web application security: input handling, session discipline, and least privilege in the app layer.
- Access control for people and services, with administrative paths kept off the public story.
- TLS, security headers, and conservative cookie/referrer policy.
- Firewall conception and rate limiting sized to the service, not copied from another host.
- Logging, monitoring, and backup/recovery treated as part of security, not as an afterthought.
- Deployment practices that do not require secrets in the public tree.
What we will not publish
Internal security products, rule sets, IP lists, and architecture diagrams stay unpublished. We do not describe or alter CDPGuard here.
Application work continues on web applications. Ongoing care is managed IT.