How well would your systems stand up to an attack?
A penetration test puts your security controls to the test within carefully agreed boundaries. I’ll investigate how weaknesses could be exploited, explain the potential business impact, and give your team practical recommendations supported by evidence.
Pricing: Quoted to scope + VAT where applicable.
The fee depends on the systems involved, the depth of testing and the access required. Scope, approach, timetable and price are agreed before you commit.
Discuss your penetration test
Tell me what you need tested and what you want to establish. I’ll reply to clarify the scope, approach and next steps.
Useful starting points:
• The applications, systems or environments you want tested.
• Whether testing will cover production, a test environment, or both.
• Your objectives and any deadlines or customer requirements.
• Who manages the systems and can authorise testing.
Before you send
Please don’t include passwords, credentials, or other sensitive information in an initial enquiry. If we need to share anything sensitive, we’ll agree a secure way to do it.
Find weaknesses. Understand the impact. Know what to fix.
Whether you’re testing an existing environment or checking security improvements, the aim is to establish what an attacker could realistically achieve within the agreed scope.
-
01
Clear testing boundaries
We agree the systems, accounts and environments included, the testing approach, and any exclusions or operational constraints before work begins.
-
02
Evidence of exploitable weaknesses
I investigate weaknesses and, where safe and authorised, demonstrate how they could be used. Findings distinguish confirmed results from potential risks and testing limitations.
-
03
Practical reporting
You receive a report explaining the findings, supporting evidence, potential impact and prioritised recommendations, with a summary for decision-makers and technical detail for those making changes.
-
04
Findings walkthrough and retesting
We walk through the results and your next steps. Retesting can be included in the agreed scope or quoted separately once fixes are ready.
You can book penetration testing directly. A previous Ronin inventory, review or implementation project is not required.
Discuss my testHow it works
Clear authorisation, agreed boundaries and communication throughout.
Testing starts only once written authorisation and scope are agreed.
If an urgent finding emerges during the work, I’ll raise it through the agreed contact route.
- Define the objective — tell me what you need tested, why, and any deadlines or assurance requirements.
- Agree the scope — confirm targets, ownership, permissions, access, testing windows, exclusions and fee.
- Prepare and test — arrange suitable access, confirm readiness and escalation contacts, then carry out the agreed testing.
- Report and explain — receive the findings and a walkthrough of the priorities and recommended actions.
- Verify fixes where agreed — retest relevant findings and record what has been resolved and what remains.
About Ben
I run Ronin, an independent cybersecurity consultancy.
I’ve spent over ten years in cybersecurity and previously worked as a consultant at NCC Group. I’m used to working with small teams, leadership stakeholders, and external IT providers — and keeping the conversation practical and constructive.
I’ll explain what the testing demonstrated, where coverage was limited, and what your team or provider can do next. The aim is a useful assessment that supports decisions and improvements.
FAQ
Common questions about scoped penetration testing.
Is this the same as a vulnerability scan?
No. Scanning can support a penetration test, but the work also involves investigating findings, validating weaknesses and assessing how they could be exploited within the agreed scope.
Do we need to buy another Ronin service first?
No. Penetration testing is available as a standalone service. Existing inventories, architecture notes and previous reports can help with scoping, but a previous Ronin engagement is not required.
What can you test?
Tell me about the applications, internet-facing systems, internal networks or cloud environment you want assessed. I’ll confirm what Ronin can cover and propose a suitable approach. Configuration review and penetration testing may require different scopes.
Could testing disrupt our systems?
Testing can carry operational risk. We agree the approach, testing windows, exclusions, escalation contacts and stop conditions beforehand. Any higher-risk activity requires specific agreement.
What do you need from us?
An initial description of the systems and objectives, an authorised decision-maker, and a technical contact. Before testing, we agree target details, written permissions and any accounts, access or preparation needed. Sensitive information is shared through an agreed secure route.
What will we receive?
A report covering the agreed scope, approach, limitations, findings, evidence and prioritised recommendations, followed by a findings walkthrough.
Is retesting included?
Only where it is explicitly included in the agreed proposal. Otherwise, it can be quoted separately when your fixes are ready.
Does a clean report guarantee we are secure?
No. A penetration test assesses an agreed scope over a limited period. It can provide useful evidence about your controls, but cannot establish that every vulnerability or attack route has been identified.
How much does it cost?
Testing is quoted to scope. The systems involved, depth of testing, access arrangements and reporting requirements determine the fee. We agree the price before you commit, with VAT added where applicable.