Archive for the ‘OFAC’ Category


Jan

15

OFAC List Prevents Professor From Slaying Imaginary Dragons


Posted by at 10:51 am on January 15, 2016
Category: OFACSDN List

Epic Building by Epic Games via https://epicgames.com/images/values/epic_building.jpg [Fair Use]
ABOVE: Epic Games HQ

Although I confess to being baffled as to why grown-ups play online video games (at least until after they have read the entire Western canon), recently a grown-up (and a college professor at that) pitched a fit after the OFAC blocking software of Epic Games choked on his name and told him he was not allowed to open an account with them and play one of their video games. More fun probably than playing the video game (and pretending to be a buff warrior in possession of awesome weapons and spells) is unraveling what occurred next.

Muhammad Zakir Khan, an assistant professor at Broward College in Florida, tried to sign up for an account online with Epic Games in order to play something called “Paragon” (which sounds more like a dish detergent than a video game, but that’s another issue). His effort to create the account was refused, and he was informed that this was because of a match against the SDN List, something that Mr. Khan had never heard of, so, like any other online warrior, he took the battle to Twitter, tweeting:

@EpicGames My name is Khan and I am not a terrorist.

Within a just a few hours, the CEO of Epic Games responded (via Twitter of course):

Sorry, this isn’t intended. We’re working to fix ASAP. Cause: Overly broad filter related to US trade restrictions.

Later, he tweeted how they thought they might fix the problem:

We’re working to figure this out. Ideally, not at signup, but by matching name and billing address at purchase time.

Obviously Epic deserves some credit for its efforts to take on OFAC and its SDN list, even though phaser energy guns and revivifying potions are of no use against either. Unfortunately, once there is a name match there is no simple automated solution to resolving the hit. In the case of Mr. Khan, having his address would have been useless because there is no address listed for the Mohammad Khan on the SDN List that caused the hit. Indeed, there is no single adequate way that one can automate resolving false hits. Computers may be able to drive cars, vacuum your living room, and play Jeopardy, but this is something that best practice requires be done by an actual human being.

But there is another point to be made here. Why on earth do we care at all whether terrorists and narcotics kingpins spend money to play online video games? In fact, wouldn’t we prefer that terrorists and drug dealers spend more time slaying imaginary dragons and enemies on their computers and less time doing what they do in the real world?

Permalink Comments (9)

Bookmark and Share


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

Jan

6

Writing Regulations Is Hard


Posted by at 8:36 pm on January 6, 2016
Category: Cuba SanctionsOFAC

