Privilege Is the New Supply Chain: What the Acronis Ban Tells Every Leader Handing AI Agents the Keys

On Thursday, October 30th, a five-page notice appeared in the Federal Register. Most notices there are routine, but this one wasn't. The Department of Homeland Security told every federal civilian agency in the United States to stop buying products from Acronis, the Swiss cybersecurity and backup company, and to tear out what they already have.

On the surface, this is a procurement story about one vendor and a few federal agencies. If you don't sell to the government, you might be tempted to stop listening right here.

Please don't. Buried in that notice is a single sentence that every CIO, CISO and AI program lead should tape to the wall, because it describes the risk profile of the AI agents most of you are about to deploy.

Why This Is Bigger Than Acronis

So let's start with the facts, and then let's zoom out.

According to the Federal Register notice, Docket DHS-2026-0694, the Secretary of Homeland Security ordered two things under the Federal Acquisition Supply Chain Security Act of 2018. That's FASCSA, the law that lets the government ban a technology vendor across agencies when an interagency council decides it's a supply-chain risk. First, exclusion: no Acronis products in civilian procurements. Second, removal: get Acronis products out of civilian agency IT systems.

The order itself is Exclusion and Removal Order number 2026-02. It's a government document, so I'll read the key part in full. Here is the entire "Summary of Risks":

"Acronis, AG (hereinafter Acronis), a foreign, privately-owned company with U.S. subsidiaries, provides data protection, data backup, secure file sharing, and disaster recovery solutions (on premises and via the cloud). Acronis's cyber and backup tools have privileged or root access to customer security systems and present significant risk to the U.S. government information systems."

That's all it says. Two sentences.

The first sentence describes the business. The second gives the reason, and the reason isn't espionage, a breach or a backdoor. The reason is access. As Justin Doubleday at Federal News Network explained, "root access" is the administrative privilege that grants virtually unlimited access to every program, file and resource on a system.

Read it literally and it's an indictment of one vendor. Read it strategically and it's a statement of principle: the more a piece of software can do to your environment, the more its supply chain becomes your supply chain.

Now zoom out further. This isn't a new idea. Riotta at BankInfoSecurity pointed out that DHS made almost the same argument in 2017 when it ordered agencies to remove Kaspersky, saying that software provided "broad access to files and elevated privileges." Congress wrote that ban into law months later. And per Riotta, Lawfare noted that Congress wrote the 2018 FASCSA law with vendors like Kaspersky and Huawei in mind.

So the lineage is clear. Nearly a decade ago the worry was antivirus. Last year it was backup and recovery, when the Director of National Intelligence issued the first-ever FASCSA order against this same company. This week it's civilian agencies broadly. And the week before, DHS released a separate order banning DeepSeek, a Chinese AI company, from federal networks.

Antivirus, backup, AI. The common thread isn't geography. It's privilege. Nearly every enterprise is about to hand that privilege to a new class of software, which is autonomous AI agents.

So here's the plan for today. First, the problems this order exposes. Then, the examples: what leaders should do differently.

Part 1: The Problem Set

Problem #1: The Root Access Paradox.

The tools you trust to protect you are, by design, the tools with the most power over you. Backup software has to read everything to back it up. It has to be able to write everything to restore it. Endpoint security has to sit beneath the operating system to catch what's moving through it.

That's not a flaw. It's the job description. But it means the risk isn't really what the tool does today. It's what the tool could do if the vendor, an acquirer, an insider or a foreign government ever decided to use that access differently.

Contrast that with a typical SaaS app, which sees only the data you put into it. Your protection stack sees all of it. Same procurement process, very different blast radius.

Problem #2: The Opacity Problem.

Let me steelman the government first. Supply-chain intelligence is often classified, and publishing the evidence can burn sources and methods. That's a real constraint.

But look at what that leaves everyone else with. Mayer Brown's analysis of the 2025 intelligence community order noted it offered no findings or rationale, which the firm said may reflect the classified nature of the evidence. Doubleday reported the IC order gave no detail at all on the underlying concerns. This new DHS order adds exactly two sentences.

So if you're a private-sector leader running Acronis today, you can't do your own risk analysis on the government's evidence. You just have a signal. A strong one, since three federal domains have now acted, but still only a signal.

