Penetration Testing Manchester

CREST accredited penetration testing for Manchester and the wider conurbation, scoped and delivered by the tester who writes the report. Remote as standard, at Shropshire rates rather than city-centre ones.

Talk to us

This is a manual penetration test, not a vulnerability scan. We are based in Albrighton and work with organisations right across Greater Manchester, remotely as standard and on site where it genuinely helps. Tell us what you are dealing with and we will tell you honestly what you need, including if that is less than you expected.

Solusec is CREST accredited as a company, and every test is carried out by a qualified, CREST registered tester. Certifications held include CREST CRT, OSCP, OSWE, CISSP and CISM, alongside registration with the UK Cyber Security Council.

Your details are handled by a real person, never fed into AI.

CREST accredited penetration testing for Manchester and the wider conurbation, scoped and delivered by the tester who writes the report. Remote as standard, at Shropshire rates rather than city-centre ones.

Penetration testing finds the flaws an automated scanner cannot reason about, before somebody else does. Manchester’s software, professional services, financial and creative organisations hold data and run systems that clients, insurers and attackers all take an interest in, and testing establishes where you actually stand rather than where you assume you do.

What we test

Web applications and APIs, which is the bulk of the work here. Internal and external infrastructure. Cloud platforms in Azure, AWS and Google Cloud, where the finding is more often a configuration than a vulnerability. Mobile applications. AI and LLM systems, where Solusec holds CREST accreditation specifically for AI-enabled testing. And device build reviews, where the question is whether the standard laptop image would survive somebody taking it home.

Everything is scoped around what the system actually does, tested by hand, and every finding is validated before it reaches the report. You get real risk rather than scanner output with a logo on it.

Book a free scoping call →

A different proposition to a Manchester consultancy

Greater Manchester has a genuinely competitive security market, so it is worth being clear about what is different here rather than claiming to be local when we are not.

We are a small CREST accredited practice based in Shropshire, and we cover the whole conurbation rather than only the city centre. Every engagement is delivered personally by a CREST-qualified tester: there is no account manager translating your requirements badly, and no junior analyst running a scanner and reformatting the output. Day rates reflect Shropshire overheads rather than Spinningfields ones, and testing is delivered remotely, so you are not paying for anybody’s travel.

For some organisations a large local provider with a bench of testers is the right answer, particularly at enterprise scale or where a framework demands a named team. For an organisation that wants the accredited expert actually doing the work, we are usually the better fit. We will tell you honestly which you are, including when that means telling you to go elsewhere.

Who buys testing in Manchester, and why

Manchester has 24,550 VAT or PAYE registered businesses, with 108,685 across Greater Manchester, on ONS UK Business Counts for 2026. Of the Greater Manchester total, about 98.5 per cent employ fewer than 250 people and roughly 88 per cent employ fewer than ten. Whatever impression the skyline gives, this is overwhelmingly a market of small and medium organisations.

The concentrations that matter for testing sit in the city itself. Manchester holds 1,510 legal and accounting businesses and 1,175 computer programming and consultancy businesses. On ONS employment figures for 2024 the city has around 22,000 people working in legal and accounting, 16,000 in financial services and 17,000 in software and IT consultancy. Greater Manchester as a whole has 4,390 software and IT consultancy businesses employing roughly 36,000 people.

Technology and digital

The region’s technology sector produces a constant stream of companies reaching the point where an enterprise customer or an investor demands a test. Frequently it is the first one they have commissioned, usually against a deadline, and often with no settled view of what should be in scope. Scoping conversations are free and we spend longer on them with these clients than with anyone else, because getting the scope right is most of the value.

Financial, legal and professional services

The professional services concentration generates the same recurring pattern: a client security questionnaire arrives demanding evidence of independent accredited testing before a contract completes. We are used to that timeline, and to writing reports for exactly that audience rather than only for developers.

Manufacturing and logistics

The North West’s manufacturing base and the logistics operations along the M60 and M62 face customer-imposed security requirements that have tightened considerably, usually arriving first as a Cyber Essentials demand rather than a request for a test. Where a test is wanted as well, availability rather than confidentiality is normally the dominant concern, and scoping has to work around shifts instead of through them.

Education, health and public sector

Four universities, a large further education sector, ten local authorities and substantial NHS provision across the integrated care system. Procurement frameworks here commonly specify CREST accreditation, and NHS suppliers sit inside PPN 014 and the Data Security and Protection Toolkit, which is where a good deal of the demand originates.

