Services
What we do
Three areas of work, each scoped in writing before it starts.
Vulnerability research
We look for security flaws in software, firmware, and network-exposed systems, work out their root cause and real-world impact, and document them so they can be fixed.
- Software: applications, services, and libraries.
- Firmware: embedded devices and the software that runs on them.
- Network-exposed systems: services and protocols reachable over a network.
Research combines source and binary analysis, reverse engineering, and testing against running systems. Each confirmed issue is written up with its root cause, the conditions needed to trigger it, a way to reproduce it, and guidance on fixing it. Issues found through our own independent research are reported to the vendor under our disclosure policy.
Security assessments and code review
We assess the security of a product, system, or codebase against an agreed scope, and report what we found, how we found it, and how to fix it.
- Security assessments of applications and systems.
- Source code review focused on security defects.
- A written report with findings, evidence, and remediation guidance.
Scope, access, timing, and rules of engagement are agreed in writing before work begins. Findings are rated by severity and written so that an engineer can reproduce and fix each one. Results are confidential to the client, and we can retest once fixes are in place.
Coordinated vulnerability disclosure support
We help researchers and vendors handle a vulnerability report properly: reaching the right contact, agreeing a timeline, and publishing accurate information once a fix is available.
- For researchers: reporting a finding to a vendor and managing the conversation.
- For vendors: receiving reports, triage, and advisory drafting.
- CVE ID requests and advisory publication.
This suits researchers who have a finding and want help reporting it well, and vendors who have received a report and do not yet have a process for handling one. Support can cover a single report or the setup of an ongoing intake process, including a published policy and a security.txt file.
Our own reporting practice is described in the disclosure policy.
Not sure which of these fits?
Describe the product or problem in a few lines and we will suggest a scope.