Help for owners
A customer wants a penetration test from me and I do not know where to begin
Short answer
A penetration test is an authorised attempt to break into your system so the weak spots are found before someone else finds them. Start by asking the customer exactly what must be tested and what proof they want, then fix obvious basics, define the scope in writing and hire an independent tester.
Does this sound like your situation?
- A contract or security form says 'annual penetration test required'.
- I do not know whether it means a scan or a person testing by hand.
- I do not know which of my systems are meant to be tested.
- I am afraid a test will take the live site down.
- The customer wants a report by a date I cannot meet.
Why does this happen?
Customers use the words 'pen test' for different things
Some mean an automated scan, some a person trying to break in for days, some just a report from any independent party. The wording of the request decides which one you need.
A test only covers what you point it at
The NCSC describes a penetration test as gaining assurance in a system's security by trying to breach it. The plan covers boundaries, test types, timeframe and effort, so a vague scope gives a vague result.
Confirmed by ncsc.gov.uk
Nobody on your side is named to support the testers
The NCSC advises naming a technical point of contact who is available at short notice during testing, and preparing what testers need such as test accounts.
Confirmed by ncsc.gov.uk
A pen test is a snapshot, not a certificate of safety
The NCSC says it is not proof of security beyond the test date, and that risk and fix decisions remain yours. Customers asking for one usually still expect you to fix what it finds.
Confirmed by ncsc.gov.uk
What can I do about it today?
- Ask the customer what they mean in writingWhich systems, how often, whether a scan is acceptable, what format the report must have and by when. Their answer sets the job.
- List what you actually runWebsite, app, back end, admin panels, servers and third-party tools. Mark which hold customer data. That list becomes the scope.
- Fix the obvious things firstShared logins, default passwords, no second sign-in step and software that is far out of date will be the first findings. Fixing them before the test makes the paid time more useful.
- Never let anyone test a live system without a written go-aheadTesting without agreement can be illegal and can break things. Agree dates, systems and a contact person in writing.
- Ask for a test copy where one existsA separate staging copy with fake data lets testers push hard without risk to customers.
- Choose an independent, qualified testerThe quality depends on the testers' skills. Ask for examples of report format and how they handle retests.
When should I bring someone in?
- You cannot list your systems with confidence.
- The customer's deadline is shorter than a proper test and fix cycle allows.
- The report arrived and you cannot tell what to fix first.
How do I handle it?
- Turn the request into a scopeI read what the customer asks and write a one-page scope: systems, dates, test type, contact and what a good report must contain.
- Do a preparation passAccess control, default settings, patch state and exposed admin pages are reviewed so that the tester's time goes on deeper problems.
- Set up a safe test targetA staging copy with test accounts is prepared where possible, with a backup before anything that touches production.
- Act as the technical contact during the testI answer the tester's questions quickly and watch your systems while they work.
- Fix and prove itFindings are ranked by what an attacker could reach, fixed in small changes, and a retest is requested so the report can be closed.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I just run an automated scanner?
Only if the customer says that is enough. Many contracts expect a person to test by hand, so confirm it in writing before you spend money.
Will the test take my site down?
It can if it is run carelessly on production. Agree timing, use a staging copy where possible and keep a backup and a rollback ready.
Is passing a pen test the same as being secure?
No. The NCSC says a test is a snapshot and does not prove security beyond the test date, so it does not replace everyday security work.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.