What actually happens, from the first call to the retest

If you have been told to get a penetration test and have never commissioned one, the useful question is not what the testing involves but what it asks of you. Durations below are indicative, and a contained scope moves faster.

  • Scoping call, around half an hour. What the system does, who uses it, how many kinds of user there are, and what you are trying to prove.
  • Written scope and fixed quote, usually within a day. What is in scope, what is excluded, and how many days the work takes.
  • Authorisation and rules of engagement, signed before anything begins. This is the document that makes the testing lawful. It names the systems, the dates, the contacts and what happens if something breaks. If you do not own the hosting, your provider may need to countersign, which is the step most likely to add a week.
  • Booking, typically two to three weeks from agreed scope. At short notice often within a week, and occasionally within a few days where the scope is small and self-contained.
  • Testing. Commonly a few days for a single application or an external perimeter, longer where there are several user roles or several different systems. Anything critical reaches you the moment it is confirmed rather than waiting for the report.
  • Report, within five working days of testing finishing. Prioritised, in plain English, with enough detail for a developer to reproduce each finding.
  • Fixes, on your timescale. Commonly the longest stage, and the one entirely in your hands.
  • Retest, included. We confirm the fixes worked and reissue the report, so you have a clean document for whoever asked.

Most slippage is waiting on the client, and it is nearly always the same short list: working credentials for every role, tested by you beforehand; written permission from any hosting or SaaS provider in scope, which can take longer to obtain than the test takes to run; confirmation of which domains and addresses are genuinely yours; and somebody who can answer a question during the testing window without three approvals. Have that ready before you ask for a date. See urgent penetration testing if the deadline is already close.

What to test first when you cannot test everything

Few organisations can examine the whole estate at once, and those that try commonly spread the effort so thin that nothing is looked at properly. One system tested thoroughly is worth more than five skimmed. A workable order:

  • Anything reachable from the internet without logging in, because that is where an attacker with no relationship to you starts.
  • The authenticated parts of the product that hold other people’s data, particularly anywhere one customer’s account might reach another’s. For a Manchester software, digital or media business whose product effectively is the company, this is usually the whole answer.
  • The identity layer: single sign-on, administrative accounts, multi-factor coverage, and what happens to access when somebody leaves.
  • Internal networks and end-user devices, which answer a different question: where a single compromised laptop leads.

Narrowing scope is not the same as quietly leaving things out. Whatever is excluded should be named in writing, so nobody reads the report a year later and assumes it covered ground it never touched. If your estate divides cleanly, testing the application this year and the network next is a sensible plan. Both are covered on our web application testing and network testing pages.

What makes a test larger or smaller

Effort follows how much the system actually does differently in each place, so two systems that look the same size from outside can differ by several days of work. For what that means commercially, see what a penetration test costs.

What pushes the effort in a penetration test up or down
FactorLess effortMore effort
User rolesOne or two that see much the same thingSeveral, each to be tested against every other
FunctionalityRepetitive screens over one data modelPayments, file handling and integrations, each behaving differently
CredentialsAccounts for every role ready on day oneAccounts arriving mid-test, or self-registration to work around
Knowledge givenGrey box, with an outline of the architectureBlack box, where reconnaissance consumes days first
EnvironmentStaging that genuinely matches productionProduction only, confined to agreed hours
Internal testingRemote access into the internal networkWork that genuinely requires physical presence on site

The black box choice is worth a moment of thought. Starting with nothing tells you what an outsider could discover unaided, a narrower question than most people mean to ask. Given credentials and an outline of how the system is built, the same days reach considerably further in.

How delivery works at this distance

External, web, API and cloud testing is delivered remotely. There is no technical reason for a tester to be in your building to attack something exposed to the internet, and a client who insists on it is paying for reassurance rather than findings.

Internal network testing is the genuine exception. There are two honest answers and we will recommend whichever is better for you. We travel, with the travel quoted as a separate line on the quote so you can see what it costs and decide whether it is worth it. Or we ship a preconfigured device that plugs into your network and connects back to us, which gives the same internal position for a fraction of the cost. For most internal tests the shipped device is the better buy.

What we see most often in Manchester

