Archive for the ‘State Department’ Category


Aug

30

To Russia With Love: State Imposes Limited Sanctions for Nerve Gas Attacks


Posted by at 3:56 pm on August 30, 2018
Category: Russia SanctionsState Department

Novichok Vodka via https://www.rt.com/business/426529-novichok-brand-russia-business/ [Fair Use]I wrote earlier this month on a State Department press release finding that Russia had used chemical weapons in the attacks on Sergei and Yulia Skirpal in the United Kingdom and that, accordingly, sanctions would be imposed on Russia pursuant to the Chemical and Biological Weapons Control and Warfare Elimination Act of 1991 (the “CBW Act”). That act requires the imposition of five sanctions, although the President has the authority to waive any or all of the sanctions based on national security considerations. On Monday, the State Department published a notice in the Federal Register imposing those sanctions, effective immediately. As expected, the application of certain of the sanctions was waived completely or partially, and the ones given full effect are unlikely to be of much concern to Russia.   As a result, it seems unlikely that Russia will find any reason to curtail its use of nerve agents around the world.

The first sanction required by the CBW Act is the termination of all foreign assistance to Russia under the Foreign Assistance Act of 1961. This sanctions was waived on national security grounds. It’s not clear why State bothered to use the national security waiver here, since Russia last received foreign assistance under the act in 2014 and none was scheduled to be provided in 2019 (or likely any time after that.)

The second required sanction is the termination of arms sales to Russia. State waived this sanction except “with respect to the issuance of licenses in support of government space cooperation and commercial space launches.” You’ve got to get supplies to the International Space Station somehow or other.  And, of course, DDTC stopped granting license to export most items on the USML back in 2014.

The notice imposes the third required sanction completely and without waiver. It terminates all “foreign military financing for Russia under the Arms Export Control Act.” This can hardly be an earth-shaking development. When was the last time the US financed arms sales to Russia? World War II?

The fourth sanction — denial to Russia of “any credit, credit guarantees, or other financial assistance by any department, agency, or instrumentality of the United States Government, including the Export-Import Bank of the United States” — is also imposed without any waiver. Again, this is a sanction without any forseeable impact given the likelihood that little, if any, such federal financial assistance is being provided to Russia.  The last transactions involving Russia financed by the EXIM Bank were in 2014.

The fifth required sanction under the CBW Act is the prohibition of “the export to Russia of any goods or technology” controlled on the Commerce Control List for NS reasons. The State Department notice here has a number of waivers that arguably are not very different from waiving the prohibition in its entirety.

Not surprisingly, the waiver includes any exports under license exception ENC. Remember that all encryption items, other than mass market items, are controlled for NS reasons, so this prohibition would have prohibited, say, exporting network equipment to Russia. How could we spy on them if we don’t sell them routers?  Which is why, of course, Russia limits imports from the United States of items, such as routers, with encryption functionality.  Other exceptions that survive the prohibition are GOV, RPL, BAG, TMP, TSU, APR, CIV, and AVS.

Beyond the waivers for exports under the aforementioned license exports, there are waivers for exports to wholly-owned U.S. subsidiaries, to commercial (i.e. non-governmental) enterprises, and to Russian nationals in the United States. Because Russia has always been subject to NS controls, these waived exports will still require, as they always have, licenses.

One final observation should be made on the meaning of “to Russia” in these sanctions. As noted the sanctions prohibit the provision of federal financial assistance “to Russia.” The reference in the fifth sanction to waivers for deemed exports to Russian nationals in the United States means that “to Russia”  means to anyone in Russia and to any Russian outside Russia.  So, if that a Russian granted asylum in the United States is one of the victims of a natural disaster, FEMA could not provide any financial relief to that Russian.  That’ll teach Russia!

Permalink Comments Off on To Russia With Love: State Imposes Limited Sanctions for Nerve Gas Attacks

Bookmark and Share


