OFAC Secondary Sanctions on Iran: 72-Hour Action Plan

Executive briefing: Early official and media indications suggest the United States has tightened Iran measures with greater secondary‑sanctions exposure for non‑US facilitators. Pending formal OFAC guidance, anchor decisions in standing authorities that already create broad OFAC secondary sanctions risk across shipping, finance, insurance, and logistics — notably E.O. 13846 (reimposed 2018 Iran sanctions, including petroleum/shipping), E.O. 13902 (2020, added sectors), the Iran Freedom and Counter‑Proliferation Act of 2012 (IFCA), and OFAC/State/USCG joint maritime guidance (updated in 2023; see Sources). These authorities remain in force as of August 25, 2026. Screening and voyage controls carry higher stakes when indirect facilitation is present under these authorities. Illustrative near‑term planning benchmarks (based on prior 2019–2021 Iran enforcement cycles and documented market responses; validate with your providers): enhanced screening SLAs of about 4–12 hours for high‑risk files; Gulf‑linked rotations that can extend by roughly 3–8 days on reroutes; and all‑in costs on exposed lanes that may increase by approximately 8–20% depending on routing, underwriter posture, and carrier policies. Carriers and insurers often add war‑risk and compliance surcharges; levels vary by market and JWC Listed Areas.

Methodology and sourcing note: This briefing synthesizes primary sources (OFAC Iran FAQs; Executive Orders 13846 and 13902; IFCA statutory text; the OFAC/State/USCG joint maritime guidance updated in 2023 on deceptive shipping/sanctions evasion practices; OFAC’s 2019 Compliance Framework; P&I Club and broker circulars; JWC Listed Areas) and documented market behaviors during prior Iran enforcement cycles (2019–2021). Benchmarks are illustrative and should be validated against your insurer, carriers, banks, and counsel. This brief will be updated when OFAC publishes any new FAQs or guidance specific to the August 2026 measures. Full references appear at the end.

Next 72 hours: immediate actions

Stabilize exposure while official and market guidance catch up. Act immediately, then refine.

• Pause bookings tied to red‑flag counterparties; hold new fixtures touching Gulf or Iran‑adjacent flows until cleared by Compliance. Set a defined turnaround for triage based on commodity and route risk tier, aligned to E.O. 13846/IFCA sectoral exposure.
• Re‑run SDN and UBO screening on all live and pending files (apply OFAC’s 50 Percent Rule and document match logic). Target same‑day match resolution for high‑risk files; log false positives and disposition codes; retain records for at least five years consistent with 31 C.F.R. § 501.601.
• Review active charters, BLs, and LOIs for sanctions clauses, termination and diversion rights; pre‑plan lawful alternatives. Prepare diversion cost models with pre‑authorized decision thresholds and caps; document who can approve reroutes.
• Confirm P&I and war‑risk cover in writing; record any exclusions or navigational limits; validate war‑risk surcharges against routing and JWC Listed Areas. Seek written insurer acknowledgment promptly; if responses exceed internal thresholds, escalate or decline.
• Enable AIS anomaly alerts, ship‑to‑ship (STS) monitoring, and port risk flags focused on the Gulf of Oman and Hormuz corridors. Set alert thresholds: an unplanned AIS gap of about two hours or a spoofing signature should trigger hold‑and‑escalate; require near‑continuous AIS uptime on Gulf passages except where port authority or safety directives under SOLAS apply (see the 2023 OFAC/State/USCG joint guidance on deceptive shipping and sanctions evasion).

What changed: scope, posture, and secondary exposure

Early indications point to a broader Iran posture with heightened OFAC secondary sanctions risk aimed at revenue‑enabling activity and facilitators. Regardless of any 2026 updates, existing authorities already reach non‑US persons who knowingly engage in significant transactions for certain Iran‑linked sectors or parties: E.O. 13846 (including Sections 3 and 5), E.O. 13902 (construction, mining, manufacturing, and textiles), and IFCA (shipping, shipbuilding, energy, and port operators). OFAC FAQs emphasize that indirect facilitation can create exposure for non‑US intermediaries.

