United States v. Heckenkamp

CourtCourt of Appeals for the Ninth Circuit
DecidedApril 4, 2007
Docket05-10322
StatusPublished

This text of United States v. Heckenkamp (United States v. Heckenkamp) is published on Counsel Stack Legal Research, covering Court of Appeals for the Ninth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
United States v. Heckenkamp, (9th Cir. 2007).

Opinion

FOR PUBLICATION UNITED STATES COURT OF APPEALS FOR THE NINTH CIRCUIT

UNITED STATES OF AMERICA,  Plaintiff-Appellee, No. 05-10322 v.  D.C. No. JEROME T. HECKENKAMP, CR-03-20041-JW Defendant-Appellant. 

UNITED STATES OF AMERICA,  No. 05-10323 Plaintiff-Appellee, v.  D.C. No. CR-00-20355-JW JEROME T. HECKENKAMP, OPINION Defendant-Appellant.  Appeal from the United States District Court for the Northern District of California James Ware, District Judge, Presiding

Argued and Submitted August 17, 2006—San Francisco, California

Filed April 5, 2007

Before: William C. Canby, Jr., Michael Daly Hawkins, and Sidney R. Thomas, Circuit Judges.

Opinion by Judge Thomas

3877 UNITED STATES v. HECKENKAMP 3881

COUNSEL

Benjamin Coleman, San Diego, California, for the appellant.

Hanley Crew, Assistant United States Attorney, San Fran- cisco, California, for the appellee.

OPINION

THOMAS, Circuit Judge:

In this case, we consider whether a remote search of com- puter files on a hard drive by a network administrator was jus- tified under the “special needs” exception to the Fourth Amendment because the administrator reasonably believed the computer had been used to gain unauthorized access to confidential records on a university computer. We conclude that the remote search was justified.

Although we assume that the subsequent search of the sus- pect’s dorm room was not justified under the Fourth Amend- ment, we conclude that the district court’s denial of the 3882 UNITED STATES v. HECKENKAMP suppression motion was proper under the independent source exception to the exclusionary rule.

I

In December 1999, Scott Kennedy, a computer system administrator for Qualcomm Corporation in San Diego, Cali- fornia, discovered that somebody had obtained unauthorized access to (or “hacked into,” in popular parlance) the compa- ny’s computer network. Kennedy contacted Special Agent Terry Rankhorn of the Federal Bureau of Investigation about the intrusion.

Kennedy was able to trace the intrusion to a computer on the University of Wisconsin at Madison network, and he con- tacted the university’s computer help desk, seeking assistance. Jeffrey Savoy, the University of Wisconsin computer network investigator, promptly responded to Kennedy’s request and began examining the university’s system. Savoy found evi- dence that someone using a computer on the university net- work was in fact hacking into the Qualcomm system and that the user had gained unauthorized access to the university’s system as well. Savoy was particularly concerned that the user had gained access to the “Mail2” server on the university sys- tem, which housed accounts for 60,000 individuals on campus and processed approximately 250,000 emails each day. At that time, students on campus were preparing for final exams, and Savoy testified that “the disruption on campus would be tremendous if e-mail was destroyed.” Through his investiga- tion of the Mail2 server, Savoy traced the source of intrusion to a computer located in university housing. The type of access the user had obtained was restricted to specific system administrators, none of whom would be working from the university’s dormitories.

Savoy determined that the computer that had gained unau- thorized access had a university Internet Protocol (“IP”) address1 1 An IP address is a standard way of identifying a computer that is con- nected to the Internet. An IP address is comprised of four integers less than 256 separated by periods. UNITED STATES v. HECKENKAMP 3883 that ended in 117. In addition, Savoy determined that Hecken- camp, who was a computer science graduate student at the university, had checked his email from that IP address 20 minutes before and 40 minutes after the unauthorized connec- tions between the computer at the IP address ending in 117, the Mail2 server, and the Qualcomm server. Savoy deter- mined that the computer at that IP address had been used reg- ularly to check Heckencamp’s email account, but no others. Savoy became extremely concerned because he knew that Heckenkamp had been terminated from his job at the univer- sity computer help desk two years earlier for similar unautho- rized activity, and Savoy knew that Heckenkamp “had technical expertise to damage [the university’s] system.”