Cuba - Havana - Car by Didier Baertschiger [CC-BY-SA-2.0 (http://creativecommons.org/licenses/by-sa/2.0)], via Flickr https://www.flickr.com/photos/didierbaertschiger/11785935544[cropped]

In late December, the Office of Foreign Assets Control (“OFAC”) updated its Cuba FAQs to add questions #57-61 on insurance issues.  Naturally, there is no explanation for why these were added but if you supposed that they were added to clarify some drafting screw-up in the Cuba regulations, you’d probably be right.  You can almost hear them saying over at OFAC:  “Don’t worry about the precise language, we can always fix it with an FAQ.  Pay no attention to that nonsense in section 552(a)(1)(D) of the Administrative Procedure Act about publishing in the Federal Register ‘interpretations of general applicability.’  That only applies to other agencies.”

The issue addressed by the new FAQs is the terrible drafting of  Note 2 to section 515.560 of the Cuba Assets Control Regulations, which says this:

This section authorizes the provision of health insurance-, life insurance-, and travel insurance-related services to authorized travelers, as well as the receipt of emergency medical services and the making of payments related thereto.

The problem here is the phrase “authorized traveler.” Who is an authorized traveler? Is it just a U.S. person traveling to Cuba under a general or specific license or does it also include a foreign person who is authorized because there is no prohibition on foreign citizens traveling to Cuba and no requirement that the foreign traveler obtain permission from OFAC for such travel? It seems to me that “authorized” can legitimately be read to include foreign travelers to Cuba.

Not so fast, according to the newly added FAQ #59

59. May U.S. insurers issue policies and pay claims related to group health, life, and travel insurance on behalf of third-country nationals traveling to or within Cuba?

Yes, provided that the insurance policy is as global policy, and not specific to the third-country national’s travel to or within Cuba.

But Note 2 says nothing about the travel insurance needing to be a global and not a specific policy. So “authorized traveler” has now effectively been redefined to exclude foreign travelers, all of whom are permitted to travel to Cuba. This was not a particularly thorny drafting issue for OFAC: the issue could have been easily and directly resolved by adding “U.S.” to “authorized travelers” when the rule was initially written and promulgated

The issue that this raises is whether OFAC, or any other agency, is entitled to regulate by Internet pronouncements notwithstanding the APA’s insistence that it use the Federal Register to publicize agency interpretations. If an insurance company reads Note 2 to cover foreign authorized travelers, is it culpable for not having scoured OFAC’s website for contrary interpretations when no such contrary interpretation appears anywhere in the Federal Register? When agencies expect those subject to their powers to respect the law, then the agencies themselves need to respect the law.

Permalink Comments Off on Writing Regulations Is Hard

Bookmark and Share


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

Jan

5

The Doctor Says You’re Gonna Die, Betty [Updated]


Posted by at 8:52 pm on January 5, 2016
Category: CybersecurityOFAC

city lights by frankieleon [CC-BY-SA-2.0 (http://creativecommons.org/licenses/by-sa/2.0)], via Flickr https://flic.kr/p/6mAPhC [cropped]The Office of Foreign Assets Control (“OFAC”) released on December 31 its cybersecurity regulations implementing Executive Order 13694 of April 1, 2015 (“EO 13694”), which permits the designation and blocking of individuals and companies that have engaged in “cyberenabled activities” that threaten the “national security, foreign policy, or economic health or financial stability.” Although no designations have been made under this order in the nine months since its issuance, OFAC didn’t want to pop open any New Year’s Eve bottles of champagne without pushing these regulations out the door. Since OFAC has yet to release regulations implementing Executive Order 13685, making Crimea the most sanctioned place on the face of the planet, this rush to implement an order under which no one has been designated is a bit puzzling. Low hanging fruit, I suppose.

The regulations are nothing more than the standard template regulations for blocking programs with  a prohibition of actions proscribed by the executive order, standard definitions, a provision implementing the 50 percent rule, and a few other basics. Three standard exceptions are provided authorizing (1) deduction of financial institution service charges from blocked accounts; (2) provision of certain legal services and (3) provision of unscheduled emergency medical services.

The emergency medical service exception, which appears in a number of regulations, is worthy of some further discussion. It addresses the issue of what happens in the case that a designated hacker or other blocked person is hit by drunken cab driver and is bleeding to death on the streets. A U.S. doctor happens by. Can he stanch the bleeding? In most blocking regulations this would be a problem because the regulations prohibit providing services to a person whose property and interests in property are blocked. Section 537.201(b)(1) of the Burma Sanctions, for example, contains such a provision. That provision would, on its face, prohibit the doctor from treating a blocked Burmese former junta member who was bleeding to death before his eyes. Hence the need for some kind of exception for unscheduled emergency treatment.

The new cybersecurity sanctions regulations do not directly prohibit providing services to a person blocked under those regulations but they do prohibit violating E.O. 13685 which itself has a provision prohibiting the provision of service to a person whose interest in property is blocked.  Thus the emergency medical exception is needed so that the doctor can apply a tourniquet without risking a jail sentence. Payment for these services, if they were sought, would be problematic without the exception because any payments to the doctor by the bleeding victim would have to be blocked. The cybercrime regulations would, however, permit this payment.

But, but, and there’s always a but when sanctions regulations are involved, these emergency services can only be provided in the United States. If the bleeding victim is on the streets of say, Canada, the U.S. doctor can’t perform or be paid for his services. He’d have to stand by and let the victim die. Fortunately, most doctors have bigger hearts than OFAC.

(The title of this post, by the way, refers to a naughty joke involving two famous actresses which can’t be repeated on a family-oriented blog such as this but which I hope some of you may have heard before. . . )

Permalink Comments (3)

Bookmark and Share


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

Dec

23

How the OFAC Stole Christmas


Posted by at 11:50 am on December 23, 2015
Category: Cuba SanctionsOFAC

Santa Flanked by F-16

A spokesman for the Treasury Department’s Office of Foreign Assets Control (“OFAC”) told Export Law Blog this morning that discussions between OFAC and the North Pole over Santa Claus’s Christmas Eve itinerary had once again broken down and were not expected to be resumed before Santa’s scheduled departure on December 24 at 10 pm EST.

The dispute arose from a dilemma that the U.S. sanctions against Cuba posed for Santa’s planned delivery of toys to children in Cuba. If Santa delivers toys for U.S. children first, there will be toys destined for Cuba in the sleigh in violation of 31 C.F.R. § 515.207(b). That rule prohibits Santa’s sleigh from entering the United States with “goods in which Cuba or a Cuban national has an interest.” On the other hand, if Santa delivers the toys to Cuban children first, then 31 C.F.R. § 515.207(a) prohibits the sleigh from entering the United States and “unloading freight for a period of 180 days from the date the vessel departed from a port or place in Cuba.”

A press release from the North Pole announced that the OFAC rules left Santa no choice but to bypass the children of the United States this Christmas. A spokesman from OFAC warned that if Santa attempted to overfly the United States, his sleigh would be forced to land and his cargo seized. He continued:

We know that the outcome is harsh, but we cannot allow the Cuban regime to continue to be propped up by Santa’s annual delivery of valuable Christmas toys to Cuban children. We told Santa that, as long as he only delivered food, books, and mobile phones to children in Cuba he would be eligible to enter the United States under the exception in § 515.550, but he insisted on delivering teddy bears as well. We draw the line at teddy bears, so in our view it’s his fault, not ours.

Congressional leaders did not return our calls.


This post is an annual tradition and has appeared every year since 2007. Alert readers will notice a slight change in this year’s post.

Export Law Blog would like to take the opportunity of this post to extend its best holiday wishes to all of its readers. Posting will be light between now and the end of the holidays.

Permalink Comments (3)

Bookmark and Share


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

Dec

2

We’re From the USDA and We’re Not Here to Help You (UPDATED)


Posted by at 11:59 pm on December 2, 2015
Category: OFACTSRAUSDA

USDA by Dlz28 via https://en.wikipedia.org/wiki/File:United_States_Department_of_Agriculture,_Jamie_L._Whitten_Federal_Building,_Washington_DC_(12_June_2007).JPG [Public Domain]Today’s post, brought to you by the United States Department of Agriculture, is yet another entry into the long and sad cavalcade of administrative incompetence that makes the life of exporters harder than it should be. If you have recently tried to export an “agricultural commodity” under the provisions of the Trade Sanctions Reform and Export Enhancement Act of 2000 (“TSRA”) you may have run into this problem. This would include trying to export an item relying on the general license in section 560.530 of the Iran Transactions and Sanctions Regulations which permits export of “agricultural commodities” without a specific license.

The first question is whether the item you want to export, say a container of wood clothes hangers, is an “agricultural commodity.” TSRA covers “agricultural commodities” which the statute defines as follows:

The term “agricultural commodity” has the meaning given the term in section 102 of the Agricultural Trade Act of 1978 (7 U.S.C. 5602).”

Cool, that’s helpful. Let’s see how section 5602 the Agricultural Trade Act defines “agricultural commodity.” So, here’s that definition

The term “agricultural commodity” means any agricultural commodity, food, feed, fiber, or livestock (including livestock as it is defined in section 1471(2) of this title and insects), and any product thereof.

Awesome:  an ” ‘agricultural commodity’ means any agricultural commodity.” Your Congress at work. That’s why we pay them their salary and send them to DC to be wined and dined by lobbyists in expensive steakhouses.

Fortunately, OFAC’s TSRA application instructions tells you that you can figure out what is an agricultural commodity by going to www.fas.usda.gov and consulting a “list of agricultural commodities that qualify for export under the TSRA program.”

Now, if you actually believe that and go to the site mentioned looking for the list, no matter how well-honed your search skills are, no matter how strong the Google Force is with you, you will not find that list. It’s nowhere to be found. Of course, you might even remember having seen that list before, and you would be right.

What’s happened here is that some web geek at the USDA convinced the agency that it needed to redesign its website so, I suppose, it looks good on an iPhone or includes the latest CSS geegaw. And in this ridiculous process, no one at the USDA actually tried to figure out whether the new site was actually useful or retained vital information. Nope, looks good, they declared, and headed off to their cars or to Metro to start the long commute home to Virginia.

As a special service to our readers, and brought to you by the magic of the Internet Wayback Machine, here is a link to that list. We have uploaded the list to our server, so that it will remain available for your reading and licensing pleasure. And, yes, those wooden clothes hangers are agricultural commodities.

UPDATE:  An alert reader has more of the Google Force with him than I do and managed to locate the elusive agricultural commodities list on the Department of Agriculture’s website. It’s here.  You’d think that OFAC would say more in its application instructions that the list can be found somewhere on www.fas.usda.gov, but, of course, you’d be wrong.

Permalink Comments Off on We’re From the USDA and We’re Not Here to Help You (UPDATED)

Bookmark and Share


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