What Changed in US-Iran Sanctions at the Strait of Hormuz?

Status, verification, and non-advice limits

This article is a compliance explainer for legal and sanctions-risk orientation. It is not legal advice, does not create an attorney-client relationship, and should not be used as approval for any payment, voyage, insurance acceptance, document submission, cargo movement, or counterparty dealing.

Legal-background review: Elena Park, J.D., sanctions and trade-controls reviewer. Status date: August 25, 2026, UTC.

The practical change on August 24 is straightforward: the Operation Economic Outcast package expanded secondary-sanctions exposure under the new EO 13902 sector determination to any person, wherever located, operating in aviation, digital assets, gold, shipping, and technology, while OFAC also suspended authorizations that firms had relied on for otherwise legitimate Iran- and Hormuz-related traffic. The same package warned that exposure may arise not only from cash or crypto toll payments, but also from in-kind transfers, insurance acceptance, and information submission connected to Iranian demands for passage through the Strait of Hormuz. [1][2][3][4]

What changed on August 24

Before August 24, a Hormuz review could still be built around a narrower set of questions: whether a counterparty was blocked, whether an Iran-related payment fit an OFAC authorization, whether a transaction involved petroleum, petrochemicals, financial services, the IRGC, or an already-designated maritime actor. Those questions still matter. They are no longer enough.

The new determination under EO 13902 adds five sectors to the Iran sanctions architecture for purposes of secondary sanctions: aviation, digital assets, gold, shipping, and technology. A foreign person does not have to be a U.S. person to fall into the exposed class. The operative hook is operating in one of the newly determined sectors of the Iranian economy, with the consequences then running through EO 13902’s sanctions mechanism. [1]

The alert matters because it frames the conduct OFAC is watching at the Strait. It does not limit the risk to a toll invoice paid in dollars. It identifies sanctions risks arising from Iranian demands for passage that may involve cash, cryptocurrency, in-kind transfers, acceptance of insurance arrangements, or submission of information. For a chartering desk or insurer, that moves the review away from “Did we pay?” and toward “Did we provide value, recognition, coverage, documentation, or operational cooperation that OFAC has now flagged?” [2][3]

The Recent Actions page is the other half of the package. It records not just a new warning, but the suspension or narrowing of previously available permissions: GL F and GL G suspensions, suspensions of ITSR § 560.544, § 560.550, and § 560.554, GL BB as a wind-down authorization only through 12:01 a.m. EDT on September 8, 2026, and GL AA for La Nivernaise de Raffinage SAS through October 23, 2026. [4]

US-person prohibitions and foreign-person exposure are not the same question

For U.S. persons, the first question remains prohibition. A U.S. person generally needs to know whether the transaction is blocked, prohibited, or authorized under the Iranian Transactions and Sanctions Regulations, an executive order, a general license, a specific license, or another OFAC authorization. If a previously available authorization has been suspended, the answer can change without the commercial facts changing at all.

That is why the August 24 suspensions are not an administrative footnote. A U.S. bank that previously treated a payment as covered by an authorization cannot keep relying on that conclusion after the operative authorization is suspended. A U.S. insurer cannot treat prior policy wording as a substitute for a current OFAC authorization. A U.S. shipping affiliate cannot assume that a wind-down period permits new business simply because the original transaction was legitimate when booked.

For foreign persons, the center of gravity is different. The question is usually not whether U.S. law directly prohibits every step in the same way it would for a U.S. person. The question is whether the conduct creates secondary-sanctions exposure: designation, blocking, correspondent-account restrictions, menu-based sanctions, or other consequences under the relevant authority. The August 24 determination matters because it broadens the class of sectoral conduct that can trigger that exposure. [1]

The distinction is practical. A non-U.S. shipowner that never touches a U.S. bank may still care about EO 13902 if it is operating in a newly determined sector of the Iranian economy. A non-U.S. insurer may still care if acceptance of coverage is part of a passage arrangement OFAC has flagged. A non-U.S. technology or digital-assets provider may still care if its service supports a demanded transfer, verification process, or passage mechanism tied to Iran’s Hormuz regime.

The authority chain now has to be read in layers