And to be fair to the company, Acronis's spokesperson told Federal News Network the order "does not affect our customers and partners." Within its legal scope, that's accurate. Whether it's the right way to think about your risk is a separate question.

Problem #3: The Inheritance Problem.

Here's the line from Doubleday's reporting that should worry you most. According to USASpending.gov, Acronis hasn't been awarded a federal contract since fiscal 2016. Yet its products are sold through a network of resellers and partners, which makes it hard to know how widely they're used by agencies, contractors and subcontractors. Riotta adds that the company sells largely through managed service providers.

So the government's question is your question too. Do you know what software your MSP installed on your endpoints? Do you know what backup agent your outsourced IT provider runs on your servers?

The DHS order addresses this directly. A footnote says it applies to all federal information systems, including systems operated by a contractor on an agency's behalf. Inherited software is still your software.

Problem #4: The Clock Problem.

Look at the timeline. The order's original release date is July 31, 2026. The public notice came out October 30th, 91 days later.

The order gave agencies 60 days from issuance to request an exception. By my math, that window closed September 29th, a full month before the public saw the order. Removal is due 180 calendar days from issuance, which lands on January 27, 2027. As of today, that's 85 days away.

This happened before, too. Wilson Sonsini reported that the intelligence community order took effect July 11, 2025, but wasn't published until September 15th.

So the lesson for any organization is that by the time a supply-chain ban becomes public, the people inside the system have often been working on it for months. If you learn about it from the news, you're already behind.

Problem #5: The Agent Problem.

This is the one I most want you to sit with.

Go to Acronis's homepage today and the headline pitches an AI-native cyber platform, one platform to protect, manage and automate IT with AI agents. It describes a journey toward autonomous IT. Agents isolate and contain threats. Agents test and roll out patches. Agents restore from a clean point.

Now, to be clear, the order doesn't mention AI. I'm not claiming the ban has anything to do with Acronis's agents. But think about the trajectory. Yesterday's privileged software held root access and waited for a human to click a button. Tomorrow's privileged software holds root access and decides when to click the button itself.

The risk DHS described in those two sentences gets more acute, not less, once you add autonomy. That's true of every vendor, not just Acronis.

So watch for the common patterns across those five problems. Each one is a gap between how much access a tool has and how much visibility you have into it. That's the gap a leader can actually close. So let's look at what closing it looks like.

Part 2: The Example Set — From X to Y

First: from a vendor list to a privilege inventory.

Most organizations can produce a list of vendors. Far fewer can produce a list of every piece of software running with root, domain admin or SYSTEM-level rights, plus every AI agent holding API keys that can change production. Build that second list. Rank it by blast radius, not by spend. Your backup tool and your AI ops agent might be line items today. They belong at the top.

Next: from "we don't contract with them" to "we know what our partners run."

The government's own data says Acronis hadn't had a direct federal contract in a decade, and its products could still be in federal environments. So stop accepting "not a vendor of ours" as an answer. Ask your MSPs, resellers and outsourced IT providers for a software bill of materials, which is simply an inventory of the components inside a product, for every agent they've installed on your systems. Make it a contract requirement at renewal.

Third: from annual review to event-driven monitoring.

The DHS order commits to reviewing itself within one year and annually after that. You can't afford to move that slowly. If you're a federal contractor, the stakes are concrete. Mayer Brown and Wilson Sonsini both noted that under the clause FAR 52.204-30, contractors must monitor for FASCSA orders, report any use of a covered product within three business days, and submit mitigation details within ten business days. Even if you're not a contractor, put a feed of these orders in front of your security team. Riotta noted that several law firms warned these orders could eventually land Acronis on the FCC's Covered List. Bans tend to spread from one domain to the next.

Fourth: from rip-and-replace panic to interim controls.

Here the order is genuinely useful as a playbook. Between issuance and full removal, it encourages agencies to monitor traffic in and out, put enhanced logging and data-exfiltration controls on the affected systems, and detect and flag anomalous activity. That's the right answer for any high-privilege tool you can't remove overnight. You can watch what it sends out before you can replace it.

Fifth: from "agents get admin" to "agents earn permissions."

I'll give Acronis credit here, because its own marketing describes the right design pattern. Its homepage says every agent runs with "least-privilege access and policy guardrails," with customers defining per tenant what an agent can read, change and act on. Most of its autonomous actions are listed as available but off by default, with a human approving first.