Copyright © 2018 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)

Oct

28

The Dog Ate The White House’s Section 231 Guidance


Posted by at 12:48 pm on October 28, 2017
Category: OFACRussia DesignationsRussia SanctionsState Department

Vladimir Putin via http://en.kremlin.ru/events/president/news/27394 [Fair Use]Because Congress was not convinced that the Trump administration would respond to Russia’s various shenanigans in Ukraine and in the U.S. elections, it passed, on August 2, 2017, the Countering America’s Adversaries Through Sanctions Act (“CAATS Act”). Section 231 of the CAATS Act targets U.S. and foreign persons that engage in a “significant transaction with a person that is part of, or operates for or on behalf of, the defense or intelligence sectors of the Government of the Russian Federation.” Under that section, the President must impose at least five of the laundry list of twelve possible (and familiar) sanctions described in section 235, including denial of export privileges, asset blocking, government procurement bans, visa and travel bans and prohibition of lending to, or investment in, the sanctioned entity. That section also permits these sanctions to be imposed not just on a corporate entity but also on its principal officers.

One immediate and obvious issue is the ban on dealing with persons acting on behalf of Russian intelligence. You don’t have to be an avid fan of “The Americans” or John le Carré to know that spooks don’t ever advertise that they are spooks. Kaspersky Labs, which may or may not be acting on behalf of the FSB, vigorously denies that it has had anything whatsoever, now or in the past, with the FSB, which, of course, is to be expected and is not in and of itself convincing proof that they are just a little anti-virus company in Moscow. So section 231(d) required the President to issue, by October 1, 2017, “regulations or other guidance to specify the persons that are part of, or operate for or on behalf of, the defense and intelligence sectors of the Government of the Russian Federation.” Not surprisingly, October 1, 2017 came and went without the required guidance. Tick. Tock. Tick. Tock.

Well, yesterday, almost a month late and after a draft of the guidance was leaked to the New York Times, the State Department released a list of thirty-nine entities associated with Russian defense and intelligence. Of those, only 10 were not previously on the SDN or SSI Lists. Of the twenty-nine already on one of those lists, eight are on the SSI List.

It is not at all clear why this list and the guidance are being issued from the State Department rather than from the Department of Treasury’s Office of Foreign Assets Control which normally handles economic sanctions of this sort. The result is that Heather Nauert, who held a State Department briefing on the new guidance and admitted that she was not a “sanctions expert,” had no idea what she was talking about. Hilariously (or perhaps tragically) she says that the entities on the list are “entities that [people] can no longer do business with.” The issued guidance says the exact opposite: “The Act does not provide for sanctions in cases in which transactions are not “significant.'” Oops.

Of course, even though the prohibition is only on “significant transactions” with these entities, it is not altogether clear what constitutes a “significant transaction.” Inexplicably, there is no dollar threshold mentioned in the guidance. The most detailed statement on what is not significant is this confusing statement: if a”transaction for goods or services has purely civilian end-uses and/or civilian end-users, and does not involve entities in the intelligence sector,”  this will “weigh heavily against” a determination that it is a significant transaction.  What this says, given that the restrictions are on dealings with the intelligence and defense sectors, is that transactions in the defense sector with purely civilian end-users or civilian end-uses won’t be deemed to be significant transactions. How a transaction in the defense sector can have purely civilian end-uses and end-users is far from clear.

Finally, it is important to understand that nothing in the guidance says that this is a comprehensive list of entities in the defense and intelligence sector where significant transactions can lead to sanctions. If you have a significant transaction with an entity in the intelligence sector, even one operating under deep cover, you and your principal officers can be sanctioned. Whether this will ever happen is unclear, but U.S. and foreign companies doing business with Russian companies will be doing so at their own risk.  Whether this is the intended result or simply an unintended result of incompetence is irrelevant.

Permalink Comments (1)

Bookmark and Share


Copyright © 2017 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)