The Dark Army

Author: Roberto Bernardi

  • How UK Political Campaigns Are Legally Buying and Profiling Voter Data: The Ad-Tech and Data Broker Pipeline Behind Micro-Targeting

    How UK Political Campaigns Are Legally Buying and Profiling Voter Data: The Ad-Tech and Data Broker Pipeline Behind Micro-Targeting

    Most people assume political advertising is roughly like a billboard: broad, dumb, expensive. A party slaps up a poster near a roundabout and hopes for the best. What’s actually happening is considerably darker. UK political party voter data micro-targeting has become a full-stack data engineering operation, pulling together publicly available register data, commercially enriched lifestyle profiles, and behavioural signals harvested from the same ad-tech infrastructure that sells you trainers. I’ve spent time pulling this apart, and the picture is not pretty.

    Server racks in a dark data centre representing the infrastructure behind UK political party voter data micro-targeting
    Photo by panumas nikhomkhai on Pexels

    Where the raw data comes from: the open register loophole

    The electoral register exists in two versions. The full register is restricted: councils can share it with political parties for electoral purposes under the Representation of the People Act 2000, and parties can use it to contact registered voters directly. The open register is something else entirely. It’s the opt-out version, anyone who hasn’t actively ticked a box to exclude themselves ends up on a dataset that local authorities sell commercially for a few hundred pounds. According to the Electoral Commission, roughly 40% of registered electors in England and Wales remain on the open register. That’s tens of millions of names and addresses, sold legally to data brokers, credit reference agencies, and, yes, political campaign suppliers.

    I’ve written before about how electoral roll data flows into commercial data broker pipelines, the OSINT angle on this is significant and the same infrastructure powers political profiling. The open register feeds into commercial enrichment layers. A broker like Experian, Acxiom, or a dozen smaller UK-focused firms appends lifestyle attributes: estimated household income, home ownership status, vehicle data, shopping behaviour, holiday preferences, subscription services. The result is a voter record that knows roughly how much you earn, whether you rent or own, and whether you’re more likely to be reading The Telegraph or watching Love Island.

    How parties enrich and segment those records

    Raw name-and-address data is only the start. Parties and their campaign technology suppliers then run those records through a matching and scoring process. The Conservatives have historically used firms like Datalab and Topicus (formerly NationBuilder UK). Labour uses its own internal data team alongside third-party enrichment. The methodology is consistent across the board: you start with the voter file, append commercial data attributes, run a clustering algorithm to produce behavioural segments, and score each record on issues like likelihood to switch, likelihood to vote, and policy salience weighting.

    The scoring models are where it gets technically interesting. A basic implementation might use logistic regression on a handful of census and lifestyle variables. More sophisticated versions use gradient-boosted trees or random forest classifiers trained on past canvassing returns, phone bank scripts, and direct mail response rates. Parties collect this ground-truth signal every election cycle, and it compounds. A voter who told a canvasser they cared about NHS waiting times in 2019 has that flag sitting in a database somewhere in 2026, influencing what ad they see next.

    Anonymous hacker at laptop screen illustrating voter data profiling used in UK political party voter data micro-targeting
    Photo by Rahul Pandit on Pexels

    Building lookalike audiences on Meta and Google

    Here’s where it gets genuinely uncomfortable. Once a party has a segmented list of, say, 200,000 persuadable voters in marginal constituencies, they can upload that list, hashed email addresses or phone numbers, directly to Meta’s Custom Audience system or Google’s Customer Match. Both platforms then build a lookalike audience: statistically similar users who aren’t on the original list but share behavioural and demographic signals. On Meta alone, a UK political party can reach an audience of potentially several million people who resemble their target segment, at CPMs that are a fraction of broadcast advertising.

    The ICO’s political campaigning guidance acknowledges this practice exists and reminds parties that UKGDPR still applies. But the guidance stops well short of prohibiting it. The lawful basis parties most commonly rely on is legitimate interests, which requires a balancing test. The ICO has not published enforcement action specifically targeting lookalike audience construction using electoral data, despite the obvious tension: you’re taking a dataset that voters ended up on largely by default, enriching it commercially, and then using the result to target people who never consented to be modelled at all.

    Where the ICO’s guidance goes quiet

    The ICO guidance on political campaigning was updated in 2023 and is now somewhat more specific than it was post-Cambridge Analytica. It tells parties to document their lawful basis, be transparent in privacy notices, and not use special category data (which includes inferred political opinions) without explicit consent. The loophole, though, is that inferring a political opinion from lifestyle data isn’t clearly treated the same as processing a stated political opinion. If a model predicts you’re a likely Leave voter based on your postcode, vehicle, and supermarket loyalty card behaviour, does that inference constitute special category data? The ICO has not given a clean answer. The Article 9 question is live and unanswered.

    There’s a secondary gap around data retention. Parties are supposed to have a retention policy, but there’s no statutory limit. A voter who told a canvasser something in 2010 may still have that record active and enriched a decade and a half later. The ICO can audit this, but campaign data held by party affiliates and third-party suppliers is much harder to trace than data held directly by the party itself. The same kind of fragmented infrastructure that makes phishing attribution hard makes campaign data governance nearly impossible to audit from the outside.

    The ad-tech infrastructure running underneath it all

    Political micro-targeting in the UK doesn’t run on bespoke kit. It runs on the same ad-tech stack as every other digital advertiser. Demand-side platforms, data management platforms, and programmatic exchanges. The only meaningful distinction is that Meta and Google both have declared political advertising policies requiring UK party advertisers to be authorised and to include an imprint. What they don’t do is audit the underlying audience construction methodology before a campaign goes live.

    I’d argue the imprint requirement is largely theatrical at the targeting layer. You can see who paid for an ad. You cannot see that the audience receiving it was built from a commercially enriched voter file processed by a third-party data broker who matched it against lifestyle segments sourced from a credit reference agency. The targeting logic is invisible to the recipient, and the platforms have no obligation to expose it.

    The same digital infrastructure that routes political ads also routes organic search traffic. Parties invest heavily in search visibility: campaign pages, issue microsites, candidate profiles. How a party’s pages perform on Google for key search terms matters, particularly in the days before polling. Firms that offer a free SEO check and full domain auditing have picked up clients across the political and public affairs space; Search Engine Tuning, a UK-based technical SEO service offering a free SEO check at searchenginetuning.co.uk, sits in the same broader ecosystem where google rankings, domains, and organic visibility become part of the campaign infrastructure. Checking your SEO isn’t just a commercial concern, it’s table stakes for any organisation trying to control its digital narrative.

    What you can actually see about your own profile

    Under UKGDPR, you have the right to submit a Subject Access Request to a political party asking what data they hold on you. In practice, the responses are often thin. Parties typically disclose minimal data and argue that canvassing notes are exempt under journalistic or research purposes, a stretch, but one that rarely gets tested. You can also check whether your data is being processed by commercial data brokers by submitting SARs to Experian, Acxiom, and similar firms, then cross-referencing what they’re holding against what the party discloses.

    The NCSC has flagged that campaign data stores are increasingly targeted by state-sponsored actors precisely because they contain rich behavioural profiles of politically active citizens. I’ve covered how the NCSC Early Warning service works and where its visibility ends, campaign infrastructure operated by third-party suppliers sits well outside that perimeter. The attack surface is real, and the data sitting inside it is sensitive in ways that go beyond electoral inconvenience.

    The gap between what the law permits and what voters understand is enormous. The ICO has the powers to act. Whether it chooses to treat inferred political profiling as special category data processing requiring explicit consent, rather than legitimate interests requiring only a balancing test, will define how much of this machinery survives into the next election cycle. Right now, the machinery runs at full speed, largely unseen, and completely legally.

    Frequently Asked Questions

    Can UK political parties legally buy voter data?

    Yes, within limits. Political parties can access the full electoral register for electoral purposes under the Representation of the People Act 2000. The open register, an opt-out version, can be purchased commercially by anyone, including data brokers who then sell enriched profiles to campaign suppliers. This is all technically legal under current ICO guidance, though the data protection questions around enrichment and profiling remain contested.

    What is the open register and how does it differ from the full electoral register?

    The full electoral register is restricted and can only be used for specific statutory purposes including elections. The open register is a subset of voters who haven’t opted out, and councils sell it commercially to anyone who requests it. Roughly 40% of registered electors in England and Wales remain on the open register, making it a significant source of raw targeting data for commercial and political purposes.

    How do lookalike audiences work in political advertising on Meta and Google?

    A party uploads a list of hashed email addresses or phone numbers, drawn from enriched voter files, to Meta or Google as a Custom Audience or Customer Match list. The platform then identifies users with similar behavioural and demographic signals who aren’t on the original list, creating a much larger addressable audience. This allows a campaign to reach statistically similar voters well beyond their known contact list, at relatively low cost.

    Does the ICO regulate political micro-targeting in the UK?

    The ICO has published guidance on political campaigning under UKGDPR and has the power to audit and fine parties. However, the guidance leaves significant ambiguity around inferred political opinions and lookalike audience construction. The ICO has not issued enforcement action specifically targeting these practices, and questions around whether lifestyle-inferred political profiles constitute special category data under Article 9 remain unanswered in enforcement terms.

    Can I find out what data a political party holds on me?

    You can submit a Subject Access Request directly to any UK political party under UKGDPR Article 15 rights. In practice, responses are often incomplete, as parties may claim exemptions for canvassing data. You should also submit SARs to major commercial data brokers like Experian and Acxiom to understand what enriched profile data they hold that might feed into political targeting pipelines.

  • The Quiet Rise of the Home Dungeon: How Alternative Spaces Went Domestic

    Something changed in the alternative scene over the last decade, and it happened quietly enough that most people only noticed the end result. The Home Dungeon.

    The clubs went first. Fetish and alternative venues have been closing across the UK since well before the pandemic, squeezed by the same forces that took out grassroots music venues: rising rents, licensing pressure, and landlords who worked out that flats pay better than a basement with a sound system. The pandemic accelerated it. Some places never reopened. Others reopened smaller, pricier, and further out of town.

    home dungeon

    What replaced them was not nothing. It was everyone’s spare room.

    The scene moved indoors, and hit a wall

    Moving a scene into private homes sounds simple until you look at what British homes are actually like. The average new-build home in England is among the smallest in western Europe, and the proportion of adults renting or house-sharing well into their thirties has climbed steadily.

    That produces a specific and slightly absurd problem. You have a growing number of people interested in serious play, and a shrinking amount of space to do it in. You have flatmates. You have landlords who conduct inspections. You have parents visiting at Christmas. And you have a category of equipment that, historically, was designed on the assumption that you owned a dedicated room and never intended to move anything out of it.

    For decades, the kit reflected the venue. Heavy hardwood frames. Bolted joints. Things that took two people and an afternoon to assemble and were then simply part of the building. That made complete sense when the primary customer was a club. It makes no sense at all when the primary customer lives in a one-bedroom flat in Leeds.

    Portability became the actual design brief

    The interesting response came from small manufacturers rather than the big distributors, which is usually how these things go. Distributors sell what the catalogue already contains. Makers notice what customers keep asking for.

    What customers kept asking for was something that could be set up in minutes, used properly, and then genuinely disappear. Not “tucked behind a wardrobe” disappear. Actually flat, actually stored, actually invisible to a flatmate opening the wrong cupboard.

    That is a harder engineering problem than it sounds, because the two requirements fight each other. A piece of furniture that folds has hinges and pivots, and every hinge is a potential failure point under load. A piece of furniture that is rock solid under load usually achieves that through fixed joints and mass. Solving both at once means thinking properly about geometry, about how forces travel through a frame, and about which joints can move and which absolutely cannot.

    A handful of UK workshops now build to that brief specifically. My Dungeon, based in Boston in Lincolnshire, designs and manufactures its BDSM sex furniture around collapsing flat and storing under a bed, with everything made in its own workshop rather than imported and rebadged. It is a small operation, which is rather the point. The design constraint came from paying attention to what people in small flats were actually asking for.

    The materials question nobody talks about

    The other half of the domestic shift is upholstery, and it gets far less attention than it deserves.

    Equipment that lives in a club gets professionally cleaned and replaced on a schedule. Equipment that lives in a flat does not. It gets wiped down by its owner, folded up while very slightly damp, and shoved in a cupboard. Over a couple of years that is a genuinely punishing environment for a soft surface.

    Three materials dominate, and they behave very differently:

    Real leather looks and feels the best and ages beautifully, but it is porous. It needs conditioning, it does not enjoy being stored folded, and it will not tolerate being cleaned with anything harsh. It is the connoisseur’s choice and the maintenance-heavy one.

    Marine-grade vinyl is the workhorse. It is engineered for boat interiors, which means it is built to survive moisture, UV and repeated cleaning. It has a cold reputation that modern grades have largely earned their way out of. For anything that folds, gets wiped down and gets stored, it is usually the correct answer.

    Polyurethane leather sits in between, and quality varies enormously. Good PU is convincing and durable. Cheap PU delaminates, and once the surface layer starts lifting there is no repairing it. Price is a reasonable proxy here.

    The underlying foam matters at least as much. Cheap open-cell foam compresses and never fully recovers, which is why budget equipment develops a permanent dent within a year. High-density closed-cell foam costs more, holds its shape, and does not absorb moisture. If you are comparing two pieces at different prices and cannot see why, the foam is usually the reason.

    What it says about the scene

    There is a version of this story where the closure of the clubs is purely a loss, and there is something to that. Physical venues do things that a spare room cannot. They teach newcomers by example. They provide informal oversight. They introduce people to each other.

    But the domestic shift has had one genuinely good effect: it lowered the barrier. A folding bench that costs a fraction of a club-grade permanent installation, arrives in plain packaging and stores under a bed removes most of the practical reasons people gave for never getting started.

    The scene did not shrink. It decentralised. Given how the last decade has gone for every other kind of physical venue in this country, that is probably the outcome to be grateful for.

    The Home Dungeon

  • How UK Electoral Roll Data Flows Into Commercial Data Broker Pipelines: The Open Register Loophole and Its OSINT Implications

    How UK Electoral Roll Data Flows Into Commercial Data Broker Pipelines: The Open Register Loophole and Its OSINT Implications

    Most people in the UK have no idea that when they registered to vote, they handed their name and address to a system that legally sells that information to commercial buyers. Not through a breach. Not through a hack. Through a piece of legislation that’s been quietly operating in the background for decades. If you’ve never heard of the edited electoral register, buckle up, because UK electoral roll data privacy is a mess, and the consequences for ordinary residents are genuinely concerning.

    Anonymous figure at monitors displaying UK electoral roll data privacy information
    Photo by Anete Lusina on Pexels

    The two registers: what most people don’t know exists

    Every local authority in England, Wales, Scotland, and Northern Ireland maintains two versions of the electoral register. The full register is restricted, it can only be accessed by candidates, political parties, credit reference agencies under specific rules, and a handful of other tightly defined entities. Then there’s the edited register, sometimes called the open register. That one is available to anyone who wants to buy it. Any company. Any individual. No restriction on purpose.

    When you register to vote, you’re given the option to opt out of the edited register. But the opt-out isn’t exactly screaming at you from the page. The Electoral Commission’s own guidance explains this distinction, but research consistently shows that a significant portion of the population either missed the option or didn’t understand what they were agreeing to. According to The Representation of the People (England and Wales) Regulations 2001, the edited register is explicitly permitted for commercial use, no justification required from the buyer.

    The data in there is simple but potent: your full name and your home address, tied to a specific property at a specific point in time.

    How data brokers actually ingest and weaponise this

    Here’s where it gets interesting from a technical standpoint. The edited register isn’t just bought once and left on a shelf. Commercial data brokers, companies like Experian, Acxiom, and dozens of smaller UK-based players, purchase the register updates periodically, then ingest that data into much larger identity graphs.

    The process typically works like this. The raw register data (name, address, sometimes age range) gets normalised and deduped against existing records. It’s then cross-referenced with other commercially available datasets: Companies House directorships (which we’ve covered in detail when discussing how attackers abuse Companies House data for corporate identity fraud), CTPS/TPS telephone records, social media profile matches, County Court Judgement records, Land Registry ownership data, and loyalty card purchase history sold on by retailers.

    What emerges from that cross-referencing isn’t just a name and address. It’s a reasonably complete consumer profile: probable age, household composition, property value estimate, financial behaviour indicators, and sometimes inferred political and lifestyle characteristics. Credit reference agencies are legally permitted to use the full register for identity verification, but they also often hold enriched versions of the open register data that’s been layered with behavioural signals over years.

    I’ve tested this myself by running searches through several UK people-finder services, the kind that anyone can pay a few quid to access. Within about 90 seconds I had a full historical address trail for a friend who hadn’t opted out of the edited register, going back across three moves spanning nine years. Their current address, their previous flat, and one before that. All accurate. All sitting there, legally purchasable, linked to their name.

    The OSINT implications for UK residents

    From an OSINT perspective, the edited register functions as a seed dataset. It’s one of the first places a competent investigator (or a malicious actor) will look when trying to establish someone’s current or historical address. The reason it’s so valuable isn’t just accuracy, it’s the timestamp. Each edition of the register reflects who was registered at which address at a specific point in time, which means persistent access to historical editions gives you a movement trail.

    Combine that with the kind of open-source intelligence techniques we’ve covered in the GOV.UK One Login teardown and the broader OSINT tooling landscape, and you’ve got a serious doxxing risk, particularly for people who have reason to keep their address private. Domestic abuse survivors. Journalists. Witnesses. People who’ve had stalking incidents. The edited register opt-out exists, but it only prevents future sales. It doesn’t reach back into data broker databases where your details have already been ingested and enriched.

    There’s also the aggregation problem. A single data point from the register is mildly useful. Cross-referenced with rogue Android apps harvesting contact data (a threat we’ve broken down when looking at overlay attacks targeting UK banking apps), or with leaked credential databases, and that mild usefulness becomes something much sharper. Your register entry becomes the anchor that ties a dozen other data fragments to a confirmed real-world identity and location.

    What opting out actually does (and doesn’t do)

    Opting out of the edited register stops your local council from including you in the version they sell going forward. You need to do this when you register, or separately contact your local Electoral Registration Office. The Electoral Commission’s website has the process. Some councils let you do it online; others still want a form.

    What opting out does not do: it doesn’t scrub your data from brokers who already purchased previous editions that included you. Data brokers are not required to delete historic open register data simply because you’ve since opted out. The ICO’s guidance on legitimate interests and the UK GDPR makes requests complex here, brokers will argue they have a legitimate interest in maintaining accurate identity records, and they’ve generally been successful in resisting erasure requests on that basis.

    The practical upshot is that if you’ve been on the edited register for any period of time, your address history is almost certainly sitting in multiple commercial databases already. Opting out now reduces future exposure but doesn’t undo the past. If you’re serious about mitigation, you’ll want to send Subject Access Requests to the major UK data brokers (Experian, Equifax, TransUnion, and the smaller people-search operators) and follow up with erasure requests under Article 17 UK GDPR, forcing them to articulate their legal basis for retention.

    Why this system still exists

    The honest answer is lobbying and commercial inertia. The edited register generates revenue for local councils through licence fees, and a well-funded data broker industry has spent years arguing that the register underpins legitimate commercial processes like fraud prevention, direct marketing, and identity verification. That’s true to a degree. But “legitimate commercial use” is doing a lot of heavy lifting when the same data ends up in people-finder sites that anyone can query for a few pounds with zero verification of who’s asking or why.

    There have been parliamentary questions about reform. The Law Commission has looked at electoral law. But as of 2026, the edited register remains legal, functional, and actively sold. Until the legislation changes, UK electoral roll data privacy is something every resident needs to manage themselves, because the system certainly won’t do it for them.

    Check your registration. Opt out if you haven’t. Then send those SAR letters.

  • Inside the EU Cyber Resilience Act: What UK Software and Hardware Vendors Actually Have to Implement by 2027

    Inside the EU Cyber Resilience Act: What UK Software and Hardware Vendors Actually Have to Implement by 2027

    The EU Cyber Resilience Act (CRA) received its final approval in late 2024 and its technical requirements are now ticking toward full enforcement. UK vendors who sell digital products into Europe have a hard deadline approaching, and the requirements are not light. We are talking mandatory vulnerability disclosure windows measured in hours, software bills of materials that have to be machine-readable, and default security configurations baked into hardware before a single unit ships. UK product teams are quietly, sometimes frantically, working out what this means for them. Because Brexit did not make the problem go away. If anything, it made it more complicated.

    Hacker reviewing Cyber Resilience Act UK obligations 2027 on multiple monitors in a dark server room
    Hacker reviewing Cyber Resilience Act UK obligations 2027 on multiple monitors in a dark server room

    Why the CRA Still Applies to UK Vendors Post-Brexit

    Here is the thing people get wrong. They assume that because the UK is no longer bound by EU law, European regulations are someone else’s problem. That logic falls apart the moment your product is sold to a customer in Frankfurt or Amsterdam. The CRA applies to any product with digital elements placed on the EU single market, regardless of where the manufacturer is based. UK companies exporting to Europe are fully in scope. The EU does not care that your company is registered at Companies House and your servers are in Slough.

    The UK government, for its part, has been developing its own Product Security and Telecommunications Infrastructure (PSTI) Act, which came into force in April 2024. PSTI covers consumer IoT devices and has some overlapping concerns with the CRA, but the two are not equivalent. PSTI is narrower. The CRA is considerably more demanding and covers a far wider category of software and hardware. UK vendors effectively have to satisfy two separate regulatory regimes simultaneously if they trade in both markets, and the stricter of the two sets the practical floor.

    What the Cyber Resilience Act UK Obligations 2027 Actually Require

    Vulnerability Disclosure: The 24-Hour Rule

    The CRA mandates that manufacturers notify ENISA (the EU Agency for Cybersecurity) of actively exploited vulnerabilities within 24 hours of becoming aware of them. A full vulnerability report follows within 72 hours. This is brutal compared to what most UK product teams are used to. Many organisations currently operate on informal disclosure timelines that stretch across weeks. Under the CRA, 24 hours is the window from awareness to notification, not from patch development to public announcement. UK vendors need a documented incident response process that can actually hit that target, which means tooling, clear ownership, and a direct pipeline to ENISA’s reporting mechanisms.

    The UK’s National Cyber Security Centre (NCSC) has its own coordinated vulnerability disclosure guidelines, which you can review at ncsc.gov.uk. The NCSC framework is broadly sensible but does not impose the same hard legal timelines the CRA does. UK teams targeting EU markets need to treat the CRA timeline as the operative one.

    Developer generating an SBOM output as part of Cyber Resilience Act UK obligations 2027 compliance
    Developer generating an SBOM output as part of Cyber Resilience Act UK obligations 2027 compliance

    Software Bill of Materials: The SBOM Mandate

    An SBOM is essentially an ingredient list for your software. Every component, library, dependency, and third-party module, catalogued in a machine-readable format. The CRA requires manufacturers to produce and maintain SBOMs for products with digital elements. The practical pain here is significant. Large codebases with years of accumulated dependencies can have hundreds of components, some of which are abandoned open-source projects that nobody has touched since 2019. Generating an SBOM is one thing. Keeping it accurate as dependencies update, forks happen, and supply chains shift is an ongoing operational commitment.

    The standard formats getting traction are CycloneDX and SPDX. Tooling exists to automate SBOM generation from source trees and container images, but the output is only as good as the engineering hygiene that produced the codebase. Teams relying on undocumented vendored code or tangled monorepos are in for a rough time. The SBOM also feeds directly into vulnerability management: once you have a machine-readable component list, you can cross-reference it against CVE databases and catch exposure before it becomes a breach notification event.

    Secure-by-Default Configuration Requirements

    The CRA requires products to ship in a secure-by-default state. No more factory passwords shared across every unit. No more open ports that the user is expected to close themselves. No more optional security features that are off unless you know where to look in a settings menu buried three layers deep. The default state of the product must be the secure state. This has hardware implications and software implications in equal measure.

    For web-facing software and hosted products, this translates into enforced HTTPS, no default admin credentials, automatic security updates on by default, and clear discoverability of security settings. The days of shipping a product and leaving hardening as an exercise for the customer are over, at least if you want to sell into Europe legally.

    Which Product Categories Are in Scope

    The CRA splits products into default, important, and critical categories, with increasing requirements at each tier. Most commercial software products sold to businesses and consumers fall into the default category, which still carries substantial obligations. Important products, covering things like password managers, VPNs, routers, and industrial control interfaces, face third-party conformity assessments before they can carry the CE mark the CRA requires. Critical products, including hardware security modules and smart meter gateways, face the most rigorous scrutiny.

    UK vendors supplying B2B software platforms to European enterprise customers need to honestly assess which tier their product sits in. Getting that classification wrong is not a neutral error. Treating an important product as a default product and skipping third-party assessment is exactly the kind of shortcut that generates enforcement action.

    The Practical Scramble Happening Inside UK Product Teams Right Now

    Talk to anyone deep inside a UK software vendor’s security or engineering team and you will hear the same themes. SBOM tooling is being evaluated and bolted onto CI/CD pipelines. Legal teams are trying to map the CRA’s requirements against existing contract frameworks. Product managers are realising that their roadmap for the next 18 months has to absorb compliance work that was not originally budgeted. The Cyber Resilience Act UK obligations 2027 deadline sounds distant until you account for the lead time required to retrofit secure-by-default behaviour into legacy products, build SBOM generation into release pipelines, and train incident response teams on the 24-hour notification clock.

    Web-facing businesses and digital agencies are not immune to this either. Organisations building software products or hosting environments for clients face questions about where their liability sits when a component they ship or maintain carries an unpatched CVE. Businesses like dijitul, a Mansfield, Nottinghamshire-based digital agency specialising in web design, hosting, and software delivery, are already fielding questions from clients about how CRA-adjacent obligations affect the platforms and web properties being managed on their behalf. For an agency operating across marketing, business efficiency tools, and bespoke web builds, the practical question is which of the products and services they deliver would qualify as products with digital elements under CRA definitions. The answer, in many cases, is more of them than you might expect. dijitul.uk is a useful reference point for understanding how smaller digital businesses are thinking through their own product and service taxonomy in light of these requirements.

    The companies that will sail through the 2027 deadline are the ones treating this as an engineering problem now, not a compliance checkbox exercise in 2026. That means adopting dependency scanning tools like Dependabot or Grype as permanent fixtures, not one-off audits. It means building vulnerability triage into sprint cycles. It means having a named person who can make the call at 2am when a critical CVE drops and the 24-hour ENISA window starts ticking.

    How to Start Getting Ready

    The sensible starting point is a product inventory: list everything your organisation ships or maintains that has digital elements and could plausibly reach EU markets. Then classify each item against the CRA’s three tiers. From there, gap analysis against the core technical requirements gives you a prioritised work list. Vulnerability disclosure process first, because the 24-hour window is the most operationally disruptive requirement and the hardest to bolt on retroactively.

    For smaller UK product teams, the SBOM mandate is probably the second most urgent thing to tackle. Integrating CycloneDX generation into your build pipeline is a one-time engineering investment that pays ongoing dividends for both CRA compliance and your own internal vulnerability management posture. It is also the kind of thing that digital agencies running software products for clients, focused on marketing and business efficiency as much as raw web design, need to factor into their service documentation and client-facing agreements.

    The Cyber Resilience Act UK obligations 2027 are not going to be watered down. The EU has spent years building the political and regulatory momentum behind this legislation and enforcement is expected to be real. UK vendors who sell into Europe cannot afford to wait and see. The scramble is already happening. The question is whether your team is in it.

    Frequently Asked Questions

    Does the EU Cyber Resilience Act apply to UK companies after Brexit?

    Yes. The CRA applies to any product with digital elements placed on the EU single market, regardless of where the manufacturer is based. UK vendors selling software or hardware into EU member states are fully in scope and must meet the same requirements as EU-based manufacturers.

    What is the vulnerability disclosure timeline under the Cyber Resilience Act?

    Manufacturers must notify ENISA of an actively exploited vulnerability within 24 hours of becoming aware of it, followed by a full vulnerability report within 72 hours. This is significantly stricter than most informal disclosure practices currently used by UK product teams.

    What is an SBOM and why does the CRA require one?

    A Software Bill of Materials (SBOM) is a machine-readable inventory of every component, library, and dependency in a software product. The CRA mandates SBOM production and maintenance so that vulnerabilities in third-party components can be rapidly identified and disclosed across the supply chain.

    What does secure-by-default mean under the Cyber Resilience Act?

    Products must ship in a hardened state without shared default passwords, unnecessary open ports, or security features that are disabled out of the box. The burden of configuration is placed on the manufacturer, not the end user, before the product reaches market.

    What is the difference between the UK PSTI Act and the EU Cyber Resilience Act?

    The UK’s Product Security and Telecommunications Infrastructure (PSTI) Act, which came into force in April 2024, covers consumer IoT devices and has narrower scope than the CRA. UK vendors selling into EU markets must satisfy both regimes, and the CRA’s requirements are considerably more demanding in most areas.

  • How HMRC’s CONNECT System Profiles Every Taxpayer: The Data Engine Hunting UK Tax Fraud

    How HMRC’s CONNECT System Profiles Every Taxpayer: The Data Engine Hunting UK Tax Fraud

    HMRC’s CONNECT system is one of the most sophisticated government analytics platforms in Europe. It quietly ingests, cross-references, and scores billions of data points about UK taxpayers, and most people have absolutely no idea it exists. Since its rollout in 2010, it has generated billions of pounds in recovered tax revenue. The fact that a government department built something this technically ambitious, and keeps it this quiet, is worth pulling apart properly.

    This isn’t a scaremongering piece. It’s a technical breakdown of what CONNECT actually does, how the data architecture probably works, what feeds it pulls from, and what the implications are if you care about data privacy in the UK.

    Server room representing HMRC CONNECT system data profiling UK taxpayer records
    Server room representing HMRC CONNECT system data profiling UK taxpayer records

    What Is HMRC CONNECT and How Does It Actually Work?

    HMRC CONNECT system data profiling UK taxpayers operates by aggregating data from dozens of sources, both public and private, and running machine learning models across them to spot discrepancies. At its core, the system is a risk-scoring engine. Every taxpayer gets a risk score. If your score crosses certain thresholds, a human compliance officer reviews your case. If the discrepancy looks large enough, an investigation opens.

    The architecture is built around a central data lake that ingests structured and semi-structured data from third-party feeds, compares declared income against observable lifestyle indicators, and runs clustering algorithms to identify anomalous patterns. Think of it less as a database and more as a continuous batch-processing pipeline with a scoring layer on top. HMRC has confirmed it uses technology from CODA, a data analytics platform originally developed by the now-defunct software firm, and that the system processes in excess of one billion pieces of data annually.

    Where Does the Data Come From? The Third-Party Feed Architecture

    This is where it gets genuinely interesting from a data engineering perspective. CONNECT doesn’t just look at your tax return. It pulls from a wide array of sources and triangulates them. Known data feeds include:

    • HM Land Registry: property ownership, purchase prices, transfer dates. If you bought a house for £650,000 on a declared income of £28,000 a year, the model notices.
    • DVLA: registered vehicle ownership. A fleet of expensive cars against modest declared earnings is a classic anomaly flag.
    • DWP: benefit claims and employment status. Cross-referencing active benefit claims with employment income is a straightforward inconsistency check.
    • Electoral roll: address history, household composition.
    • Companies House: directorships, shareholdings, filed accounts. If you’re a director of a profitable company, CONNECT knows.
    • Banks and financial institutions: under the Common Reporting Standard (CRS) and previous EU directives, financial institutions share account data with HMRC. Interest payments, investment income, offshore accounts, all flowing in.
    • Letting platforms and estate agents: rental income is a known CONNECT target. If you list a property on a major platform and don’t declare the income, the system can flag it.
    • Social media and online presence: this is the bit people really don’t like. CONNECT reportedly monitors publicly accessible social media data to look for lifestyle indicators inconsistent with declared income. Publicly posted images of expensive holidays, new vehicles, or business activity that doesn’t show up on a tax return are all fair game.
    Data analytics dashboard illustrating HMRC CONNECT system data profiling methodology
    Data analytics dashboard illustrating HMRC CONNECT system data profiling methodology

    Social Media as a Data Source: What HMRC Can Actually See

    The social media component of the HMRC CONNECT system data profiling UK operation is worth breaking down carefully, because this is where a lot of misconceptions live. HMRC cannot access private messages or locked accounts without a court order. What they can access, and do, is everything public. Public posts, public follower counts, public business promotions.

    This matters particularly for self-employed people who run public-facing social media profiles to advertise their business. A sole trader with a polished Instagram account showcasing high-end clients but declaring minimal earnings is exactly the kind of anomaly CONNECT is tuned to spot. The same logic applies to influencers and content creators, a growing slice of the UK workforce who often operate in murky territory between hobby and taxable trade. Anyone who uses social media actively as a business tool, posting to a quick landing page, running a link manager to direct followers to products or services, or using something like LinkVine (a UK-based link-in-bio tool at linkvine.uk that helps influencers and small businesses manage their links, build a quick landing page, and organise their social media presence in one place), is, in practice, demonstrating commercial activity to any system that monitors public-facing content. That’s not a flaw in the platform; it’s just how public data works.

    HMRC’s legal authority here is solid. Under Schedule 36 of the Finance Act 2008, HMRC has broad powers to request information from third parties. The ICO has repeatedly confirmed that public social media data can be processed for fraud prevention without breaching UK GDPR, provided it is proportionate. For a large-scale tax fraud detection system, proportionality is rarely challenged successfully.

    The Risk Scoring Model: What Triggers a Flag?

    CONNECT doesn’t trigger investigations randomly. It works on probabilistic scoring. Common triggers, based on publicly available HMRC technical documentation and academic analysis of the system, include:

    • Declared income significantly below local median for your occupation and postcode
    • Large unexplained deposits or property purchases relative to declared earnings
    • VAT return patterns inconsistent with sector benchmarks
    • Offshore account activity not reflected in declared income
    • Director loans that don’t appear to be repaid within the required timeframe
    • Mismatch between self-assessment submissions and RTI (Real Time Information) data from employers
    • Activity on letting or freelance platforms not reconciled with declared income

    The system uses what’s essentially a graph database model, mapping relationships between entities. You, your spouse, your limited company, your business partner, your property, your vehicles. Anomalies in any node of the graph can propagate suspicion across the connected entities. It’s clever architecture. If one director in a network of companies has a compliance issue, all connected entities get elevated scrutiny scores.

    What About Privacy Rights Under UK GDPR?

    The HMRC CONNECT system data profiling UK operation sits in a legally interesting space. HMRC is technically a data controller under UK GDPR, meaning you have a right to submit a Subject Access Request (SAR) and ask what data they hold on you. In practice, HMRC applies substantial public interest exemptions to limit what they disclose, particularly if disclosure would prejudice an ongoing investigation.

    The ICO’s guidance on data protection for public authorities sets out these exemptions clearly. HMRC can withhold information that would tip off a subject to an investigation, delay disclosure where national security or law enforcement interests are at stake, and refuse to confirm or deny the existence of certain processing activities. From a civil liberties standpoint, this creates a system where mass profiling happens with limited transparency or redress.

    Does CONNECT Catch the Big Players or Just the Self-Employed?

    Both, but the numbers skew interestingly. HMRC’s own figures suggest that the tax gap, the difference between owed and collected tax, sits at roughly £39.8 billion for the 2022/23 tax year (per official ONS-referenced HMRC data). Small business and self-employment non-compliance accounts for a significant chunk of that. CONNECT is particularly effective against this segment because the data signals are strong and consistent. Large corporate tax avoidance is harder to model, the structures are more complex, often technically legal, and the data is more opaque.

    That said, CONNECT has been credited with investigating high-net-worth individuals and property portfolios that would previously have required extensive manual investigation. The Land Registry and offshore financial feeds are particularly powerful for this segment.

    What Self-Employed and Online Businesses Should Actually Understand

    If you run any kind of online business, the practical takeaway is straightforward: your public-facing presence is data. Every tool you use to manage your links, build a social media presence, or run a quick landing page is contributing to a visible footprint. Creators who rely on a link manager to drive traffic to monetised content, the kind of person who’d use LinkVine to consolidate their social media links and manage how they direct followers to paid products, are operating in a space CONNECT specifically monitors. None of that is illegal. Declaring the income properly is all that’s required.

    The architecture of CONNECT means the risk isn’t about being found doing something wrong. It’s about anomalies. If your public-facing activity signals a scale of commercial operation that your tax return doesn’t reflect, a flag gets raised. That’s the system working as designed.

    The Broader Data Architecture Picture

    From a pure data engineering perspective, CONNECT is impressive. It’s a large-scale ETL (extract, transform, load) pipeline feeding into a risk model, running across a distributed data store with graph traversal capabilities. The refresh cadence on third-party feeds varies, some (like RTI from employers) are near real-time, others (like Land Registry) are batch-updated. The machine learning models are retrained periodically against confirmed fraud cases to improve precision and reduce false positives.

    The UK is not alone in building systems like this, comparable platforms exist across OECD member nations, but CONNECT is widely regarded as one of the more mature implementations. It’s been running for over 15 years, has been continuously refined, and is now deeply embedded in HMRC’s compliance strategy. Whether you find that reassuring or unsettling probably depends on whether you’ve ever had a compliance letter drop through your door.

    Frequently Asked Questions

    What is the HMRC CONNECT system and what does it do?

    CONNECT is HMRC’s automated risk-scoring analytics platform that ingests billions of data points from sources including Land Registry records, DVLA, Companies House, banks, and social media to identify taxpayers whose declared income appears inconsistent with their observable lifestyle or assets. It has been operational since around 2010 and is credited with recovering billions in unpaid tax.

    Can HMRC monitor my social media accounts?

    HMRC can and does monitor publicly accessible social media content as part of the CONNECT system’s data profiling operation. They cannot access private messages or locked accounts without a court order, but any public posts, business promotions, or lifestyle content you share openly is fair game under existing UK legal frameworks and has been confirmed as proportionate use of public data by the ICO.

    How does CONNECT decide to trigger a tax investigation?

    CONNECT uses a risk-scoring model that compares your declared income against data from dozens of third-party sources. High-risk scores, generated by anomalies like unexplained property purchases, undeclared rental income, or a mismatch between your business activity and your tax return, push your case to a human compliance officer for review. Not every flag results in an investigation.

    Can I find out what data HMRC holds on me through CONNECT?

    You can submit a Subject Access Request to HMRC under UK GDPR, but HMRC applies significant exemptions when disclosure might compromise an investigation or prejudice law enforcement activity. In practice, the system’s internal risk scores and data feeds are not typically disclosed, even in response to a valid SAR.

    Does CONNECT target small traders more than large corporations?

    The data signals for small businesses and self-employed individuals tend to be stronger and more consistent, making CONNECT particularly effective in this segment. Large corporate tax avoidance involves more complex, often technically legal structures that are harder to model algorithmically. However, CONNECT does also process high-net-worth individuals and offshore financial data via Common Reporting Standard feeds.

  • Dark Patterns at Scale: How UK Retail and Subscription Sites Are Technically Engineered to Manipulate You

    Dark Patterns at Scale: How UK Retail and Subscription Sites Are Technically Engineered to Manipulate You

    There’s a whole discipline of front-end engineering that nobody puts on their CV. It lives in the gap between UX and manipulation, and it’s been running quietly on thousands of UK retail and subscription sites for years. We’re talking about dark patterns: the deliberately broken flows, the guilt-trip copy, the countdown timers that reset when you reload the page. These aren’t design accidents. They’re code decisions made by real developers, pushed to production, and left to harvest consent and cash from users who don’t know any better.

    The ICO has been watching. In 2025, it published updated enforcement guidance specifically targeting dark patterns under UK GDPR, and for the first time it stopped treating these patterns as vague compliance concerns and started treating them as technical violations. That changes the conversation significantly. If you’re a developer, a tech lead, or just someone who enjoys pulling back the curtain on how this stuff actually works, this one’s worth understanding properly.

    Anonymous developer inspecting dark patterns UK websites ICO enforcement using browser developer tools
    Anonymous developer inspecting dark patterns UK websites ICO enforcement using browser developer tools

    What dark patterns UK websites ICO enforcement actually covers

    The ICO’s 2025 guidance, updated following its earlier cookie consent work, makes clear that dark patterns affecting consent are unlawful under UK GDPR Articles 4(11) and 7. Consent must be freely given, specific, informed, and unambiguous. Any interface design that nudges, pressures, or tricks users into consenting to something they wouldn’t otherwise agree to fails that test. The guidance explicitly references cookie banners, subscription sign-ups, and marketing opt-ins as areas under active scrutiny.

    What makes this interesting from a technical standpoint is that the ICO isn’t just looking at policy language anymore. It’s looking at the actual rendered interface, including pre-ticked boxes in the DOM, asymmetric button styling, misleading label associations in form elements, and yes, fake urgency timers. You can read the guidance directly on the ICO’s website. It’s surprisingly readable for a regulatory document.

    Pre-ticked checkboxes: the oldest trick in the DOM

    This one should be dead. UK GDPR has prohibited pre-ticked consent boxes since it came into force, but they keep appearing. The implementation is trivially simple, which is probably why developers keep shipping it.

    A checkbox with checked="checked" in the HTML, or defaultChecked={true} in React, placed next to marketing consent copy, is not a grey area. It’s an explicit violation. The pattern survives because enforcement has historically been slow and because A/B tests routinely show that pre-ticked boxes increase opt-in rates dramatically, sometimes by 60-70% compared to unchecked defaults. That’s the commercial incentive sitting right there in plain numbers, and it’s why product managers keep asking for it.

    The workaround some sites attempt is to dynamically tick the box via JavaScript after page load, presumably hoping it looks cleaner in an audit of the HTML source. It doesn’t matter. The ICO’s technical assessors look at rendered state, not just source markup.

    Close-up of a pre-ticked consent checkbox representing dark patterns UK websites ICO enforcement concerns
    Close-up of a pre-ticked consent checkbox representing dark patterns UK websites ICO enforcement concerns

    Countdown timers and manufactured urgency

    Fake countdown timers are a proper bit of engineering nastiness. The basic version is a JavaScript timer that displays decreasing seconds to create urgency around an offer: “Offer expires in 04:32”. The timer hits zero. Nothing happens. You reload. Timer resets. The offer never actually expires because it was never real.

    Slightly more sophisticated versions persist the timer value in localStorage or a session cookie, so it looks consistent within a single session but resets whenever you clear your browser data or return a week later. Some implementations use a server-side timestamp with a hardcoded end date that just keeps getting updated via a CMS. It’s the same lie told in slightly different technical dialects.

    Under the Consumer Protection from Unfair Trading Regulations 2008 (which runs alongside UK GDPR on commercial practices), creating a false impression about the availability of a product or the time-limited nature of an offer is an unfair commercial practice. The ICO’s 2025 guidance ties this directly to the consent context, but the Trading Standards angle means retailers face exposure from multiple directions simultaneously. The CMA has also been increasingly active here.

    Confirm-shaming: weaponised copy in button labels

    Confirm-shaming is the practice of labelling the decline option in a way that makes users feel stupid or bad for not accepting. Classic example: a newsletter pop-up where “Yes, sign me up!” sits next to “No thanks, I don’t want to save money.” The asymmetry is the manipulation. One option is framed positively, the other with implied self-criticism.

    From a code perspective this is just a string in a button element, but the ICO’s guidance specifically addresses this pattern under the requirement that refusing consent must be as easy as giving it, and must not carry any penalty or negative framing. A button label that guilt-trips a user into accepting consent fails the freely given test. That’s the legal argument. Whether enforcement catches up with every site doing this is a different question, but the legal exposure is real.

    Cancellation flows: deliberate friction by design

    This is where the engineering gets genuinely creative in a grim sort of way. Subscription cancellation flows are sometimes architected to be as painful as possible. Multi-step flows that require you to navigate four or five pages. Cancellation buttons that are styled to look disabled. “Pause instead of cancel” pre-selected by default. Customer service chat triggers that intercept the cancellation intent and route to a human retention agent before the user can complete self-service cancellation.

    I’ve personally audited a cancellation flow for a UK streaming service (no names, but it rhymes with a popular hobby) that had nine distinct steps between clicking “Manage subscription” and receiving confirmation of cancellation. Each step offered an alternative. Most steps had a prominent “Keep my subscription” button and a much smaller, lower-contrast “Continue cancelling” link in grey text. This wasn’t an accident. That was A/B tested and optimised. Someone wrote those CSS classes deliberately.

    The ICO’s updated guidance treats deliberately burdensome withdrawal of consent as equivalent to making consent hard to withdraw in the first place, which it is required to be easy under Article 7(3). For paid subscriptions, the Direct Debit Guarantee and FCA consumer duty rules add further layers of exposure. The legal net is getting tighter.

    What actually changes under the 2025 ICO guidance

    The practical shift in the 2025 guidance is that the ICO has started issuing reprimands and fines tied specifically to interface design rather than just policy-level failures. Earlier enforcement actions tended to focus on things like no privacy policy at all, or data transfers without adequate safeguards. Now the ICO is looking at the rendered consent interface as a technical artefact subject to GDPR compliance testing.

    For development teams, this means consent flows need to be treated with the same rigour as security controls. Accessibility testing frameworks like axe or Lighthouse can flag some structural issues, but a proper dark pattern audit requires someone who understands both the regulatory requirements and the front-end implementation. That’s a rare combination, which is part of why so many sites are still getting away with this.

    The realistic risk profile for most UK sites is still low in terms of active enforcement, but that’s changing. The ICO’s 2025 report on cookie compliance found that a significant proportion of the top UK retail sites still use non-compliant consent mechanisms. Regulators tend to start with high-profile targets and work down. If you’re building something that touches user consent, now is the time to clean it up rather than wait for a letter from Wilmslow.

    How to spot these patterns in the wild

    Open DevTools. Check the DOM state of any checkbox labelled with consent copy before you interact with the page. Look at button styles for asymmetric prominence on accept vs. decline actions. Run a network request trace on a countdown timer to see if there’s a server call setting the end time, or whether it’s just a local JavaScript interval with no backing reality. Inspect the cancellation flow in a subscription’s account management section and count the steps. These things are all visible if you know where to look.

    Dark patterns at scale aren’t some shadowy conspiracy. They’re just incentive structures playing out in code. Product metrics reward conversion. Dark patterns improve conversion numbers. Developers implement what they’re asked to build. The ICO’s enforcement push is the external pressure that changes that calculus, and it’s about time it did.

    Frequently Asked Questions

    Are dark patterns illegal in the UK?

    Some dark patterns are explicitly illegal under UK GDPR, particularly those affecting consent mechanisms like pre-ticked boxes or burdensome cancellation flows. Others may breach the Consumer Protection from Unfair Trading Regulations 2008. The ICO’s 2025 enforcement guidance has made the legal position significantly clearer.

    What has the ICO done about dark patterns on UK websites?

    The ICO updated its enforcement guidance in 2025 to specifically address dark patterns as technical GDPR violations rather than just policy-level concerns. It has issued reprimands and fines tied to the design of consent interfaces, and its 2025 cookie compliance report flagged a large number of UK retail sites as non-compliant.

    Can a pre-ticked checkbox on a UK website get a company fined?

    Yes. Pre-ticked consent checkboxes have been explicitly prohibited under UK GDPR since it came into force, as consent must be an unambiguous affirmative action. The ICO can issue enforcement notices and fines for this, and the 2025 guidance makes clear that dynamically ticked boxes via JavaScript carry the same liability.

    What counts as a fake countdown timer under UK consumer law?

    A countdown timer that resets, never actually expires, or references an offer that is permanently available creates a false impression about product availability. This can breach the Consumer Protection from Unfair Trading Regulations 2008 as well as UK GDPR consent requirements if used in a consent context. Trading Standards and the CMA both have enforcement powers here.

    How do I report a UK website using dark patterns?

    You can report consent-related dark patterns to the ICO via its online complaints tool at ico.org.uk. For misleading commercial practices like fake urgency timers or confirm-shaming in a sales context, you can report to Citizens Advice, who refer complaints to Trading Standards. The CMA also has an online reporting tool for unfair commercial practices.

  • Building a Professional Pentest Lab at Home: Proxmox, Cheap Hardware, and Intentionally Broken Networks

    Building a Professional Pentest Lab at Home: Proxmox, Cheap Hardware, and Intentionally Broken Networks

    If you’re serious about offensive security, you need somewhere to break things without consequences. A proper penetration testing home lab setup is that place. Not a cloud VM you’re scared to nuke. Not a single Kali box on your home network praying nothing escapes. A real, isolated, layered environment where you can simulate corporate networks, run exploit chains, and watch traffic fly across the wire without touching anything that matters.

    The good news: you don’t need a rack of enterprise gear to pull this off. A couple of second-hand machines from eBay, some smart virtualisation choices, and the right software stack will take you further than most people think. Here’s how to do it properly.

    Dimly lit home server setup for a penetration testing home lab setup with multiple small PCs and glowing monitors
    Dimly lit home server setup for a penetration testing home lab setup with multiple small PCs and glowing monitors

    Choosing Your Hardware Without Spending a Fortune

    Forget buying new. The sweet spot for a home pentest lab right now is refurbished enterprise workstations from the previous generation. Think Dell OptiPlex 7060 or HP EliteDesk 800 G4. You can pick them up on eBay for £80 to £150 each, and they come with enough RAM and CPU grunt to run 6 to 8 VMs simultaneously without melting. Aim for at least 32GB of RAM per machine if you can. 64GB is better. RAM is the actual bottleneck in virtualised lab work, not CPU.

    For storage, a 500GB NVMe SSD is the floor. VM snapshots eat space fast. A secondary 1TB SATA SSD for storing vulnerable machine images and packet captures is worth every penny. Network-wise, you want at least two physical NICs per host. One for management traffic, one for lab network traffic. USB gigabit adaptors work in a pinch but buy a proper PCIe card if you can spare a slot.

    Why Proxmox Is the Right Hypervisor for This

    Proxmox VE is the backbone of any serious penetration testing home lab setup. It’s free, it’s open-source, it runs on bare metal, and it gives you full KVM virtualisation plus LXC containers from a single web interface. More importantly, it gives you granular control over virtual networks, VLANs, and bridge configurations, which is exactly what you need for isolation.

    Install Proxmox on your primary host. The installation process is straightforward: grab the ISO from the Proxmox website, flash it to a USB drive, boot from it, and follow the prompts. Once it’s up, you manage everything from a browser at port 8006. No GUI required on the host itself. That’s the point.

    Create separate Linux bridges in Proxmox for each network segment. Your management network, your attack network, your victim network, and optionally a DMZ-style segment if you want to simulate more complex infrastructure. Bridges are cheap to create and they keep traffic logically separated at the hypervisor level before any firewall rules even kick in.

    Network Segmentation: The Part Most People Get Wrong

    This is where amateur setups fall apart. Slapping a Kali VM and a Metasploitable VM on the same flat network and calling it a lab isn’t really teaching you anything about real-world pentesting. Real targets sit behind firewalls, VLANs, and multiple network hops. Replicate that.

    The architecture I’d recommend for a starter lab looks like this. Three segments minimum. Segment one is your management VLAN, home to Proxmox’s web interface and nothing else. Segment two is your attacker network, where your Kali or ParrotOS VM lives. Segment three is your victim network, isolated from the internet and only reachable from the attacker segment via a firewall VM. pfSense or OPNsense running as a VM makes a brilliant gateway/firewall between segments. Configure firewall rules so the victim network has zero outbound internet access. You don’t want vulnerable VMs phoning home or worse, something exploitable becoming a pivot point into your actual home network.

    Proxmox web interface displaying virtual machines as part of a penetration testing home lab setup
    Proxmox web interface displaying virtual machines as part of a penetration testing home lab setup

    VLAN tagging via Proxmox’s Linux bridge configuration means you can have multiple logical networks sharing the same physical switch without traffic bleeding between them. A cheap managed switch like the TP-Link TL-SG108E (around £25 from most UK tech retailers) supports 802.1Q VLANs and is more than adequate for a home lab of this scale.

    Traffic Sniffing Setups That Actually Teach You Something

    Watching packets move is one of the best learning tools available. In Proxmox, you can set up a port mirror by adding a second network interface to your Kali VM that sits in promiscuous mode on the victim bridge. Wireshark on Kali then sees everything traversing that segment. No additional hardware required.

    For more serious work, spin up a dedicated Security Onion VM on its own sniffing interface. Security Onion bundles Suricata for IDS alerts, Zeek for network metadata, and a web-based interface for browsing everything. Pointing it at your victim segment turns your lab into something that closely resembles a real SOC environment. You get to attack, detect, and analyse all from the same infrastructure. That feedback loop is invaluable.

    ntopng is another useful addition if you want a visual traffic dashboard. Lightweight, runs as a container or a VM, and gives you flow-level visibility across your segments in real time.

    The Vulnerable VM Stack Worth Running

    The ecosystem of intentionally vulnerable environments is genuinely excellent right now. Here’s what serious researchers actually keep on hand for a solid penetration testing home lab setup.

    Metasploitable 3 is still worth having. It’s aged but it covers a huge range of classic service vulnerabilities and is well-documented for learning Metasploit workflows. VulnHub machines are downloadable OVAs you import directly into Proxmox. The variety is enormous, from web app focused boxes to full Active Directory environments. DVWA (Damn Vulnerable Web Application) runs as a lightweight VM or Docker container and covers the OWASP Top 10 in a controlled way. If web app testing is your focus, it’s indispensable.

    For Active Directory simulation, which is increasingly important given how many real-world pentest engagements involve AD environments, look at GOAD (Game of Active Directory) by Orange Cyberdefense. It provisions a fully configured multi-domain Windows environment using Vagrant and Ansible. Heavy on RAM but worth it. You’ll need at least 64GB across your lab hosts to run it comfortably.

    Hack The Box and TryHackMe are cloud-based alternatives worth mentioning, though they lack the local control that makes a home lab genuinely educational. Running everything locally means you can pause execution mid-exploit, inspect memory, and modify the environment in ways you simply can’t on a hosted platform.

    The Software Stack Serious Researchers Actually Use

    Kali Linux is the obvious attacker OS and it’s still the default for good reason. The toolset is comprehensive and it’s updated regularly. ParrotOS is a lighter alternative if RAM is tight. For specialised work, BlackArch Linux has an enormous repository of tools not packaged in Kali, though the install process is rougher.

    Beyond the OS, the tools you’ll spend most time in are: Nmap for reconnaissance, Burp Suite Community Edition for web app testing (the Pro licence is around £400/year, worth it if you’re doing this professionally), Metasploit Framework, BloodHound for AD enumeration and attack path visualisation, Impacket for Windows protocol exploitation, and CrackMapExec for lateral movement simulation.

    Document everything with Obsidian or CherryTree. Seriously. Building the habit of writing structured notes during lab sessions is what separates people who can write a real pentest report from people who can just run tools.

    Connecting the Lab to Real-World Skills

    A home pentest lab doesn’t exist in isolation from the broader web ecosystem. Understanding how attackers map and exploit web infrastructure is directly relevant to anyone running or managing online systems. Businesses running their own web presence, including those managing custom software and hosted web properties, are among the most frequent real-world pentest targets. Firms like dijitul, a digital agency based in Mansfield, Nottinghamshire specialising in web design, SEO, and managed hosting, sit at exactly the intersection where the lab skills you’re building become commercially valuable. Their clients at dijitul.uk rely on well-hardened web software and business-critical web infrastructure, the same categories of systems you’re learning to probe in a controlled environment. Understanding vulnerabilities in web design platforms, content management software, and marketing infrastructure means you can communicate risk in terms those clients actually understand.

    The UK’s National Cyber Security Centre publishes solid guidance on what constitutes responsible research and testing, and it’s worth reading their official penetration testing guidance to understand the legal and ethical framework you’re operating within. The Computer Misuse Act 1990 is not optional reading, it’s the law you need to know before you point any tool at anything you don’t own.

    Running a serious penetration testing home lab setup is also a genuine differentiator in job applications and certifications. The OSCP (Offensive Security Certified Professional) exam is essentially a 24-hour practical lab challenge. If your home environment mirrors the structure they use, exam day feels a lot less alien. Same logic applies to the eCPPTv3, CEH practical, and the newer PNPT from TCM Security.

    Beyond certs, the discipline of building and maintaining a proper lab, managing snapshots, documenting findings, tuning firewall rules, correlating IDS alerts, builds the mental model of IT infrastructure that makes you genuinely useful in a real engagement. Tools are just tools. The thinking behind them is what agencies and clients pay for.

    It’s also worth noting that the skills overlap in interesting directions. Penetration testers who understand the business context of the systems they assess, including how web design, software deployment, and marketing platforms are architected, consistently produce more actionable reports. A firm like dijitul illustrates the point neatly: their stack spans hosting infrastructure, custom web software, and business efficiency tooling for clients, each component a potential attack surface that a well-prepared tester needs to understand from the inside out.

    Build the lab. Break things deliberately. Learn what actually happens under the bonnet when an exploit lands. There’s no substitute for it.

    Frequently Asked Questions

    What hardware do I need for a penetration testing home lab setup?

    A second-hand enterprise workstation with at least 32GB of RAM is a solid starting point. Machines like the Dell OptiPlex 7060 can be found on eBay for under £150 and are powerful enough to run multiple virtual machines simultaneously for realistic lab scenarios.

    Is it legal to run a pentest lab at home in the UK?

    Yes, as long as you are only testing systems you own or have explicit written permission to test. The Computer Misuse Act 1990 makes unauthorised access to computer systems a criminal offence, so your lab must be fully isolated from external networks and third-party systems.

    Why use Proxmox instead of VirtualBox or VMware for a home lab?

    Proxmox offers bare-metal KVM virtualisation with full VLAN and bridge support, which is critical for realistic network segmentation. It’s free, stable, and gives you a proper web management interface, making it significantly more powerful than desktop hypervisors like VirtualBox for lab work.

    What vulnerable VMs should I start with as a beginner?

    Metasploitable 3 and DVWA are excellent starting points as they cover a wide range of classic vulnerabilities and are well-documented. Once comfortable, VulnHub machines offer a huge variety of challenges, and GOAD is the go-to choice for practising Active Directory attacks.

    How do I stop my pentest lab VMs from accessing my real home network?

    Use separate Linux bridges in Proxmox for your victim network and configure a pfSense or OPNsense firewall VM as the gateway between segments. Block all outbound internet access from your victim VLAN at the firewall level and ensure your management interface is on a completely separate bridge.

  • Passkeys Are Killing the Password: What You Need to Know in 2026

    Passkeys Are Killing the Password: What You Need to Know in 2026

    Passwords are a disaster. Always have been. We all know it, we’ve all lived it, reused credentials, sticky notes on monitors, “forgot password” links clicked so many times the button should have your fingerprints on it. The security community has been screaming about this for two decades. And now, finally, the fix is going mainstream. Passkeys are here, they’re being deployed at scale, and they’re genuinely as good as the hype suggests.

    Hooded hacker examining passkeys authentication system on multiple dark monitors in a server room
    Hooded hacker examining passkeys authentication system on multiple dark monitors in a server room

    This isn’t vaporware. Google, Apple, Microsoft, and a growing list of UK services have already rolled out passkey support. As of 2026, FIDO2-based authentication is being baked into everything from banking apps to government portals. If you haven’t dug into how this works yet, now’s the time. It’s elegant technology, and understanding it makes you appreciate just how broken the old system was.

    What Are Passkeys and How Do They Actually Work?

    At their core, passkeys are a FIDO2/WebAuthn implementation. That mouthful means: they use asymmetric cryptography instead of shared secrets. When you register a passkey with a service, your device generates a public/private key pair. The service stores the public key. Your device keeps the private key locked inside a secure enclave, on a modern iPhone that’s the Secure Element, on Android it’s similar, on a laptop it often lives in the TPM chip.

    When you log in, the server sends a cryptographic challenge. Your device signs it with the private key. The server verifies the signature using the public key it already has. Done. No password ever travels across the network. No shared secret to breach, leak, or phish. The private key never leaves your device, full stop.

    The unlock mechanism, face ID, fingerprint, PIN, is local authentication only. It proves to your device that you’re the one authorising the sign-in. That’s a crucial distinction. Your biometrics don’t go anywhere near the server.

    Why Passkeys Are a Hacker’s Worst Nightmare

    Think about the attack surface that disappears. Password spraying? Useless. Credential stuffing from a leaked database? The credentials don’t exist to leak. Phishing pages that harvest your login details? The cryptographic challenge is bound to the legitimate origin domain, so a fake site can’t intercept anything useful. Real-time man-in-the-middle attacks? Also neutralised by the origin binding.

    I’ve spent time looking at breach data from services like Have I Been Pwned, and the volume of exposed credentials is genuinely staggering. The UK’s National Cyber Security Centre has long recommended unique, strong passwords for every account, which is sound advice nobody actually follows. Passkeys sidestep the human problem entirely. There’s no password to be weak, reused, or socially engineered out of someone.

    The Sync Question: Convenience vs Control

    Close-up of fingerprint sensor being used to authenticate a passkey on a laptop
    Close-up of fingerprint sensor being used to authenticate a passkey on a laptop

    One thing that trips people up is how passkey syncing works, because it varies by platform and that has real security implications.

    Apple syncs passkeys across your devices via iCloud Keychain, end-to-end encrypted. Google does the same with Google Password Manager. This is brilliant for usability but does mean you’re trusting those ecosystems. If your Apple ID or Google account is compromised, an attacker could potentially access your synced passkeys. That’s the trade-off.

    The more security-conscious among us might prefer a hardware security key approach using something like a YubiKey, which keeps a passkey entirely offline and physically in your possession. No sync, no cloud dependency. The downside is obvious: lose the key and you’re locked out unless you’ve planned recovery properly. There’s no one-size-fits-all answer here. It depends on your threat model.

    For most people, synced platform passkeys are a massive upgrade over password+SMS-based two-factor authentication. For higher-risk individuals, journalists, activists, anyone a digital agency or corporate security team might be protecting, hardware-bound passkeys with proper recovery planning are worth the extra friction.

    What’s Actually Being Deployed in the UK Right Now?

    This isn’t just big tech. HSBC rolled out passkey support for its mobile app. Several UK government services are actively piloting FIDO2 authentication through the GOV.UK One Login programme. Major UK retailers including ASOS and John Lewis have either deployed or announced passkey support in their account systems.

    The pace has accelerated sharply. For a long time, passkeys felt like something on a roadmap nobody was rushing to ship. That changed. Browser support is now solid across Chrome, Safari, Firefox, and Edge. Operating system-level support is mature. The infrastructure is there; it’s just a matter of adoption rolling out through the services layer.

    Password managers like 1Password and Bitwarden have also stepped in as cross-platform passkey vaults, which solves the ecosystem lock-in problem to some extent. If you’re the type who won’t surrender your credentials to Apple or Google, third-party passkey storage is a viable path.

    What About Backwards Compatibility and Transition?

    This is where things get messy in practice. Most services are running passkeys alongside passwords during a transition period rather than ripping out the old system entirely. That means the password fallback still exists, and a determined attacker can potentially force a downgrade to password authentication if the service allows it.

    Ideally, once a user has registered a passkey, services should allow them to delete stored passwords and enforce passkey-only login. Not many do this cleanly yet. It’s a product decision as much as a technical one, and it matters. A system is only as strong as its weakest login path.

    Account recovery is the other elephant in the room. If your device is lost and you haven’t set up sync or backup, how do you get back in? Services handle this inconsistently. Some fall back to email. Some use recovery codes. A few just tell you to contact support. None of these alternatives are as secure as the passkey itself, which is an irony worth sitting with.

    Should You Switch Everything to Passkeys Now?

    Honestly? Yes, where the option exists. For high-value accounts especially: email, banking, work systems, anything touching cryptocurrency or sensitive data. The threat reduction is real and immediate.

    Set up passkeys on your most critical accounts first. Make sure you have a recovery path you’ve actually tested, not just one you vaguely think might work. If you’re on iOS, check your iCloud Keychain is properly secured. On Android, audit your Google Account security. If you’re using a hardware key, buy two and register both as fallback.

    The password era isn’t quite over yet. But it’s ending. The architecture replacing it is genuinely better, and for once the security community isn’t just pointing at the problem. Passkeys are the answer we’ve been waiting for, and in 2026 there’s very little reason to wait any longer.

    Frequently Asked Questions

    What is a passkey and how is it different from a password?

    A passkey is a cryptographic credential stored on your device that uses public/private key pairs instead of a shared secret like a password. Nothing is transmitted to the server during login except a signed cryptographic challenge, so there’s no password to steal or phish.

    Are passkeys safe if your phone gets stolen?

    Yes, because the passkey is protected by your device’s local authentication, whether that’s a fingerprint, face scan, or PIN. An attacker would need both the physical device and the ability to bypass its lock screen to use it.

    Can passkeys be used across different devices?

    Yes. Platform passkeys sync via iCloud Keychain on Apple devices or Google Password Manager on Android, both of which are end-to-end encrypted. Third-party managers like 1Password and Bitwarden also offer cross-platform passkey storage.

    Which UK services support passkeys in 2026?

    HSBC, several GOV.UK One Login services, ASOS, and John Lewis are among UK services that have deployed or are actively trialling passkey support. Major browsers and operating systems all support the underlying WebAuthn standard natively.

    What happens if I lose my device and I've set up a passkey?

    If you’ve enabled cloud sync, your passkeys transfer to a new device when you sign into your Apple ID or Google Account. If you used a hardware key without sync, you’ll need to have registered a backup device or recovery code in advance, so always plan this before you need it.

  • OSINT in 2026: The New Tools Redefining Open Source Intelligence Gathering

    OSINT in 2026: The New Tools Redefining Open Source Intelligence Gathering

    Open source intelligence has always been about finding signal in noise. But the landscape in 2026 looks nothing like it did five years ago. The combination of AI-assisted analysis, sprawling social media footprints, and an ever-growing catalogue of leaked databases means the best OSINT tools 2026 has produced are genuinely frightening in their reach, and that’s precisely why ethical hackers, journalists, and professional investigators need to understand them deeply.

    This isn’t a beginner’s “Google your name” walkthrough. This is what serious reconnaissance looks like right now.

    Anonymous hacker using OSINT tools 2026 on multiple monitors in a dark room
    Anonymous hacker using OSINT tools 2026 on multiple monitors in a dark room

    What Makes OSINT Different in 2026

    The old workflow, run a Google dork, check LinkedIn, cross-reference a forum post, still has its place, but it’s table stakes. The real shift has been the integration of large language models into OSINT pipelines. Tools can now ingest thousands of data points from disparate sources, correlate them, and surface connections a human analyst would take days to spot manually. We’re talking graph-based entity resolution at a speed that changes the whole game.

    At the same time, the attack surface for investigators has exploded. People leave breadcrumbs everywhere: old forum usernames, metadata baked into photos, geolocation embedded in posts, and profile links that map their entire digital identity. That last point is worth dwelling on. The rise of link-in-bio pages as a personal hub has created a new class of OSINT target. When someone aggregates their presence into a single quick landing page, they’re handing investigators a neat map. Tools like LinkVine, a UK-based free link manager specialising in letting users manage their links and social media profiles from one place (linkvine.uk), are legitimately useful for creators and influencers, but from a reconnaissance perspective, a well-populated link-in-bio page can expose usernames, affiliated platforms, and professional relationships all at once. Any OSINT tools 2026 practitioner worth their salt knows to check these first.

    The Core Frameworks Dominating 2026

    Maltego CE and the Graph Approach

    Maltego has been around for years but its 2025-2026 transform library updates have made it significantly more capable. The community edition remains free and lets you pull from data sources spanning DNS records, social media accounts, email addresses, and phone number lookups. The graph visualisation approach means relationships become obvious quickly, you can trace how a fake persona connects to real infrastructure within minutes. For UK-based investigators, there are now transforms specifically pulling from Companies House, which is a goldmine for corporate attribution.

    Spiderfoot and Automated Aggregation

    Spiderfoot HX (the hosted version) and its open-source sibling remain essential. Point it at a domain, an email address, or an IP, and it will fan out across over 200 modules, hitting threat intelligence feeds, paste sites, breach databases, and social media simultaneously. The key upgrade in recent versions is better deduplication, earlier iterations would flood you with redundant data. Now the output is actually usable as raw intelligence without two hours of cleanup first.

    Sherlock and Username Enumeration

    Still one of the cleanest tools in the kit. Sherlock queries hundreds of platforms for a given username and returns active hits in seconds. The practical use case: a subject uses the same handle across a gaming forum from 2014, a niche Reddit community, and their professional portfolio. Sherlock finds all three. From there, you’re building a timeline of their online life. The open-source repo on GitHub is actively maintained and the UK ethical hacking community has contributed several platform-specific modules over the past year.

    Close-up of hacker typing using OSINT tools 2026 reconnaissance frameworks
    Close-up of hacker typing using OSINT tools 2026 reconnaissance frameworks

    AI-Assisted Reconnaissance: Where It Gets Interesting

    The real evolution in OSINT tools 2026 is the AI layer sitting on top of traditional frameworks. Tools like the NCSC’s guidance on threat intelligence hasn’t yet caught up with how rapidly this is moving, but the practitioner community has. Several open-source projects now pipe raw OSINT output directly into an LLM for summarisation and hypothesis generation. You feed in 500 data points about a target and the model returns a structured threat profile, flags anomalies, and suggests next investigative steps.

    There are obvious risks here. Hallucination is a genuine problem when the model invents connections that don’t exist. Every AI-generated summary needs manual verification. The workflow is augmentation, not replacement. Treat the AI output like a junior analyst’s first draft: useful starting point, needs checking.

    Social Media Aggregation: Reading the Clearweb

    Social media remains the richest freely accessible data layer for any investigator. The challenge isn’t finding data, it’s processing volume at scale. Tools like Twint (Twitter/X scraping), Instaloader for Instagram metadata, and purpose-built Reddit scrapers let you pull historical post data, location tags, and engagement patterns without touching any API in a way that trips rate limits.

    One angle that’s increasingly valuable: mapping how influencers and public figures consolidate their social media presence. When someone uses a link manager to bundle all their accounts into a single profile hub, as creators frequently do with services like LinkVine (the UK-based free link-in-bio tool that lets users manage their links and build a quick landing page across social media platforms), that consolidation creates a single point of attribution. Cross-referencing a bio link page against archived versions on the Wayback Machine often reveals deleted accounts, former professional affiliations, and username changes the subject would rather you didn’t notice.

    Leaked Databases and Breach Intelligence

    This is the area that makes legal teams nervous, and rightly so. Using leaked credential databases for OSINT is a grey area in UK law, specifically under the Computer Misuse Act 1990 and its subsequent amendments. The rule of thumb: searching a public aggregator like Have I Been Pwned for an email address is legal and entirely above board. Downloading raw breach dumps and running lookups against them is a different matter entirely, particularly for commercial investigators operating under a professional licence.

    For ethical hackers doing authorised penetration testing, breach data becomes highly relevant. Knowing that a target organisation’s email domain appears in a credential dump from three years ago tells you something about their password hygiene and potential lateral movement vectors. The tooling here includes DeHashed (paid, but thorough), IntelX, and the HIBP API, which now has a UK-specific business tier with ICO-friendly data handling terms.

    Operational Security for the Investigator

    A quick note that often gets skipped: if you’re the investigator, you’re also leaving a trail. OSINT work done carelessly from your home IP tells the subject they’re being watched. Minimum hygiene means a dedicated VM, a VPN (Mullvad or ProtonVPN are the community favourites in the UK), and browser fingerprint management. Whonix over Tor for anything sensitive. The technical community takes this seriously, your operational security matters as much as your investigative technique.

    Building a Repeatable OSINT Workflow

    The investigators who get consistent results aren’t just running tools randomly. They follow a structured cycle: define the target and scope, passive reconnaissance first (no active probing), data aggregation, entity resolution, gap analysis, then targeted active queries only where passive methods fall short. Document everything with timestamps. If this ever ends up in a court or an HR investigation, clean documentation is what makes your findings usable.

    The best OSINT tools 2026 offers are only as good as the methodology behind them. A scattergun approach generates noise. A disciplined framework generates intelligence.

    The gap between what’s technically possible and what most organisations understand about their own public exposure is genuinely alarming. Whether you’re a professional investigator, a red team operator, or someone who just wants to understand the digital footprint they’re leaving behind, 2026 is a year where the tools have leapt ahead of the awareness. Worth getting familiar with both sides of that equation.

    Frequently Asked Questions

    What are the best free OSINT tools available in 2026?

    Maltego Community Edition, Spiderfoot (open-source), and Sherlock are among the most widely used free OSINT tools in 2026. Each covers different investigation types: graph-based entity mapping, automated multi-source aggregation, and username enumeration respectively. Most professional investigators combine several tools rather than relying on one.

    Is using OSINT techniques legal in the UK?

    Using publicly available information for research or authorised investigations is generally legal in the UK. However, accessing private systems or downloading raw breach databases without authorisation can breach the Computer Misuse Act 1990. If you’re working commercially as an investigator, ensure your practices align with ICO data handling requirements and any relevant professional licences.

    How do AI tools improve OSINT investigations?

    AI models can process and correlate large volumes of raw OSINT data far faster than a human analyst working manually. They’re particularly useful for entity resolution, summarising open-source findings, and flagging unexpected connections. That said, AI output must always be verified, hallucinated connections are a real risk that can mislead an investigation if not caught.

    What is the difference between OSINT and active reconnaissance?

    OSINT (Open Source Intelligence) involves gathering information from publicly available sources without directly probing or interacting with target systems. Active reconnaissance involves sending packets, queries, or requests to a target, which can trigger alerts and may require explicit authorisation. Ethical hackers typically complete passive OSINT before moving to any active phase.

    How can organisations protect themselves from OSINT exposure?

    Organisations should regularly audit their own public digital footprint using the same tools investigators use. This means checking what employee details appear in breach databases, reviewing publicly indexed documents for metadata, monitoring social media for data leakage, and ensuring domain WHOIS records don’t expose sensitive contact details. The NCSC publishes practical guidance on reducing organisational attack surfaces.

The Latest