A Client Asks for a Penetration Test: What UK Postal and Courier Firms Need to Know

By EJN Labs · 17 Nov 2026 · 9 min read

No public rule names a penetration test for a postal, courier or parcel business. When a client’s security questionnaire or contract asks for one, that is a private requirement, set by the client. Two public texts sit behind it: UK GDPR Article 32, which asks for regular testing without naming a method, and PCI DSS Requirement 11.4 where you take card payments.

Does a client’s security questionnaire require a penetration test?

A retailer, marketplace or enterprise client is a private party, so there is no regulation, statute or published standard that says a courier must hand over a penetration test report. The client decides what it asks for in its onboarding form, supplier questionnaire or contract. In our experience the wording ranges from a one-line tick box to a named report on named systems.

That makes the exact wording the most important thing you have. Look for four details: which systems the client means, how recent the test must be, whether it names an accreditation, and whether it asks for the full report or a summary. A request that says “annual penetration test of systems holding our customers’ data” is a very different job from one that says “penetration test of your API”.

If the wording is vague, ask the client. Most security teams will tell you what they have in mind, and a short call can save you from buying a test that answers the wrong question.

What does a client actually ask a courier or parcel business for?

In our experience clients focus on what a parcel business holds about their customers: names, delivery addresses, contact numbers and delivery history. The questions usually target the systems that expose that data, and the way one client’s data is kept apart from another’s. They are asked on behalf of the client’s own data protection duties.

  • Tracking and customer portals. Whether a tracking reference alone can expose more than its own parcel, and whether one customer can reach another’s address.
  • Integration APIs. Whether a marketplace or retailer feed lets one retailer see another’s consignments.
  • Separation between clients. For fulfilment and third-party logistics operators, whether several retailers on one platform stay properly apart.
  • Address and redirection changes. What verifies a request to redirect or hold a parcel, and what is logged.
  • Recent test evidence. A dated report or letter, and confirmation that serious findings were fixed.

Some clients ask for a certificate rather than a test. Cyber Essentials Plus is an assessor-led technical audit, which is a different thing from a penetration test. If the request names it, a test report does not answer it, so check before you commission anything.

Does UK GDPR require a penetration test?

No. UK GDPR Article 32(1)(d) asks for a process for regularly testing, assessing and evaluating the effectiveness of your security measures, but does not name penetration testing as the method. It matters for parcel firms because a tracking number, delivery address and contact number are personal data.

This is also why clients ask. A retailer that passes customer addresses to a courier remains responsible for that data, so it asks the courier how the data is protected and how that is tested. A penetration test is the most direct evidence you can offer, but Article 32 itself leaves the method open. Our page on GDPR penetration testing covers it in more detail.

Does PCI DSS apply to a courier that takes card payments?

Yes, where you take card payments directly. If your platform takes cards for postage, shipping labels, redelivery fees or locker access, PCI DSS 4.0.1 Requirement 11.4.2 requires internal penetration testing and Requirement 11.4.3 requires external testing, each at least once every 12 months and after significant change. Requirement 11.4.1 requires a documented testing methodology.

Not every checkout is in scope. If a payment provider hosts the page and you never handle card data, much less of your estate is affected, and your acquiring bank or assessor confirms which applies. The PCI Security Standards Council document library holds the standard, and our PCI DSS penetration testing page goes through the requirements.

The Council’s own penetration testing guidance is an information supplement written in 2017 against the earlier numbering of the standard, so use it for method and scope. It says that where an application has user roles, testing should be performed against all roles or types of access, which is useful if your portal serves customers, depot staff and retailers.

Who can carry out the test?

Neither UK GDPR Article 32 nor a typical client questionnaire names a scheme by default. Postal and courier organisations can use a CREST-accredited company or another provider, depending on what their requirement states. EJN Labs is CREST-accredited. Start with the document that triggered the request and use the accreditation it names.

Where PCI DSS applies, the Council’s guidance says qualified internal resources or a qualified third party may perform the test as long as they are organisationally independent. It says certifications are not required, and that the Council does not validate or endorse them. Independence is the practical point: the supplier that built or runs your tracking platform is not the best choice to test it.

Ask which legal entity holds any accreditation you are told to look for, and whether the testers doing your work are the certified individuals.

What should a postal, courier or parcel business test?

