Skip to content

Chapter 11: Insider Threats and Supply-Chain Attacks

Not every attack comes from a stranger outside. Some of the most damaging breaches start with an employee, a contractor or a trusted software supplier. This chapter covers three kinds of insider threat (malicious, negligent and compromised) and four kinds of supply-chain attack (software, hardware, open source and third-party). Both families are hard to detect because everything looks authorised.

Layman analogy

Insider threat: hiring a contractor to renovate your house, only to discover they've made copies of all your keys, photographed your valuables, and sold the information to a third party.

Layman analogy

Supply chain attack: trusting a reputable pharmacy to fill your prescription accurately, not realising a compromised employee at the pharmaceutical manufacturer has already adulterated the medication at the source — you trust the brand implicitly and never question it.

11.1 Malicious Insider

An employee, contractor, or partner who intentionally steals data, sabotages systems, leaks sensitive information, or aids external attackers. Often motivated by financial gain, ideology, competitor offers, or resentment (particularly when leaving the organisation).

Example 11.1: Malicious Insider

Edward Snowden (2013): NSA contractor who copied 1.7 million classified US intelligence documents and leaked them to journalists, exposing mass surveillance programmes operated by the NSA and allied agencies. Regardless of the moral debate, this is the textbook definition of a malicious insider with catastrophic, global consequences.

11.2 Negligent Insider

No malicious intent — but careless, uninformed, or hasty actions cause significant data breaches. This includes falling for phishing attacks, misconfiguring cloud storage, using weak passwords, or accidentally emailing sensitive data to the wrong recipient.

Example 11.2: Negligent Insider

2021: A UK university employee accidentally emailed a spreadsheet containing the personal details of 300 students (names, addresses, health information) to the entire student body — a simple but devastating "fat-finger" email error.

11.3 Compromised Insider

A legitimate employee's credentials are stolen by an external attacker, who then uses them to blend in as a trusted insider. This is particularly dangerous because all activity appears to come from a known, trusted employee.

Example 11.3: Compromised Insider

SolarWinds (2020): Attackers used stolen, valid administrator credentials to move through victim networks, appearing to all security monitoring systems as legitimate, authorised administrators conducting routine work.

Detection challenge: All three insider threat types appear as legitimate, authorised users in system logs. Insider threats are among the most difficult attacks to detect and are often discovered months or years after the fact.

11.4 Software Supply Chain Attack

Compromise the software vendor's systems or build process to insert malware into an otherwise legitimate software product. The malware is then distributed to all customers through trusted, digitally signed software updates.

Why it's devastating: Victims voluntarily install the malware themselves. The software is from a trusted, reputable vendor. It is digitally signed. It passes all security scans. There is no suspicious link to click.

Example 11.4: Software Supply Chain Attack

SolarWinds Orion (2020): Attackers attributed to Russian SVR intelligence compromised SolarWinds' build system and inserted the "SUNBURST" backdoor into updates for the Orion IT monitoring platform. 18,000 organisations — including the US Treasury, State Department, Department of Energy, Microsoft, and FireEye — installed the backdoored update. Attackers maintained undetected access for 9 months.

11.5 Hardware Implants

Malicious chips or firmware inserted into hardware components during manufacturing or at some point in the supply chain. Survives complete software reinstallation. Extremely difficult to detect without specialised hardware analysis.

Example 11.5: Hardware Implants

Bloomberg Businessweek (2018) reported that Chinese spy chips were allegedly implanted in Supermicro server motherboards during manufacturing, found in servers used by Apple, Amazon Web Services, and multiple US government contractors. (The companies named disputed the report, but the incident sparked major government review of hardware supply chains.)

11.6 Open Source Poisoning

Inject malicious code into widely used open-source libraries or packages that thousands of other software projects depend on as building blocks.

Example 11.6: Open Source Poisoning

event-stream npm package (2018): A bad actor gained maintainership of this popular JavaScript package (fetched about 2 million times per week). They added a malicious dependency containing code specifically designed to steal Bitcoin wallet credentials from the Copay cryptocurrency app. The malicious code was distributed for weeks before discovery.

11.7 Third-Party Breach (Vendor Pivot)

Attack a smaller, less secure vendor that has legitimate network access to a larger, better-defended target organisation. Use the vendor's credentials and access as a pivot point to reach the primary target.

Example 11.7: Third-Party Breach (Vendor Pivot)

Target Data Breach (2013): Attackers compromised Fazio Mechanical Services — Target's HVAC (heating/ventilation/air conditioning) maintenance vendor. Using Fazio's remote monitoring credentials, attackers pivoted through the vendor access to Target's payment network and installed card-skimming malware on point-of-sale terminals. 40 million credit and debit card numbers were stolen. The breach was traced to an HVAC contractor.

11.8 Defence tips

  • Apply least privilege rigorously — employees should only have access to what they specifically need for their role
  • Deploy User and Entity Behaviour Analytics (UEBA) to detect anomalous access patterns
  • Audit and tightly restrict all third-party vendor access — monitor it continuously
  • Require vendors to provide software integrity checksums; verify them before deploying updates
  • Maintain a Software Bill of Materials (SBOM) listing all software dependencies and their versions
  • Revoke ALL employee access immediately on their last day of employment — not the following week
  • Conduct thorough background checks for roles with privileged access
  • Implement Data Loss Prevention (DLP) tools to detect and alert on unusual data exfiltration

11.9 Summary

  • Insiders are malicious, negligent or compromised; all three look like authorised users in logs.
  • Supply-chain attacks target software vendors, hardware, open-source dependencies and third-party vendors, so victims install the attack themselves.
  • SolarWinds (2020) reached 18,000 organisations through a signed update; Target (2013) was breached through an HVAC contractor.
  • Defences: least privilege, behaviour analytics, vendor access control, checksums, SBOMs, prompt de-provisioning and data loss prevention.

11.10 Exercises

  1. Classify each as malicious, negligent or compromised insider: (a) an engineer copies the customer database before resigning to join a competitor, (b) an employee emails a spreadsheet of 300 students to the wrong list, (c) an attacker logs in to the VPN with a stolen administrator password.

    Answer

    (a) Malicious. (b) Negligent. (c) Compromised.

  2. Why are insider threats among the hardest attacks to detect?

    Answer

    All three types appear in logs as legitimate, authorised users doing things they are permitted to do, so the usual indicators of an outsider are missing. They are often found months or years later.

  3. Why did the SolarWinds backdoor pass the victims' security checks?

    Answer

    The malicious code was inserted into the vendor's own build process, so the update came from a trusted vendor, was digitally signed and passed all scans. There was no suspicious link to click, and victims installed the update themselves.

  4. What is a Software Bill of Materials and why does it help?

    Answer

    An SBOM lists every component and dependency of a piece of software with its version. When a vulnerable or poisoned library is discovered (as with event-stream), an organisation can immediately tell which of its products contain it.

  5. What lessons does the Target breach teach about third-party access?

    Answer

    A small vendor with network access (an HVAC contractor) was used as a pivot point to reach the payment systems. Vendor access should be limited to the minimum, segmented from sensitive systems and monitored continuously.