<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fidelis Uzoezie on Medium]]></title>
        <description><![CDATA[Stories by Fidelis Uzoezie on Medium]]></description>
        <link>https://medium.com/@uzoeziefc?source=rss-5f8bb71aa5c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3eNLKDDcWQ6NuJrjPw1JyQ.jpeg</url>
            <title>Stories by Fidelis Uzoezie on Medium</title>
            <link>https://medium.com/@uzoeziefc?source=rss-5f8bb71aa5c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:00:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uzoeziefc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NIS2 Is Changing More Than Cybersecurity: The New Rules of Cloud Supply Chain Strategy]]></title>
            <link>https://medium.com/@uzoeziefc/nis2-is-changing-more-than-cybersecurity-the-new-rules-of-cloud-supply-chain-strategy-f5f8aa8b8629?source=rss-5f8bb71aa5c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5f8aa8b8629</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Fidelis Uzoezie]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 01:38:19 GMT</pubDate>
            <atom:updated>2026-10-14T12:10:27.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*2Cb5OZBLSCsqrqMUoTLueg.jpeg" /></figure><p><em>How multinational businesses should rethink cloud suppliers, contractual risk, operational resilience and international competitiveness.</em><br>A company can invest heavily in securing its cloud infrastructure and still face serious cybersecurity risks through the suppliers it depends on.<br>Its cloud provider may rely on subcontractors. Its software platform may integrate third-party services. Its managed service provider may have privileged access to critical systems. And a vulnerability in one part of this ecosystem can create consequences far beyond the organisation where it originates.<br>This is why the European Union’s Network and Information Security Directive 2 (NIS2) matters beyond the cybersecurity department.<br><strong><em>NIS2 makes cybersecurity supply-chain risk a governance, procurement and business-resilience issue—not merely a technical problem.</em></strong><br>For multinational enterprises (MNEs), the challenge is not simply to comply with a regulation. It is to decide how to select suppliers, structure contracts, manage cross-border operations and maintain resilience without unnecessarily restricting innovation or increasing costs.</p><p><strong>1. Why NIS2 changes the conversation</strong></p><p>NIS2, formally Directive (EU) 2022/2555, strengthens cybersecurity risk-management and incident-reporting requirements for entities within its scope.<br>Article 21 addresses cybersecurity risk-management measures, including supply-chain security. Article 20 places responsibility on the management bodies of essential and important entities to approve and oversee cybersecurity risk-management measures.<br>The implications extend into commercial relationships.<br>Consider a multinational organisation that depends on a cloud provider for customer data, a software-as-a-service platform for business operations and a managed service provider for infrastructure support.<br>Even if these suppliers are not all directly subject to NIS2, the organisation may need to assess their security practices, understand their dependencies and ensure that the arrangements supporting critical services are sufficiently resilient.<br>That can influence supplier selection, procurement standards, contractual negotiations and decisions about where workloads are hosted.<br>There is an important distinction, however: <strong>NIS2 does not automatically bring every supplier within its direct regulatory scope, nor does it require organisations to terminate every supplier that fails a security assessment. </strong>The applicable duties depend on the entity, service, jurisdiction and relevant implementing rules.<br>The practical lesson is that supplier risk must be understood and managed—not simply transferred through a contract.</p><p><strong>2</strong>. <strong>The cloud supply chain is a business dependency</strong></p><p>Cloud services can make international expansion faster and more cost-effective. Organisations can enter new markets, deploy digital services and scale infrastructure without building every capability themselves.<br>But this convenience creates dependencies.<br>A business may rely on a cloud provider for computing, another company for identity management, a third party for security monitoring and several software vendors for daily operations. Each dependency introduces questions about availability, security, incident communication and recovery.<br>Three areas deserve particular attention.<br><strong>Supplier visibility</strong>. Does the organisation understand which providers support its critical services, what access they have and which subcontractors they depend on?<br><strong>Shared responsibility</strong>. Does the organisation know which security controls belong to the cloud provider and which remain its own responsibility? Using a secure cloud platform does not remove the customer’s responsibility for matters such as identity configuration, access governance and workload security.<br><strong>Operational resilience.</strong> If a critical supplier experiences a major outage or security incident, can the organisation continue operating, recover its services and meet its obligations?<br>These questions connect cybersecurity directly to business continuity, customer trust and the ability to operate across borders.</p><p><strong>3. Incident reporting requires more than a technical response</strong></p><p>NIS2’s Article 23 establishes a staged reporting process for significant incidents affecting entities within scope.<br>Under the Directive, the process generally includes:</p><p><strong>Within 24 hours</strong>: an early warning after becoming aware of a significant incident.</p><p><strong>Within 72 hours</strong>: an incident notification, with an initial assessment of the incident’s severity and impact.</p><p><strong>Within one month</strong>: a final report, subject to the Directive’s conditions and the incident-reporting process.</p><p>Additional reporting may apply where an incident is ongoing.<br>These timelines create an operational challenge for organisations with fragmented cloud environments, multiple service providers and teams operating in different countries.<br>A supplier may detect an incident before its customer understands the business impact. The customer may then need to establish which systems are affected, whether critical services are disrupted and which reporting obligations apply.<br>A contractual requirement to notify the customer quickly is useful, but it does not by itself guarantee that the customer can meet a regulatory deadline.<br>Organisations should therefore align supplier incident-notification procedures with their own incident-response and regulatory-reporting processes.<br>That means defining escalation contacts, specifying the information suppliers must provide, agreeing how evidence will be preserved and testing the process before a major incident occurs.</p><p><strong>4. From annual questionnaires to risk-based supplier governance</strong></p><p>Traditional supplier assessments often depend on questionnaires, certificates and periodic reviews. These remain useful, but they provide only a partial picture of a supplier’s current risk.<br>A more effective approach combines documentary assurance with operational evidence.<br>For critical cloud and ICT suppliers, organisations should consider:</p><p><strong>Classifying suppliers by business criticality</strong>. A provider supporting a core customer-facing service may warrant more intensive oversight than a supplier whose failure would have limited operational impact.</p><p><strong>Assessing concentration and dependency</strong> <strong>risk</strong>. Determine whether several critical services rely on the same provider, region, identity platform or underlying technology.</p><p><strong>Reviewing assurance evidence.</strong> Consider relevant security certifications, independent assessments, incident history, vulnerability-management practices and control evidence. No single certificate proves that a supplier is secure in every respect.</p><p><strong>Strengthening contractual provisions.</strong> Address incident notification, cooperation, audit or assurance rights, subcontracting, business continuity, data handling and termination or transition assistance where appropriate.</p><p><strong>Monitoring material changes.</strong> Reassess risk when a supplier changes its ownership, service architecture, subcontractors, hosting arrangements or security posture.</p><p><strong>Testing recovery and exit options.</strong> Understand whether critical workloads and data can be migrated, restored or operated through an alternative arrangement within an acceptable timeframe.</p><p>The objective is not to subject every supplier to the same level of scrutiny. It is to direct attention and resources towards the dependencies that could cause the greatest harm.</p><p><strong>5. The international strategy question: one global standard or local adaptation?</strong></p><p>Multinational businesses face a strategic choice.<br>Should they apply one consistent cybersecurity baseline across all operations, or design separate controls for each jurisdiction?<br>A single global baseline can simplify governance, reduce duplication and make supplier expectations easier to communicate. It may also help a company demonstrate consistent security practices to customers and business partners.<br>However, a blanket approach can create unnecessary costs or overlook differences in national legislation, sector-specific obligations and local operating conditions.<br><strong>A more practical model combines global consistency with local legal mapping</strong>.<br>The organisation establishes a common baseline for supplier governance, identity security, incident response, resilience testing and risk reporting. It then identifies additional requirements that apply to particular entities, services or jurisdictions.<br>This approach can help management balance several competing priorities:</p><p>Regulatory compliance and market access.</p><p>Cybersecurity and operational resilience.</p><p>Supplier diversity and concentration risk.</p><p>Cost efficiency and contractual flexibility.</p><p>Innovation speed and risk management.</p><p>The strategic advantage does not come from applying the strictest imaginable controls everywhere. It comes from understanding which controls are necessary, where they apply and how they support the organisation’s commercial objectives.</p><p><strong>6. A practical implementation roadmap</strong></p><p>For organisations reviewing their NIS2-related cloud supply-chain arrangements, a phased approach can help turn regulatory expectations into operational decisions.<br><strong>Phase 1: Establish applicability.</strong><br>Identify the relevant legal entities, services, sectors and jurisdictions. Confirm whether each entity falls within NIS2’s scope and identify applicable national implementing legislation and sector-specific requirements.<br><strong>Phase 2: Map critical dependencies.</strong><br>Document the cloud services, ICT suppliers and subcontractors that support important business services. Record criticality, privileged access, geographic dependencies and potential concentration risks.<br><strong>Phase 3: Prioritise supplier risk.</strong><br>Assess critical suppliers using proportionate criteria covering security, resilience, incident cooperation, assurance evidence and exit feasibility. Document material gaps and decisions about residual risk.<br><strong>Phase 4: Align contracts and operating procedures.</strong><br>Work with procurement, legal, security and business teams to address incident notification, supplier cooperation, subcontracting, assurance, continuity and transition arrangements.<br><strong>Phase 5: Test the model.</strong><br>Run incident-response exercises, review recovery capabilities and test whether the organisation can obtain the information needed to make timely decisions during a supplier incident.<br><strong>Phase 6: Report meaningful outcomes.</strong><br>Give management a concise view of critical supplier coverage, unresolved high-risk findings, incident-escalation readiness, concentration risks and recovery-test results.<br>Useful indicators might include the percentage of critical suppliers assessed, the age of unresolved high-risk findings, the proportion of critical services with tested recovery arrangements and the time required to escalate a supplier incident.<br>The measures should support decisions—not become a reporting exercise for its own sake.</p><p><strong>7. What this means for competitive advantage</strong></p><p>Compliance is often treated as a cost of doing business. But supplier governance can also improve the quality of strategic decisions.<br>An organisation that understands its cloud dependencies may be better positioned to negotiate meaningful contractual protections, plan market entry, assess acquisition risks and avoid excessive reliance on a single technology provider.<br>Stronger incident coordination can reduce confusion during disruptions. Tested recovery arrangements can improve confidence in business continuity. Clear supplier-selection criteria can help prevent commercial decisions from creating unmanaged technical risk.<br>These benefits are not automatic. They depend on whether governance practices lead to better operational decisions rather than simply producing more documentation.<br>For multinational enterprises, cybersecurity and international strategy are increasingly connected. The ability to operate reliably across jurisdictions depends partly on the organisation’s ability to understand and govern the technology ecosystem on which it relies.</p><p><strong>Planning Your NIS2 and Cloud Supply-Chain Strategy?<br></strong>If your organisation is reviewing NIS2 readiness, cloud security governance or critical supplier risk, let’s discuss your priorities and identify practical next steps<strong>.</strong><br>I welcome conversations with business leaders, CISOs, CIOs, cloud teams and organisations seeking to strengthen their cybersecurity governance and supplier-risk management.<br>I can support advisory discussions around:</p><p><strong>NIS2 readiness and gap identification</strong>: Understanding potential applicability, identifying areas that require further assessment and prioritising next steps.</p><p><strong>Cloud security and governance:</strong></p><p>Reviewing cloud security responsibilities, identity and access controls, logging, monitoring and resilience considerations.</p><p><strong>Third-party and cloud supply-chain risk:</strong> Developing supplier assessment criteria, risk registers, security requirements and governance processes.</p><p><strong>Incident-response readiness:</strong> Reviewing escalation workflows, supplier notification arrangements and coordination procedures.</p><p><strong>Cybersecurity strategy:</strong> Connecting security priorities with operational resilience, business objectives and international growth plans.</p><p>My approach is practical and risk-based: helping organisations move from regulatory awareness to clearer priorities, stronger governance and actionable security improvements.</p><p><em>For advisory enquiries, professional collaboration, or a discussion about your organisation’s cloud security and NIS2-related priorities, connect with me on </em><a href="/service/scheme:/www.linkedin.com/in/fidelis-uzoezie"><em>LinkedIn</em></a><em> or send me a direct message.</em></p><p><strong>Conclusion: Treat supplier security as a strategic capability</strong></p><p>NIS2 should not be interpreted as a blanket instruction to replace suppliers, standardise every global workload or purchase more security tools.<br>Its practical significance is more nuanced.<br>For entities within scope, the Directive strengthens expectations around cybersecurity risk management, supply-chain security, management oversight and significant-incident reporting. Those expectations can also influence commercial relationships with suppliers that are not directly regulated.<br>The response should be proportionate and evidence-led: establish applicability, map critical dependencies, assess supplier risk, improve contractual and incident-response arrangements, test resilience and communicate material risks to management.<br><strong>The organisations best positioned to respond will be those that treat cloud supply-chain security as part of how they design, govern and grow the business—not as an isolated compliance task.</strong></p><p><strong>References and further reading</strong></p><p><strong><em>European Parliament and Council.</em></strong><em> Directive (EU) 2022/2555 (NIS2 Directive).<br>https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng</em></p><p><strong><em>European Commission</em></strong><em>. Commission Implementing Regulation (EU) 2024/2690. This regulation sets technical and methodological cybersecurity risk-management requirements for specified entities.<br>https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj/eng</em></p><p><strong><em>European Union Agency for Cybersecurity (ENISA).</em></strong><em> NIS2 Technical Implementation Guidance (2025).<br>https://www.enisa.europa.eu/publications/nis2-technical-implementation-guidance</em></p><p><em>Disclaimer: This article provides general information and strategic analysis, not legal advice or a company-specific compliance assessment. NIS2 obligations depend on the relevant entity, jurisdiction, national implementing legislation and applicable sector-specific rules. Organisations should consult qualified legal and cybersecurity professionals when assessing their obligations.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5f8aa8b8629" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>