Feb 25 2010

DHS accomplices face legal liability

The most recently filed lawsuit to result from detention of a would-be traveler at a TSA checkpoint highlights an interesting pattern:

While Federal departments themselves, and their agents in their official capacities, have thus far largely escaped legal liability for interference with travelers’ rights, multiple lawsuits against individuals who have enforced secret DHS directives — including DHS officers in their individual capacities as well as city, state, and tribal police acting as their accomplices and/or at their behest — are moving forward.  Yet at the same time, the DHS continues to use local law enforcement officers to carry out its secret orders, and has in some cases revealed policies directing DHS agents to take a literal “hands-off” attitude themselves, even while calling in local police to enforce what are at root (illegal) Federal orders.

Here’s a round-up of some pending cases across the country, leading up to the latest, with apologies for the sometimes tortured procedural histories which tend to characterize such cases and obscure the real issues: Read More

Feb 23 2010

DHS using ICAO again for policy laundering

News reports about recent diplomatic initiatives by the US Department of Homeland Security suggest that the DHS may once again be using the International Civil Aviation Organization (ICAO) as a vehicle for policy laundering.

In the past, ICAO has been the focus of attention for its role in the imposition of RFID passports and the associated systems of automated monitoring and control of international travel.

Now, the DHS appears to be trying to use ICAO as the vehicle through which to impose its ideas of passenger searching (virtual strip-search machines) and passenger surveillance (pre-flight government access to PNR data and its use in conjunction with identity-linked travel histories and personal profiles for control of who is allowed to fly)  as global norms.

Secretary of Homeland Security Napolitano, accompanied by Asst. Secretary for Policy David Heyman (successor to former NSA and DHS attorney Stewart Baker), has been barnstorming the globe in pursuit of this agenda over the last month.  She met with ICAO officials and their airline industry partners at IATA in Geneva, attended a regional European ministerial meeting on aviation security in Spain which issued a joint statement agreeing to “Promote international co-ordination … through ICAO”, followed by a regional ICAO meeting in Mexico for the Americas and the Caribbean (attended by ICAO’s Secretary General) which declared participating goverments’ commitment to “systematically collaborate within ICAO… with a view to convene both international expert and intergovernmental meetings to agree upon actions in the following fields:”

  • Broaden existing cooperation mechanisms among our countries and with other parties to the Chicago Convention, and the civil aviation industry, for information exchange …
  • Share best practices in a range of areas related to civil aviation, such as … screening and inspection techniques, airport security, behavioral detection, passenger targeting analysis…
  • Utilize modern technologies to detect prohibited materials and to prevent the carriage of such materials on board aircraft.
  • Transmit in a timely manner passengers’ information prior to takeoff to effectively support screening … as well as develop and improve compatible systems for the collection and use of advance passenger information (API) and passenger name record (PNR) information.

In a detailed video news release, Napolitano herself described this as “an unprecedented international initiative” centered on “a series of regional meetings around the globe facilitated by ICAO”:

There were four broad areas for discussion: Information sharing, passenger vetting, technology, and international standards…. Look for announcement in each of these four areas in the weeks ahead.

The agenda and the forum could not be more clear: Unless defenders of civil liberties and human rights mobilize effective opposition, the goal of the US and the DHS is for ICAO to put forward “international standards”, effectuated by national laws on “compliance with standards”, which will mandate virtual strip-search machines (“modern technology”), worldwide government access to PNR data, and government “vetting” (identity-based and permission-based control) of international air travelers.  That is perfectly in line with the 10-year plan of ICAO’s working group on Machine-Readable Travel Documents (MRTD), “MRTD Vision 2020,” as laid out in the latest ICAO MRTD Report.

ICAO is a UN-affiliated intergovernmental organizing most of whose decisions are made in invitation-only working groups. The interests of citizens are supposed to be represented in ICAO decision-making by their national governments, but national delegations to ICAO are invariably drawn from security, surveillance, law enforcement, and aviation regulatory agencies, and have never included representatives of data protection, civil liberties, or human rights authorities.

In effect, ICAO’s decisions reflect the desires of the world’s police.  By enacting national laws requiring “compliance” with ICAO “standards”, national governments can effectively outsource national law-making to those police, while justifying repressive measures (which their own representatives have proposed and championed at ICAO) as being the reult of an extenral, international mandate for which they aren’t responsible. Policy laundering.

