// service
Fixed-scope security research engagements with a written scope and a fixed price before any work starts. Every finding is reproduced against the build in scope, tied to a real attacker position and written up at advisory grade: the same standard the published CVEs had to meet.
Source review and live testing of the layer your AI product runs on: inference servers, LLM gateways, application platforms, RAG pipelines, agents and MCP integrations, accelerator runtimes. Typical engagement window: 2 to 4 weeks.
Scope & deliverables→Implementation review of boot-chain firmware, privileged handlers and the drivers that sit between an AI workload and the hardware. Typical engagement window: 3 to 4 weeks.
Scope & deliverables→Review of cryptographic implementations and the code around them: post-quantum and classical schemes, TLS stacks, signature verification and key handling. The area behind most of the published CVEs. Typical engagement window: 3 to 4 weeks.
Scope & deliverables→Each engagement is a source-level review backed by live testing of the running build. Reading the code finds what a test cannot reach, and testing the build proves what the code only suggests. Nothing reaches the report on the strength of reading code alone.
For teams that ship security fixes continuously: a monthly research retainer covering variant analysis of the security fixes you merge, watch on the upstream projects you depend on, and a written advisory for anything that turns up. Sized to the codebase, monthly notice.
The report is written to be handed straight to whoever asked for it: customer security questionnaires, SOC 2 / ISO 27001 evidence requests, ISO/IEC 42001 and NIST AI RMF work for AI systems, procurement or investor review.
// scope & quote
Send the repository or product, the component you care about most, the build under review and the window you have in mind. A written scope and a fixed price come back before any work begins.
