What they have actually built
We examine the architecture and critical code supporting the target’s claims.
Independent security diligence for investors, acquirers, and enterprise buyers who need to know what they would actually be taking on.
Diligence scope
We check the target’s claims against available evidence and identify what remains unverified.
We examine the architecture and critical code supporting the target’s claims.
We separate demonstrated security posture (findings, fixes, incident history) from assertions with nothing behind them.
We surface the vendors, platforms, and technical debt that become yours on the day the deal closes.
We state the evidence gaps plainly, so an unanswered question never reads as a clean result.
Timing
A commitment depends on the target's technical reality.
A strategic platform will inherit trust and operational reach.
A grant or partnership needs independent validation.
Security assertions made during a deal require technical review.
Our approach
Agree the investment, acquisition, vendor, grant, or partnership question. Identify the technical claims to check and the evidence needed to assess them.
Review architecture, code, controls, and incident history within the access provided. Record what supports each claim and what remains unverified.
Investigate the gaps with the greatest impact on the decision. Rank red flags and unresolved questions, with the evidence needed to close them.
Prepare an executive summary connecting findings and remaining unknowns to the transaction or commitment under review.
What you receive
Risk drivers and the evidence behind them.
The questions still open, and the evidence we would need to close them.
Findings translated into implications for the transaction or commitment.
Your engagement team
A principal leads each engagement. Your proposal names the specialists assigned to the scope.
Principal Advisor
Head of Security at Agora, responsible for security, data protection, and corporate IT risk. Earlier at EY, led assessments across financial services, healthcare, and government.
Founder & Partner
Led a security engineering practice for Rust and non-EVM systems across Substrate and NEAR. Earlier, built vulnerability-detection engines at Invicti used by Fortune 50 and public-sector organizations.
Specialist Advisor
Head of Security at Gauntlet, with experience in product security, IAM, cloud, DevSecOps, and blockchain. Previously held security roles at Tensor, EY, Broadcom, and ADP.
FAQ
We scope the work around the available documentation, interviews, and operational evidence. If the review includes code, we need access to it during scoping. Without code, some implementation claims may remain unverified. The report distinguishes supported conclusions from open questions.
Yes. Diligence can support vendor selection, investment, acquisition, partnership, or grant decisions. We tailor the review to the technical risks and dependencies you would take on.
We scope the work around your decision date and available access. If the timeline limits what can be examined, the report identifies those gaps and their implications.
We explain the technical risks, remediation effort, and unresolved questions relevant to the decision. The investment, acquisition, or vendor decision remains with you.
Yes. We assess their scope, findings, remediation evidence, and relevance to the current system. Previous reports help focus the work, but they do not establish the security of changes made since the review.
Describe the decision, available access, and deadline. We will propose a diligence scope.
Discuss your scope