Based on prior OFAC guidance and joint maritime advisories, expect a sharper focus on maritime services connected to oil, petrochemicals, metals, and dual‑use goods; increased attention on foreign financial institutions clearing related payments; and closer scrutiny of concealment patterns such as AIS gaps, spoofing, STS transfers near Iranian waters, and opaque ownership chains (see the 2023 OFAC/State/USCG joint guidance updating the 2020 advisory). During the September–October 2019 enforcement cycle, designations affecting COSCO Shipping Tanker (Dalian) units drove vessel repositioning, disrupted fixtures, and complicated insurance, showing how “facilitators” can become focal points alongside cargo owners.

The stakes are high: roughly one‑fifth of global petroleum liquids flows pass through the Strait of Hormuz in a typical year — EIA estimates have ranged around 18–21% in recent years — so even modest disruption or self‑sanctioning can shift tanker earnings, reprice risk premia, and create second‑order effects for container and bulk rotations tied to Gulf calls (U.S. EIA chokepoint analysis).

Operator benchmarks and impact ranges (for planning; verify against live market)

• Compliance handling and diligence: Expect incremental administrative effort per high‑risk booking, potential enhanced due diligence for sensitive counterparties, and outside counsel opinions where exposure is unclear. Set clear approval thresholds with Legal/Finance.
• Banking exposure: Payments routed via foreign financial institutions implicated by Iran‑related authorities can face higher rejection/return risk in early cycles, with additional reprocessing and potential delays. Monitor bank notices and correspondent policy changes closely.
• Insurance: Underwriters commonly adjust war‑risk additional premiums (AP) and voyage‑specific endorsements after advisories; surcharge levels and timing vary by route, hull value, and underwriter stance. Cross‑check with P&I/broker circulars and JWC updates.
• Schedule reliability: Gulf‑linked rotations may widen on‑time windows by several days during review cycles, then normalize if no kinetic escalation, subject to carrier advisories and port conditions.
• Screening performance: UBO enrichment and watchlist tuning typically reduce false positives versus baseline; define SLAs and QA sampling to measure gains and document controls for auditors and insurers.
• Onboarding timeline: Policy updates, training, and vendor data‑feed changes often require weeks; full program stabilization depends on complexity and integrations.

Compliance checklist for 3PLs, carriers, NVOCCs, and freight buyers

• Counterparties: Identify UBOs down to natural persons; screen against SDN and other restricted lists; apply OFAC’s 50 Percent Rule; assess correspondent banks and payment routes for secondary exposure. Re‑verify promptly on any change in control. Source: OFAC FAQ 401 and Iran FAQs.
• Cargo screening: Flag oil, petrochemicals, steel/aluminum, and aviation or dual‑use parts; confirm end‑use and end‑user; obtain supplier and buyer attestations in writing. For flagged cargo, require dual sign‑off (Compliance + Business) and insurer acknowledgment before release.
• Voyage checks: Review ports, terminals, STS plans, and transshipment hubs (UAE, Oman, Turkey, Red Sea nodes); require near‑continuous AIS with any exceptions justified and logged. Any unplanned STS or dark activity in proximity to Iranian waters should trigger an automatic hold.
• Documentation: Insert or refresh sanctions clauses in charterparties and house bills; update LOI templates; retain screening logs and approvals for a minimum of five years. Ensure logs capture who/what/when with UTC timestamps and hash‑locked PDFs for integrity.
• Escalation: Route red flags to Legal/Compliance quickly; hold cargo or booking until cleared; record the rationale for accept or decline decisions. Track SLA adherence and initiate corrective action if a material share of cases breach targets.

Booking decision tree: Gulf/Iran‑adjacent lanes and high‑risk commodities

