Archive for the ‘OFAC’ Category


Nov

2

Let Them Write Letters


Posted by at 8:34 pm on November 2, 2009
Category: Economic SanctionsOFAC

Twitter Keeps Iran AfloatLast week several readers brought to my attention a Bloomberg story that announced in its headline “U.S. Wants Microsoft to End Message Ban in Iran, Cuba.” This created a bit of a hubbub at the world headquarters of Export Law Blog, since this blog has been advocating for some time that the information exception be read to cover instant messaging, twittering, and the like. Alas, as we learned at a tender age, you can’t believe everything you read in the newspapers. (You can, of course, believe everything you read in blogs.)

The Bloomberg story referenced a letter that OFAC sent last month to the Center for Democracy in the Americas, a group that, like Export Law Blog, has been a persistent critic of the Cuba sanctions. But when you read the letter, it’s quite clear that the letter doesn’t exactly say that the U.S. wants to end the application of sanctions to instant messaging services:

We assure you that the discontinuation of instant messaging services [by Microsoft to users in Cuba, Syria, Iran, Sudan and North Korea] was not directed by OFAC or, to our knowledge, any other Federal agency. Ensuring the flow and access to information available through the Internet and similar public sources is consistent with the policy interests of the United States Government.

OFAC is participating in an interagency effort to review any discontinuation of certain instant messaging services to sanctioned countries, with the goal of insuring that such services will be available to persons in sanctioned countries to the extent permitted by current U.S. law. [emphasis added]

The last clause is the catch here. OFAC has typically interpreted the information exception very narrowly, and there is no indication that OFAC has changed its view of what’s “permitted by current U.S. law.”

Instant messaging services require the download of software, and OFAC takes the position that software isn’t information covered by the information exception. Twitter creates a miniblog page with a unique URI for each user, which would, under OFAC’s narrow view of “information,” be considered provision of a service in violation of the sanctions regulations.

OFAC’s antiquated view of information, apparently formulated sometime between the invention of the printing press and Columbus’s discovery of the Americas, comprises only things written in ink on paper. Throw a few electrons into the mix and all bets are off.

So I wouldn’t take this OFAC letter to the bank if I were you. At least not yet.

Permalink Comments (3)

Bookmark and Share


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

Oct

7

OFAC Guidance Imposes New Burdens on Exports of Medical Devices


Posted by at 11:47 pm on October 7, 2009
Category: OFAC

Star Trek Dermal RegeneratorThe Treasury Department’s Office of Foreign Assets Control (“OFAC”) issued a guidance today on exports of medical parts to support medical devices legally exported under OFAC licenses to Iran or Sudan, the two countries for which OFAC exercises licensing authority over medical devices. And, not surprisingly, OFAC continues its efforts to resist the mandate of the Trade Sanctions Reform and Export Enhancement Act of 2000, which sought, on obvious humanitarian grounds, to prevent OFAC and other export agencies, from restricting exports of food, medicine and medical devices to sanctioned countries.

Under the new guidance, rather than saying simply that exports of replacement parts are ordinarily incident to the export of medical device itself, and therefore allowed, OFAC imposes burdensome conditions on those exports. The potential impact of this red tape on ordinary citizens in Iran and Sudan who are sick or dying just doesn’t matter. Worse, such punitive measures directed at the sick and dying are not going to cause Iran to give up its nuclear aspirations or cause the regime in Sudan to rethink its genocidal policies.

First, if the part that needs to be replaced fails during the one-year period of validity of the export license for the medical device itself, the part can be exported, but only as a one-for-one replacement. But there is another, and more significant, catch. The replacement part must have obtained a specific classification as EAR99 from the Bureau of Industry and Security (“BIS”). And even if the exporter has a classification for the medical device as EAR99, it doesn’t count unless that classification specifically mentions the replacement part in question.

Medical devices on this list don’t require a specific BIS classification, but the list doesn’t include parts. So even though an OFAC license for a digital blood pressure monitor doesn’t require a specific classification from BIS, exporting a replacement display screen for that device does!

Second, if the underlying license has expired, a new OFAC license is required to export the replacement parts. And, again, a specific BIS classification is required for each of the replacement parts exported, even if the device itself was classified as EAR99 or was on the exempted list and did not require a BIS classification. OFAC license approvals can take from 40 days to six months or more, which means that patients may go without care while the exporter waits for a BIS classification and an OFAC license.

Third, even an import of the device back to the United States for repair will require a license — as will the re-export after the device is repaired. The application will require, among other things, a “statement regarding the circumstances under which the medical device broke.” It’s not clear that simply saying that the device was being used and it just failed will suffice as a justification for a license.

If you are an exporter of medical devices under TSRA licenses to either Iran or Sudan, you should make sure that any request for a required BIS classification of the device also includes a request for classification of the important parts of that device. You also should be aware that you can’t solve this problem by continually renewing the license. Parts can only be shipped without a license under this guidance if they are shipped during the original period of validity of the license under which the medical device for which the parts are destined was exported.

Permalink Comments (2)

Bookmark and Share


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

Oct

6

N.J. Pol Nixes N.Y. Philharmonic Gig in Cuba


Posted by at 7:32 pm on October 6, 2009
Category: Cuba SanctionsOFAC

Empty StageLast week the New York Philharmonic announced that it had been forced to cancel its planned concert in Cuba at the end of October. Although the Office of Foreign Assets Control (“OFAC”) granted licenses to let the instrumentalists travel to Cuba, it declined to permit the orchestra’s patrons who were footing the bill for the trip to tag along.

