Frequently Asked Questions

Timelines vary by scope. A focused external pentest can be completed in 5-7 business days. A full red team engagement typically runs 3-6 weeks. Compliance-driven assessments are scoped based on your specific requirements. We provide a detailed project timeline in every Statement of Work.

A penetration test is comprehensive and systematic, we're trying to find all vulnerabilities within a defined scope. A red team engagement simulates a real, targeted threat actor operating stealthily toward a specific objective while remaining undetected. Red team tests your detection and response capabilities as much as your technical defences.

Absolutely. We're happy to sign a mutual NDA before any sensitive discussions begin. All initial consultations are treated as confidential regardless of whether an NDA is in place.

Every engagement includes: a full technical report with reproduction steps and remediation guidance; an executive summary with business risk narrative for leadership and board; a live debrief call walking through all findings; and remediation support; and retest services available as an additional engagement at a separate fee to verify remediations have been correctly implemented.

We scope based on your environment size, number of targets, test type, and compliance requirements. Pricing is transparent, we provide a fixed-fee proposal after an initial discovery call so there are no surprises. Engagements are never billed on a time-and-materials basis.

Yes, safely operating in production environments is a core competency. We define detailed rules of engagement before every engagement, including out-of-scope systems, fragile systems to treat carefully, and emergency stop procedures.

Yes. Retesting is available as an additional service engagement at a separate fee. Once you have completed your remediation work, we can perform a targeted retest to verify that findings have been correctly resolved and that the same or similar attack paths are no longer viable. Contact us to scope a retest engagement.

Yes, and we particularly enjoy helping organisations build a security testing programme from scratch. We'll guide you through scoping your first engagement and creating a roadmap for ongoing testing.

Internal teams should own continuous security work such as vulnerability management, monitoring, and secure code review, but they cannot provide an independent, adversarial penetration test of their own environment. Familiarity bias and conflict of interest mean internal staff tend to find individual issues while missing the chained attack paths an external specialist surfaces. See can internal employees do penetration testing? for the full breakdown.