1. Commodity test: Is the cargo oil, petrochemicals, metals, or aviation/dual‑use parts? If yes, apply enhanced due diligence. If no, proceed to port and counterparty checks. If commodity risk is high, set provisional status = HOLD until insurer confirms in writing.
2. Port and route test: Any call, STS, or transshipment touching the Gulf of Oman, Hormuz, southern Iran coastline, or high‑risk free zones? If yes, require senior sign‑off. If multiple high‑risk nodes appear, escalate to regional counsel and obtain a war‑risk position from insurers before pricing (consider JWC Listed Areas).
3. Counterparty test: Any SDN proximity, missing UBO data, or payments via banks with elevated Iran exposure? If yes, decline or seek an independent legal opinion. If UBO certainty is low or bank routing includes a flagged FI, set status = DECLINE unless remediated promptly.
4. Concealment risk: AIS gaps, spoofing, or complex ship‑to‑ship sequences? If yes, deny unless a verified audit trail and live monitoring are in place. Outages beyond policy thresholds without legitimate justification should trigger a decline.
5. Insurance test: Written P&I and war‑risk confirmation that coverage stands for the specific voyage and cargo. If absent, decline. Require endorsements naming cargo class and geographical limits; renew confirmations if voyage timing shifts materially.

Price and confirm space only after all five tests are satisfied. Document each step for audit and insurer queries.

Rapid triage scoring matrix (use with the decision tree)

Score each criterion on a relative scale and apply internal weights (High/Medium/Low). Sum to an overall risk rating. Proceed/Hold/Decline by internal threshold, and re‑score after remediation (e.g., alternate bank or route).

Contract and insurance: clauses, cover, and premiums

Charterparties and service contracts: Add or update BIMCO Sanctions Clause (2020) language where missing (confirm you are using the latest BIMCO sanctions clause available). Define clear diversion rights, who pays for delay and off‑hire tied to sanctions checks, and termination triggers if sanctions strike mid‑voyage. Consider force majeure and frustration thresholds for prolonged closures or denied services.

Bills of lading and LOIs: Embed warranties on lawful trade, true end‑use, and continuous AIS. Require shipper indemnities for misdeclaration and reserve the right to inspect or offload if red flags arise.

Insurance: Obtain voyage‑specific confirmations from P&I and war‑risk underwriters for named commodities. Expect exclusions on any breach, plus tighter navigational limits. Club and broker circulars during prior sanctions cycles indicate premiums can step up on Gulf exposure, with surcharges linked to routing and port intensity. Cross‑reference JWC Listed Areas and insurer guidance.

Contract & SLA specifics you can implement now

• Term and termination: Use multi‑year service agreements with mutual termination for convenience on reasonable notice; immediate termination for sanctions breach or designation. Include short cure windows for documentation gaps (not for violations).
• Volume commitments/variance: Forecast volumes by lane; define a variance band; outside the band, allow repricing or flex‑capacity fees with clear triggers.
• Service credits: Set screening SLAs for high‑risk files and define service credits for sustained misses; include a right to step‑in audit on repeated breaches.
• Detention/demurrage: Specify free‑time and daily charges by mode and port/country. Allocate responsibility when delays stem from sanctions checks versus shipper documentation.
• Fuel and war‑risk indexing: Link BAF to a recognized fuel index and any war‑risk surcharge to JWC Listed Areas; trigger reviews when indices move materially or listings change.
• Indemnities and warranties: Shipper warrants no SDN involvement, lawful end‑use, continuous AIS, and no STS without written consent; breach → indemnify carrier/3PL for fines, loss of cover, and consequential costs subject to a negotiated cap.
• Audit and evidence: Counterparty agrees to provide UBO evidence within agreed timelines and transaction docs promptly; failure → right to suspend services. Records retention should meet or exceed OFAC’s five‑year minimum.

Operational and commercial impacts to plan around

Chokepoints and routing: Higher exposure across Hormuz and nearby anchorages is possible. Build alternates via the Red Sea or West Coast India transshipment where feasible, and check feeder reliability and berth windows.

Network effects: Some carriers may self‑restrict calls or impose holds pending review. Expect bunching, rolling risk, and container imbalance as import and export flows adjust across Gulf ports.

Rate outlook: Expect early effects in tankers; tighter compliance can lift TCEs and war‑risk premiums. VLCC rates spiked in 2019 after Iran‑related actions (historical example), underscoring short‑term volatility. Containers and bulk should plan for temporary surcharges and several days of schedule variance on Gulf‑linked rotations. As a planning range, all‑in freight and accessorials on exposed lanes may move materially versus recent averages, subject to carrier and insurer advisories.

Monitoring plan and customer communications