EO 13902 is the immediate source of the August 24 sectoral expansion. The order authorizes sanctions against persons operating in sectors of the Iranian economy determined by the Secretary of the Treasury, in consultation with the Secretary of State, and it already had a history of sector determinations before the Hormuz package. The record used here identifies an October 8, 2020 financial-sector determination and an October 11, 2024 petroleum and petrochemical determination as the relevant contrast points. [6]

That EO 13902 layer now sits on top of the older Iran sanctions architecture. The relevant background includes the EO 12957 national emergency, EO 13846 authorities, EO 13224 terrorism authorities as applied to the IRGC-related overlay, and statutory mandates including the Iran Sanctions Act, CISADA, CAATSA, IFCA, the SHIP Act, and MAHSA. CRS’s current Iran sanctions report is useful for that statutory and structural map, but its August 7 update predates the August 24 package and therefore cannot be the final word on current Hormuz exposure. [8]

EO 14382 is a separate tariff-related layer in the 2026 architecture. It should not be collapsed into the EO 13902 sectoral determination or the SDN blocking analysis. For a live matter, the point is not to recite every Iran authority in the file; it is to identify which authority actually attaches to the proposed act. [7]

Deadlines that matter before money moves

The most dangerous deadline in a sanctions file is often the one treated as a housekeeping date. OFAC’s August 24 Recent Actions record gives two dates that should be separated from the broader policy discussion: GL BB is a wind-down authorization only through 12:01 a.m. EDT on September 8, 2026, and GL AA for La Nivernaise de Raffinage SAS runs through October 23, 2026. [4]

A wind-down license is not a general permission slip for new business. The file should show what is being wound down, why the act falls within the license text, who is performing it, whether any blocked person is involved, and whether another suspension or determination independently changes the analysis. If the payment depends on GL BB, the time stamp matters because OFAC set the end at 12:01 a.m. EDT, not at close of business.

Do not blur the SDN overlay with the new sector determination

The SDN overlay is already severe without the August 24 sectoral expansion. Treasury’s July 2026 record identified PGSA, PGMIC, and HormuzSafe as part of the Strait-related sanctions stack: PGSA was designated on May 27, 2026 under EO 13224, while PGMIC and HormuzSafe were designated on July 29, 2026 under EO 13902. Treasury also highlighted strict-liability civil penalties, the 50% rule, and FinCEN whistleblower awards of more than $1,000,000. [9]

That overlay creates one kind of problem: dealings with blocked persons or entities owned 50% or more by blocked persons. The August 24 determination creates another kind of problem: exposure for operating in newly determined sectors of the Iranian economy. A diligence memo that says only “Hormuz counterparty risk” is not doing enough work. It should say whether the problem is a blocked person, ownership aggregation, a suspended authorization, a toll-demand fact pattern, sectoral exposure, or a statutory secondary-sanctions trigger.

The distinction is especially important for insurers and maritime teams already tracking the July PGMIC/HormuzSafe designations. The earlier designation record remains relevant, but the August 24 package broadens the analysis beyond named parties. Our prior tracker on Hormuz insurers and the PGMIC/HormuzSafe designation record is now a starting point, not a current complete answer.

Why the Strait is the focal point, not the whole story

The scale context explains why Treasury is treating Hormuz conduct as more than a local transit dispute. CRS reports that the Strait accounted for roughly 25% of world oil trade, about 20 million barrels per day, and about 19% of world LNG transit in 2025. Those figures explain the compliance pressure on banks, insurers, charterers, and energy traders. They do not decide whether a particular transaction is authorized. [8]

The legal status of the passage regime has also moved too quickly for a static explainer. OFAC FAQ 1249, first issued on April 28, 2026 and updated on May 29, 2026, remains part of the background on toll-regime exposure, but the page failed to verify directly for this snapshot and is treated here as second-hand verified through law-firm references, not as the operative August 24 source. [5]

That is why earlier work on Strait of Hormuz sanctions exposure has to be read with an August 24 overlay. A March, May, July, or early-August answer may still describe the architecture, but it cannot establish current authority after the five-sector determination and licensing suspensions.

The non-U.S. layers are context, not a substitute for OFAC analysis

