For security product teams and engineering organizations building analysis capabilities, extending scanners or evaluating the quality of their security testing tools.
When you need to build, extend or evaluate a security analysis capability.
What we examine
- Define the analysis goal, target technologies, access, constraints and acceptance criteria.
- Design the agreed architecture or implement and extend selected analysis, detection or scanning components.
- Evaluate the agreed capabilities against representative targets, documenting coverage, findings and limitations.
- Plan integration and handoff around the team’s workflow and maintenance needs.
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 build software, so my fixes fit your codebase.
I have led web development and designed a DAST scanner from its architecture up. When I recommend a fix, I have already considered how your team will implement and test it.
See how I built HendraQuestions before we begin
Do you develop security tools?
Yes. I design and develop SAST and DAST applications. An engagement can cover architecture, selected detection components, extensions, integration or evaluation. The proposal defines the target technologies and what will be delivered.
What have you built?
Hendra is my modular, context-aware DAST scanner developed during completed doctoral research at ITMO University. I designed its core architecture, technology identification, scan planning, request deduplication, finding review and benchmarking approach.
Can you extend an existing tool?
Yes, where its architecture, access and licensing permit the agreed work. We first establish the extension points, required behavior and tests for the target capability.
Which languages can a SAST project cover?
Language coverage is defined for each project. We review the target language, available analysis infrastructure, code patterns and evaluation cases before agreeing development. Coverage and limitations are documented.
Can you evaluate a tool before we invest in development?
Yes. A scoped evaluation can examine detection behavior, useful coverage, triage effort and integration constraints. Published lab benchmarks provide context; the evaluation needs targets and criteria relevant to your team.
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
- PHP2Shell: CVE-2026-109618 and the Runtime Boundary
- Lovable and Supabase security checklist: what to check before launch
- How much does a web application pentest cost, and what is included?