Kaveh Waddell | The Atlantic | February 13, 2017 | 0 Comments

A NASA Engineer Was Required to Unlock his Phone at the Border

A CBP Officer processes an incoming passenger at the Newark International Airport in 2010. James Tourtellotte / CBP file photo

Everything started to go wrong just after 5 a.m., when Sidd Bikkannavar scanned his passport, placed his hand on a fingerprint reader, and watched as the automated customs kiosk spat out a receipt with a black X drawn across it.

It was January 31. Bikkannavar had just arrived at Houston’s George Bush Intercontinental Airport after a nine-hour flight from Santiago, Chile, where he’d competed in a two-week race from the southern tip of the country to its capital in a solar-powered car. In a few hours, he would board a connecting flight back home to California, where he’s worked at the NASA Jet Propulsion Laboratory in Pasadena for over a decade. Bikkannavar, a 35-year-old engineer who was bornin Pasadena, designs technology for space telescopes like the enormous James Webb telescope that’s set to be launched into orbit in 2018.

But before boarding his next plane, Bikkannavar would have to clear customs and immigration. Usually, it’s a breeze: He’s a part of the Customs and Border Protection Global Entry program, whose members are waved through the line after just scanning their passport and fingerprints. But the receipt with the X meant things wouldn’t go so smoothly this time.

He presented it to an agent and was promptly led to a holding room. The customs checkpoint had only been open for business for 10 or 20 minutes, so the room was mostly empty. But several occupied cots were arranged in the room, suggesting that some people had spent the night. A table was arranged with peanut butter biscuits, crackers, and instant noodle cups.

After about 40 minutes, Bikkannavar was called up. He was led to a small door labeled “Interview Room,” and seated across from a border agent, who said he needed to search Bikkannavar’s things.

Bikkannavar asked why he was singled out for questioning, but the agent wouldn’t tell him. There can't have been any suspicion about his identity, Bikkannavar thought: Not only was he a member of Global Entry—a program that requires applicants to submit to an extensive background check and fingerprinting—but his work at NASA requires him to be vetted regularly by the federal government. He was, he thought, a particularly known entity.

“I’m always super cooperative about this stuff. This isn’t a story about me being super offended and being inconvenienced,” Bikkannavar told me. “I get it. I was with them up to this point.”

But the agent never touched Bikkannavar’s bag—instead, he asked for his smartphone. Bikkannavar handed it over, assuming the agent might just want to inspect it to make sure it wasn’t something more dangerous in disguise. The agent turned it over in his hand and asked for the passcode.

Bikkannavar was taken aback. The phone was Jet Propulsion Lab property, he explained, pointing out the barcode stuck to the back. It was his duty to protect its sensitive contents, and he couldn’t give out the passcode.

The border agent wouldn’t relent. He needed to access the device, he said, and had the authority to do so. He’d handed Bikkannavar a document titled “Inspection of Electronic Devices” when they first sat down, and Bikkannavar gave it a quick scan. The document claimed that CBP had the right to search “all persons, baggage, and merchandise arriving in, or departing from, the United States.” On the backside, in fine print at the bottom, there was a section with the heading, “Consequences of Failure to Provide Information.” The section said that giving up the information is “mandatory” and not cooperating could lead to the “detention and/or seizure” of the electronic device in question.

Bikkannavar didn’t feel like he had a choice. “I’d read the headlines of people being stranded in airports and having problems entering the country, so I was still in the mode of being as cooperative and polite and courteous as possible,” he said to me. Just a few days prior, President Donald Trump had signed an executive order that excluded nationals of seven Muslim-majority countries from entering the U.S. Bikkannavar, a U.S. citizen, would not have been affected by the new policy, which has since been temporarily put on pause by a federal court—but turmoil and confusion at the border had led to many people being improperly detained.

What’s more, he said, he wasn’t sure of his legal rights in that moment. In the CBP interview room, did he still have the Fourth Amendment rights that he’d have if he were stopped by police on the street?

That’s a question I addressed in a story last week. Although the Fourth Amendment protects people from unreasonable search and seizure in the U.S., border agents have a very wide latitude to conduct searches—and often do so in situations that wouldn’t meet the standards of reasonable suspicion required elsewhere in the country. A new proposal from Homeland Security Secretary John Kelly would codify invasive digital searches into policy: He recently told a panel of U.S. representatives that he’s considering a rule that would allow agents to turn away visitors if they didn’t submit their browsing history and device or account passwords. It’s not clear whether the proposal would apply to U.S. citizens as well.

