Sectoral Sanctions
Sanctions targeting specific sectors of a country's economy rather than the entire country. Example: Russia's financial, energy, and defense sectors under Directive 1-4.
TL;DR
TL;DR: Sectoral sanctions restrict dealings with specific sectors of a country's economy rather than the whole country. Russia's financial, energy, and defense sectors are examples covered by directives.
What sectoral sanctions are
Some sanctions programs do not block a country outright. Instead they target specific sectors, such as energy, finance, or defense, and restrict certain dealings with the entities operating in them. The rules are often issued through directives that define which activities and entities are covered, and the scope can change as new directives are added.
How they differ from full blocking
Full blocking freezes the assets of listed parties and prohibits all transactions with them. Sectoral sanctions are narrower: they limit particular types of activity, such as certain financing or the supply of specific goods, while other dealings may remain permitted. The distinction matters because the obligations and the screening logic differ between the two.
The screening implication
Sectoral sanctions are harder to screen for than a simple name match. They require knowing not just who the counterparty is, but which sector it sits in and which directive applies. That is why risk scoring and up-to-date list data matter as much as name matching. A tool that only checks the SDN List will not catch a sectoral restriction that lives in a separate directive.
The agent payment angle
An AI agent paying a vendor in a sanctioned sector inherits these layered rules. Screening against the SDN List is the first gate, but a risk_score step, as in the SCREEN, SCORE, STOP, STAMP protocol supported by sanctionsai.dev, helps surface counterparties that need a closer look even when no exact list match exists.