Guerassim Nikolov on Supply Chain Security in 2026

The World Economic Forum’s Global Cybersecurity Outlook 2026 identifies supply chain disruption as the second-highest concern for CISOs globally – a position it has held for two consecutive years.

The same report documents that 65% of large organizations now identify third-party and supply chain vulnerabilities as their greatest challenge to cyber resilience, up from 54% the year prior.

Yet fewer than one-third of organizations comprehensively map their supply chain ecosystems, and only 27% regularly simulate incidents with supply chain partners.

The gap between concern and action is understandable, if dangerous. Modern enterprise software supply chains involve hundreds of vendors, open-source components, cloud services, and managed providers each a potential point of entry.

Organizations cannot directly audit the security practices of most of these dependencies. They inherit their vendors’ risk whether they choose to or not.

“Supply chain risk is inherited risk,” says Guerassim Nikolov, entrepreneur and enterprise security advisor with more than twenty years in cybersecurity strategy.

“You don’t choose to accept your vendor’s security posture you inherit it the moment you integrate their software. Most organizations understand this in theory but haven’t built the continuous assessment processes that the threat actually demands.”

The SolarWinds compromise, disclosed in December 2020, remains the defining illustration of what this inherited risk looks like at scale.

Russian intelligence actors infiltrated SolarWinds’ software build pipeline and embedded malicious code into routine Orion platform updates.

According to the US Government Accountability Office, approximately 18,000 customers installed the compromised update including the US Departments of Treasury, State, Commerce, and Homeland Security.

CISA’s emergency directive issued in response was among the most significant government cybersecurity interventions in US history.

The attack succeeded not by breaking through perimeter defenses, but by riding through them on software that customers trusted completely.

More recently, the XZ Utils backdoor discovered in March 2024 demonstrated that supply chain attacks can be extraordinarily patient.

An entity operating under the name ‘Jia Tan’ spent approximately three years from late 2021 through early 2024 contributing legitimate code to the open-source XZ Utils compression library, building credibility and eventually achieving co-maintainer status.

Once trusted, the attacker introduced a sophisticated backdoor capable of providing remote code execution on any Linux system running the affected library.

The attack was discovered accidentally by a Microsoft engineer who noticed a 500-millisecond SSH latency anomaly. Had he not investigated, the backdoor would have shipped to hundreds of millions of systems worldwide.

Nikolov points to the XZ Utils case as a particular wake-up call for security leadership. “Three years of patient social engineering, building legitimate credibility in an open-source project before introducing a backdoor. That’s not the threat model most enterprises are planning against but it should be. The attack surface for modern software supply chains extends well beyond your direct vendor relationships.”

Both cases point to the same structural problem: organizations routinely trust software and services they have no direct visibility into.

The US government’s response to SolarWinds requiring Software Bills of Materials (SBOMs) for federal software procurement through Executive Order 14028 in May 2021 provides a practical model.

SBOMs create a complete inventory of every component inside a software product, enabling rapid identification of affected systems when any component is compromised.

For enterprise security teams, the practical steps are: requiring continuous security assessments rather than point-in-time audits for critical vendors; mandating SBOM disclosure for custom-built software; implementing zero-trust architecture for all third-party integrations so that vendor access is segmented, time-limited, and monitored; and conducting regular tabletop exercises that simulate vendor compromise scenarios.