You should be able to check our work. We test against eight public standards, so every finding carries references you can look up and a score you can recalculate yourself. Here is what we follow, what ends up in your report and what we hold.
PROVEN OWNERSHIP FIRSTACTIVE TESTS RUN ONLY ON ASSETS YOU HAVE SHOWN ARE YOURS, THROUGH A DNS RECORD OR A SIGNED AUTHORISATION.
A PERSON BEFORE YOUNO RAW SCANNER OUTPUT REACHES YOU. ONE OF OUR SPECIALISTS CHECKS EVERY RESULT BEFORE IT IS RELEASED.
THE SMALLEST PROOFWE SHOW A PROBLEM WITH A SMALL, MASKED SAMPLE. WE NEVER PULL WHOLE DATABASES TO MAKE A POINT.
A FULL RECORDSCOPE, APPROVALS, EVERY COMMAND AND EVERY FILE WE CREATED OR REMOVED ARE LOGGED, READY FOR YOUR AUDITOR.
ONE FINDINGILLUSTRATION
STANDARDS
Eight standards anyone can look up
Our catalogue holds 105 checks in 14 categories. Each one points back to a public standard, so nothing in a report rests on a definition we made up.
We also say where we cannot certify you: nobody issues a NIST CSF certificate, and the ISO 27001 certificate comes from an accredited body, not from us.
HOW WE TEST WEB APPS
The checklist that sets the order of a web test. Coverage follows the guide, so it does not change with the person doing the work.
IN THE REPORT · SECTIONS 02 AND 06, 105 CHECKS
HOW WE TEST MOBILE APPS
The equivalent for iOS and Android: what the app stores, how it talks to the system, its cryptography and the build checks a mobile release needs.
IN THE REPORT · MOBILE APP TESTS AND THE API BEHIND THEM
HOW AN ENGAGEMENT RUNS
The phases of a test from beginning to end: scope, reconnaissance, threat modelling, exploitation and the report.
IN THE REPORT · SECTIONS 01, 02 AND 07, FROM SCOPE TO SIGN-OFF
WHAT AN ATTACKER WOULD DO
Every finding is tagged with the technique an attacker would use. You can hold our findings next to what your monitoring already detects.
IN THE REPORT · SECTIONS 03 AND 05, TACTIC AND TECHNIQUE ID
WHY IT HAPPENED
The class of mistake behind each finding, so your developers can look for the same pattern elsewhere in the code.
IN THE REPORT · SECTIONS 03 AND 05, ROOT-CAUSE CWE ID
WHERE YOU STAND OVERALL
There is no NIST certificate. We show you, one function at a time from Govern to Recover, where you already meet the framework and where you fall short.
IN THE REPORT · SECTION 05, ALL SIX FUNCTIONS
HOW SEVERE IT IS
Each score comes with its full vector. Anyone can recalculate it, and other tools and vendors read it the same way.
IN THE REPORT · SECTION 03, BASE SCORE AND VECTOR
BEFORE YOUR AUDIT
We are not a certification body and do not issue the certificate. We check you against the 93 Annex A controls and give you written evidence, so you walk into the formal audit knowing what is still open.
IN THE REPORT · ORGANISATIONAL, PEOPLE, PHYSICAL AND TECHNOLOGICAL CONTROLS
THE REPORT
Seven sections, always in this order
A PDF you can forward as it is to a large customer, your DPO or an auditor. Every finding inside it carries the same ten fields.
SeverityCVSS v3.1 scoreExact locationEvidenceOWASP Top 10CWEATT&CK techniqueNIST CSF functionConfirmed or notThe fix
01Executive summaryYour position, the main risks and the key numbers on one or two pages, readable without an engineer in the room.
02Scope and methodWhat was tested, what was left out, when, and which method we followed.
03FindingsCritical first. Each one has evidence, steps to reproduce and a concrete fix.
04What to fix firstOrdered by how exposed you really are. Anything already exploited in the wild goes to the top.
05Compliance mappingFindings counted by OWASP category, ATT&CK technique and NIST CSF function, ready for an audit file.
06What passedEvery check that came out clean. Without it you cannot tell a good result from a test that skipped things.
07Sign-offWho tested, under which authorisation, and the retest results once you have fixed things.
HOW AN ENGAGEMENT RUNS
From signed scope to closed finding
01Scope and sign-offWe agree in writing what may be tested, when, with which techniques, and who to call on each side if something goes wrong.
02TestAutomated checks find the known problems. Our specialists look for flaws in logic and access, and for small issues that add up. We stop once a problem is proven.
03Report, in two partsFull technical detail for your engineers and a short summary for whoever signs off the budget. Both list what passed.
04Retest and debriefWe test each fixed finding again and record whether it is really closed, then walk your team through the results.
HELD BY THE COMPANY
None yet
We only list certifications issued to the company itself, and we say so when there are none.
HELD BY OUR SPECIALISTS
Currently pursuing
Personal certifications belong to the person who passed the exam. Once obtained, each is listed with the holder’s name, the credential number and a link to check it with the issuer.
FILLING IN A VENDOR QUESTIONNAIRE?
Write to us and we will send what applies to the specialists who would work on your project.
Tell us what you need to protect and what you can spend, monthly or yearly. We put the products together in one offer and one contract, sized to your budget, and stay with you after it is signed.
Ask for an offerTakes two answers: how many assets, and your budget.
VULNERABILITY SCANNINGATTACK SURFACEPENTESTSIGNALBUG HUNTINGCOMPLYSOURCE CODE SCANNINGDARK WEB MONITORINGQUANTUM READINESSQUANTUM ASSURANCE