• Regulatory feeds: Set alerts for OFAC, EU, and UK sanctions updates; track central bank and customs notices across Gulf states and key transshipment hubs.
• Insurance and intel: Subscribe to P&I circulars and maritime intelligence services covering AIS, STS, and port risk advisories; monitor JWC Listed Area changes.
• Internal cadence: Name an owner (Head of Compliance or Regional Counsel). Run a sanctions update meeting at a frequent cadence until risk stabilizes. KPI pack: number of holds/declines, SLA adherence, insurer response time, and false‑positive rate.

Customer‑facing templates:

• Advisory email: “We are reviewing the updated Iran measures and enhancing screenings. Some bookings may be paused pending checks. We will confirm status case by case.” Include expectations on screening turnaround and insurer confirmations.
• Booking questionnaire addendum: Add UBO fields, end‑user declaration, commodity HS codes, and routing confirmation (ports, STS, transshipment nodes). Require bank routing details if non‑USD and name of correspondent bank.
• Sanctions attestation form: Shipper or consignee certifies no SDN involvement, lawful end‑use, continuous AIS, and no STS without prior written consent.
• Sales or ops briefing script: “We can move approved cargo with documented diligence, alternative routings, and confirmed insurance. Timelines and pricing may adjust to ensure compliance.” Include likely surcharges and schedule buffers in summary.

What this means: key takeaways for 3PL buying and operations

• Risk has shifted to services and facilitators: OFAC secondary sanctions can extend to revenue‑enabling activities across shipping, finance, and logistics — including for certain non‑US persons under IFCA and E.O. 13846/13902. Map exposure before accepting bookings.
• Documentation will decide outcomes: Clean audit trails on UBOs, cargo, and voyages are your best defense in inquiries or insurance disputes. Align to OFAC’s Compliance Framework.
• Pricing power moves to compliant capacity: Operators with strong controls will be better positioned to secure space and pass through war‑risk and compliance costs.
• Plan for volatility: Design routing options around Hormuz, carry inventory buffers, and insert flexible service‑level terms.

About the author: Alex Morgan is Editor, Sanctions & Maritime Risk. This article follows our editorial standards (fact‑checking against primary sources, legal peer review where appropriate) and will be updated as official guidance is released. See our Sanctions Resource Hub for tools and updates.

Where OFAC secondary sanctions compliance fails: failure modes, hidden costs, and secondary‑sanctions traps

• Payment friction and returns: Correspondent banks can still reject non‑USD payments if they detect exposure to sanctioned sectors or persons; rejection rates often rise in early enforcement cycles, adding reprocessing time and bank fees. Build alternate corridors and collect bank attestations where possible.
• Insurance denial or reservation of rights: Missing or ambiguous sanctions warranties let insurers reserve rights; claims denials in prior cycles have clustered around AIS anomalies and misdeclared cargo. Budget for protracted claims recovery timelines and associated legal spend if disputed.
• Vessel and cargo delays: Holds for enhanced screening, dark activity investigation, or port state queries can add days to schedules; demurrage exposure on tankers can materially alter voyage economics.
• SLA disputes with customers: Without explicit sanctions‑related carve‑outs, missed ETAs can trigger service credits or chargebacks. Insert language capping total monthly sanctions‑related credits at a negotiated share of affected invoice value.
• Data and tech integration gaps: AIS and STS alert feeds often require custom logic; false alarms tend to be elevated in the first month. Allocate engineering hours for tuning; target measurable improvements in alert precision within the first month.
• Documentation drift: Outdated templates (LOIs, BL terms) lack current sanctions language; remediation across global stations often takes multiple weeks and risks inconsistent application in the interim.
• Indirect facilitation risk: Routing cargo through non‑US hubs with no USD leg can still constitute facilitation if the activity is material to restricted trade. OFAC FAQs warn that non‑US persons can trigger exposure through significant transactions in targeted sectors.
• Counterparty identity cycling: Entities may change names and ownership. Without frequent UBO refresh cycles, false negatives increase; tighten refresh cadence for high‑risk corridors.

Proprietary HORMUZ‑7 Controls (operationalize in ops systems)

