What types of penetration testing do you offer?
+
We test web applications, APIs, external and internal networks, wireless networks and cloud environments. We can also include social engineering scenarios, such as help desk pretext calls, when leadership approves them and the rules of engagement allow it.
How is a penetration test different from a vulnerability scan?
+
A vulnerability scan is automated and lists known weaknesses. A penetration test is performed by people who chain weaknesses together the way an attacker would, confirm what is actually exploitable, and show the business impact. Both are useful; they answer different questions.
How often should we run a penetration test?
+
At least annually and after significant changes to your environment, such as a new application, a major infrastructure change or a merger. Some frameworks set their own requirements; PCI DSS, for example, requires penetration testing at least once every 12 months and after significant changes.
Will testing disrupt our production systems?
+
Testing is planned to avoid disruption. Scope, timing, out-of-bounds systems and emergency contacts are agreed in the rules of engagement before testing starts, and higher-risk activities can be scheduled outside business hours.
What do we receive at the end?
+
You receive an executive summary for leadership and a technical report with each finding, its severity, evidence and remediation guidance. After you remediate, we retest the fixed findings and confirm in writing which are closed; retest timing and terms are agreed in the statement of work.
How long does a penetration test take?
+
It depends on scope. A small external test can take two or three tester days; an engagement covering external, internal and a customer-facing application is more often two to four weeks of effort, with modules running in parallel. Reporting follows testing, and the retest is scheduled once you have remediated. The scope builder on this page gives an indicative range, which we confirm after a scoping call.
Should we tell our IT provider, SOC or MDR before the test?
+
Usually yes, so that alerts are not escalated as a real incident and nobody blocks our source addresses halfway through. The exception is when detection is part of what you want tested, for example in an assumed breach scenario. In that case a small number of named people know, and the rules of engagement say how a real incident is told apart from the test.
Do we need permission from our cloud or hosting provider?
+
AWS, Microsoft Azure and Google Cloud allow customers to test their own resources without prior approval for most services, within their published policies. Some hosting and managed service providers do require notice. We check the relevant policy during scoping, and the rules of engagement record any approvals.
What is assumed breach testing?
+
An assumed breach test starts from a standard employee laptop and account, as if a phishing email had already worked. It skips the part attackers usually succeed at anyway and spends the time on what matters next: how far that account can get, and whether your monitoring notices. It suits organizations that already test their perimeter regularly.