---
title: "Security Supplier Continuity: What If Service Stops?"
description: "Sanctions, export controls or a market exit can cut off a security product's updates and support. How to test supplier continuity and plan a workable exit."
url: https://panop.io/blog/security-supplier-continuity-exit/
---

Article November 18, 2026 [Panop Research](https://panop.io/company) · Security research team, Panop SA

# Security Supplier Continuity: What If Service Stops?

Sanctions, export controls or a market exit can cut off a security product's updates and support. How to test supplier continuity and plan a workable exit.

On this page

1. [The update service matters as much as the installed software](#the-update-service-matters-as-much-as-the-installed-software)
2. [Different restrictions, similar operational questions](#different-restrictions-similar-operational-questions)
3. [Look beyond the supplier’s headquarters](#look-beyond-the-suppliers-headquarters)
4. [Ask what stops working first](#ask-what-stops-working-first)
5. [Make continuity part of procurement](#make-continuity-part-of-procurement)
6. [Test the plan before the notice arrives](#test-the-plan-before-the-notice-arrives)
7. [Review one critical security dependency](#review-one-critical-security-dependency)
8. [Where Panop fits](#where-panop-fits)
9. [Sources](#sources)

A security product can work well and still become unavailable to the organization that relies on it. The sovereignty question is whether protection, updates and support will still be there when legal, political or commercial conditions change. Where the data sits is only one part of that decision.

## The update service matters as much as the installed software

In 2024 a regulatory decision changed the position for organizations using Kaspersky in the United States. The US Bureau of Industry and Security [prohibited Kaspersky from specified transactions](https://media.bis.gov/kaspersky) in the United States or with US persons. From September 29, 2024, the prohibited transactions included antivirus signature and codebase updates and operation of the Kaspersky Security Network in the United States. Reselling Kaspersky software and integrating it into other products and services were also covered.

That makes the continuity question concrete. Having software installed is one thing. Being able to keep it updated, supported and useful is another, and an organization assessing a security product needs to understand both.

The decision concerned one supplier and one US national-security determination. It doesn’t establish that every product from a particular country is unsafe. What it shows is why procurement has to consider whether a supplier can keep serving the business in every place the business operates.

## Different restrictions, similar operational questions

Sanctions, export controls, national-security restrictions and a supplier’s commercial decision to leave a market can all affect continuity. They work through different mechanisms, and each one has its own scope. BIS stated that the Kaspersky determination did not apply to Kaspersky’s threat intelligence products and services or to services that are purely informational or educational in nature. Read any restriction on its own terms.

The US Treasury’s Office of Foreign Assets Control [explains its June 12, 2024 determination](https://ofac.treasury.gov/faqs/1184) on IT and software services. It prohibits US persons, and anyone acting from the United States, from supplying IT consultancy and design services, and IT support and cloud-based services for certain enterprise management and design and manufacturing software, to persons located in Russia. It comes with exclusions and related general licenses, and OFAC says its aim is not to prohibit all IT and software-related services to Russia. Export authorization has its own conditions as well: for encryption products, BIS notes that the [authorizations under license exception ENC](https://www.bis.gov/learn-support/encryption-controls?id=1159) vary with the item, the end user, the end use and the destination.

Legal specialists have to establish which restrictions apply. Security, procurement and operations then work through the consequences: what might stop, how much notice there would be and how the organization would keep protecting itself.

Hosting data locally doesn’t answer those questions by itself. The contracting entity, the operating company, the support team and upstream suppliers can each create a dependency that a data-residency commitment leaves untouched. Our article on [digital sovereignty for security teams](https://panop.io/blog/digital-sovereignty-for-security-teams) treats residency, jurisdiction and exit as separate controls for the same reason.

## Look beyond the supplier’s headquarters

A national flag on a website says very little about how a service would survive disruption. A locally incorporated provider may depend on overseas hosting, software licensing, threat intelligence or specialist support. A global provider may have sound continuity arrangements. Both need evidence.

NIST’s July 2026 [due diligence quick-start guide](https://csrc.nist.gov/pubs/sp/1326/final) lists foreign ownership, control or influence as one assessment component, next to provenance, resilience, foundational cyber practices and supply-chain tiers. That is a useful frame for the discussion. Nationality becomes one input, and the assessment looks at the actual dependency.

For each critical security service, trace who contracts with you, who operates it, who can administer it and which other services it needs. Include managed security providers, penetration testing firms and incident response partners. A local agency may rely on another company’s platform, analysts or infrastructure. Ask about subprocessors as well as the provider named on the contract.

If the organization relies on a government cyber agency for an operational service or a privileged information-sharing arrangement, clarify eligibility and scope there too. Public guidance, an alert feed and guaranteed incident support are different things. Write down what is actually available instead of assuming that a relationship provides continuity.

## Ask what stops working first

The most useful review starts with a business service and works backward. Take customer payments. Which security products let staff administer the service, detect suspicious activity, investigate incidents and recover safely? Then ask what happens if a critical supplier becomes unavailable.

Treat the answers as scenarios to test. They say nothing about how any particular provider will behave. An endpoint product might keep running while it stops receiving new detections. A cloud-managed control might keep its last policy and refuse changes. Threat intelligence or incident support might stop before the underlying technology does. The outcome depends on the product and the contract.

Pay particular attention to identity, privileged access and recovery. An alternative platform is of little use if the team can’t authenticate, retrieve configuration or reach the credentials needed to restore service. Emergency access has to be controlled, documented and exercised.

Concentration deserves a closer look as well. Two providers give little real independence if both depend on the same licensing service, cloud platform or subcontractor. Adding suppliers also brings integration and running costs, so any diversification should address a failure route you have identified.

## Make continuity part of procurement

A supplier questionnaire earns its place when the answers can change a decision. For critical cybersecurity products and agencies, put the questions below next to capability, price and implementation effort. Where the consequence of failure is significant, ask for documentation or a demonstration.

- Which entities and jurisdictions deliver the service, and what restrictions or suspension rights could affect our locations and users?
- Which hosting, licensing, identity, intelligence and subcontracted services does the service need, and how are material changes communicated?
- What keeps working without the supplier’s cloud, license checks or update service, for how long, and with what loss of protection?
- Can we retrieve logs, findings, policies and configurations in usable formats, and how do we keep authorized administrative access during a transition?
- What assistance, notice, cost and deletion commitments apply on exit, including when an urgent legal restriction limits what the supplier can do?
- Which alternative has been evaluated, what would have to be rebuilt, and who owns the time, budget and risk of the transition?

The exit question carries the most weight. The scorecard in [digital sovereignty for security teams](https://panop.io/blog/digital-sovereignty-for-security-teams) asks for findings, evidence and the asset graph to be exportable in a usable form and tested once before signature, and the Panop Research paper [Digital Sovereignty: Why, What, How](https://panop.io/blog/digital-sovereignty-why-what-how) makes the same case for keeping a tested migration path.

## Test the plan before the notice arrives

Start with the few dependencies whose loss would materially weaken protection or interrupt a critical business service. Agree how much degradation is acceptable and for how long. That gives the team something concrete to test.

Run a tabletop exercise in which one supplier becomes unavailable. In an authorized test environment, check that exported records are readable, that configurations can be rebuilt and that emergency access works. Measure the effort needed to bring an alternative into service. A contractual right to export data helps. A successful restoration is stronger evidence.

Give someone the job of watching relevant restrictions, supplier notices, ownership changes and material subcontractor changes. Review the plan when the organization enters a new market or widens a provider’s role. Security, procurement, legal and operations each hold part of the answer.

The aim is a proportionate decision. Keep the supplier with a tested fallback, reduce a specific dependency, negotiate stronger terms or replace it. A geographic preference can inform that choice, and it can’t make it for you.

## Review one critical security dependency

Choose one product or security agency whose loss would materially weaken protection. Record the business service, the internal owner and the review date. Use the evidence column to show what you have checked; a reassuring answer on its own doesn’t complete the review.

| Check | Evidence to bring | Decision to record |
| --- | --- | --- |
| Ability to keep supplying | Contracting and operating entities, relevant locations, suspension terms and legal assessment | Which restrictions or withdrawal decisions could affect our service? |
| Protection after disconnection | Documented behavior and a controlled test covering updates, licenses, policy changes and support | What degradation can we accept, and for how long? |
| Dependencies behind the provider | Hosting, identity, intelligence and subcontractor dependencies, including any shared with alternatives | Which common failure needs a fallback? |
| Access and usable records | An authorized export and restore test for findings, logs, policies and configuration | Who can preserve access and evidence during a transition? |
| A workable replacement | Evaluated alternative, migration effort, notice terms, cost and a named transition owner | Retain, reduce the dependency, renegotiate or replace, with the next action and date |

Finish with the most consequential untested assumption. Make someone responsible for testing it, and agree which change would reopen the decision. Revisit legal applicability whenever circumstances change.

## Where Panop fits

Panop SA is a Swiss company. Our [October 14, 2026 announcement with Exoscale](https://panop.io/newsroom/panop-exoscale-sovereign-exposure-management/) describes the Panop platform running on Exoscale’s European infrastructure, with the data location chosen by the customer, and the [security and compliance page](https://panop.io/security-compliance) states that customer exposure data is hosted in Switzerland. The [sub-processor list](https://panop.io/sub-processors) names each provider that processes customer data and where it is located, and separately lists the corporate service providers, some of them US-based, that are not engaged to process customer data.

That is a deployment option to assess within the wider review. It leaves the questions of ownership, operating dependencies, support, portability and continuity open, and they apply to Panop as much as to any other security supplier. Swiss or European positioning is where the diligence starts, and the same geopolitical questions apply to it.

## Sources

1. Bureau of Industry and Security: [Kaspersky Lab, Inc. Prohibition](https://media.bis.gov/kaspersky)
2. US Department of the Treasury, Office of Foreign Assets Control: [FAQ 1184: What action did Treasury take on June 12, 2024 with regards to prohibiting certain information technology (IT) and software-related services?](https://ofac.treasury.gov/faqs/1184), June 12, 2024
3. Bureau of Industry and Security: [Encryption controls](https://www.bis.gov/learn-support/encryption-controls?id=1159)
4. NIST: [SP 1326, NIST Cybersecurity Supply Chain Risk Management: Due Diligence Assessment Quick-Start Guide](https://csrc.nist.gov/pubs/sp/1326/final), July 2026
5. Panop: [Panop and Exoscale Partner to Bring Sovereign Exposure Management to European Enterprises](https://panop.io/newsroom/panop-exoscale-sovereign-exposure-management/), October 14, 2026

About the author

[Panop Research](https://panop.io/company)

Security research team, Panop SA

Panop Research is the security research function of Panop SA, a Swiss exposure management company founded in July 2024 by three practitioners with nearly twenty years each inside large international organisations. It publishes analysis built on primary public datasets, with every figure attributed and linked to the publisher that produced it.

- [LinkedIn](https://www.linkedin.com/company/panop-io)

[← Back to blog](https://panop.io/blog/)
