Question 1

What is a supply chain attack?

Accepted Answer

A **supply chain attack** compromises an organisation indirectly, by attacking something it **trusts and installs** — a software vendor, a library, an update mechanism or a service provider. Rather than breaking through the defences, the attacker arrives through the front door as an authorised delivery.

**Why it is so effective.** Organisations verify software from trusted vendors far less rigorously than they inspect unsolicited email. Updates are frequently automatic, signed, and installed with high privileges. One successful compromise of a widely used supplier reaches every customer simultaneously — so the attack **scales** in a way direct intrusion cannot.

**The main forms:**

**Compromised software updates.** The **SolarWinds** attack in 2020 is the defining example: attackers inserted a backdoor into the build process of a network management product, and it was distributed through legitimate signed updates to thousands of organisations including government agencies. It went undetected for months precisely because it arrived through a trusted channel.

**Malicious or compromised dependencies.** Modern software is assembled from large numbers of open-source packages, each with its own dependencies. An attacker who compromises a maintainer account, or publishes a package with a name resembling a popular one (**typosquatting**), reaches every project that installs it. Incidents in the npm and PyPI ecosystems occur regularly.

**Compromised build systems**, which insert malicious code between source and release — so reviewing the source code does not reveal it.

**Hardware and firmware** tampering.

**Third-party service compromise**, reaching customers through a managed provider.

**What reduces exposure:**

**Know what you depend on.** A **software bill of materials (SBOM)** lists components so you can identify affected versions quickly, which is the difference between hours and weeks when a vulnerability is disclosed.

**Pin and verify dependencies**, with lockfiles and checksum verification.

**Least privilege**, so a compromised component cannot reach everything.

**Reproducible builds** and signed artefacts.

**Network segmentation and monitoring**, since prevention will sometimes fail.

Question 2

Why do software updates matter for security?

Accepted Answer

Most successful attacks exploit vulnerabilities that were fixed months or years earlier. The window that matters is not between discovery and patch, it is between patch and installation, and that

Question 3

What are the common cybersecurity threats for small businesses?

Accepted Answer

Small businesses face various cybersecurity threats like phishing, ransomware, and malware. Understanding these risks is essential for effective protection.

Question 4

What is a zero-day vulnerability?

Accepted Answer

A zero-day is a security flaw that the vendor does not yet know about, or has known about for zero days — so no patch exists and defenders have had no opportunity to prepare. The related terms are

Question 5

How can I troubleshoot common cybersecurity issues in my organization?

Accepted Answer

Troubleshooting common cybersecurity issues involves identifying problems, checking logs, updating software, conducting scans, training users, and implementing response plans. Each method is crucial for maintaining security.

Question 6

What actually happens during a security incident response?

Accepted Answer

A structured process rather than improvisation — and the organisations that handle incidents well are almost always the ones that decided what to do before anything happened, because the middle of a

Question 7

What is a DDoS attack and how does it work?

Accepted Answer

A DDoS — distributed denial of service — attack overwhelms a service with traffic until it cannot serve legitimate users. The goal is not to steal data or break in; it is simply to make something

Related Questions