ICAO’s importance to the DHS (and its counterparts in Europe and elsewhere) is heightened by the likelihood that, in the wake of the precedent set by its rejection of the SWIFT agreement on financial transaction data sharing with the US government, the European Parliament will reject the similar PNR agreement for travel transaction data sharing with the US government. The DHS had been pressuring the Europarl to fast-track approval of the PNR agreement. With the writing on the wall that the PNR agreement is headed for defeat in the Europarl, the DHS is already making it clear that ICAO standards are their back-door “Plan B” for how to impose a global PNR and identity-based travel sureveillance and control regime.  They are losing in Brussels, so they are trying to shift to more “Big Brother friendly” ICAO forums in Geneva and Montreal.

ICAO draws on invited technical experts from the aviation industry, but unfortunately their interests in surveillance for commercial purposes coincide with those of the police in the same surveillance for political purposes. Airlines and other travel companies are happy to help governments monitor travelers, as long as they get get paid for collecting the data and are allowed to use it themselves too. We’ve heard them tell ICAO so in so many words.

ICAO’s dual secretariats in Montreal and Geneva, and its process in which most decisions have effectively been made before they are presented to rubber-stamp plenaries, makes effective civil society participation difficult without long-term commitment and international cooperation.  A useful model is provided by environmental activists, who have formed a single-issue international NGO coalition for the sole purpose of obtaining accreditation and observer status with ICAO. Despite previous joint appeals to ICAO by an ad hoc international civil liberties coalition, human rights groups haven’t yet formalized their coalition or sought observer status with ICAO, and have had no presence at ICAO meetings or working groups.

If you are interested in working with the Identity Project to get our voices heard at ICAO, please get in touch — before its too late.

Feb 19 2010

TSA, DHS unresponsive to human rights complaints

After two months, we’ve gotten an initial round of non-responses from the DHS and TSA to our complaint that their procedures for subjecting holders of certain passports to more intrusive search and/or interrogation as a condition of domestic common-carrier air travel violate published TSA civil rights policies, Federal laws, Constitutional rights, and rights guaranteed by international human rights treaties.

The Director of the TSA’s Office of Civil Rights and Liberties refers vaguely and inaccurately to “our letter expressing concerns about recent press reports” (in fact, our letter said nothing about any press reports), but makes no mention of our complaint that specific TSA practices and procedures are illegal, or what if anything any TSA or DHS compliance, oversight, or enforcement office intends to do about it.

The closest they come to engaging with the basis of our complaint is a sentence only a lawyer could love: “Please note that a passport-issuing country is not coextensive with a person’s national origin.”  It remains to be seen what they think is better evidence of national origin than a passport.  Will they issue yet another new travel credential by which someone with a Pakistani passport can establish, for example, that their nation of “origin” is India, and thus that they are not “from” a “country of interest”?  Or vice versa? What are they thinking?

They also completely ignore our mention of international treaties, which are likely to become a growing issue not just for the DHS and TSA but for their counterparts imposing similar restrictions on freedom of movement in other countries, such as mandatory submission to virtual strip searches.

We’ve sent the TSA and DHS a follow-up letter reminding them that we still expect, and are entitled to, a response.

Meanwhile, the DHS has announced similar procedures for more intrusive search and perhaps interrogation of travelers “coming from” a larger list of “countries of interest”.    It’s unclear — since of course the procedures aren’t enforceable rules and are being kept secret, whether “coming from” means having flown directly from, having visited earlier on the same trip, having visited within a specified time period (the life of the current passport?), having ever in one’s life visited, or carrying a passport issued by any of these countries.  These new procedures have prompted a more recent joint complaint similar to ours from a broad coalition of civil rights organizations, as well as separate complaints from some of these groups.

Feb 08 2010

DHS exempts dossiers used for “targeting” from the Privacy Act

In a final rule published last week at 75 Federal Register 5487-5481, the Customs and Border Protection (CBP) division of the Department of Homeland Security has exempted most of the data used by the illegal “Automated Targeting System – Passenger” (ATS-P) from the various requirements of the Privacy Act that information used to make decisions about individuals must be accessible to them on request, accurate, relevant, collected directly from the data subjects whenever possible, and so forth.

The proposal to exempt ATS records from the Privacy Act has been pending for more than two years. In the final rule, the Obama administration adopts, with no changes whatsoever, all of the exemptions proposed by the DHS under the previous administration.  The analysis accompanying the final rule acknowledges, but dismisses more or less out of hand, our comments from two years ago objecting to the proposed exemptions as illegal.  (These followed two sets of comments we filed in 2006, when the ATS itself was first disclosed, objecting to the entire system as illegal.)

