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.

A circuit board's UART debug header wired to a USB serial adapter, with boot output on a console.SoCTXRXGNDVCCVCC left unconnectedUSB-UARTRXTXGND115200 8N1Hit any key to stop autoboot: 2
Finding a debug interface: a board's UART header wired to a serial adapter.
An SPI flash memory chip lifted from a circuit board and read out as a firmware image, shown as a hex dump.U4SPI flashCSVCCDOHOLDWPCLKGNDDIflash.bin8 MiB00000027 05 19 56 5a 1f0000063c 9e 00 00 5f 8c00000c00 1f 4a b0 80 0000001200 00 6d 0e 91 c40000204c 69 6e 75 78 200000266b 65 72 6e 65 6cยทยท1f000068 73 71 73 2e 071f000600 00 9a 4c d1 631f000c00 00 04 00 1d 00
Reading firmware: a flash chip lifted from the board and dumped for analysis.

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.

A source code listing with one line flagged as a finding: a copy whose length is never checked against the buffer size.parser.c38static int handle(pkt_t *pkt) {39 uint8_t buf[64];40 uint16_t len = read_u16(pkt);41 memcpy(buf, pkt->data, len);42 return parse(buf, len);43}FINDING stack buffer overflowlen is never checked against sizeof(buf)
An illustrative finding, using example code.

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.

Coordinated disclosure: a private report to the vendor, then a fix, then a published advisory, within 90 days.Reportto the vendorFixvendor patchesCVEAdvisorypublishedDay 0coordinationDay 90
From private report to published advisory.

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.

Get in touch