Test the systems that expose delivery data and the boundaries between clients, depots and drivers. Start with parcel tracking and customer portals, then the integrations with retailers and marketplaces, then driver and depot apps. These are the places where one wrong permission shows a customer’s address to someone else.

  • Parcel tracking and customer portals. Public tracking-by-reference pages and logged-in accounts, with checks for one tracking number exposing another parcel.
  • Fulfilment and warehouse management. Pick-pack-ship workflows, label generation and separation between clients on a shared platform.
  • Depot and driver apps. Proof-of-delivery capture, round reassignment and permission separation between depots. See mobile application penetration testing.
  • Redelivery, hold and locker networks. Address and redirection-change verification, and PIN or QR-code replay against lockers.
  • Carrier, marketplace and EDI integrations. The interfaces behind retailer feeds and label plugins. See API penetration testing.
  • Depot, sortation and corporate networks. Separation between sortation control systems, depot floor networks and corporate IT.

What evidence do you hand back to the client?

Hand back a dated report stating scope, method, each finding with a severity score, and what was fixed. No public rule sets a format for postal and courier firms, so match the evidence to the question. In our experience a client questionnaire is usually satisfied by a summary letter naming the scope and the testing company.

Keep the full report for clients who ask to read it, shared under a confidentiality agreement. Clients and insurers also tend to want confirmation that serious findings were fixed, which a retest provides. Some clients ask for a recent report each year, so keep the scope document with each one, because it shows exactly which systems were covered and which were not.

Insurers ask about testing too. One published cyber proposal form asks whether you conduct penetration tests of your network at least annually. Requirements vary by insurer and policy.

What does it cost?

Price follows the number of testing days, and the number of days follows the scope. UK day rates for CREST-accredited penetration testing typically run £1,100 to £1,400. The pricing page shows typical engagement lengths for each type of test, and the quote form gives an exact figure for your scope.

How EJN Labs approaches testing for postal, parcel and courier services

EJN Labs is a CREST-accredited UK penetration testing company with a dedicated postal, parcel and courier service. We test parcel tracking and customer portals, warehouse and fulfilment platforms, depot and driver apps, redelivery and locker networks, carrier and marketplace integrations, cloud infrastructure and depot networks.

We check three trust boundaries on every platform: who can see a delivery address, who can redirect a parcel, and whether a proof-of-delivery record can be tampered with. Testing runs against staging or non-production environments with synthetic address and parcel data wherever possible, and is safe by default on production, with no denial of service.

The work is done by UK-based, CREST-certified testers. You get a fixed price for a defined scope, findings in a client portal, CVSS-scored findings with a walkthrough call, and the report on the last day of testing. Retests are free until findings are resolved, and there are no out-of-hours, callout, cancellation or rescheduling fees.

Frequently Asked Questions

Is a penetration test a legal requirement for a courier?

No public rule names one. UK GDPR Article 32(1)(d) asks for a process for regularly testing your security measures but does not name a method. PCI DSS Requirements 11.4.2 and 11.4.3 require testing where you take card payments. Otherwise the request comes from a client’s questionnaire or contract.

What should we do when a client asks for a penetration test report?

Read the exact wording first. Check which systems it means, how recent the test must be and whether it names an accreditation. Then ask the client if anything is unclear. In our experience a summary letter plus the full report under a confidentiality agreement answers most requests.

Does the test need to be done by a CREST-accredited company?

Only if your client’s requirement says so. Postal and courier organisations can use a CREST-accredited company or another provider, depending on what their requirement states. EJN Labs is CREST-accredited. Check the questionnaire or contract that triggered the request and use the accreditation it names.

Do we need to test driver and depot apps as well as the website?

It depends on what the request covers and what the apps do. Driver and depot apps handle proof of delivery, round reassignment and depot permissions, so they are a common place for a client to look. Scope them if the questionnaire names them or if they hold delivery data.

How often should a postal or courier business test?

No rule for postal firms sets a frequency. Where PCI DSS applies, Requirements 11.4.2 and 11.4.3 set it at once every 12 months and after significant change. Some cyber insurance forms ask about annual testing, so once a year, and again after a major platform change, is a common starting point.

Get a quote for your parcel business

Tell us which systems are in scope and who has asked for the evidence. Request a fixed-price quote and we will come back with the number of days, the price and the earliest start date.

Related: Penetration Testing Cost for UK Postal, Parcel and Courier Businesses, Best Penetration Testing Companies for UK Postal, Parcel and Courier Services, penetration testing for UK postal, parcel and courier services, GDPR penetration testing, PCI DSS penetration testing and API penetration testing.

Leave a Reply

Your email address will not be published. Required fields are marked *