On the same day last week, the DHS published a separate final rule similarly exempting from the Privacy Act portions of the “Border Crossing Information” (BCI) system, a log of each person’s entries to and exits from the U.S. which was first disclosed as a part of ATS before being declared a separate system of records. The final BCI exemption rule similarly adopted all of the proposals the previous administration has proposed in 2008, and dismissed our objections to its illegality out of hand.

You can still request your own ATS and other travel records from the DHS.  Even if the newly-promulgated exemptions are upheld, they leave you entitled to substantial portions of your ATS dossier.  We are continuing to pursue our own pending Privacy Act requests and appeals, some of which are themselves more than two years old and all of which were made before the new exemptions were finalized and thus are not subject to the “exemptions”.

The Privacy Act gives agencies the authority to exempt certain types of information, by rulemaking, from certain of the requirements of the Privacy Act.  The rules published last week are, however, the first time that the DHS has attempted to  exercise this authority with request to ATS records.

In the meantime, the CBP has simply ignored the Privacy Act and its lack of exemptions entirely: Every response we have seen to a request pursuant to the Privacy Act for PNR or other ATS data has been processed by the CBP under the Freedom of Information Act (FOIA) instead of the Privacy Act.  Information exempt from disclosure under FOIA has been withheld or redacted, citing specific FOIA exemptions, even when that same information was required by the Privacy Act to be disclosed. This has been in flagrant violation of the Privacy Act, which has different disclosure requirements and exemptions which only partially overlap with those of FOIA. So far as we know, however, CBP and DHS have never responded to a Privacy Act appeal of these wihtholdings and redactions at all — some of our Privacy Act appeals are more than two years old — and while there have been several lawsuits under FOIA concerning ATS data, there have been none yet under the Privacy Act.

Our primary objection is to the very existence of a system under which the government requires common carriers to identify each would-be traveler and get the government’s permission (“clearance”) before they can travel.  Such a scheme is made far worse, however, when those “fly/no-fly” or “cleared/inhibited/not cleared” decisions are made not only in secret by unknown bureaucrats, not judges, and on the basis of secret files about each citizen.

The new exemptions, applicable to future requests for ATS records, are sweeping.  But we are particularly disturbed that the exemption rules purport to authorize the DHS to collect and use an entirely undefined and open-ended category of commercial data obtained from airlines as part of their Passenger Name Records (PNR), and withhold that commercial data, on grounds of “business confidentiality”, from the would-be travelers against whom it is used.

That exemption for commercial data in PNRs creates a limitless loophole through which the DHS could secretly make use, in passenger profiling and “targeting” decisions, of commercial data of any sort.  As long as it is channeled to the DHS through inclusion in PNRs (which as commercial records are themselves subject to no U.S. privacy or disclosure requirements at all), the DHS could base passenger “targeting” decisions on derogatory free-text remarks by customer service representatives, commercial blacklists, credit scores, or records or ratings by data aggregators.  But those are not legal grounds to prevent travel by common carrier.

Feb 01 2010

Albuquerque police still pressing charges against traveler who tried to exercise his rights

The trial originally scheduled for this Friday of Phil Mocek, who was arrested by local police at a TSA checkpoint in the Albuquerque airport in November, has been postponed at least until early May.  But that only happened after he retained retained private defense counsel, at considerable personal expense. You can help out by making a donation to his defense fund.

Mocek has made no comment, on the advice of his attorney.  But from news reports, it appears that he was arrested in retaliation for trying to exercise his right to travel without showing tangible evidence of his identity, and or for recording and/or photographing the TSA’s response to his assertion of his rights.  Since everything he did was entirely within his rights, and the TSA agents have no authority to make arrests, they followed their de facto standard operating procedures by calling in the local police and getting them to trump up an array of false and/or unconstitutional charges under local and state law: criminal trespass (Albuquerque Code of Ordinances § 12-2-3), resisting, obstructing or refusing to obey a lawful order of an officer (§ 12-2-19), concealing identity with intent to obstruct, intimidate, hinder or interrupt (§ 12-2-16), and disorderly conduct (NMSA § 30-2-1). [Note: It appears that direct links to sections of the Albuquerque Code of Ordinances will work only after you click on the Albuquerque Code of Ordinances link and then on either “frames” or “no frames”, to set the required cookies in your Web browser.] The “trespass” charge seems particularly problematic in light of the fact that the airport is publicly owned and that Mocek was attempting to exercise his right to travel by common carrier, a right not only guaranteed by Federal law but protected by explicit Federal statutory preemption against any local or state interference.