Use these seven hard gates with documented, enforceable thresholds. Failing two or more should trigger a decline; failing any Zero‑Tolerance gate should trigger immediate decline per policy.

1. H — Hull & P&I confirmation: Obtain written confirmation naming cargo and voyage on a timely basis; Zero‑Tolerance if insurer declines or adds Iran‑adjacent exclusions.
2. O — Ownership/UBO resolution: Map multiple ownership layers to natural persons; require high certainty; Zero‑Tolerance if SDN proximity or unverifiable UBO.
3. R — Routing & AIS integrity: Enforce strict AIS uptime and gap thresholds aligned to policy; Zero‑Tolerance for GPS spoofing patterns without legitimate justification.
4. M — Money flows & banks: Pre‑clear correspondent banks; avoid FIs with heightened Iran exposure or cited in recent actions; where unavoidable, seek an external counsel memo before execution.
5. U — Use‑case/end‑user validation: Require signed end‑use certificates, HS codes, and dual‑use review; for aviation/dual‑use, add third‑party verification when warranted.
6. Z — Zero‑tolerance triggers: Any sanctioned port call, disguised STS, forged documents, or insurer reservation of rights → Decline.
7. 7 — Seven‑day revalidation: If voyage timing slips materially, re‑run screening, insurer confirmations, and bank checks before proceeding.

Complexity threshold model: when to escalate

• Smaller exposure programs: Apply standard controls; designate a part‑time compliance owner; engage external counsel as needed.
• Mid‑range exposure programs: Implement enhanced controls; dedicate a sanctions analyst; refresh UBO data on a frequent cadence; obtain insurer positions for high‑risk cargo; schedule periodic external counsel reviews.
• Larger exposure programs: Stand up a dedicated sanctions desk with continuous monitoring, automated AIS/STS analytics, bank routing playbooks, and pre‑negotiated war‑risk endorsements. Implement the triage matrix as SOP and run monthly audits.

Option‑by‑option comparison (operators’ quick reference)

Cost & pricing line‑item template (copy/paste into RFQs)

Example structure (illustrative; verify with providers). Replace ranges with carrier/insurer/broker quotations prior to use.

Pricing normalization framework (compare proposals like‑for‑like)

Fully loaded cost (FLC) formula: FLC = Base freight + Accessorials (BAF, terminals, etc.) + War‑risk surcharges + Compliance handling (screening, due diligence, legal) + Insurance (P&I/endorsements) + Detour/delay costs + Banking fees/FX + Expected service credits (negative) + Claims reserve (if self‑insured).

• Scenario comparison: Build at least two scenarios for each lane: Baseline (no high‑risk exposure) and Gulf‑exposed (with Listed‑Area calls or adjacent routing). Include alternate routings where feasible.
• Time bands: Model normal operations versus disruption windows (e.g., immediate 2–4 weeks post‑advisory and stabilization thereafter), aligning to your contract review cadence.
• Sensitivity testing: Vary war‑risk surcharges, schedule variance, and compliance workload. Identify breakpoints where a reroute or a decline becomes economically or risk‑wise necessary.
• Normalization mechanics: Standardize to cost per TEU/FEU or per metric ton for sea freight and cost per order for logistics services. Ensure all proposals include or exclude the same elements (e.g., who bears war‑risk, who funds legal opinions, storage responsibility during holds).

Hidden cost traps in sanctions‑era pricing

• Accessorial drift: Incremental storage, inspection, and manual handling fees during holds can outpace freight savings if not capped.
• Insurance carve‑outs: Reservation‑of‑rights language can shift risk back to the operator; require explicit voyage and commodity endorsements.
• Banking reprocessing: Returned or delayed wires add bank fees and internal labor; build a buffer for alternative routing or correspondent changes.
• Integration work: AIS/STS data feeds and alert tuning require engineering time and vendor costs; include in TCO.
• Over‑distribution of inventory: If rerouting via alternates, inventory positioning and inland dray can add hidden carrying and repositioning costs.
• 3PL fee offsets: Additional compliance handling by a 3PL can neutralize headline freight reductions if not scoped and rate‑capped.

Illustrative mini‑case (before/after)