That's exactly the standard you should hold every AI agent to, from every vendor. Agents should have scoped permissions, autonomy that's off by default, a human approval step for anything destructive, and full logs. If a vendor can't show you those controls in writing, the agent shouldn't get root.

Lastly today: from a single backup vendor to recovery portability.

Think about the agencies holding years of backups in a format only one vendor's tools can restore, with a removal deadline coming. The lesson isn't to avoid this vendor. It's to make sure you could leave any vendor. Test whether your backups can be restored without the vendor's agent. Keep an exit plan for your most privileged tools, so a ban, an acquisition or a breach becomes a migration instead of a crisis.

Synthesis

So let me name my biases and uncertainty before I land this. I'm not a lawyer, and nothing here is legal advice. I haven't seen the classified evidence, and neither have you. It's entirely possible Acronis is being treated more harshly than the public record justifies. The company has said it continues to work with agencies to address their concerns, and FASCSA does give targeted firms notice, a chance to respond, and a path to federal appeals court. Neither hype nor doom is warranted. This isn't a reason for private companies to rip out a vendor tomorrow.

But the core idea holds up either way. The government looked at a backup and security vendor and didn't argue about features, price or even proven wrongdoing. It argued about privilege. Root access is the risk. That's the whole case.

Ultimately, the idea is this. Privilege is the new supply chain. Every tool that can read everything, change everything or act on its own extends your trust boundary to its owners, its investors, its resellers and its jurisdiction. AI agents are about to be the most privileged software most companies have ever run. Govern them that way now, before a two-sentence notice forces you to.

Call to Action

Here's your homework this week. Pull the list of every tool and agent in your environment with admin-level access, and next to each one, write down who owns the vendor and who installed it. If you can't fill in that second column, that's where to start.

Related Resources

1. U.S. Department of Homeland Security, "Notice of Order Regarding Exclusion and Removal of Acronis Products From Federal Civilian Executive Branch Information Technology Systems and Procurements," Federal Register Vol. 91, No. 209, pp. 68528–68532, October 30, 2026 (FR Doc. 2026-22215). https://www.govinfo.gov/content/pkg/FR-2026-10-30/html/2026-22215.htm
2. Public Inspection copy of the same notice, including the Appendix (Exclusion and Removal Order #2026-02). https://public-inspection.federalregister.gov/2026-22215.pdf
3. Justin Doubleday, "DHS bans Swiss cyber firm from federal systems," Federal News Network, October 28, 2026. https://federalnewsnetwork.com/cybersecurity/2026/10/dhs-bans-swiss-cyber-firm-from-federal-systems/
4. Chris Riotta, "DHS Orders Civilian Agencies to Purge Acronis Software," BankInfoSecurity / ISMG, October 30, 2026. https://www.bankinfosecurity.com/dhs-orders-civilian-agencies-to-purge-acronis-software-a-33264
5. Mayer Brown, "DNI Issues First FASCSA Exclusion and Removal Order Against Acronis AG," October 2, 2025. https://www.mayerbrown.com/en/insights/publications/2025/10/dni-issues-first-fascsa-exclusion-and-removal-order-against-acronis-ag
6. Wilson Sonsini, "DNI Issues First-Ever FASCA Order, Excludes Acronis from Intelligence Community Contracts," September 26, 2025. https://www.wsgr.com/en/insights/dni-issues-first-ever-fasca-order-excludes-acronis-from-intelligence-community-contracts.html
7. Acronis corporate homepage (product positioning as an AI-native cyber platform). https://www.acronis.com/en/
8. ExecutiveGov, "DHS to Remove Acronis Products From IT Systems." https://www.executivegov.com/articles/dhs-remove-acronis-products-it-systems (provided as a source; page text could not be retrieved, so nothing in this brief relies on it)
9. VitalLaw, "Citing security concerns, DHS bans Swiss tech firm from federal networks." https://www.vitallaw.com/news/citing-security-concerns-dhs-bans-swiss-tech-firm-from-federal-networks/cspd01c9fd5f5f1723476594cb69849f0e4f42 (provided as a source; page text could not be retrieved, so nothing in this brief relies on it)