There is a pattern here that is worth naming, because it catches organisations that are in most respects well run. Highly technical companies frequently fail on basic device management, and the reason is cultural rather than technical. The autonomy that makes good engineers, control over your own machine and freedom to adopt a tool the same afternoon you hear about it, works directly against centralised management and enforced multi-factor authentication.

  • Developer and designer machines deliberately kept outside the managed estate.
  • Cloud tools adopted by individual teams without central identity or multi-factor authentication.
  • Fast-growing organisations whose IT was set up for fifteen people and now serves ninety.
  • Single sign-on covering the main applications but not the two that predate it.
  • Leavers whose access was removed from the directory but not from the tools bought on a team credit card.

None of these is unusual, and none is a reason to put the work off. They are simply the things worth checking before you commit to a date.

Three Manchester incidents, and what they have in common

The locally documented breaches of recent years make a point worth more than any statistic, which is that the system that fails is frequently not your own.

Greater Manchester Police, September 2023. GMP confirmed that a ransomware attack on a third-party supplier, one serving multiple UK organisations, had exposed information held on GMP employees. The force did not name the supplier. A police force is about as security-conscious a buyer as exists, and the exposure still arrived through a contract.

Greater Manchester councils, August 2024. An attack on Locata, a supplier running housing application websites, led to phishing emails being sent to users of housing services at Manchester, Salford and Bolton councils. Salford said at the time that the supplier was unable to confirm the extent to which personal data had been revealed. Three separate public bodies, one shared supplier.

Manchester Airports Group, August 2026. MAG confirmed a data security incident in which customer data was obtained by an unauthorised third party, affecting Manchester, London Stansted and East Midlands airports. Contact details, vehicle registrations and postcodes were involved; payment data was not. Reporting at the time put the number of customers affected at around 8.7 million, a figure MAG has not itself published, and the attribution circulated in coverage remains unconfirmed.

The University of Manchester makes a fourth, from June 2023, where the university stated that a small proportion of data relating to some students and alumni had been copied. Much larger figures circulated at the time. They came from the attackers rather than the university, which is a reason to be careful about what gets repeated.

If you supply any of these kinds of organisation, the practical consequence is the assurance you will be asked for. Buyers who have been through a supplier incident stop accepting a policy document and start asking for a certificate and a test report with a date on it.

Vulnerability assessment and penetration testing are different products

Worth separating clearly, because both are sold across the city at very different prices and the words get used as though they were interchangeable.

A vulnerability assessment is a tool run against your systems, producing a list of known issues matched against a database. It is fast and inexpensive, and the North West Cyber Resilience Centre offers versions of it delivered by supervised university students, which for a small organisation with nothing in place at all is a sensible first step and better than doing nothing.

A penetration test is a qualified person attempting to reach something they should not reach. The scan is where that person starts. What they add is the part no tool does: chaining two harmless-looking findings into one that matters, reasoning about what your application is for, and telling you which of thirty issues is the one that gets somebody into customer data.

Neither substitutes for the other, and the honest recommendation depends on where you are. If nobody has ever looked, a vulnerability assessment tells you the obvious things cheaply. If a customer contract or an ISO 27001 auditor requires an annual penetration test by an accredited third party, an automated assessment does not satisfy it, and submitting one as though it did tends to be noticed. The distinction is covered further on penetration testing versus vulnerability scanning.

How often to retest, and what a test will not tell you

Annually is the usual baseline, and it is what most customer questionnaires and insurers have in mind when they ask for a recent report. That cycle assumes nothing much changed. Bring testing forward when a release alters authentication, roles or permissions; when you start handling a category of data you did not handle before, such as payments or health information; when you move hosting or identity providers; when an acquisition adds an estate you did not build; or after a near miss.

The limits deserve the same clarity. A test describes a set of systems at a point in time, using the access and the days agreed. It does not certify that you are secure, it says nothing about what was excluded, and it will not tell you whether your monitoring would have noticed any of it unless detection and response were part of the brief. Nor is it a compliance certificate: if what you have been asked for is a baseline standard rather than a test, Cyber Essentials is the more direct answer.

Checking an accreditation claim before you buy

Testing requirements here usually arrive through one of three routes: a tender asking for a recent independent test report, an insurer asking at renewal, or a customer’s security questionnaire. In all three the detail that matters most is who holds the accreditation.

If the requirement names CREST, check that your provider holds it at company level rather than relying on an individual certification held by one member of staff. The wording in proposals is sometimes deliberately blurred, and the two are not the same thing to a procurement team that checks. Solusec holds both: company-level CREST accreditation and individual CREST registration, each verifiable on the CREST marketplace rather than asserted on a website. We also hold CREST accreditation for AI-enabled penetration testing.

