Contact us

Questions, answered.

How we work, how we keep testing safe, what drives the price, and what to do if you're under attack.

01Engagements

How do we get started?

With a quick scoping call. We learn what you want to achieve, which systems matter and what limits apply. Then we propose a scope, approach and deliverables, and agree the ground rules in writing before any testing starts.

Can you cover several areas in one engagement?

Yes, and it often works better. For example, a pen test followed by detection engineering for the techniques we used, or a cloud review paired with a compliance gap assessment. One team means consistent findings and no duplicated effort.

Who will we actually be working with?

The experts doing the work, not just an account manager. Every engagement has a named lead who handles communication, coordinates the team and stays your main contact from scoping to retest.

Will you replace our internal security team?

No. We make it stronger. Some clients use us for specialist testing, others for managed operations or senior advice. We work alongside your people, share our methods and aim to leave your team better than we found it.

02Testing & safety

Will pen testing break our live systems?

We plan carefully so it doesn't. Testing windows, fragile systems and banned techniques are agreed upfront. Anything destructive needs your explicit approval, and if a test ever affects availability, we stop and call your contact straight away.

What's the difference between a vulnerability scan and a pen test?

A scan is a tool listing things that might be wrong. A pen test is a skilled human proving which ones are exploitable, chaining them together and showing the real impact. We use scans as a starting point, never as the deliverable.

What happens to sensitive data you see during testing?

We only access what's needed to prove impact, never bulk-copy data, and protect all evidence in transit and at rest. How long we keep it and how it's destroyed is agreed during scoping, and it's shared only with your named contacts.

Do you test live production or a staging environment?

Either, depending on your goals. Production gives the most realistic picture; staging lets us be more aggressive. We'll help you weigh it up during scoping and note any differences in the report.

03Scoping & pricing

How much does it cost?

It depends on the effort involved: how many targets, how complex they are, how deep we test, any compliance reporting, and whether fix support and retesting are included. We quote after scoping, not before, so you only pay for what you need.

How do you scope a web app or API test?

We look at the number of user roles, features, integrations and API endpoints, and whether we test logged in, logged out or both. Documentation, test accounts and a quick walkthrough help us scope accurately and spend time where it counts.

Can we start small and grow later?

Absolutely. Many clients start with a focused test of their most exposed systems, then expand based on what we find. Starting small is also a good way to see how we work before committing to more.

What do you need from us for a proposal?

A short description of the systems involved, your goals, any compliance drivers and practical limits like testing windows. A short call usually covers it. Architecture diagrams or asset lists help us be more precise.

04Compliance

Can you help us get ready for ISO/IEC 27001?

Yes. We run readiness assessments against ISO/IEC 27001:2022, find the gaps in your management system and Annex A controls, and help you build the policies, risk processes and evidence an auditor expects. The certificate itself is issued by an accredited certification body.

Do your pen tests meet PCI DSS requirements?

They can be scoped to support PCI DSS v4.0 requirements for internal, external and segmentation testing, with methods and reporting that match what assessors look for. Your QSA or acquirer makes the final call on compliance.

Which frameworks do you map to?

Usually NIST CSF 2.0, ISO/IEC 27001:2022, CIS Controls v8, OWASP standards and MITRE ATT&CK. We map to whatever framework you or your regulator uses, so results slot straight into your existing compliance and risk reporting.

If we pass an audit, are we secure?

Not necessarily. An audit shows the required controls exist; testing shows whether they actually stop an attacker. We treat frameworks as the baseline and use real testing to prove controls work, which also makes audits easier.

05Incidents

We think we're under attack right now. What do we do?

Contact us immediately through the contact page and mark it as an active incident. Meanwhile, don't switch off affected systems or wipe anything, write down what you've seen, and keep the conversation to people who need to know.

What's the difference between incident response and forensics?

Incident response is about stopping the threat and getting back to business. Forensics is about preserving and analyzing evidence to work out exactly what happened, how and when. Serious incidents need both, run together so cleanup doesn't destroy the evidence.

Can you check if we've already been hacked?

Yes. A compromise assessment checks endpoints, logs, accounts and network activity for signs of a current or past intrusion. It's a good fit if you've seen something odd, just acquired a company, or simply want peace of mind.

How can we prepare before anything happens?

Make a plan and practice it. We help write incident response plans, run tabletop exercises with technical and leadership teams, and check how ready you are for ransomware. Preparation means faster decisions on the day, and better evidence for investigators.

06Working with us

How do you keep our work confidential?

Details, findings and evidence go only to your named contacts. We never name clients or share results without written consent, and we're happy to sign your NDA on top of our own contract terms.

What happens after we get the report?

We hold a debrief to walk through the findings and agree priorities. Your team can then come to us with fix questions, and once fixes are in, we retest them and update the report with their verified status.

Can you present the results to our board?

Yes. We prepare executive briefings that explain exposure, business impact and priorities without the jargon. Your leadership gets a clear view of risk, and your security team gets backup when asking for budget.

What certifications does your team hold?

Team members hold OSEP, C|PENT, LPT, CEH, CHFI, eCIR, CISSP, IBM QRadar SIEM V7.5 Administration, Forcepoint DLP Administrator, AWS Certified Solutions Architect – Associate, AZ-104 and AZ-400. That covers offense, forensics, governance, operations, data and cloud.

Still have a question?

Ask us directly. A practitioner, not a salesperson, will answer.

Start a project