Context: Non‑US NVOCC moving petrochemical intermediates with Gulf transshipment; no USD leg; program seeks to maintain lawful trade while addressing secondary‑sanctions exposure.

Before controls: Screening handled ad hoc; single‑pass review approximately 24 hours; no defined AIS thresholds; insurer confirmation obtained post‑booking; baseline routing via Hormuz.

After controls (90 days post‑implementation): High‑risk file screening SLA about 4–12 hours depending on commodity and routing; AIS gap threshold set to about two hours with near‑continuous uptime targets; insurer confirmations obtained pre‑pricing; when risk escalates, reroute via alternates, adding roughly 3–8 days and an estimated 8–20% increase in all‑in cost on exposed lanes. Impacts vary by underwriter posture, carrier capacity, commodity sensitivity, and port conditions.

Limitations and counterpoints

• Over‑compliance risk: Excessive de‑risking can forfeit lawful business and strain customer relations. Calibrate controls to documented risk and authorities; not all Gulf‑linked cargo is in scope.
• Jurisdictional divergence: EU/UK sanctions regimes may differ in scope and licensing from U.S. measures. Multinational operators should align the most restrictive applicable regime while exploring lawful licensing options with counsel.
• Information lag: Market and insurer positions can evolve daily following new measures. Set fixed duration limits for holds and establish explicit refresh cadences for screening and insurer confirmations.

Executive closing: Iran enforcement continues to tighten around facilitators and revenue‑enabling services. Pair disciplined screening SLAs, defined AIS thresholds, pre‑priced alternates, and insurer‑backed documentation. Build a repeatable program with pricing normalization, hidden‑cost controls, and explicit decline criteria.

References

• OFAC Iran Sanctions FAQs: https://ofac.treasury.gov/faqs/topic/1541
• OFAC FAQ on the 50 Percent Rule: https://ofac.treasury.gov/faqs/401
• Executive Order 13846 (Reimposing Certain Sanctions With Respect to Iran), Federal Register: https://www.federalregister.gov/documents/2018/08/07/2018-17065/reimposing-certain-sanctions-with-respect-to-iran
• Executive Order 13902 (Imposing Sanctions With Respect to Additional Sectors of Iran), Federal Register: https://www.federalregister.gov/documents/2020/01/14/2020-00604/imposing-sanctions-with-respect-to-additional-sectors-of-iran
• Iran Freedom and Counter‑Proliferation Act of 2012 (IFCA), Public Law 112‑239: https://www.congress.gov/112/plaws/publ239/PLAW-112publ239.pdf
• OFAC/State/USCG Global Maritime Advisory on Deceptive Shipping Practices (May 2020) — note: updated by joint guidance issued in Oct 2023; consult OFAC for the latest version: https://home.treasury.gov/news/press-releases/sm1016
• OFAC/State/USCG joint guidance update (Oct 2023) — Guidance to Address Illicit Shipping and Sanctions Evasion Practices (refer to OFAC’s website for the current document): https://ofac.treasury.gov/
• OFAC “A Framework for OFAC Compliance Commitments” (May 2019): https://home.treasury.gov/system/files/126/framework_ofac_cc.pdf
• U.S. EIA – Strait of Hormuz Chokepoint Analysis: https://www.eia.gov/international/content/analysis/regions_of_interest/Strait_of_Hormuz/hormuz.pdf
• Joint War Committee (LMA) – Listed Areas: https://www.lmalloyds.com/LMA/News/JWC/Listed_Areas.aspx
• International Group of P&I Clubs – Sanctions Resources: https://www.igpandi.org/sanctions
• BIMCO Sanctions Clause for Time Charter Parties 2020: https://www.bimco.org/contracts-and-clauses/bimco-clauses/current/sanctions-clause-2020
• Reuters – Tanker rates surge on U.S. sanctions/Mideast tensions (Oct 2019) [historical example]: https://www.reuters.com/world/tanker-rates-soar-record-high-us-sanctions-mideast-tensions-2019-10-11/
• OFAC Recordkeeping Requirements (31 C.F.R. § 501.601): https://ofac.treasury.gov/faqs/29

Reporting informed by coverage from gulf-times.com.