We are not an NCSC CHECK provider and do not hold SC clearance. Where a tender specifically requires either, we will say so at the first conversation rather than let you waste a bid. If you are still deciding who should do the work, our page on choosing a penetration testing provider covers what to ask, and penetration testing companies in Manchester covers the local market.

Penetration testing for Manchester organisations

Typical lead time is two to three weeks from order, and we can sometimes move faster where a contract date demands it. If you are working to a deadline, say so at the first conversation: it is far easier to protect a date at scoping than to rescue one a fortnight later.

For organisations testing repeatedly across a release cycle we offer a retainer and a banked-days arrangement, where a block of days is bought up front and drawn down across projects. It is better value than quoting each test separately and considerably quicker to mobilise at short notice.

Common questions

How much does penetration testing cost in Manchester?

It depends on scope, and we quote a fixed price after a short scoping call rather than publishing a figure that will be wrong for you. What a penetration test costs sets out the ranges and what moves them. Discounted rates apply for schools and for small or pre-revenue organisations, and where budget is the constraint we would rather narrow the scope honestly than quietly cut the days.

Do you have an office in Manchester?

No, and we will not pretend otherwise. We are in Albrighton, Shropshire. Testing is delivered remotely as standard, which is how it would run even with an office on Deansgate, and our rates reflect Shropshire overheads rather than city-centre ones. Where attending genuinely helps, travel is quoted as a separate line rather than built into the day rate.

How is internal network testing handled remotely?

Either we travel, with travel quoted separately, or we ship a preconfigured device that plugs into your network and connects back to us. The device gives the same internal position as a tester sitting in your office and costs considerably less, so it is usually what we recommend. We will tell you when it is not the better option.

How much of our own time will a test take?

Less than people expect, but it is not nothing. Half an hour for scoping, then the real work is preparation: working credentials for every user role, tested by you beforehand, written permission from any hosting or SaaS provider in scope, and somebody available to answer a question during the testing window. That last one is where most delays come from.

Should we give the tester credentials, or is it more realistic without?

Give credentials in almost every case. Starting with nothing tells you what an outsider could discover unaided, which is a narrower question than most people mean to ask. With credentials and an outline of the architecture, the same number of days reaches considerably further into the system you are actually paying to have examined.

Can you test our live system, or do we need staging?

Either, and live is common. Production testing is agreed in writing beforehand, confined to hours that suit you, and excludes anything destructive. Denial of service testing is out unless you specifically ask for it. Staging only helps if it genuinely matches production, and a staging environment that has drifted is worse than testing live.

How often should we have a penetration test?

Annually is the baseline most customer questionnaires and insurers have in mind. Bring it forward when a release changes authentication or permissions, when you start handling a new category of data, when you change hosting or identity provider, when an acquisition adds an estate you did not build, or after a near miss.

Does passing a test mean we are secure?

No, and any provider who says otherwise is selling something. A test describes specific systems at a point in time using the access and days agreed. It says nothing about what was excluded, and nothing about whether your monitoring would have noticed, unless detection was part of the brief.

Our enterprise customer wants an annual test. Will a vulnerability scan satisfy that?

Usually not. Where a contract or an ISO 27001 auditor requires an annual penetration test by an accredited third party, an automated assessment does not meet it, and submitting one as though it did tends to be noticed. Send us the clause and we will tell you which you actually need.

We were affected by a supplier breach, not our own. Does testing help?

It helps with the question that follows. Every documented Greater Manchester incident of recent years reached the organisation through somebody else’s system, and the consequence is that buyers stop accepting policy documents and start asking for a certificate and a dated test report. Testing does not secure your supplier, but it answers what your own customers will now ask you.

Is a retest included?

Yes. A retest of the findings you remediate is included rather than sold separately, and the report is reissued afterwards so you have a clean document for whoever asked for it. A report full of open findings rarely satisfies the customer or insurer who prompted it.

Do you cover the whole of Greater Manchester or just the city centre?

The whole of it. Bolton, Bury, Oldham, Rochdale, Salford, Stockport, Tameside, Trafford, Wigan and the city itself. Because delivery is remote as standard, where you sit inside the conurbation makes no difference to the service, the timetable or the price.

Related

Penetration testing across Manchester.

CREST accredited, human-led testing with a report your customers can actually read. Free scoping call, fixed-price quote, retest included.