2 Computer Fraud and Abuse Act (CFAA) 2 Computer Fraud and Abuse Act (CFAA)
Weeks 3 & 4
Weeks 3 & 4 (Oct. 11 & 18, 2023): Computer Fraud and Abuse Act (CFAA)
The primary federal anti-hacking law in the United States is the Computer Fraud and Abuse Act (CFAA), originally enacted in 1986. This will be a two-part unit, so we'll spend two weeks with the CFAA. The first week will focus on understanding the basics about the statute and what it means. In the second week, we'll study courts' interpretations of the CFAA, ranging from the first CFAA criminal prosecution back in the 1980s, up to the Supreme Court's first-ever CFAA case, 2021's Van Buren v. United States.
For the first lecture on the CFAA (Oct. 11), it will be helpful if you have seen the movie Die Hard before you arrive in class.
2.1 CFAA unit 1 2.1 CFAA unit 1
Week 3
2.1.1 Computer Fraud and Abuse Act, 18 U.S.C. 1030 2.1.1 Computer Fraud and Abuse Act, 18 U.S.C. 1030
Here is a redacted Word document, in which I've made the same elisions as I've made in the text below (to take out the parts of the statute that you don't need to read). Here is the full, unredacted statute.
18 U.S.C. § 1030
United States Code > TITLE 18. CRIMES AND CRIMINAL PROCEDURE (§§ 1 — 6005) > Part I. Crimes (Chs. 1 — 123) > CHAPTER 47. Fraud and false statements (§§ 1001 — 1070)
1030. Fraud and related activity in connection with computers
(a) Whoever—
(1) having knowingly accessed a computer without authorization or exceeding authorized access, and by means of such conduct having obtained information that has been determined by the United States Government pursuant to an Executive order or statute to require protection against unauthorized disclosure for reasons of national defense or foreign relations, or any restricted data, as defined in paragraph y.[(y)] of section 11 of the Atomic Energy Act of 1954 [42 U.S.C. § 2014(y)], with reason to believe that such information so obtained could be used to the injury of the United States, or to the advantage of any foreign nation willfully communicates, delivers, transmits, or causes to be communicated, delivered, or transmitted, or attempts to communicate, deliver, transmit or cause to be communicated, delivered, or transmitted the same to any person not entitled to receive it, or willfully retains the same and fails to deliver it to the officer or employee of the United States entitled to receive it;
(2) intentionally accesses a computer without authorization or exceeds authorized access, and thereby obtains—
(A) information contained in a financial record of a financial institution, or of a card issuer as defined in section 1602(n) of title 15, or contained in a file of a consumer reporting agency on a consumer, as such terms are defined in the Fair Credit Reporting Act (15 U.S.C. 1681 et seq.);
(B) information from any department or agency of the United States; or
(C) information from any protected computer;
(3) intentionally, without authorization to access any nonpublic computer of a department or agency of the United States, accesses such a computer of that department or agency that is exclusively for the use of the Government of the United States or, in the case of a computer not exclusively for such use, is used by or for the Government of the United States and such conduct affects that use by or for the Government of the United States;
(4) knowingly and with intent to defraud, accesses a protected computer without authorization, or exceeds authorized access, and by means of such conduct furthers the intended fraud and obtains anything of value, unless the object of the fraud and the thing obtained consists only of the use of the computer and the value of such use is not more than $5,000 in any 1-year period;
(5)
(A) knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer;
(B) intentionally accesses a protected computer without authorization, and as a result of such conduct, recklessly causes damage; or
(C) intentionally accesses a protected computer without authorization, and as a result of such conduct, causes damage and loss. [;]
(6) knowingly and with intent to defraud traffics (as defined in section 1029 [18 U.S.C. § 1029]) in any password or similar information through which a computer may be accessed without authorization, if—
(A) such trafficking affects interstate or foreign commerce; or
(B) such computer is used by or for the Government of the United States; [or]
(7) with intent to extort from any person any money or other thing of value, transmits in interstate or foreign commerce any communication containing any—
(A) threat to cause damage to a protected computer;
(B) threat to obtain information from a protected computer without authorization or in excess of authorization or to impair the confidentiality of information obtained from a protected computer without authorization or by exceeding authorized access; or
(C) demand or request for money or other thing of value in relation to damage to a protected computer, where such damage was caused to facilitate the extortion;
shall be punished as provided in subsection (c) of this section.
(b) Whoever conspires to commit or attempts to commit an offense under subsection (a) of this section shall be punished as provided in subsection (c) of this section.
(c) The punishment for an offense under subsection (a) or (b) of this section is—
[…]
(4)
(A) […] a fine under this title, imprisonment for not more than 5 years, or both, in the case of—
(i) an offense under subsection (a)(5)(B), which does not occur after a conviction for another offense under this section, if the offense caused (or, in the case of an attempted offense, would, if completed, have caused)—
(I) loss to 1 or more persons during any 1-year period (and, for purposes of an investigation, prosecution, or other proceeding brought by the United States only, loss resulting from a related course of conduct affecting 1 or more other protected computers) aggregating at least $5,000 in value;
(II) the modification or impairment, or potential modification or impairment, of the medical examination, diagnosis, treatment, or care of 1 or more individuals;
(III) physical injury to any person;
(IV) a threat to public health or safety;
(V) damage affecting a computer used by or for an entity of the United States Government in furtherance of the administration of justice, national defense, or national security; or
(VI) damage affecting 10 or more protected computers during any 1-year period; […]
(d)
(1) The United States Secret Service shall, in addition to any other agency having such authority, have the authority to investigate offenses under this section.
[…]
(e) As used in this section—
(1) the term “computer” means an electronic, magnetic, optical, electrochemical, or other high speed data processing device performing logical, arithmetic, or storage functions, and includes any data storage facility or communications facility directly related to or operating in conjunction with such device, but such term does not include an automated typewriter or typesetter, a portable hand held calculator, or other similar device;
(2) the term “protected computer” means a computer—
(A) exclusively for the use of a financial institution or the United States Government, or, in the case of a computer not exclusively for such use, used by or for a financial institution or the United States Government and the conduct constituting the offense affects that use by or for the financial institution or the Government;
(B) which is used in or affecting interstate or foreign commerce or communication, including a computer located outside the United States that is used in a manner that affects interstate or foreign commerce or communication of the United States; or
(C) that—
(i) is part of a voting system; and
(ii)
(I) is used for the management, support, or administration of a Federal election; or
(II) has moved in or otherwise affects interstate or foreign commerce;
[…]
(6) the term “exceeds authorized access” means to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter;
[…]
(8) the term “damage” means any impairment to the integrity or availability of data, a program, a system, or information;
[…]
(11) the term “loss” means any reasonable cost to any victim, including the cost of responding to an offense, conducting a damage assessment, and restoring the data, program, system, or information to its condition prior to the offense, and any revenue lost, cost incurred, or other consequential damages incurred because of interruption of service;
(12) the term “person” means any individual, firm, corporation, educational institution, financial institution, governmental entity, or legal or other entity;
(13) the term “Federal election” means any election […] for Federal office […]; and
(14) the term “voting system” has the meaning given the term in section 301(b) of the Help America Vote Act of 2002 (52 U.S.C. 21081(b)).
(f) This section does not prohibit any lawfully authorized investigative, protective, or intelligence activity of a law enforcement agency of the United States, a State, or a political subdivision of a State, or of an intelligence agency of the United States.
(g) Any person who suffers damage or loss by reason of a violation of this section may maintain a civil action against the violator to obtain compensatory damages and injunctive relief or other equitable relief. A civil action for a violation of this section may be brought only if the conduct involves 1 of the factors set forth in subclauses [subclause] (I), (II), (III), (IV), or (V) of subsection (c)(4)(A)(i). Damages for a violation involving only conduct described in subsection (c)(4)(A)(i)(I) are limited to economic damages. No action may be brought under this subsection unless such action is begun within 2 years of the date of the act complained of or the date of the discovery of the damage. No action may be brought under this subsection for the negligent design or manufacture of computer hardware, computer software, or firmware.
[…]
2.1.2. ‘WarGames’ and Cybersecurity’s Debt to a Hollywood Hack
New York Times (Feb. 19, 2016)
Here's a little background about how federal policy on computer hacking was influenced by a 1983 movie starring a young Matthew Broderick. PDF version here.
2.1.3. Grimes interview on YouTube (February 2022)
Watch the portion of this video from 2:19 to 3:13, of a Vanity Fair interview with the musician Grimes. (You can watch the rest too if you like, but we'll only discuss that one portion.) Here's press coverage of the interview in Vice; be ready to discuss why, as the Vice article notes, "DDOSing someone is a federal crime, as would be destroying their property in the form of erasing backups."
2.2 CFAA unit 2 2.2 CFAA unit 2
Week 4
2.2.1 United States v. Morris (2d Cir. 1991) 2.2.1 United States v. Morris (2d Cir. 1991)
Here's a Word version of the opinion, with redactions as per the elided text in this online version. However, this online version has notes appended to the text; the Word version doesn't.
928 F.2d 504 (1991)
UNITED STATES of America, Appellee,
v.
Robert Tappan MORRIS, Defendant-Appellant.
No. 774, Docket 90-1336.
United States Court of Appeals, Second Circuit.
Argued December 4, 1990.
Decided March 7, 1991.
Thomas A. Guidoboni, Washington, D.C., for defendant-appellant.
Ellen R. Meltzer, U.S. Dept. of Justice, Washington, D.C. (Frederick J. Scullin, Jr., U.S. Atty., Syracuse, N.Y., Mark D. Rasch, U.S. Dept. of Justice, Washington, D.C., on the brief), for appellee.
[505] Before NEWMAN and WINTER, Circuit Judges, and DALY, District Judge.[1]
JON O. NEWMAN, Circuit Judge:
This appeal presents two narrow issues of statutory construction concerning a provision Congress recently adopted to strengthen protection against computer crimes. Section 2(d) of the Computer Fraud and Abuse Act of 1986, 18 U.S.C. § 1030(a)(5)(A) (1988), punishes anyone who intentionally accesses without authorization a category of computers known as "[f]ederal interest computers" and damages or prevents authorized use of information in such computers, causing loss of $1,000 or more. The issues raised are (1) whether the Government must prove not only that the defendant intended to access a federal interest computer, but also that the defendant intended to prevent authorized use of the computer's information and thereby cause loss; and (2) what satisfies the statutory requirement of "access without authorization."
These questions are raised on an appeal by Robert Tappan Morris from the May 16, 1990, judgment of the District Court for the Northern District of New York (Howard G. Munson, Judge) convicting him, after a jury trial, of violating 18 U.S.C. § 1030(a)(5)(A). Morris released into INTERNET, a national computer network, a computer program known as a "worm"[2] that spread and multiplied, eventually causing computers at various educational institutions and military sites to "crash" or cease functioning.
We conclude that section 1030(a)(5)(A) does not require the Government to demonstrate that the defendant intentionally prevented authorized use and thereby caused loss. We also find that there was sufficient evidence for the jury to conclude that Morris acted "without authorization" within the meaning of section 1030(a)(5)(A). We therefore affirm.
FACTS
In the fall of 1988, Morris was a first-year graduate student in Cornell University's computer science Ph.D. program. Through undergraduate work at Harvard and in various jobs he had acquired significant computer experience and expertise. When Morris entered Cornell, he was given an account on the computer at the Computer Science Division. This account gave him explicit authorization to use computers at Cornell. Morris engaged in various discussions with fellow graduate students about the security of computer networks and his ability to penetrate it.
In October 1988, Morris began work on a computer program, later known as the INTERNET "worm" or "virus." The goal of this program was to demonstrate the inadequacies of current security measures on computer networks by exploiting the security defects that Morris had discovered. The tactic he selected was release of a worm into network computers. Morris designed the program to spread across a national network of computers after being inserted at one computer location connected to the network. Morris released the worm into INTERNET, which is a group of national networks that connect university, governmental, and military computers around the country. The network permits communication and transfer of information between computers on the network.
Morris sought to program the INTERNET worm to spread widely without drawing attention to itself. The worm was supposed to occupy little computer operation time, and thus not interfere with normal use of the computers. Morris programmed the worm to make it difficult to detect and read, so that other programmers would not be able to "kill" the worm easily.
[506] Morris also wanted to ensure that the worm did not copy itself onto a computer that already had a copy. Multiple copies of the worm on a computer would make the worm easier to detect and would bog down the system and ultimately cause the computer to crash. Therefore, Morris designed the worm to "ask" each computer whether it already had a copy of the worm. If it responded "no," then the worm would copy onto the computer; if it responded "yes," the worm would not duplicate. However, Morris was concerned that other programmers could kill the worm by programming their own computers to falsely respond "yes" to the question. To circumvent this protection, Morris programmed the worm to duplicate itself every seventh time it received a "yes" response. As it turned out, Morris underestimated the number of times a computer would be asked the question, and his one-out-of-seven ratio resulted in far more copying than he had anticipated. The worm was also designed so that it would be killed when a computer was shut down, an event that typically occurs once every week or two. This would have prevented the worm from accumulating on one computer, had Morris correctly estimated the likely rate of reinfection.
Morris identified four ways in which the worm could break into computers on the network:
(1) through a "hole" or "bug" (an error) in SEND MAIL, a computer program that transfers and receives electronic mail on a computer;
(2) through a bug in the "finger demon" program, a program that permits a person to obtain limited information about the users of another computer;
(3) through the "trusted hosts" feature, which permits a user with certain privileges on one computer to have equivalent privileges on another computer without using a password; and
(4) through a program of password guessing, whereby various combinations of letters are tried out in rapid sequence in the hope that one will be an authorized user's password, which is entered to permit whatever level of activity that user is authorized to perform.
On November 2, 1988, Morris released the worm from a computer at the Massachusetts Institute of Technology. MIT was selected to disguise the fact that the worm came from Morris at Cornell. Morris soon discovered that the worm was replicating and reinfecting machines at a much faster rate than he had anticipated. Ultimately, many machines at locations around the country either crashed or became "catatonic." When Morris realized what was happening, he contacted a friend at Harvard to discuss a solution. Eventually, they sent an anonymous message from Harvard over the network, instructing programmers how to kill the worm and prevent reinfection. However, because the network route was clogged, this message did not get through until it was too late. Computers were affected at numerous installations, including leading universities, military sites, and medical research facilities. The estimated cost of dealing with the worm at each installation ranged from $200 to more than $53,000.
Morris was found guilty, following a jury trial, of violating 18 U.S.C. § 1030(a)(5)(A). He was sentenced to three years of probation, 400 hours of community service, a fine of $10,050, and the costs of his supervision.
DISCUSSION
I. The intent requirement in section 1030(a)(5)(A)
Section 1030(a)(5)(A), covers anyone who
(5) intentionally accesses a Federal interest computer without authorization, and by means of one or more instances of such conduct alters, damages, or destroys information in any such Federal interest computer, or prevents authorized use of any such computer or information, and thereby
(A) causes loss to one or more others of a value aggregating $1,000 or more during any one year period; ... [emphasis added].
The District Court concluded that the intent requirement applied only to the accessing and not to the resulting damage. [507] Judge Munson found recourse to legislative history unnecessary because he considered the statute clear and unambiguous. However, the Court observed that the legislative history supported its reading of section 1030(a)(5)(A).
Morris argues that the Government had to prove not only that he intended the unauthorized access of a federal interest computer, but also that he intended to prevent others from using it, and thus cause a loss. The adverb "intentionally," he contends, modifies both verb phrases of the section. The Government urges that since punctuation sets the "accesses" phrase off from the subsequent "damages" phrase, the provision unambiguously shows that "intentionally" modifies only "accesses." Absent textual ambiguity, the Government asserts that recourse to legislative history is not appropriate. See Burlington N.R. Co. v. Oklahoma Tax Comm'n, 481 U.S. 454, 461, 107 S.Ct. 1855, 1859, 95 L.Ed.2d 404 (1987); Consumer Product Safety Comm'n v. GTE Sylvania, Inc., 447 U.S. 102, 108, 100 S.Ct. 2051, 2056, 64 L.Ed.2d 766 (1980); United States v. Holroyd, 732 F.2d 1122, 1125 (2d Cir.1984).
With some statutes, punctuation has been relied upon to indicate that a phrase set off by commas is independent of the language that followed. See United States v. Ron Pair Enterprises, Inc., 489 U.S. 235, 241, 109 S.Ct. 1026, 1030, 103 L.Ed.2d 290 (1989) (interpreting the Bankruptcy Code). However, we have been advised that punctuation is not necessarily decisive in construing statutes, see Costanzo v. Tillinghast, 287 U.S. 341, 344, 53 S.Ct. 152, 153, 77 L.Ed. 350 (1932), and with many statutes, a mental state adverb adjacent to initial words has been applied to phrases or clauses appearing later in the statute without regard to the punctuation or structure of the statute. See Liparota v. United States, 471 U.S. 419, 426-29, 105 S.Ct. 2084, 2088-90, 85 L.Ed.2d 434 (1985) (interpreting food stamps provision); United States v. Nofziger, 878 F.2d 442, 446-50 (D.C.Cir.) (interpreting government "revolving door" statute), cert. denied, ___ U.S. ___, 110 S.Ct. 564, 107 L.Ed.2d 559 (1989); United States v. Johnson & Towers, Inc., 741 F.2d 662, 667-69 (3d Cir.1984) (interpreting the conservation act), cert. denied, 469 U.S. 1208, 105 S.Ct. 1171, 84 L.Ed.2d 321 (1985). In the present case, we do not believe the comma after "authorization" renders the text so clear as to preclude review of the legislative history.
The first federal statute dealing with computer crimes was passed in 1984, Pub.L. No. 98-473 (codified at 18 U.S.C. § 1030 (Supp. II 1984)). The specific provision under which Morris was convicted was added in 1986, Pub.L. No. 99-474, along with some other changes. The 1986 amendments made several changes relevant to our analysis.
First, the 1986 amendments changed the scienter requirement in section 1030(a)(2) from "knowingly" to "intentionally." See Pub.L. No. 99-474, section 2(a)(1). The subsection now covers anyone who
(2) intentionally accesses a computer without authorization or exceeds authorized access, and thereby obtains information contained in a financial record of a financial institution, or of a card issuer as defined in section 1602(n) of title 15, or contained in a file of a consumer reporting agency on a consumer, as such terms are defined in the Fair Credit Reporting Act (15 U.S.C. 1681 et seq.).
According to the Senate Judiciary Committee, Congress changed the mental state requirement in section 1030(a)(2) for two reasons. Congress sought only to proscribe intentional acts of unauthorized access, not "mistaken, inadvertent, or careless" acts of unauthorized access. S.Rep. No. 99-432, 99th Cong., 2d Sess. 5 (1986), reprinted in 1986 U.S.Code Cong. & Admin.News 2479, 2483 [hereinafter Senate Report].
Also, Congress expressed concern that the "knowingly" standard "might be inappropriate for cases involving computer technology." Id. The concern was that a scienter requirement of "knowingly" might encompass the acts of an individual "who inadvertently `stumble[d] into' someone else's computer file or computer data," especially where such individual was authorized [508] to use a particular computer. Id. at 6, 1986 U.S.Code Cong. & Admin.News at 2483. The Senate Report concluded that "[t]he substitution of an `intentional' standard is designed to focus Federal criminal prosecutions on those whose conduct evinces a clear intent to enter, without proper authorization, computer files or data belonging to another." Id., U.S.Code Cong. & Admin.News at 2484. Congress retained the "knowingly" standard in other subsections of section 1030. See 18 U.S.C. § 1030(a)(1), (a)(4).
This use of a mens rea standard to make sure that inadvertent accessing was not covered is also emphasized in the Senate Report's discussion of section 1030(a)(3) and section 1030(a)(5), under which Morris was convicted. Both subsections were designed to target "outsiders," individuals without authorization to access any federal interest computer. Senate Report at 10, U.S.Code Cong. & Admin.News at 2488. The rationale for the mens rea requirement suggests that it modifies only the "accesses" phrase, which was the focus of Congress's concern in strengthening the scienter requirement.
The other relevant change in the 1986 amendments was the introduction of subsection (a)(5) to replace its earlier version, subsection (a)(3) of the 1984 act, 18 U.S.C. § 1030(a)(3) (Supp. II 1984). The predecessor subsection covered anyone who
knowingly accesses a computer without authorization, or having accessed a computer with authorization, uses the opportunity such access provides for purposes to which such authorization does not extend, and by means of such conduct knowingly uses, modifies, destroys, or discloses information in, or prevents authorized use of, such computer, if such computer is operated for or on behalf of the Government of United States and such conduct affects such operation.
The 1986 version changed the mental state requirement from "knowingly" to "intentionally," and did not repeat it after the "accesses" phrase, as had the 1984 version. By contrast, other subsections of section 1030 have retained "dual intent" language, placing the scienter requirement at the beginning of both the "accesses" phrase and the "damages" phrase. See, e.g., 18 U.S.C. § 1030(a)(1).
Morris notes the careful attention that Congress gave to selecting the scienter requirement for current subsections (a)(2) and (a)(5). Then, relying primarily on comments in the Senate and House reports, Morris argues that the "intentionally" requirement of section 1030(a)(5)(A) describes both the conduct of accessing and damaging. As he notes, the Senate Report said that "[t]he new subsection 1030(a)(5) to be created by the bill is designed to penalize those who intentionally alter, damage, or destroy certain computerized data belonging to another." Senate Report at 10, U.S.Code Cong. & Admin.News at 2488. The House Judiciary Committee stated that "the bill proposes a new section (18 U.S.C. § 1030(a)(5)) which can be characterized as a `malicious damage' felony violation involving a Federal interest computer. We have included an `intentional' standard for this felony and coverage is extended only to outside trespassers with a $1,000 threshold damage level." H.R.Rep. No. 99-612, 99th Cong.2d Sess. at 7 (1986). A member of the Judiciary Committee also referred to the section 1030(a)(5) offense as a "malicious damage" felony during the floor debate. 132 Cong.Rec. H3275, 3276 (daily ed. June 3, 1986) (remarks of Rep. Hughes).
The Government's argument that the scienter requirement in section 1030(a)(5)(A) applies only to the "accesses" phrase is premised primarily upon the difference between subsection (a)(5)(A) and its predecessor in the 1984 statute. The decision to state the scienter requirement only once in subsection (a)(5)(A), along with the decision to change it from "knowingly" to "intentionally," are claimed to evince a clear intent upon the part of Congress to apply the scienter requirement only to the "accesses" phrase, though making that requirement more difficult to satisfy. This reading would carry out the Congressional objective of protecting the individual who "inadvertently `stumble[s] into' someone else's computer file." Senate Report at 6, U.S.Code Cong. & Admin.News at 2483.
[509] The Government also suggests that the fact that other subsections of section 1030 continue to repeat the scienter requirement before both phrases of a subsection is evidence that Congress selectively decided within the various subsections of section 1030 where the scienter requirement was and was not intended to apply. Morris responds with a plausible explanation as to why certain other provisions of section 1030 retain dual intent language. Those subsections use two different mens rea standards; therefore it is necessary to refer to the scienter requirement twice in the subsection. For example, section 1030(a)(1) covers anyone who
(1) knowingly accesses a computer without authorization or exceeds authorized access, and by means of such conduct obtains information that has been determined by the United States Government pursuant to an Executive order or statute to require protection against unauthorized disclosure for reasons of national defense or foreign relations, or any restricted data ... with the intent or reason to believe that such information so obtained is to be used to the injury of the United States, or to the advantage of any foreign nation.
Since Congress sought in subsection (a)(1) to have the "knowingly" standard govern the "accesses" phrase and the "with intent" standard govern the "results" phrase, it was necessary to state the scienter requirement at the beginning of both phrases. By contrast, Morris argues, where Congress stated the scienter requirement only once, at the beginning of the "accesses" phrase, it was intended to cover both the "accesses" phrase and the phrase that followed it.
There is a problem, however, with applying Morris's explanation to section 1030(a)(5)(A). As noted earlier, the predecessor of subsection (a)(5)(A) explicitly placed the same mental state requirement before both the "accesses" phrase and the "damages" phrase. In relevant part, that predecessor in the 1984 statute covered anyone who "knowingly accesses a computer without authorization, ... and by means of such conduct knowingly uses, modifies, destroys, or discloses information in, or prevents authorized use of, such computer...." 18 U.S.C. § 1030(a)(3) (Supp. II 1984) (emphasis added). This earlier provision demonstrates that Congress has on occasion chosen to repeat the same scienter standard in the "accesses" phrase and the subsequent phrase of a subsection of the Computer Fraud Statute. More pertinently, it shows that the 1986 amendments adding subsection (a)(5)(A) placed the scienter requirement adjacent only to the "accesses" phrase in contrast to a predecessor provision that had placed the same standard before both that phrase and the subsequent phrase.
Despite some isolated language in the legislative history that arguably suggests a scienter component for the "damages" phrase of section 1030(a)(5)(A), the wording, structure, and purpose of the subsection, examined in comparison with its departure from the format of its predecessor provision persuade us that the "intentionally" standard applies only to the "accesses" phrase of section 1030(a)(5)(A), and not to its "damages" phrase.
II. The unauthorized access requirement in section 1030(a)(5)(A)
Section 1030(a)(5)(A) penalizes the conduct of an individual who "intentionally accesses a Federal interest computer without authorization." Morris contends that his conduct constituted, at most, "exceeding authorized access" rather than the "unauthorized access" that the subsection punishes. Morris argues that there was insufficient evidence to convict him of "unauthorized access," and that even if the evidence sufficed, he was entitled to have the jury instructed on his "theory of defense."
We assess the sufficiency of the evidence under the traditional standard. Morris was authorized to use computers at Cornell, Harvard, and Berkeley, all of which were on INTERNET. As a result, Morris was authorized to communicate with other computers on the network to send electronic mail (SEND MAIL), and to find out certain information about the users of other computers [510] (finger demon). The question is whether Morris's transmission of his worm constituted exceeding authorized access or accessing without authorization.
The Senate Report stated that section 1030(a)(5)(A), like the new section 1030(a)(3), would "be aimed at `outsiders,' i.e., those lacking authorization to access any Federal interest computer." Senate Report at 10, U.S.Code Cong. & Admin.News at 2488. But the Report also stated, in concluding its discussion on the scope of section 1030(a)(3), that it applies "where the offender is completely outside the Government, ... or where the offender's act of trespass is interdepartmental in nature." Id. at 8, U.S.Code Cong. & Admin.News at 2486 (emphasis added).
Morris relies on the first quoted portion to argue that his actions can be characterized only as exceeding authorized access, since he had authorized access to a federal interest computer. However, the second quoted portion reveals that Congress was not drawing a bright line between those who have some access to any federal interest computer and those who have none. Congress contemplated that individuals with access to some federal interest computers would be subject to liability under the computer fraud provisions for gaining unauthorized access to other federal interest computers. See, e.g., id. (stating that a Labor Department employee who uses Labor's computers to access without authorization an FBI computer can be criminally prosecuted).
The evidence permitted the jury to conclude that Morris's use of the SEND MAIL and finger demon features constituted access without authorization. While a case might arise where the use of SEND MAIL or finger demon falls within a nebulous area in which the line between accessing without authorization and exceeding authorized access may not be clear, Morris's conduct here falls well within the area of unauthorized access. Morris did not use either of those features in any way related to their intended function. He did not send or read mail nor discover information about other users; instead he found holes in both programs that permitted him a special and unauthorized access route into other computers.
Moreover, the jury verdict need not be upheld solely on Morris's use of SEND MAIL and finger demon. As the District Court noted, in denying Morris' motion for acquittal,
Although the evidence may have shown that defendant's initial insertion of the worm simply exceeded his authorized access, the evidence also demonstrated that the worm was designed to spread to other computers at which he had no account and no authority, express or implied, to unleash the worm program. Moreover, there was also evidence that the worm was designed to gain access to computers at which he had no account by guessing their passwords. Accordingly, the evidence did support the jury's conclusion that defendant accessed without authority as opposed to merely exceeding the scope of his authority.
In light of the reasonable conclusions that the jury could draw from Morris's use of SEND MAIL and finger demon, and from his use of the trusted hosts feature and password guessing, his challenge to the sufficiency of the evidence fails.
Morris endeavors to bolster his sufficiency argument by contending that his conduct was not punishable under subsection (a)(5) but was punishable under subsection (a)(3). That concession belies the validity of his claim that he only exceeded authorization rather than made unauthorized access. Neither subsection (a)(3) nor (a)(5) punishes conduct that exceeds authorization. Both punish a person who "accesses" "without authorization" certain computers. Subsection (a)(3) covers the computers of a department or agency of the United States; subsection (a)(5) more broadly covers any federal interest computers, defined to include, among other computers, those used exclusively by the United States, 18 U.S.C. § 1030(e)(2)(A), and adds the element of causing damage or loss of use of a value of $1,000 or more. If Morris violated subsection (a)(3), as he concedes, then his conduct in inserting the worm into the INTERNET [511] must have constituted "unauthorized access" under subsection (a)(5) to the computers of the federal departments the worm reached, for example, those of NASA and military bases.
To extricate himself from the consequence of conceding that he made "unauthorized access" within the meaning of subsection (a)(3), Morris subtly shifts his argument and contends that he is not within the reach of subsection (a)(5) at all. He argues that subsection (a)(5) covers only those who, unlike himself, lack access to any federal interest computer. It is true that a primary concern of Congress in drafting subsection (a)(5) was to reach those unauthorized to access any federal interest computer. The Senate Report stated, "[T]his subsection [(a)(5)] will be aimed at `outsiders,' i.e., those lacking authorization to access any Federal interest computer." Senate Report at 10, U.S.Code Cong. & Admin.News at 2488. But the fact that the subsection is "aimed" at such "outsiders" does not mean that its coverage is limited to them. Congress understandably thought that the group most likely to damage federal interest computers would be those who lack authorization to use any of them. But it surely did not mean to insulate from liability the person authorized to use computers at the State Department who causes damage to computers at the Defense Department. Congress created the misdemeanor offense of subsection (a)(3) to punish intentional trespasses into computers for which one lacks authorized access; it added the felony offense of subsection (a)(5) to punish such a trespasser who also causes damage or loss in excess of $1,000, not only to computers of the United States but to any computer within the definition of federal interest computers. With both provisions, Congress was punishing those, like Morris, who, with access to some computers that enable them to communicate on a network linking other computers, gain access to other computers to which they lack authorization and either trespass, in violation of subsection (a)(3), or cause damage or loss of $1,000 or more, in violation of subsection (a)(5).
Morris also contends that the District Court should have instructed the jury on his theory that he was only exceeding authorized access. The District Court decided that it was unnecessary to provide the jury with a definition of "authorization." We agree. Since the word is of common usage, without any technical or ambiguous meaning, the Court was not obliged to instruct the jury on its meaning. See, e.g., United States v. Chenault, 844 F.2d 1124, 1131 (5th Cir.1988) ("A trial court need not define specific statutory terms unless they are outside the common understanding of a juror or are so technical or specific as to require a definition.").
An instruction on "exceeding authorized access" would have risked misleading the jury into thinking that Morris could not be convicted if some of his conduct could be viewed as falling within this description. Yet, even if that phrase might have applied to some of his conduct, he could nonetheless be found liable for doing what the statute prohibited, gaining access where he was unauthorized and causing loss.
Additionally, the District Court properly refused to charge the jury with Morris's proposed jury instruction on access without authorization. That instruction stated, "To establish the element of lack of authorization, the government must prove beyond a reasonable doubt that Mr. Morris was an `outsider,' that is, that he was not authorized to access any Federal interest computer in any manner." As the analysis of the legislative history reveals, Congress did not intend an individual's authorized access to one federal interest computer to protect him from prosecution, no matter what other federal interest computers he accesses.
CONCLUSION
For the foregoing reasons, the judgment of the District Court is affirmed.
[1] The Honorable T.F. Gilroy Daly of the District Court for the District of Connecticut, sitting by designation.
[2] In the colorful argot of computers, a "worm" is a program that travels from one computer to another but does not attach itself to the operating system of the computer it "infects." It differs from a "virus," which is also a migrating program, but one that attaches itself to the operating system of any computer it enters and can infect any other computer that uses files from the infected computer.
2.2.2 Van Buren v. United States (2021) 2.2.2 Van Buren v. United States (2021)
Here's a Word version of the opinion, with redactions as per the elided text in this online version. However, this online version has notes appended to the text; the Word version doesn't.
141 S.Ct. 1648
Supreme Court of the United States.
Nathan VAN BUREN, Petitioner
v.
UNITED STATES
Argued November 30, 2020
Decided June 3, 2021
BARRETT, J., delivered the opinion of the Court, in which BREYER, SOTOMAYOR, KAGAN, GORSUCH, and KAVANAUGH, JJ., joined. THOMAS, J., filed a dissenting opinion, in which ROBERTS, C. J., and ALITO, J., joined.
Opinion
Justice BARRETT delivered the opinion of the Court.
Nathan Van Buren, a former police sergeant, ran a license-plate search in a law enforcement computer database in exchange for money. Van Buren's conduct plainly flouted his department's policy, which authorized him to obtain database information only for law enforcement purposes. We must decide whether Van Buren also violated the Computer Fraud and Abuse Act of 1986 (CFAA), which makes it illegal “to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter.”
He did not. This provision covers those who obtain information from particular areas in the computer—such as files, folders, or databases—to which their computer access does not extend. It does not cover those who, like Van Buren, have improper motives for obtaining information that is otherwise available to them.
I.
A.
Technological advances at the dawn of the 1980s brought computers to schools, offices, and homes across the Nation. But as the public and private sectors harnessed the power of computing for improvement and innovation, so-called hackers hatched ways to coopt computers for illegal ends. After a series of highly publicized hackings captured the public's attention, it became clear that traditional theft and trespass statutes were ill suited to address cybercrimes that did not deprive computer owners of property in the traditional sense. See Kerr, Cybercrime's Scope: Interpreting “Access” and “Authorization” in Computer Misuse Statutes, 78 N. Y. U. L. Rev. 1596, 1605–1613 (2003).
Congress, following the lead of several States, responded by enacting the first federal computer-crime statute as part of the Comprehensive Crime Control Act of 1984. § 2102(a), 98 Stat. 2190–2192. A few years later, Congress passed the CFAA, which included the provisions at issue in this case. The Act subjects to criminal liability anyone who “intentionally accesses a computer without authorization or exceeds authorized access,” and thereby obtains computer information. 18 U.S.C. § 1030(a)(2). It defines the term “exceeds authorized access” to mean “to access a computer with authorization and to use such access to obtain or alter information in the computer that the accesser is not entitled so to obtain or alter.” § 1030(e)(6).
Initially, subsection (a)(2)’s prohibition barred accessing only certain financial information. It has since expanded to cover any information from any computer “used in or affecting interstate or foreign commerce or communication.” § 1030(e)(2)(B). As a result, the prohibition now applies—at a minimum—to all information from all computers that connect to the Internet. §§ 1030(a)(2)(C), (e)(2)(B).
Those who violate § 1030(a)(2) face penalties ranging from fines and misdemeanor sentences to imprisonment for up to 10 years. § 1030(c)(2). They also risk civil liability under the CFAA's private cause of action, which allows persons suffering “damage” or “loss” from CFAA violations to sue for money damages and equitable relief. § 1030(g).
B.
This case stems from Van Buren's time as a police sergeant in Georgia. In the course of his duties, Van Buren crossed paths with a man named Andrew Albo. The deputy chief of Van Buren's department considered Albo to be “very volatile” and warned officers in the department to deal with him carefully. Notwithstanding that warning, Van Buren developed a friendly relationship with Albo. Or so Van Buren thought when he went to Albo to ask for a personal loan. Unbeknownst to Van Buren, Albo secretly recorded that request and took it to the local sheriff ’s office, where he complained that Van Buren had sought to “shake him down” for cash.
The taped conversation made its way to the Federal Bureau of Investigation (FBI), which devised an operation to see how far Van Buren would go for money. The steps were straightforward: Albo would ask Van Buren to search the state law enforcement computer database for a license plate purportedly belonging to a woman whom Albo had met at a local strip club. Albo, no stranger to legal troubles, would tell Van Buren that he wanted to ensure that the woman was not in fact an undercover officer. In return for the search, Albo would pay Van Buren around $5,000.
Things went according to plan. Van Buren used his patrol-car computer to access the law enforcement database with his valid credentials. He searched the database for the license plate that Albo had provided. After obtaining the FBI-created license-plate entry, Van Buren told Albo that he had information to share.
The Federal Government then charged Van Buren with a felony violation of the CFAA on the ground that running the license plate for Albo violated the “exceeds authorized access” clause of 18 U.S.C. § 1030(a)(2).[FN1] The trial evidence showed that Van Buren had been trained not to use the law enforcement database for “an improper purpose,” defined as “any personal use.” App. 17. Van Buren therefore knew that the search breached department policy. And according to the Government, that violation of department policy also violated the CFAA. Consistent with that position, the Government told the jury that Van Buren's access of the database “for a non[-]law[-]enforcement purpose” violated the CFAA “concept” against “using” a computer network in a way contrary to “what your job or policy prohibits.” Id., at 39. The jury convicted Van Buren, and the District Court sentenced him to 18 months in prison.
Van Buren appealed to the Eleventh Circuit, arguing that the “exceeds authorized access” clause applies only to those who obtain information to which their computer access does not extend, not to those who misuse access that they otherwise have. While several Circuits see the clause Van Buren's way, the Eleventh Circuit is among those that have taken a broader view.[FN2] Consistent with its Circuit precedent, the panel held that Van Buren had violated the CFAA by accessing the law enforcement database for an “inappropriate reason.” 940 F.3d 1192, 1208 (2019). We granted certiorari to resolve the split in authority regarding the scope of liability under the CFAA's “exceeds authorized access” clause. 590 U. S. ––––, 140 S.Ct. 2667, 206 L.Ed.2d 822 (2020).
II.
A.
1.
Both Van Buren and the Government raise a host of policy arguments to support their respective interpretations. But we start where we always do: with the text of the statute. Here, the most relevant text is the phrase “exceeds authorized access,” which means “to access a computer with authorization and to use such access to obtain ... information in the computer that the accesser is not entitled so to obtain.” § 1030(e)(6).
The parties agree that Van Buren “access[ed] a computer with authorization” when he used his patrol-car computer and valid credentials to log into the law enforcement database. They also agree that Van Buren “obtain[ed] ... information in the computer” when he acquired the license-plate record for Albo. The dispute is whether Van Buren was “entitled so to obtain” the record.
“Entitle” means “to give ... a title, right, or claim to something.” Random House Dictionary of the English Language 649 (2d ed. 1987). See also Black's Law Dictionary 477 (5th ed. 1979) (“to give a right or legal title to”). The parties agree that Van Buren had been given the right to acquire license-plate information—that is, he was “entitled to obtain” it—from the law enforcement computer database. But was Van Buren “entitled so to obtain” the license-plate information, as the statute requires?
Van Buren says yes. He notes that “so,” as used in this statute, serves as a term of reference that recalls “the same manner as has been stated” or “the way or manner described.” Black's Law Dictionary, at 1246; 15 Oxford English Dictionary 887 (2d ed. 1989). The disputed phrase “entitled so to obtain” thus asks whether one has the right, in “the same manner as has been stated,” to obtain the relevant information. And the only manner of obtaining information already stated in the definitional provision is “via a computer [one] is otherwise authorized to access.” Reply Brief 3. Putting that together, Van Buren contends that the disputed phrase—“is not entitled so to obtain”—plainly refers to information one is not allowed to obtain by using a computer that he is authorized to access. On this reading, if a person has access to information stored in a computer—e.g., in “Folder Y,” from which the person could permissibly pull information—then he does not violate the CFAA by obtaining such information, regardless of whether he pulled the information for a prohibited purpose. But if the information is instead located in prohibited “Folder X,” to which the person lacks access, he violates the CFAA by obtaining such information.
The Government agrees that the statute uses “so” in the word's term-of-reference sense, but it argues that “so” sweeps more broadly. It reads the phrase “is not entitled so to obtain” to refer to information one was not allowed to obtain in the particular manner or circumstances in which he obtained it. The manner or circumstances in which one has a right to obtain information, the Government says, are defined by any “specifically and explicitly” communicated limits on one's right to access information. Brief for United States 19. As the Government sees it, an employee might lawfully pull information from Folder Y in the morning for a permissible purpose—say, to prepare for a business meeting—but unlawfully pull the same information from Folder Y in the afternoon for a prohibited purpose—say, to help draft a resume to submit to a competitor employer.
The Government's interpretation has surface appeal but proves to be a sleight of hand. While highlighting that “so” refers to a “manner or circumstance,” the Government simultaneously ignores the definition's further instruction that such manner or circumstance already will “ ‘ha[ve] been stated,’ ” “ ‘asserted,’ ” or “ ‘described.’ ” Id., at 18 (quoting Black's Law Dictionary, at 1246; 15 Oxford English Dictionary, at 887). Under the Government's approach, the relevant circumstance—the one rendering a person's conduct illegal—is not identified earlier in the statute. Instead, “so” captures any circumstance-based limit appearing anywhere—in the United States Code, a state statute, a private agreement, or anywhere else. And while the Government tries to cabin its interpretation by suggesting that any such limit must be “specifically and explicitly” stated, “express,” and “inherent in the authorization itself,” the Government does not identify any textual basis for these guardrails. Brief for United States 19; Tr. of Oral Arg. 41.
Van Buren's account of “so”—namely, that “so” references the previously stated “manner or circumstance” in the text of § 1030(e)(6) itself—is more plausible than the Government's. “So” is not a free-floating term that provides a hook for any limitation stated anywhere. It refers to a stated, identifiable proposition from the “preceding” text; indeed, “so” typically “[r]epresent[s]” a “word or phrase already employed,” thereby avoiding the need for repetition. 15 Oxford English Dictionary, at 887; see Webster's Third New International Dictionary 2160 (1986) (so “often used as a substitute ... to express the idea of a preceding phrase”). Myriad federal statutes illustrate this ordinary usage.[FN3] We agree with Van Buren: The phrase “is not entitled so to obtain” is best read to refer to information that a person is not entitled to obtain by using a computer that he is authorized to access.[FN4]
2.
The Government's primary counterargument is that Van Buren's reading renders the word “so” superfluous. Recall the definition: “to access a computer with authorization and to use such access to obtain ... information in the computer that the accesser is not entitled so to obtain.” § 1030(e)(6) (emphasis added). According to the Government, “so” adds nothing to the sentence if it refers solely to the earlier stated manner of obtaining the information through use of a computer one has accessed with authorization. What matters on Van Buren's reading, as the Government sees it, is simply that the person obtain information that he is not entitled to obtain—and that point could be made even if “so” were deleted. By contrast, the Government insists, “so” makes a valuable contribution if it incorporates all of the circumstances that might qualify a person's right to obtain information. Because only its interpretation gives “so” work to do, the Government contends, the rule against superfluity means that its interpretation wins. See Republic of Sudan v. Harrison, 587 U. S. ––––, ––––, 139 S.Ct. 1048, 1058, 203 L.Ed.2d 433 (2019).
But the canon does not help the Government because Van Buren's reading does not render “so” superfluous. As Van Buren points out, without “so,” the statute would allow individuals to use their right to obtain information in nondigital form as a defense to CFAA liability. Consider, for example, a person who downloads restricted personnel files he is not entitled to obtain by using his computer. Such a person could argue that he was “entitled to obtain” the information if he had the right to access personnel files through another method (e.g., by requesting hard copies of the files from human resources). With “so,” the CFAA forecloses that theory of defense. The statute is concerned with what a person does on a computer; it does not excuse hacking into an electronic personnel file if the hacker could have walked down the hall to pick up a physical copy.
This clarification is significant because it underscores that one kind of entitlement to information counts: the right to access the information by using a computer. That can expand liability, as the above example shows. But it narrows liability too. Without the word “so,” the statute could be read to incorporate all kinds of limitations on one's entitlement to information. The dissent's take on the statute illustrates why.
3.
While the dissent accepts Van Buren's definition of “so,” it would arrive at the Government's result by way of the word “entitled.” One is “entitled” to do something, the dissent contends, only when “ ‘proper grounds’ ” are in place. Post, at 1663 – 1664 (opinion of THOMAS, J.) (quoting Black's Law Dictionary, at 477). Deciding whether a person was “entitled” to obtain information, the dissent continues, therefore demands a “circumstance dependent” analysis of whether access was proper. Post, at 1663 – 1664. This reading, like the Government's, would extend the statute's reach to any circumstance-based limit appearing anywhere.
The dissent's approach to the word “entitled” fares fine in the abstract but poorly in context. The statute does not refer to “information ... that the accesser is not entitled to obtain.” It refers to “information ... that the accesser is not entitled so to obtain.” 18 U.S.C. § 1030(e)(6) (emphasis added). The word “entitled,” then, does not stand alone, inviting the reader to consider the full scope of the accesser's entitlement to information. The modifying phrase “so to obtain” directs the reader to consider a specific limitation on the accesser's entitlement: his entitlement to obtain the information “in the manner previously stated.” Supra, at 1650. And as already explained, the manner previously stated is using a computer one is authorized to access. Thus, while giving lipservice to Van Buren's reading of “so,” the dissent, like the Government, declines to give “so” any limiting function.[FN5]
The dissent cannot have it both ways. The consequence of accepting Van Buren's reading of “so” is the narrowed scope of “entitled.” In fact, the dissent's examples implicitly concede as much: They all omit the word “so,” thereby giving “entitled” its full sweep. See post, at 1663 – 1664. An approach that must rewrite the statute to work is even less persuasive than the Government's.
4.
The Government falls back on what it describes as the “common parlance” meaning of the phrase “exceeds authorized access.” Brief for United States 20–21. According to the Government, any ordinary speaker of the English language would think that Van Buren “exceed[ed] his authorized access” to the law enforcement database when he obtained license-plate information for personal purposes. Id., at 21. The dissent, for its part, asserts that this point “settles” the case. Post, at 1667.
If the phrase “exceeds authorized access” were all we had to go on, the Government and the dissent might have a point. But both breeze by the CFAA's explicit definition of the phrase “exceeds authorized access.” When “a statute includes an explicit definition” of a term, “we must follow that definition, even if it varies from a term's ordinary meaning.” Tanzin v. Tanvir, 592 U. S. ––––, ––––, 141 S.Ct. 486, 490, 208 L.Ed.2d 295 (2020) (internal quotation marks omitted). So the relevant question is not whether Van Buren exceeded his authorized access but whether he exceeded his authorized access as the CFAA defines that phrase. And as we have already explained, the statutory definition favors Van Buren's reading.
That reading, moreover, is perfectly consistent with the way that an “appropriately informed” speaker of the language would understand the meaning of “exceeds authorized access.” Nelson, What Is Textualism? 91 Va. L. Rev. 347, 354 (2005). When interpreting statutes, courts take note of terms that carry “technical meaning[s].” A. Scalia & B. Garner, Reading Law: The Interpretation of Legal Texts 73 (2012). “Access” is one such term, long carrying a “well established” meaning in the “computational sense”—a meaning that matters when interpreting a statute about computers. American Heritage Dictionary 10 (3d ed. 1992). In the computing context, “access” references the act of entering a computer “system itself ” or a particular “part of a computer system,” such as files, folders, or databases.[FN6] It is thus consistent with that meaning to equate “exceed[ing] authorized access” with the act of entering a part of the system to which a computer user lacks access privileges.[FN7] The Government and the dissent's broader interpretation is neither the only possible nor even necessarily the most natural one.
B.
While the statute's language “spells trouble” for the Government's position, a “wider look at the statute's structure gives us even more reason for pause.” Romag Fasteners, Inc. v. Fossil Group, Inc., 590 U. S. ––––, –––– – ––––, 140 S.Ct. 1492, 1495, 206 L.Ed.2d 672 (2020).
The interplay between the “without authorization” and “exceeds authorized access” clauses of subsection (a)(2) is particularly probative. Those clauses specify two distinct ways of obtaining information unlawfully. First, an individual violates the provision when he “accesses a computer without authorization.” § 1030(a)(2). Second, an individual violates the provision when he “exceeds authorized access” by accessing a computer “with authorization” and then obtaining information he is “not entitled so to obtain.” §§ 1030(a)(2), (e)(6). Van Buren's reading places the provision's parts “into an harmonious whole.” Roberts v. Sea-Land Services, Inc., 566 U.S. 93, 100, 132 S.Ct. 1350, 182 L.Ed.2d 341 (2012) (internal quotation marks omitted). The Government's does not.
Start with Van Buren's view. The “without authorization” clause, Van Buren contends, protects computers themselves by targeting so-called outside hackers—those who “acces[s] a computer without any permission at all.” LVRC Holdings LLC v. Brekka, 581 F.3d 1127, 1133 (CA9 2009); see also Pulte Homes, Inc. v. Laborers’ Int'l Union of North Am., 648 F.3d 295, 304 (CA6 2011). Van Buren reads the “exceeds authorized access” clause to provide complementary protection for certain information within computers. It does so, Van Buren asserts, by targeting so-called inside hackers—those who access a computer with permission, but then “ ‘exceed’ the parameters of authorized access by entering an area of the computer to which [that] authorization does not extend.” United States v. Valle, 807 F.3d 508, 524 (CA2 2015).
Van Buren's account of subsection (a)(2) makes sense of the statutory structure because it treats the “without authorization” and “exceeds authorized access” clauses consistently. Under Van Buren's reading, liability under both clauses stems from a gates-up-or-down inquiry—one either can or cannot access a computer system, and one either can or cannot access certain areas within the system.[FN8] And reading both clauses to adopt a gates-up-or-down approach aligns with the computer-context understanding of access as entry. See supra, at 1657 – 1658.[FN9]
By contrast, the Government's reading of the “exceeds authorized access” clause creates “inconsistenc[ies] with the design and structure” of subsection (a)(2). University of Tex. Southwestern Medical Center v. Nassar, 570 U.S. 338, 353, 133 S.Ct. 2517, 186 L.Ed.2d 503 (2013). As discussed, the Government reads the “exceeds authorized access” clause to incorporate purpose-based limits contained in contracts and workplace policies. Yet the Government does not read such limits into the threshold question whether someone uses a computer “without authorization”—even though similar purpose restrictions, like a rule against personal use, often govern one's right to access a computer in the first place. See, e.g., Royal Truck & Trailer Sales & Serv., Inc. v. Kraft, 974 F.3d 756, 757 (CA6 2020). Thus, the Government proposes to read the first phrase “without authorization” as a gates-up-or-down inquiry and the second phrase “exceeds authorized access” as one that depends on the circumstances. The Government does not explain why the statute would prohibit accessing computer information, but not the computer itself, for an improper purpose.[FN10]
The Government's position has another structural problem. Recall that violating § 1030(a)(2), the provision under which Van Buren was charged, also gives rise to civil liability. See § 1030(g). Provisions defining “damage” and “loss” specify what a plaintiff in a civil suit can recover. “ ‘[D]amage,’ ” the statute provides, means “any impairment to the integrity or availability of data, a program, a system, or information.” § 1030(e)(8). The term “loss” likewise relates to costs caused by harm to computer data, programs, systems, or information services. § 1030(e)(11). The statutory definitions of “damage” and “loss” thus focus on technological harms—such as the corruption of files—of the type unauthorized users cause to computer systems and data. Limiting “damage” and “loss” in this way makes sense in a scheme “aimed at preventing the typical consequences of hacking.” Royal Truck, 974 F.3d at 760. The term's definitions are ill fitted, however, to remediating “misuse” of sensitive information that employees may permissibly access using their computers. Ibid. Van Buren's situation is illustrative: His run of the license plate did not impair the “integrity or availability” of data, nor did it otherwise harm the database system itself.
C.
Pivoting from text and structure, the Government claims that precedent and statutory history support its interpretation. These arguments are easily dispatched.
As for precedent, the Government asserts that this Court's decision in Musacchio v. United States, 577 U.S. 237, 136 S.Ct. 709, 193 L.Ed.2d 639 (2016), bolsters its reading. There, in addressing a question about the standard of review for instructional error, the Court described § 1030(a)(2) as prohibiting “(1) obtaining access without authorization; and (2) obtaining access with authorization but then using that access improperly.” Id., at 240, 136 S.Ct. 709. This paraphrase of the statute does not do much for the Government. As an initial matter, Musacchio did not address—much less resolve in the Government's favor—the “point now at issue,” and we thus “are not bound to follow” any dicta in the case. Central Va. Community College v. Katz, 546 U.S. 356, 363, 126 S.Ct. 990, 163 L.Ed.2d 945 (2006). But in any event, Van Buren's interpretation, no less than the Government's, involves “using [one's] access improperly.” It is plainly “improper” for one to use the opportunity his computer access provides to obtain prohibited information from within the computer.
As for statutory history, the Government claims that the original 1984 Act supports its interpretation of the current version. In a precursor to the “exceeds authorized access” clause, the 1984 Act covered any person who, “having accessed a computer with authorization, uses the opportunity such access provides for purposes to which such authorization does not extend,” and thus expressly alluded to the purpose of an insider's computer access. 18 U.S.C. § 1030(a)(2) (1982 ed. Supp. III). According to the Government, this confirms that the amended CFAA—which makes no mention of purpose in defining “exceeds authorized access”—likewise covers insiders like Van Buren who use their computer access for an unauthorized purpose.[FN11] The Government's argument gets things precisely backward. “When Congress amends legislation, courts must presume it intends the change to have real and substantial effect.” Ross v. Blake, 578 U. S. 632, 641–642, 136 S.Ct. 1850, 195 L.Ed.2d 117 (2016) (internal quotation marks and brackets omitted). Congress’ choice to remove the statute's reference to purpose thus cuts against reading the statute “to capture that very concept.” Brief for United States 22. The statutory history thus hurts rather than helps the Government's position.
III.
To top it all off, the Government's interpretation of the statute would attach criminal penalties to a breathtaking amount of commonplace computer activity. Van Buren frames the far-reaching consequences of the Government's reading as triggering the rule of lenity or constitutional avoidance. That is not how we see it: Because the text, context, and structure support Van Buren's reading, neither of these canons is in play. Still, the fallout underscores the implausibility of the Government's interpretation. It is “extra icing on a cake already frosted.” Yates v. United States, 574 U.S. 528, 557, 135 S.Ct. 1074, 191 L.Ed.2d 64 (2015) (KAGAN, J., dissenting).
If the “exceeds authorized access” clause criminalizes every violation of a computer-use policy, then millions of otherwise law-abiding citizens are criminals. Take the workplace. Employers commonly state that computers and electronic devices can be used only for business purposes. So on the Government's reading of the statute, an employee who sends a personal e-mail or reads the news using her work computer has violated the CFAA. Or consider the Internet. Many websites, services, and databases—which provide “information” from “protected computer[s],” § 1030(a)(2)(C)—authorize a user's access only upon his agreement to follow specified terms of service. If the “exceeds authorized access” clause encompasses violations of circumstance-based access restrictions on employers’ computers, it is difficult to see why it would not also encompass violations of such restrictions on website providers’ computers. And indeed, numerous amici explain why the Government's reading of subsection (a)(2) would do just that—criminalize everything from embellishing an online-dating profile to using a pseudonym on Facebook. See Brief for Orin Kerr as Amicus Curiae 10–11; Brief for Technology Companies as Amici Curiae 6, n. 3, 11; see also Brief for Reporters Committee for Freedom of the Press et al. as Amici Curiae 10–13 (journalism activity); Brief for Kyratso Karahalios et al. as Amici Curiae 11–17 (online civil-rights testing and research).
In response to these points, the Government posits that other terms in the statute—specifically “authorization” and “use”—“may well” serve to cabin its prosecutorial power. Brief for United States 35; see Tr. of Oral Arg. 38, 40, 58 (“instrumental” use; “individualized” and “fairly specific” authorization). Yet the Government stops far short of endorsing such limitations. Cf. Brief for United States 37 (concept of “authorization” “may not logically apply”); id., at 38 (“ ‘use’ ” might be read in a more “limited” fashion, even though it “often has a broader definition”); see also, e.g., post, at 1668 – 1669 (mens rea requirement “might” preclude liability in some cases). Nor does it cite any prior instance in which it has read the statute to contain such limitations—to the contrary, Van Buren cites instances where it hasn't. See Reply Brief 14–15, 17 (collecting cases); cf. Sandvig v. Barr, 451 F.Supp.3d 73, 81–82 (D.D.C. 2020) (discussing Department of Justice testimony indicating that the Government could “ ‘bring a CFAA prosecution based’ ” on terms-of-service violations causing “ ‘de minimis harm’ ”). If anything, the Government's current CFAA charging policy shows why Van Buren's concerns are far from “hypothetical,” post, at 1668 – 1669: The policy instructs that federal prosecution “may not be warranted”—not that it would be prohibited—“if the defendant exceed[s] authorized access solely by violating an access restriction contained in a contractual agreement or term of service with an Internet service provider or website.”[FN12] And while the Government insists that the intent requirement serves as yet another safety valve, that requirement would do nothing for those who intentionally use their computers in a way their “job or policy prohibits”—for example, by checking sports scores or paying bills at work. App. 39.
One final observation: The Government's approach would inject arbitrariness into the assessment of criminal liability. The Government concedes, as it must, that the “exceeds authorized access” clause prohibits only unlawful information “access,” not downstream information “ ‘misus[e].’ ” Brief in Opposition 17 (statute does not cover “ ‘subsequen[t] misus[e of] information’ ”). But the line between the two can be thin on the Government's reading. Because purpose-based limits on access are often designed with an eye toward information misuse, they can be expressed as either access or use restrictions. For example, one police department might prohibit using a confidential database for a non-law-enforcement purpose (an access restriction), while another might prohibit using information from the database for a non-law-enforcement purpose (a use restriction). Conduct like Van Buren's can be characterized either way, and an employer might not see much difference between the two. On the Government's reading, however, the conduct would violate the CFAA only if the employer phrased the policy as an access restriction. An interpretation that stakes so much on a fine distinction controlled by the drafting practices of private parties is hard to sell as the most plausible.
IV
In sum, an individual “exceeds authorized access” when he accesses a computer with authorization but then obtains information located in particular areas of the computer—such as files, folders, or databases—that are off limits to him. The parties agree that Van Buren accessed the law enforcement database system with authorization. The only question is whether Van Buren could use the system to retrieve license-plate information. Both sides agree that he could. Van Buren accordingly did not “excee[d] authorized access” to the database, as the CFAA defines that phrase, even though he obtained information from the database for an improper purpose. We therefore reverse the contrary judgment of the Eleventh Circuit and remand the case for further proceedings consistent with this opinion.
It is so ordered.
Footnotes
[FN1] Van Buren also was charged with and convicted of honest-services wire fraud. In a separate holding not at issue here, the United States Court of Appeals for the Eleventh Circuit vacated Van Buren's honest-services fraud conviction as contrary to this Court's decision in McDonnell v. United States, 579 U. S. 550, 136 S.Ct. 2355, 195 L.Ed.2d 639 (2016).
[FN2] Compare Royal Truck & Trailer Sales & Serv., Inc. v. Kraft, 974 F.3d 756 (CA6 2020); United States v. Valle, 807 F.3d 508 (CA2 2015); WEC Carolina Energy Solutions LLC v. Miller, 687 F.3d 199 (CA4 2012); United States v. Nosal, 676 F.3d 854 (CA9 2012) (en banc), with United States v. Rodriguez, 628 F.3d 1258 (CA11 2010); United States v. John, 597 F.3d 263 (CA5 2010); International Airport Centers, L.L.C. v. Citrin, 440 F.3d 418 (CA7 2006); EF Cultural Travel BV v. Explorica, Inc., 274 F.3d 577 (CA1 2001).
[FN3] See, e.g., 7 U.S.C. § 171(8) (authorizing Secretary of Agriculture “[t]o sell guayule or rubber processed from guayule and to use funds so obtained in replanting and maintaining an area”); 18 U.S.C. § 648 (any person responsible for “safe-keeping of the public moneys” who “loans, uses, or converts to his own use ... any portion of the public moneys ... is guilty of embezzlement of the money so loaned, used, converted, deposited, or exchanged”); § 1163 (“[W]hoever embezzles, steals, [or] knowingly converts to his use” money or property “belonging to any Indian tribal organization,” or “[w]hoever, knowing any such moneys ... or other property to have been so embezzled, stolen, [or] converted ... retains the same with intent to convert it to his use,” is subject to punishment); § 1708 (“[W]hoever steals, takes, or abstracts, or by fraud or deception obtains, or attempts so to obtain,” parcels of mail is subject to punishment).
[FN4] The dissent criticizes this interpretation as inconsistent with “basic principles of property law,” and in particular the “familiar rule that an entitlement to use another person's property is circumstance specific.” Post, at 1664 (opinion of THOMAS, J.). But common-law principles “should be imported into statutory text only when Congress employs a common-law term”—not when Congress has outlined an offense “analogous to a common-law crime without using common-law terms.” Carter v. United States, 530 U.S. 255, 265, 120 S.Ct. 2159, 147 L.Ed.2d 203 (2000) (emphasis deleted). Relying on the common law is particularly ill advised here because it was the failure of pre-existing law to capture computer crime that helped spur Congress to enact the CFAA. See supra, at 1652.
[FN5] For the same reason, the dissent is incorrect when it contends that our interpretation reads the additional words “under any possible circumstance” into the statute. Post, at 1663 – 1664 (emphasis deleted). Our reading instead interprets the phrase “so to obtain” to incorporate the single “circumstance” of permissible information access identified by the statute: obtaining the information by using one's computer.
[FN6] 1 Oxford English Dictionary 72 (2d ed. 1989) (“[t]o gain access to ... data, etc., held in a computer or computer-based system, or the system itself ”); Random House Dictionary of the English Language 11 (2d ed. 1987) (“Computers. to locate (data) for transfer from one part of a computer system to another ...”); see also C. Sippl & R. Sippl, Computer Dictionary and Handbook 2 (3d ed. 1980) (“[c]oncerns the process of obtaining data from or placing data in storage”); Barnhart Dictionary of New English 2 (3d ed. 1990) (“to retrieve (data) from a computer storage unit or device ...”); Microsoft Computer Dictionary 12 (4th ed. 1999) (“[t]o gain entry to memory in order to read or write data”); A Dictionary of Computing 5 (6th ed. 2008) (“[t]o gain entry to data, a computer system, etc.”).
[FN7] The dissent makes the odd charge that our interpretation violates the “ ‘presumption against’ ” reading a provision “contrary to the ordinary meaning of the term it defines.” Post, at 1667. But when a statute, like this one, is “addressing a ... technical subject, a specialized meaning is to be expected.” Scalia, Reading Law, at 73. Consistent with that principle, our interpretation tracks the specialized meaning of “access” in the computer context. This reading is far from “ ‘repugnant to’ ” the meaning of the phrase “exceeds authorized access,” post, at 1667—unlike, say, a definitional provision directing that “ ‘the word dog is deemed to include all horses.’ ” Scalia, supra, at 232, n. 29.
[FN8] For present purposes, we need not address whether this inquiry turns only on technological (or “code-based”) limitations on access, or instead also looks to limits contained in contracts or policies. Cf. Brief for Orin Kerr as Amicus Curiae 7 (urging adoption of code-based approach).
[FN9] Van Buren's gates-up-or-down reading also aligns with the CFAA's prohibition on password trafficking. See Tr. of Oral Arg. 33. Enacted alongside the “exceeds authorized access” definition in 1986, the password-trafficking provision bars the sale of “any password or similar information through which a computer may be accessed without authorization.” § 1030(a)(6). The provision thus contemplates a “specific type of authorization—that is, authentication,” which turns on whether a user's credentials allow him to proceed past a computer's access gate, rather than on other, scope-based restrictions. Bellia, A Code-Based Approach to Unauthorized Access Under the Computer Fraud and Abuse Act, 84 Geo. Wash. L. Rev. 1442, 1470 (2016); cf. A Dictionary of Computing, at 30 (defining “authorization” as a “process by which users, having completed an ... authentication stage, gain or are denied access to particular resources based on their entitlement”).
[FN10] Unlike the Government, the dissent would read both clauses of subsection (a)(2) to require a circumstance-specific analysis. Doing so, the dissent contends, would reflect that “[p]roperty law generally protects against both unlawful entry and unlawful use.” Post, at 1666. This interpretation suffers from structural problems of its own. Consider the standard rule prohibiting the use of one's work computer for personal purposes. Under the dissent's approach, an employee's computer access would be without authorization if he logged on to the computer with the purpose of obtaining a file for personal reasons. In that event, obtaining the file would not violate the “exceeds authorized access” clause, which applies only when one accesses a computer “with authorization.” § 1030(e)(6) (emphasis added). The dissent's reading would therefore leave the “exceeds authorized access” clause with no work to do much of the time—an outcome that Van Buren's interpretation (and, for that matter, the Government's) avoids.
[FN11] While the Government insists that Congress made this change “ ‘merely to clarify the language’ ” of § 1030(a)(2), Brief for United States 28, the dissent has a different take. In the dissent's telling, the 1986 amendment in fact “expand[ed]” the provision to reach “time and manner” restrictions on computer access—not just purpose-based ones. Post, at 1667 – 1668. The dissent's distinct explanation for why Congress removed § 1030(a)(2)’s reference to “purpose” requires accepting that the “exceeds authorized access” definition supports a circumstance-specific approach. We reject the dissent's premise for the textual and structural reasons already discussed.
[FN12] Memorandum from U. S. Atty. Gen. to U. S. Attys. & Assistant Attys. Gen. for the Crim. & Nat. Security Divs., Intake and Charging Policy for Computer Crime Matters 5 (Sept. 11, 2014), https://www.justice.gov/criminal-ccips/file/904941/download (emphasis added). Although the Government asserts that it has “[h]istorically” prosecuted only “core conduct” like Van Buren's and not the commonplace violations that Van Buren fears, Brief for United States 40, the contrary examples Van Buren and his amici cite give reason to balk at that assurance. See Brief for Petitioner 32–33; Brief for Orin Kerr as Amicus Curiae 18–23; Brief for Technology Companies as Amici Curiae 11.
2.2.3. Blog Post About Web Scraping & the Law (December 2022)
As we'll discuss, the CFAA is just one of multiple laws that web scrapers might be accused of violating. This blog post gives a cheerfully sarcastic overview of the legal landscape for scraping data online, as of December 2022.
Since then, AI companies' use of scraping to train their LLMs has begotten a tidal wave of lawsuits. In June 2023, the same blogger covered one early court decision in a case against GitHub, and discussed a pressing question: how can AI models legally obtain training data?
2.3 Optional Reading 2.3 Optional Reading
Here are some additional resources to help you make sense of the CFAA, its background, and its judicial interpretation.
2.3.1. The World's First Cyber Crime: The Morris Worm - YouTube
Here's a 20-minute video about the early days of the Internet - and the Morris worm that took down a significant portion of it in November of 1988, leading to the first criminal prosecution under the new CFAA statute.
2.3.2. SCOTUSblog's post about the Van Buren ruling
This blog post gives a thorough overview of the Supreme Court's Van Buren ruling. However, it assumes a certain level of familiarity with the legal system, so the way it's written might not be super accessible if you aren't a law student.
Note that SCOTUSblog is a blog about the Supreme Court; it is not published by the Supreme Court.
2.3.3. Prof. Orin Kerr's response to the Van Buren ruling
Kerr, a professor at UC Berkeley Law, is a top cyberlaw scholar and expert in the CFAA. His academic publications are frequently cited in opinions of the federal courts of appeals and the Supreme Court - including the Van Buren decision. (He also wrote the "how to read a legal opinion" guide that was assigned reading recently.) Here, he's writing for a general audience, meaning the tone is probably more accessible than the SCOTUSblog optional reading is.
2.3.4. Where to stream "Die Hard"
The first lecture on the CFAA will make a lot more sense if you've seen "Die Hard."
2.3.5. Legal Issues | Nmap Network Scanning
What's the legality of port scanning using a tool such as nmap, like you'll do in lab? This webpage on the nmap website goes over some things that users should think about. It mentions the only court case to date that has directly addressed the issue of the legality of port scanning, a 2000 case from a Georgia federal district court that we'll discuss in class.