Industry

Offensive Security for RETAIL.

Retailers hold what attackers want: payment data, customer accounts and the systems that keep shops and checkout trading. The Swarm attacks your whole organisation the way they would, across digital, social and physical, so you know what holds before peak trading tests it for you.

What would an attacker take from you first?

Your business changes at pace: new channels, new suppliers, new stores, new staff every season. That change keeps you competitive. It is also what keeps attackers interested, because every change is a window they can wait for.

The real risk isn’t a vulnerability. It’s what happens when one is exploited: shops that can’t take payment, online orders paused, customer data on a leak site and the ICO to notify. Trading continuity, not security theatre.

They want your customers’ cards.

A single malicious script on your checkout page can copy every card typed into it. Customers pay as normal, and you find out from your card scheme.

They want you closed.

Ransomware doesn’t need to steal a thing. Take down shops, distribution or online ordering, and every hour offline is revenue you never get back.

They want your customers.

Loyalty accounts, saved cards, order history. Taken over or leaked, they become fraud, notifications and customers who shop somewhere else.

We attack the paths into your shops.

Attackers don’t pick one way in. They chain a service desk call, a supplier connection and an unwatched checkout script until they reach something that pays. The Swarm works the same way.

Identity and service desk

Shops, warehouses, contact centres and seasonal staff make for a huge, changing workforce. One convincing call to the service desk can reset a password, re-register MFA and hand an attacker a working account.

Suppliers and third parties

Every integration is a way in, and supplier access is rarely reviewed after onboarding. We test the routes into your business that run through someone else’s.

Checkout and payment pages

Tag managers, analytics, personalisation and consent tools: your checkout runs dozens of third-party scripts. Each one is a potential injection point, and every change cycle opens new exposure.

Customer data and AI

Loyalty platforms, CRM, marketing automation and AI-assisted customer service, all connected to vast customer datasets and often with weak access controls.

Store estate and edge

POS, payment terminals, kiosks, Wi-Fi, CCTV and back-office systems across hundreds of sites. Always on, widely spread and rarely treated as part of the perimeter.

Physical access and insiders

High staff turnover, seasonal workers and busy stock rooms. We test whether someone can walk in, plug in or be let in, and what they can reach once they are.

We know that real attack surfaces don’t come in neat categories. If yours doesn’t fit above, tell us what you’re working with.

What a Finding Looks Like

Finding

A Swarm operator called the internal support line posing as an employee just back from holiday. Despite several verification questions, the desk issued a password reset and changed the MFA device to a burner phone.

Impact

Full mailbox access within minutes. A second operator joined and enumerated internal project data, sensitive client information, credentials and access tokens.

Remediation

Apply identity verification consistently on every reset, require a callback to a known number before any MFA change, and back staff who refuse.

Want the full picture?

The full range of offensive security the Swarm runs: every discipline, how they connect, and what each one tests.

Proof your board, insurers and auditors can see.

Every checkout change, new supplier and platform migration is a security event and, increasingly, a compliance one. Every Swarm cycle produces evidence of what was attacked, what held and what was fixed.

ObligationWhat it asks forHow the Swarm supports it
PCI DSS v4.0.1Penetration testing at least annually and after significant changes, plus script management and change detection on payment pages, mandatory since 31 March 2025.Checkout and payment paths attacked every cycle, including after changes, with evidence for your regulators.
Cyber Governance Code of PracticeGovernment guidance setting out how boards and directors should govern cyber risk.Board-ready evidence of where you stand, cycle after cycle.
UK GDPR and Data (Use and Access) Act 2025Personal data breaches reported to the ICO within 72 hours where required. Data Act changes bring new workflows, APIs and admin roles.New data workflows and APIs tested as attack surface as they appear.
Cyber Security and Resilience BillWould extend NIS-style regulation to managed service providers and more digital service providers, the supply chain retailers depend on.Supplier routes tested as part of every cycle.

Stories from the Swarm

These stories are real, but the names are deeply redacted. We'll tell you how we uncovered the threats no one else could see, and why constant cyber attack is the best way to outpace cyber threats.

Frequently Asked Questions

What is retail cyber security testing?

Retail cyber security testing is a controlled attack on a retailer by qualified ethical hackers, to find the weaknesses a real attacker would use to reach payment data, customer accounts or the systems that keep you trading. Continuous red teaming goes further, chaining weaknesses across checkout, shops, suppliers and staff the way real attackers do.

How do cyber attacks on retailers usually start?

Most often through people and partners rather than code. That could be a call to the service desk that resets a password and MFA, a supplier connection nobody reviews, or a malicious script added to checkout. That’s why the Swarm attacks all three, not just your websites.

Does continuous testing help with PCI DSS 4.0.1?

Yes, it supports it. PCI DSS requires penetration testing at least annually and after significant changes, and continuous cycles test your checkout and payment paths as those changes happen. It supports your regulator’s assessment rather than replacing it.

Will testing disrupt trading or peak season? 

No. We work with the restraint a live retail estate needs. Guardrails, priorities and timing are agreed in your Attack Thesis before anything runs, so we find what breaks without breaking your operations.

What does the Cyber Governance Code mean for retail boards?

Government guidance sets out how boards and directors should govern cyber risk. Continuous attack evidence gives directors something concrete to govern with: proof of what held and what broke, cycle after cycle.

How is continuous red teaming different from an annual penetration test?

An annual test is a photograph of one moment; continuous red teaming is the film. Between tests you add staff, suppliers, campaigns and platforms, and the Swarm tests each change as it happens instead of a year later.