For product and engineering teams acting on an assessment, vulnerability report or important security change.
When you have findings and need a clear path to closing them.
What we examine
- Review the original evidence, affected version and proposed changes.
- Discuss root causes, remediation options and priorities with the responsible team.
- Verify agreed fixes against the original issue and relevant related behavior.
How an engagement runs
Send a short brief
The product, what changed, what you need to know and by when. A paragraph is enough, and I reply within three days.
Get a written proposal
Scope, method, exclusions, deliverables, price and dates. Confidentiality, NDA and retesting terms are agreed in the same proposal.
Follow the work as it develops
For assessments, you see evidence and priorities as they emerge. For engineering, you review the agreed milestones.
Report and walkthrough
You receive the report or the delivered work and a walkthrough with your team. Any further fixes or verification are agreed with you.
I find the cause, then write the fix.
I wrote the patches behind two Linux kernel CVEs and seven more fixes now in mainline. On your product, each finding comes with the code path, the conditions that trigger it and a fix your team can review.
See the 9 merged kernel patchesQuestions before we begin
Can you work with a report from another assessor?
Yes, subject to access and sufficient evidence. We first establish what the original findings show and what needs reproduction, clarification or verification.
Will you implement the fixes?
Developer consultation and verification can be scoped independently. Any implementation or patch work requires its own agreed responsibility, access and acceptance criteria.
Does a successful retest mean the whole product is secure?
It establishes the result of the agreed checks on the tested version. The verification report identifies its scope and does not substitute for an assessment of unrelated areas.
How quickly will you reply?
Within three days at most. You get questions about your product or an outline of the proposal.
What does it cost?
Published prices are starting points. The final price depends on scope and technical complexity and is fixed in the written proposal before work starts.
How long does it take, and when can you start?
Duration and start date depend on the scope, the technical complexity and my current workload. The proposal states the dates.
Can we work under an NDA?
Yes. Confidentiality terms, including an NDA if you need one, are agreed as part of the proposal before you share code, credentials or findings.
Is a retest included?
Retesting is agreed for each engagement in the proposal: which findings, which version and the time window.
Do you work with agencies?
Yes. Agencies can bring me in for a client’s project. Delivery terms, including white-label reports, are agreed case by case in the proposal.
Related reading
- CVE-2026-118527: The Ivanti CVE CISA's Own Catalog Can't Explain
- GhostAction: deleting a secret is not revoking it
- ConnectWise Cloud Backup: the app never needed MFA