Although Savoy was confident that the computer that had gained the unauthorized access belonged to Heckenkamp, he checked the housing records to ensure that the IP address was assigned to Heckenkamp’s dorm room. The housing depart- ment initially stated that the IP address corresponded to a dif- ferent room down the hall from Heckenkamp’s assigned room. The housing department acknowledged that the records could be inaccurate but stated that they would not be able to verify the location of the IP address until the next morning. In order to protect the university’s server, Savoy electroni- cally blocked the connection between IP address 117 and the Mail2 server.

After blocking the connection, Savoy contacted Rankhorn. After Savoy informed Rankhorn of the information he had found, Rankhorn told Savoy that he intended to get a warrant for the computer, but he did not ask Savoy to take any action or to commence any investigation.

Later that night, Savoy decided to check the status of the 117 computer from home because he was still concerned about the integrity of the university’s system. He logged into the network and determined that the 117 computer was not attached to the network. However, Savoy was still concerned 3884 UNITED STATES v. HECKENKAMP that the same computer could have “changed its identity,” so he checked the networking hardware to determine if the com- puter that was originally logged on at the 117 address was now logged on at a different IP address. His search confirmed that the computer was now logged on at an IP address ending in 120.

Based on this discovery, Savoy became even more con- cerned that the Mail2 server “security could be compromised at any time,” particularly because “the intruder at this point knows that he’s being investigated” and might therefore inter- fere with the system to cover his tracks. Savoy concluded that he needed to act that night.

Before taking action, Savoy wanted to verify that the com- puter logged on at 120 was the same computer that had been logged on at 117 earlier in the day. He logged into the com- puter, using a name and password he had discovered in his earlier investigation into the 117 computer. Savoy used a series of commands to confirm that the 120 computer was the same computer that had been logged on at 117 and to deter- mine whether the computer still posed a risk to the university server. After approximately 15 minutes of looking only in the temporary directory, without deleting, modifying, or destroy- ing any files, Savoy logged off of the computer.

Savoy then determined that “[the 120] machine need[ed] to get off line immediately or as soon as possible” based on “a university security need.” He contacted both Rankhorn and a Detective Scheller, who worked for the university police. Savoy informed them of his discoveries and concerns. Rank- horn asked Savoy to wait to take action because he was attempting to get a search warrant. However, Savoy felt that he needed to protect the university’s system by taking the machine off line immediately. Therefore, he made the deci- sion to coordinate with the university police to take the com- puter off line and to “let [the] university police coordinate with the FBI.” UNITED STATES v. HECKENKAMP 3885 Together with Scheller and other university police officers, Savoy went to the room assigned to Heckenkamp.2 When they arrived at the room, the door was ajar, and nobody was in the room. Savoy and Scheller entered the room and disconnected the network cord attaching the computer to the network.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Rakas v. Illinois
439 U.S. 128 (Supreme Court, 1979)
New Jersey v. T. L. O.
469 U.S. 325 (Supreme Court, 1985)
Griffin v. Wisconsin
483 U.S. 868 (Supreme Court, 1987)
Murray v. United States
487 U.S. 533 (Supreme Court, 1988)
Minnesota v. Olson
495 U.S. 91 (Supreme Court, 1990)
Ferguson v. City of Charleston
532 U.S. 67 (Supreme Court, 2001)
United States v. Angevine
281 F.3d 1130 (Tenth Circuit, 2002)
United States v. Frederick Silvestri, Elder
787 F.2d 736 (First Circuit, 1986)
United States v. Michael Allen Vasey
834 F.2d 782 (Ninth Circuit, 1987)
United States v. Thurman Reed, Jr.
15 F.3d 928 (Ninth Circuit, 1994)
United States v. Mark L. Simons
206 F.3d 392 (Fourth Circuit, 2000)
United States v. Kevin Joseph Bautista
362 F.3d 584 (Ninth Circuit, 2004)
United States v. Brandon Michael Lifshitz
369 F.3d 173 (Second Circuit, 2004)
United States v. Frank Gary Buckner
473 F.3d 551 (Fourth Circuit, 2007)
Leventhal v. Knapek
266 F.3d 64 (Second Circuit, 2001)
Trulock v. Freeh
275 F.3d 391 (Fourth Circuit, 2001)
Henderson v. City of Simi Valley
305 F.3d 1052 (Ninth Circuit, 2002)
United States v. Broadhurst
805 F.2d 849 (Ninth Circuit, 1986)

Cite This Page — Counsel Stack

Bluebook (online)
United States v. Heckenkamp, Counsel Stack Legal Research, https://law.counselstack.com/opinion/united-states-v-heckenkamp-ca9-2007.