Bikkannavar gave up the phone’s passcode to the agent, who immediately wrote it down on a notepad. He was led back to the waiting room, where he sat for another 30 minutes.

The agent eventually emerged with Bikkannavar’s phone and handed it back to him. CBP had run “algorithms” on the device, the agent said, to search for threats. It came up clean, so Bikkannavar was free to go. His flight to Los Angeles was boarding, so he ducked out of the office without asking the agent what had been done to the phone in detail. But given the circumstances, and the document he’d been given, Bikkannavar felt it safe to assume that CBP had copied the contents of his work phone.

As soon as he touched down at LAX, Bikkannavar headed into work. “The second that phone was out of my sight and they had the PIN—right away, I knew I’m reporting the hell out of this,” he said. “This is a huge, huge violation of my work policy. This is a matter of great concern.” Bikkannavar declined to share details about what sort of information was on the phone. But since it was connected to both personal and sensitive work accounts, losing control of the device was no small matter.

He delivered the phone to JPL’s technology department and told them what had happened; they took in the phone for examination and gave him a loaner. He also alerted JPL’s security services, and spoke to members of JPL’s Office of General Counsel.

He deactivated his accounts on social media, fearing they may have been compromised. Once he was convinced they weren’t, he came back online. Last weekend, he wrote a short post detailing what had happened, to reassure friends who were might have been worried about his radio silence. Unexpectedly, it exploded. Screenshots of the post went viral on Twitter, and once a friend asked him to set the post to be viewable to the public, it was shared on Facebook thousands of times. (Bikkannavar took down the public post over the weekend, to head off speculation and political commentary on his page. “It served its purpose in informing my friends,” he told me.)

A representative for Customs and Border Patrol declined to comment on the specific incident in Houston. “CBP officers are charged with enforcing not only immigration and customs laws, but they also enforce over 400 laws for 40 other agencies,” the spokesperson said.

It’s still unclear what was done to Bikkannavar’s phone while it was in CBP custody. The CBP document says that after reviewing the information on a seized device, “if there exists no probable cause to seize it, CBP will not retain any copies” of the information. It’s not clear whether information from Bikkannavar’s phone was retained or deleted, if it was indeed copied.

Bikkannavar says he doesn’t feel like his privacy was unduly violated. But his work phone was connected to some of his personal accounts, and he worries that the search compromised the privacy of his more reclusive friends and family.

“To get my information and data is one thing; to bring those other people into it is another thing,” Bikkannavar said. “They didn’t choose it. Because of the kinds of things I work on, I gave up my privacy to the government a long time ago. But they didn’t.”

Though he’s submitted to government background checks before, Bikkannavar says he was initially reluctant to go public with his story. But widespread interest in his Facebook post, plus a few nudges from close friends, made him change his mind. Plus, he says, his deep roots in the country upend assumptions that invasive vetting measures are keeping the U.S. safe by investigating immigrants with dodgy backgrounds. His mother’s ancestors fought in the American revolution, he says, and two of his grandparents worked at JPL. One of his younger brothers is a Marine, he says, and the other is enlisting this year.

“I’m definitely not an immigrant or a newcomer to the country, despite my foreign-sounding name and the color of my skin,” Bikkannavar said. “If this had happened to a guy who’s just like me, but works in some other job, it’s not as black-and-white of a story. But there couldn’t be a person that’s more safe or more vetted than me.”

Comments
JOIN THE DISCUSSION

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

    Download
  • Cyber Risk Report: Cybercrime Trends from 2016

    In our first half 2016 cyber trends report, SurfWatch Labs threat intelligence analysts noted one key theme – the interconnected nature of cybercrime – and the second half of the year saw organizations continuing to struggle with that reality. The number of potential cyber threats, the pool of already compromised information, and the ease of finding increasingly sophisticated cybercriminal tools continued to snowball throughout the year.

    Download
  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

    Download
  • GBC Issue Brief: The Future of 9-1-1

    A Look Into the Next Generation of Emergency Services

    Download
  • GBC Survey Report: Securing the Perimeters

    A candid survey on cybersecurity in state and local governments

    Download
  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.

    Download
  • eBook: State & Local Cybersecurity

    CenturyLink is committed to helping state and local governments meet their cybersecurity challenges. Towards that end, CenturyLink commissioned a study from the Government Business Council that looked at the perceptions, attitudes and experiences of state and local leaders around the cybersecurity issue. The results were surprising in a number of ways. Learn more about their findings and the ways in which state and local governments can combat cybersecurity threats with this eBook.

    Download

When you download a report, your information may be shared with the underwriters of that document.