Nothing we’ve learned has suggested that any of these charges are supported by the facts, or are other than retaliation.  So we’re disturbed that the prosecutor hasn’t dropped the charges yet, even though a review of the evidence and the case should have made clear that these charges were unfounded.  We hope the district attorney will come to their senses and drop the charges.

[For the status of the case, go to the county court website, complete the “captcha”, and enter “2573709” in the “criminal case number” field.  Documents obtained by Mr. Mocek in response to his requests under New Mexico’s public records laws, including police reports and audio recordings, have been posted here.  For further updates, see the ongoing discussion in the travel “security” forum at Flyertalk.com.]

Jan 08 2010

Lessons from the case of the man who set his underpants on fire

We’ve been having a hard time keeping up with events over the last few weeks. Every time we think the keystone cops from the Department of Homeland Security can’t come up with anything dumber to do, they prove us wrong. At this point we’re not sure who is most deserving of derision: (1) the would-be terrorist who tried but failed to explode his underpants, and succeeded only in burning his balls, (2) the goons the TSA sent to intimidate bloggers who tried to tell travelers what to expect when they got to the airport, and find out who had “leaked” the TSA’s secrets, but who left their own notebook of “secret” notes about their investigation of this and other cases behind in a public place, or (3) the TSA agents who felt so ill at the smell of honey they found in checked luggage that they checked themselves into a hospital and shut down the airport. It’s a tough call. Leave your votes, or other nominations, in the comments.

What’s most striking about the government’s response to this unsuccessful bombing attempt is the complete lack of any rational relationship between the actions that have been taken and are being proposed, any analysis of which of these and similar tactics did or did not contribute to the success or failure of the Christmas Day attack on Northwest Airlines flight 253, and any likelihood that they would make future attempts at terrorism less likely to succeed.

Now that the dust has settled a bit, perhaps it’s time to survey the security, security theater, surveillance, and travel control techniques at issue: Read More

Dec 13 2009

Congress members: “Kill the messenger!”

Three members of Congress have sent a joint letter to Secretary of Homeland Security Janet Napolitano about the posting of a version of the TSA’s Screening Management Standard Operating Procedures on a Federal government website.  (We’re still pursuing our FOIA appeal for the current version and related documents, which the TSA has been stonewalling, as well as our complaint against the blatantly discriminatory portions of the procedures.)

The signers of the letter to the DHS Secretary include Rep. Pete King, ranking Republican members of the House Homeland Security Committee, which has scheduled a hearing on the release of the TSA procedures this Wednesday, December 16, 2009.  (The Committee’s Chairman has already sent the TSA some questions of his own in advance of the hearing.)

Among the questions the three Representatives ask are the following:

6. How has the Department of Homeland Security and the Transportation Security Administration addressed the repeated reposting of this security manual to other websites and what legal action, if any, can be taken to compel its removal?

7. Is the Department considering issuing new regulations pursuant to its authority in section 114 of title 49, United States Code, and are criminal penalties necessary or desirable to ensure such information is not reposted in the future?

Perhaps these members of Congress haven’t bothered to read the current law that protects the right to “use” (such as by removing the black blocks that were coded to appear over portions of the document) and “redissemination” of documents (such as by reposting on other websites), once they are made available to the public as this one was on a public government website:

44 U.S.C. 3506(d)

With respect to information dissemination, each agency shall—

(1) ensure that the public has timely and equitable access to the agency’s public information, including ensuring such access through—
(A) encouraging a diversity of public and private sources for information based on government public information;
(B) in cases in which the agency provides public information maintained in electronic format, providing timely and equitable access to the underlying data (in whole or in part); and
(C) agency dissemination of public information in an efficient, effective, and economical manner;

(2) regularly solicit and consider public input on the agency’s information dissemination activities;

(3) provide adequate notice when initiating, substantially modifying, or terminating significant information dissemination products; and

(4) not, except where specifically authorized by statute—
(A) establish an exclusive, restricted, or other distribution arrangement that interferes with timely and equitable availability of public information to the public;
(B) restrict or regulate the use, resale, or redissemination of public information by the public;
(C) charge fees or royalties for resale or redissemination of public information; or
(D) establish user fees for public information that exceed the cost of dissemination.

Dec 10 2009

TSA discloses discriminatory and improperly withheld procedures

