Engineering checklists for the teams who build security products.
Every checklist is fifteen questions our engineers ask before a kernel driver, an EDR agent, or a detection pipeline ships. Read the background here, then take the full list into your next planning meeting.
Risk checklist for kernel-level development projects
A single oversight in ring 0 becomes system instability or a production outage. Fifteen checks across three areas before your driver ships.
Secure coding practices for C and C++ in cybersecurity products
In security products, a coding defect is a vulnerability, not an inconvenience. Fifteen checks that pair memory, privilege and supply chain for any C/C++ security codebase.
Secure memory management in C++ cybersecurity codebases
Memory handling is still the largest single source of vulnerabilities in C++ security software. Fifteen checks across lifetime, boundaries and runtime assertions.
Evaluating EDR agent performance and security
An agent that detects well but eats the CPU, or can be switched off, is a different kind of risk. Fifteen checks across footprint, detection and resilience.
Is your EDR solution scalable to 100K+ endpoints?
Most platforms look fine in a 5,000-endpoint pilot. Fifteen checks across agent efficiency, detection at scale, and platform operations.
Is your detection system ready for Zero Trust?
Zero Trust means nothing is trusted by default — including your own agent. Fifteen checks across verification, agent integrity, and response.
No checklists in this category yet.