There are UN and EU layers in the same factual environment. The record used here identifies an E3 snapback effective September 28, 2025 that Russia and China contested, and an EU layer that includes a February 2026 IRGC listing and June 8, 2026 freedom-of-navigation listings of two individuals and one entity. The EU action is relevant for sanctions-screening and group-wide policy design, but it does not answer the U.S. question created by EO 13902 and the August 24 OFAC documents. [8][10]

The Islamabad MOU and ceasefire sequence also belong in the file, but only for the role they actually play. The record used here treats the June 17 Islamabad MOU as a political framework, not a self-executing legal authorization; its 60-day window lapsed in mid-August 2026, and the ceasefire collapsed on July 7, 2026 with the blockade reimposed. For the treaty-status question, see the separate analysis of the U.S.-Iran MOU legal status; for the ceasefire/passage-rights question, see Iran ceasefire and Hormuz passage rights. [8]

International-law questions about attacks, navigation, and passage restrictions are related but separate. They may matter to a government-facing brief or insurance coverage dispute, but they should not be allowed to obscure the immediate OFAC question. For that layer, use the separate analyses on Hormuz ship attacks and international law and Iran-Hormuz tanker attacks.

A usable August 25 compliance map

For a live Hormuz matter as of August 25, the review should start with the August 24 Treasury records, not with a general Iran sanctions summary. The first pass should identify the actor, the conduct, the counterparty, the sector, the payment route, the documentation demanded, the insurance position, and the date on which the act will occur.

• If a U.S. person is involved, check whether the act is directly prohibited, blocked, or still authorized after the GL F/G and ITSR suspensions.
• If a foreign person is involved, check whether the conduct falls within the newly determined EO 13902 sectors or another secondary-sanctions trigger.
• If a named counterparty, affiliate, vessel interest, insurer, platform, or port-facing entity is involved, run the SDN and 50% rule analysis separately from the sectoral analysis.
• If a toll, fee, crypto transfer, in-kind transfer, insurance acceptance, or information submission is requested as a condition of passage, check the August 24 OFAC alert before treating the step as merely administrative.
• If the file relies on GL BB, GL AA, or any prior ceasefire-era authorization, tie the conclusion to the exact license text and deadline.

Steptoe’s August 24 sanctions update is useful as a law-firm corroboration that the Operation Economic Outcast package is the operative turn in the current record. It should not replace the Treasury documents themselves. [11]

The narrow conclusion is that “US-Iran sanctions at the Strait of Hormuz” is no longer a stable shorthand. It is a layered, recently changed framework: direct U.S.-person prohibitions, suspended authorizations, EO 13902 sectoral exposure, SDN blocking rules, statutory secondary sanctions, and non-U.S. sanctions layers all operating in the same channel. Any sanctions snapshot for Hormuz should be treated as stale unless it is re-anchored to the August 24 Treasury package and to record-level verification timestamps before it is used.

References

1. Determination Pursuant to Section 1(a)(i) of Executive Order 13902, U.S. Department of the Treasury / OFAC, August 24, 2026.
2. OFAC Alert on Sanctions Risks of Iranian Demands for Hormuz Passage, U.S. Department of the Treasury / OFAC, August 24, 2026.
3. Treasury Takes Additional Actions Under Operation Economic Outcast, U.S. Department of the Treasury, August 24, 2026.
4. Recent Actions: 20260824, U.S. Department of the Treasury / OFAC, August 24, 2026.
5. FAQ 1249, U.S. Department of the Treasury / OFAC, April 28, 2026; updated May 29, 2026.
6. Executive Order 13902 of January 10, 2020, Imposing Sanctions With Respect to Additional Sectors of Iran, Federal Register, January 14, 2020.
7. Executive Order 14382, Federal Register, 2026.
8. Iran Sanctions, Congressional Research Service, updated August 7, 2026.
9. Treasury Targets Iranian Regime’s Maritime Coercion Network, U.S. Department of the Treasury, 2026.
10. Freedom of navigation in the Strait of Hormuz: EU lists two individuals and one entity, Council of the European Union, June 8, 2026.
11. Sanctions Update: August 24, 2026, Steptoe, August 24, 2026.