This decision seems at odds with current initiatives by the White House to ease travel restrictions to Cuba. It now appears that the outcome was the handiwork of New Jersey Senator Bob Menendez, who threatened to vote against health reform if a single note of Gershwin was heard in a Havana concert hall. Menendez was reportedly infuriated by the recent success of a concert by a Colombian pop-star in Cuba, and didn’t want such a horrifying event to recur if the New York orchestra traveled to the island. Apparently for every note of Beethoven that a Cuban hears, Raúl Castro gets another week in office and Fidel draws another thousand breaths.

Permalink Comments (4)

Bookmark and Share


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

Sep

24

The Firefox in the Win House?


Posted by at 7:55 pm on September 24, 2009
Category: BISIran SanctionsOFAC

firefox_iranLast week an obviously confused reporter at internetnews.com reported what he thought were the details of a letter from the Bureau of Industry and Security (“BIS”) received by Mozilla, the open-source project responsible for Firefox, Thunderbird and other Internet applications, relating to downloads of the program by computer users in Iran. The article seemed to suggest that Mozilla had filed a voluntary disclosure with BIS that it had allowed downloads of its open-source encryption source code by Iranians. The article seemed to suggest further that Mozilla had received a letter from BIS stating that this was not a violation.

But that’s not what happened. BIS released yesterday an Advisory Opinion that, although identifying details have been removed, clearly addresses the situation described in the internetnews.com article. And, significantly, the advisory opinion doesn’t address exports of source code but instead addresses export of compiled source code and, specifically, compiled source code including mass market encryption software. Under section 746.7(a)(1) of the Export Administration Regulations (“EAR”) exports of compiled mass market encryption software (or any other compiled encryption software) to Iran would require a BIS license. The Advisory Opinion held that as long as the IP address of the party downloading the software in Iran (or other sanctioned country) was logged by Mozilla’s server but not otherwise used by Mozilla (say, for example, to serve to the user a web page in Farsi), the company did not have sufficient knowledge of an export of encryption software to Iran to be liable under the regulations.

Even though I don’t believe that, as a matter of policy, downloads of web browsers with encryption features ought to be subject to export controls, the reasoning of the Advisory Opinion is, to say the least, a bit odd. It seems fairly well-established that knowledge is not a required to establish a violation of the EAR. Specifically, section 764.2(a), which defines violations of the EAR, doesn’t contain a knowledge requirement, nor does General Prohibition No. 1 which would be the predicate to a violation of section 764.2(a). Perhaps this signals a retreat by BIS from its traditional concept of strict liability for violations of the EAR.

Even so, the final sentence of the Advisory Opinion may nullify, as a practical matter, any significance the opinion may have with respect to software downloads in sanctioned countries:

Please note that this advisory opinion is confined to interpretation of the EAR, and does not address the sanctions regulations implemented by the Office of Foreign Assets Control [“OFAC”]

And, as we all know, other major software companies, such as Google and Microsoft, have prohibited downloads in sanctioned countries due to fears of OFAC penalties.

Permalink Comments (5)

Bookmark and Share


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

Aug

26

Australian Bank Agrees to Pay $5.75 Million to OFAC


Posted by at 7:08 pm on August 26, 2009
Category: OFAC

ANZ BranchANZ Bank, Australia’s third largest bank, recently agreed to pay to the Office of Foreign Assets Control (“OFAC”) a fine of $5.75 million to settle allegations that the bank had engaged in transactions in Sudan and Cuba in violation of the U.S. embargo on those two countries. The OFAC announcement of the settlement noted that ANZ manipulated the SWIFT messages related to the Sudan transactions by removing all references to Sudan. ANZ was liable for these violations as a result of its banking office in New York City.

According to the announcement, 31 transactions with a total value of $106 million were involved. Given the size of the agreed penalty, it is clear that the applicable penalty to this case was not the penalty applicable before the International Economic Powers Penalty Enhancement Act (or $50,000 per transaction) but the enhanced penalties of $250,000 per violation or twice the value of the transaction imposed by that legislation. Under the enhanced penalties, ANZ was theoretically liable for $212 million. [UPDATE: Actually the maximum liability was $57,040,000. The Cuban transactions were subject to a maximum fine of $65,000 each. Thanks to Jim Slear in the comments for catching my mistake]

OFAC cited a number of mitigating factors justifying the reduced penalty including ANZ’s cooperation in the investigation, its voluntary disclosure of the Cuba violations, its adoption of revised compliance procedures, and its agreement to engage in, and report to OFAC, further audits of its activities to insure that it doesn’t process financial transactions involving embargoes countries through U.S. financial institutions. Australian banking authorities have agreed to review these examinations. The $5.75 million paid by ANZ is substantially less than the fines paid by Lloyds, ABN Amro and USB for similar violations which were, respectively, $350 million, $80 million and $100 million.

An article in the Brisbane Times provides more background on ANZ’s dealing with embargoed countries:

ANZ initially became aware of the issue in late 2006 when regulators last year blocked a $US15,000 transaction involving the import of stone from Iran.

ANZ appointed Deloitte to conduct an independent investigation of more than 330,000 trade finance transactions for Australian and international clients going back five years. This ultimately turned up 42 deals found to have breached US economic bans on 13 countries. However the fine from the US Treasury only relates to 31 trade finance transactions involving parties in Sudan and Cuba.

The OFAC announcement states that ANZ didn’t voluntarily disclose the Sudan transactions. That is somewhat hard to reconcile with this report of the Deloitte investigation unless ANZ kept the Deloitte investigation internal until OFAC independently uncovered the Sudan transactions.

Permalink Comments (7)

Bookmark and Share


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