There are no legally binding rules (other than those provided by the federal Privacy Act, the U.S. Constitution, and international human rights treaties, all of which the TSA routinely ignores) specifying the limits of TSA authority at checkpoints, what you do and don’t have to do, and which questions you have to answer or orders you have to obey.

So the traveling public, and public interest organizations like the Identity Project, have been reduced to trying deduce the de facto “rules” from the TSA’s internal procedures manuals and directives to its staff, using the Freedom of Information Act — to the extent that we’ve been able to find out what documents to ask for by name, and that the TSA has been willing to release them, usually in incomplete and censored (“redacted”) form.

Now the TSA has done us a favor by posting an unredacted version of the document of which we’ve received only portions of an earlier version, and the complete current version of which is the subject of one of our current FOIA requests: the TSA’s “Screening Management Standard Operating Procedures (SOP)”.

In posting the document on a federal government website (fbo.gov, for “Federal Business Opportunities”) as part of the public specifications for bidders on a TSA contract, the TSA added red outlines highlighting certain portions of the PDF document, and coded black rectangles to overlay them as a separate layer of the PDF file.  But they left the complete text and images unredacted, so that they could be selected, cut, and pasted into a text editor from any PDF reading software.  For your convenience, we’ve posted a copy with the black blocks removed, but the red highlights and everything else retained, so you can see what portions the TSA might have been trying (ineptly) to hide.  Despite false TSA claims that it “was immediately taken down from the Web site”, as of today the original version is still available on the same government site, although at a slightly more obscure URL.

If, like us, you were hoping to learn the non-rules for TSA checkpoints and “screening” (search and interrogation), the Screening Management SOP is disappointing.  It’s mostly about bureaucratic procedures for checkpoint supervisors.  There’s been a lot of excessive commotion about whether its posting was a security breach or provides a “road map for terrorists” (it doesn’t), but little attention is being paid to some more significant things it reveals.

Here’s what we think is really significant about this document, and its release, and what we’re doing next: Read More

Nov 17 2009

Traveler arrested at Albuquerque TSA checkpoint

A traveler attempting to return home from a political conference (a gathering clearly protected by the First Amendment right to assemble) was arrested at a TSA checkpoint at the airport in Albuquerque, New Mexico on Sunday after he (1) politely declined to show tangible evidence of his identity and (2) began recording audio, video, and/or still photographs of the incident with a handheld device. The traveler, Phil Mocek, has been a regular participant in discussions of ID requirements and TSA procedures on Flyertalk.com, and has been mentioned here before for his efforts to uncover what the “rules” if any) are at TSA checkpoints. According to initial reports and discussion elsewhere, he was released Monday, after a night in jail, and charged with criminal trespass (Albuquerque Code of Ordinances § 12-2-3), resisting, obstructing or refusing to obey a lawful order of an officer (§ 12-2-19), concealing identity with intent to obstruct, intimidate, hinder or interrupt (§ 12-2-16), and disorderly conduct (NMSA § 30-2-1). [Note: It appears that direct links to sections of the Albuquerque Code of Ordinances will work only after you click on the Albuquerque Code of Ordinances link and then on either “frames” or “no frames”, to set the required cookies in your Web browser.]

As of now, it’s unclear whether the arrest was primarily in retaliation for Mr Mocek’s declining to proffer evidence of his identity or his recording of audio, video, and/or still photographs.  It’s also unclear whether he was arrested by, or at the behest of, Feds or local or state law enforcement officers (or TSA contractor rent-a-cops?), an issue that has figured prominently and sometimes decisively in other ID-demand and checkpoint cases.

We wish Mr. Mocek success in defending against these bogus charges and obtain obtaining redress from those responsible. We’ll have more to say as soon as we have a chance to see the actual complaint.

(We’ve been in touch with Mr. Mocek. As of now, he can’t comment on what happened, on the advice of counsel.  But if you’d like to help him fight back, you can contribute to his legal defense fund.)

[UPDATE: The trial which was scheduled to begin June 14, 2010 has been postponed. Check  our FAQ about the case or the court calendar for further updates as soon as they are available. For the status of the case, go to the county court website, complete the “captcha”, and enter “2573709” in the “criminal case number” field.  Documents obtained by Mr. Mocek in response to his requests under New Mexico’s public records laws, including police reports and audio recordings, have been posted here.  For further updates, see the ongoing discussion in the travel “security” forum at Flyertalk.com. Mr. Mocek is represented by private defense counsel, at considerable personal expense. You can help by making a donation to his defense fund.]