Enforcement27 Oct 20264 min read

Test the release: Three controls from DOJ’s Extreme Networks agreement

DOJ’s Extreme Networks agreement describes compliance holds lifted despite conflicting customer information. Three practical tests examine the evidence supporting an approval.

This post is for general information and is not legal advice. Sanctions determinations turn on specific facts; consult counsel about your situation.

A compliance hold records a pause. The evidence supporting its release shows what the reviewer resolved. On October 27, 2026, the Department of Justice announced a non-prosecution agreement with Extreme Networks concerning sales to a Russian weapons manufacturer owned by a sanctioned entity. The detailed record is useful for companies whose sales, service and compliance teams see different parts of a customer relationship.

The mismatch survived the review

Extreme Networks designs and manufactures networking equipment and software. According to the agreement’s Statement of Facts, its Russian subsidiary sold through distributors and resellers. Certain subsidiary employees concealed the actual end user, Moscow Machinery Building Plant Avangard (MMZA), behind the name Dmitrovskiy Experimental Mechanical Plant (DEMZ). Extreme’s U.S.-based Global Trade Compliance group and order management approved Russian sales, which were subject to automatic compliance holds. Statement of Facts ¶¶ 1–3, 27–29.

The customer portal exposed the problem. A request submitted under DEMZ’s name was initially denied for incomplete information. When resubmitted, it still used an MMZA email address and gave MMZA’s address for DEMZ. The compliance hold was lifted that day despite the conflicting company name, address and domain. The portal allowed customers to request service and download software. Statement of Facts ¶ 35.

A later order produced another inconsistency. In October 2020, a distributor changed the website and email-domain information associated with the purported DEMZ customer, but MMZA’s address remained on the purchase order. The end-user certificate then supplied carried a different address from that order. Its Russian-language company name also did not match the purported end user. The agreement records questions from order management and failures by Global Trade Compliance to identify the red flags appropriately. Statement of Facts ¶ 37.

The history was also relevant. Extreme inherited customer accounts and service orders through an acquisition. One inherited service contract expressly identified MMZA as the end user. That record provided another place to test the identity appearing on a later order. Statement of Facts ¶¶ 30–32.

What DOJ resolved

Extreme admitted responsibility for the conduct in the Statement of Facts and accepted those facts as true and accurate. This is an agreed corporate resolution, rather than an unproven indictment account. The agreement provides for a $487,860.92 criminal fine and $487,860.92 forfeiture, totaling $975,721.84. DOJ also reported a separate OFAC administrative action. The criminal amount should not be presented as the combined cost of both proceedings. Agreement ¶¶ 2(f)–(h), 3–4.

DOJ credited cooperation and remediation. The agreement identifies expanded end-user diligence, revised screening parameters and country holds, additional compliance personnel, and acquisition diligence procedures. A new screening process required documented reasons for terminating a compliance hold and daily rescreening of counterparties in the customer database. Agreement ¶ 2(c)–(d). These are case-specific measures and resolution considerations, not a universal checklist or assurance of the same outcome elsewhere.

Three practical tests for company controls

The following are our observations drawn from the record. They are suggested tests, not generally applicable legal requirements imposed by this agreement.

1. Test the reason for release. Select a sample of closed holds and reconstruct each decision. Record the original concern, the evidence resolving it, the reviewer and any remaining conditions. Have someone outside the originating sales team challenge unsupported closures. If the file cannot explain an unresolved inconsistency, return it for assessment before further fulfillment or access. The practical question is whether the approval record explains why the evidence was sufficient.

2. Reconcile the customer across systems. Compare the company name, address and email domain in portal registrations, service records, orders and end-user certificates. Assign an owner to investigate mismatches and preserve the explanation with the transaction. Where language differences matter, obtain a competent review of the underlying name and address. A new certificate should be checked against the conflicting record it is meant to resolve.

3. Carry customer history into integration. After an acquisition or customer-system migration, compare inherited service contracts and customer accounts with current identities. Review unexplained replacements or renamed accounts, particularly where earlier records identify a different end user. Keep the historical record accessible to compliance and support teams. MMZA’s appearance in an inherited service contract illustrates why a current account label may be insufficient.

These tests can be applied outside Russia and without assuming that every mismatch signals wrongdoing. Their purpose is to make the evidence behind a company decision reviewable. They do not guarantee that concealment will be detected.

Scope of this analysis

This article relies on DOJ’s announcement and the executed agreement published with it. It does not independently assess current sanctions or export-control requirements, item classifications, the parallel OFAC resolution or eligibility under DOJ’s disclosure policy. The agreement binds its parties; it does not itself impose these suggested controls on other companies.

This post is for general information and is not legal advice. Sanctions determinations turn on specific facts; consult counsel about your situation.

Sources

DOJ Office of Public Affairs, release 26-1264, October 27, 2026; Extreme Networks non-prosecution agreement, letter dated October 20, 2026, main agreement ¶¶ 2–5 and Statement of Facts ¶¶ 27–38. These are official U.S. federal resolution materials; the agreement’s obligations are party-specific.

Questions about the evidence supporting your company’s sanctions-control decisions?

Contact Zimmermann Law→