What Common Law and Common Sense Teach Us About Corporate Cyberse
What Common Law and Common Sense Teach Us About Corporate Cyberse
What Common Law and Common Sense Teach Us About Corporate Cyberse
Volume 49
2016
Part of the Common Law Commons, Communications Law Commons, Criminal Law Commons, and
the Privacy Law Commons
Recommended Citation
Stephanie Balitzer, What Common Law and Common Sense Teach Us About Corporate Cybersecurity, 49
U. MICH. J. L. REFORM 891 (2016).
Available at: https://repository.law.umich.edu/mjlr/vol49/iss4/5
This Note is brought to you for free and open access by the University of Michigan Journal of Law Reform at
University of Michigan Law School Scholarship Repository. It has been accepted for inclusion in University of
Michigan Journal of Law Reform by an authorized editor of University of Michigan Law School Scholarship
Repository. For more information, please contact [email protected].
WHAT COMMON LAW AND COMMON SENSE TEACH US
ABOUT CORPORATE CYBERSECURITY
Stephanie Balitzer*
Network intrusions and the consequential losses of data and confidentiality plague
corporations. With each of these breaches, corporations suffer financial and reputa-
tional losses, leaving them scrambling to defend their networks and curb future
hacks. Moreover, because their attackers strike from around the globe, are fueled by
many motivations, and have ample tools at their disposal, hacks can be almost
impossible to predict. The imperfect legal framework in this area only exacerbates
this climate of uncertainty. Although active defense strategies like “hacking back”
currently exceed the scope of corporate legal rights, many commentators have advo-
cated for the legalization of these practices in the realm of corporate cybersecurity.
This Note argues that active defense strategies do not present a viable option for
corporations, as they contravene well-developed common law property principles
and would generate several negative legal and practical consequences. Instead of
deregulating the sphere of corporate cybersecurity to permit corporations to hack
back, the Cyber Threat Intelligence Integration Center (CTIIC) should utilize its
expertise and functionality as an inter-agency data repository to formulate regula-
tions in conjunction with the Federal Communications Commission (FCC). Such
regulations, which would clarify the scope of permissible corporate cyberdefense
strategies, would create a viable and sustainable framework for corporations to
follow.
INTRODUCTION
* J.D. Candidate, University of Michigan Law School, 2016; B.A., Tufts University,
2010. I would like to thank my fellow editors of the Michigan Journal of Law Reform,
Professor Julian Mortenson, and my friends Joseph Celentino and Benjamin Reese for their
invaluable feedback.
1. See, e.g., Michael Riley, Ben Elgin & Carol Matlack, Missed Alarms and 40 Million Stolen
Credit Card Numbers: How Target Blew It, BLOOMBERG BUS. (Mar. 17, 2014, 10:31 AM), http://
www.bloomberg.com/bw/articles/2014-03-13/target-missed-alarms-in-epic-hack-of-credit-
card-data.
891
892 University of Michigan Journal of Law Reform [VOL. 49:4
1. Quantitative Costs
6. Ponemon Institute, 2015 Cost of Data Breach Study: United States, IBM, 1 (May 2015),
http://public.dhe.ibm.com/common/ssi/ecm/se/en/sew03055usen/SEW03055USEN.pdf.
7. Id. at 2.
8. See FBI, FBI Internet Crime Complaint Center 2013 Report, INTERNET CRIME COMPLAINT
CENTER, (Nov. 9, 2014 8:51 PM), https://www.ic3.gov/media/annualreport/
2013_IC3Report.pdf.
9. Id. at 3.
10. See Symantec Internet Security Threat Report, SYMANTEC, at 5; WARREN L. DAVIS IV &
DANIEL M. DUNLAVY, HYBRID METHODS FOR CYBERSECURITY ANALYSIS LDRD FINAL REPORT 7
(2014).
11. Spear phishing is “an email that appears to be from an individual or business that
you know” but is actually from hackers seeking “credit card and bank account numbers,
passwords, and . . . financial information.” Spear Phishing: Scam, Not Sport, NORTON BY SY-
MANTEC, http://us.norton.com/spear-phishing-scam-not-sport/article (last visited Apr. 8,
2016).
12. A watering-hole attack is “a targeted attack designed to compromise users within a
specific industry or function by infecting a website they typically visit and luring them to a
malicious site.” Threat #6 Watering Hole, PROOFPOINT THREATINSIGHT, (Nov. 9, 2014 10:43
PM), https://www.proofpoint.com/us/threat-insight/introduction-to-threats.
894 University of Michigan Journal of Law Reform [VOL. 49:4
2. Qualitative Costs
13. Aaron Boyd, Malware Getting More Advanced, Easier to Use in 2015, FEDERAL TIMES (Jan.
19, 2015), http://www.federaltimes.com/story/government/cybersecurity/2015/01/19/
malware-attacks-advanced-2015/21108035/.
14. See Symantec Internet Security Threat Report, supra note 10, at 13.
15. See Sam Young, Contemplating Corporate Disclosure Obligations Arising from Cybersecurity
Breaches, 38 J. CORP. L. 659, 661 (2013).
16. Paul Ziobro & Danny Yadron, Target Now Says 70 Million People Hit in Data Breach,
WALL STREET J., (Jan. 10, 2014, 8:36 PM), http://online.wsj.com/articles/SB1000142405270
2303754404579312232546392464.
17. Id.; see also Teri Radichel, Case Study: Critical Controls that Could Have Prevented Target
Breach, SANS INST. 1, 2 (Aug. 5, 2014), https://www.sans.org/reading-room/whitepapers/
casestudies/case-study-critical-controls-prevented-target-breach-35412.
18. Id. at 4.
19. Id.
20. Id.
SUMMER 2016] Common Law and Common Sense 895
21. Id.
22. Id.
23. Id.
24. Id.
25. Adriana Cheng, Target Data Breach Has Lingering Effect on Customer Service, Reputation
Scores, WALL STREET J. (Apr. 2, 2014, 12:40 PM), http://blogs.marketwatch.com/behindthe
storefront/2014/04/02/target-data-breach-has-lingering-effect-on-customer-service-reputa
tion-scores/.
26. SANS INST., supra note 17, at 4.
27. Facilitating Cyber Threat Information Sharing and Partnering with the Private Sector to Pro-
tect Critical Infrastructure: An Assessment of DHS Capabilities Before the Subcomm. on Cybersecurity,
Infrastructure Prot., & Sec. Tech. of the House Comm. on Homeland Sec’y, 113th Cong. 8 (2013).
28. Id.
29. Symantec, Anatomy of a Data Breach: Why Breaches Happen and What to Do About It,
SYMANTEC, 5 (2009), http://eval.symantec.com/mktginfo/enterprise/white_papers/b-anato
my_of_a_data_breach_WP_20049424-1.en-us.pdf.
30. Id. at 3.
31. Swathi Padmanabhan, Hacking for Lulz: Employing Expert Hackers to Combat Cyber Terror-
ism, 15 VAND. J. ENT. & TECH. L. 191, 193–94, 199–204 (2012).
896 University of Michigan Journal of Law Reform [VOL. 49:4
1. Passive Defense
42. See Teplinsky, infra note 139, at 314; Lieutenant Commander Matthew J. Sklerov,
Solving the Dilemma of State Responses to Cyberattacks: A Justification for the Use of Active Defenses
Against States Who Neglect Their Duty to Prevent, 2010 MIL. L. REV. 1, 3 n.5 (2009).
43. Id. at 21.
44. Id. at 22.
45. Id.
46. Access control systems employ authentication processes to deny some users because
they are “undefined,” or because they do not have any designated label in the system. Legacy
Authentication, CHECK POINT SOFTWARE TECHNOLOGIES, https://sc1.checkpoint.com/docu
ments/R76/CP_R76_SGW_WebAdmin/6721.htm (last visited Apr. 8, 2016); Fundamentals of
Information Systems Security: Access Control Practices, WIKIBOOKS, http://en.wikibooks.org/wiki/
Fundamentals_of_Information_Systems_Security/Access_Control_Systems#Access_Control_
Practices (last visited Apr. 8, 2016).
47. Fundamentals of Information Systems Security: Access Control Practices, WIKIBOOKS, http://
en.wikibooks.org/wiki/Fundamentals_of_Information_Systems_Security/Access_Control_
Systems#Access_Control_Practices (last visited Apr. 8, 2016).
48. Sklerov, supra note 42, at 22. According to Sklerov, tokens “contain electronic code
that allows access [to] a system, and may even be so sophisticated as to continually calculate
new passwords based on time of day or secure algorithms. The computer system being ac-
cessed will have matching information to the security device, and will grant access once the
petitioning party’s password matches.” Id. at 22 n.130.
49. Id. at 23.
50. See, e.g, Thomson Reuters Data Access Control System (DACS), (DACS, Open DACS Permis-
sions Server, DACS On-Demand): Administering Your Enterprise Information Flows, THOMSON
898 University of Michigan Journal of Law Reform [VOL. 49:4
2. Active Defense
74. Sean L. Harrington, Cyber Security Active Defense: Playing with Fire or Sound Risk Manage-
ment?, 20 RICH. J.L. & TECH. 1, 4 (2014).
75. Id. at 11. Harrington discusses the ambiguities surrounding the potential legality or
illegality of beaconing. Id. at 9–10.
76. Id. at 9.
77. These attacks would functionally cause the hacker’s computer to stop working.
Shane McGee, Randy V. Sabett & Anand Shah, Adequate Attribution: A Framework for Developing
a National Policy for Private Sector Use of Active Defense, 8 J. BUS. & TECH. L. 1, 12 (2013).
78. Westby, supra note 66.
79. Lachow, supra note 63, at 6.
80. Id.
81. Id. at 6–7.
SUMMER 2016] Common Law and Common Sense 901
82. See Shane Huang, Proposing a Self-Help Privilege for Victims of Cyber Attacks, 82 GEO.
WASH. L. REV. 1229, 1233 (2014) (noting that “current law is ambiguous regarding private
sector counterattacks”).
83. CHARLES DOYLE, CONGRESSIONAL RESEARCH SERVICE, CYBERCRIME: AN OVERVIEW OF
THE FEDERAL COMPUTER FRAUD AND ABUSE STATUTE AND RELATED FEDERAL CRIMINAL LAWS 1
(2014).
84. See OFFICE OF LEGAL EDUC., EXEC. OFFICE FOR U.S. ATTORNEYS, PROSECUTING COM-
PUTER CRIMES 3 (2010) (internal formatting omitted).
85. Id. at 1.
86. Id. at 1–2.
87. Id. at 2.
88. 18 U.S.C. § 1030(g) (2008); see also Deborah F. Buckham, Annotation, Validity, Con-
struction, and Application of Computer Fraud and Abuse Act (18 U.S.C.A. §1830), 174 AM. L. REP.
FED. 101 (2001).
89. OFFICE OF LEGAL EDUC., supra note 84, at 20.
902 University of Michigan Journal of Law Reform [VOL. 49:4
6. Other Statutes
118. See Andy Greenberg & Yael Grauer, CISA Security Bill Passes Senate With Privacy Flaws
Unfixed, WIRED (Oct. 27, 2015 5:30 PM), http://www.wired.com/2015/10/cisa-cybersecurity-
information-sharing-act-passes-senate-vote-with-privacy-flaws/.
119. Id.
120. Id.
121. To date, the Cybersecurity Information Sharing Act, which has not yet been enacted
as law, is the most relevant cybersecurity statute passed by Congress.
122. 428 F.3d 504, 506, 513 (3d Cir. 2005).
123. Id. at 509.
124. Id.
906 University of Michigan Journal of Law Reform [VOL. 49:4
125. United States v. Ropp, 347 F. Supp. 2d 831, 832 (C.D. Cal. 2004).
126. “Ropp placed the [keylogger] on the cable that connects [victim’s] keyboard to her
computer’s central processing unit . . . . [T]he [keylogger] recorded and stored the elec-
tronic impulses traveling down the cable between her keyboard and the computer to which it
was attached. The [keylogger], in this way, ‘eavesdrops’ on the person typing messages into
the computer.” Id. at 831.
127. Id. at 832.
128. Hilderman v. Enea TekSci, Inc., 551 F. Supp. 2d 1183, 1204 (S.D. Cal. 2008).
129. Id.
130. Id. at 1205.
131. See Identity Theft and Assumption Deterrence Act, S. Rep. 105–274, 105th Cong.
(2nd Sess. 1998).
132. Id.
133. United States v. Phillips, 477 F.3d 215, 218–19, 225 (5th Cir. 2007).
SUMMER 2016] Common Law and Common Sense 907
1. Legislative Attempts
2. Executive Orders
141. See e.g., James Arden Barnett Jr., Cyber Security: Fixing Policy with New Principles and
Organization, in RECENT TRENDS IN NATIONAL SECURITY LAW 25, 25 (Aspatore 2014).
142. Id. at 1–2; Exec. Order 13,636, 78 Fed. Reg. 11,739; NIST, Framework for Improving
Critical Infrastructure Cybersecurity, NIST, 3, http://www.nist.gov/cyberframework/upload/
cybersecurity-framework-021214.pdf (last visited Apr. 8, 2016).
143. Id.
144. Exec. Order 13,681, 79 Fed. Reg. 63,491 (2014).
145. Id.
146. See Exec. Order 13,691, 79 Fed. Reg. 9,349 (2015).
147. Fact Sheet: Executive Order Promoting Private Sector Cybersecurity Information Sharing, THE
WHITE HOUSE (Feb. 12, 2015), https://www.whitehouse.gov/the-press-office/2015/02/12/
fact-sheet-executive-order-promoting-private-sector-cybersecurity-inform (last visited Apr. 8,
2016).
148. See Information Sharing and Analysis Organizations, DEPARTMENT OF HOMELAND SECUR-
ITY, http://www.dhs.gov/isao (last visited Apr. 8, 2016).
149. Fact Sheet: Cyber Threat Intelligence Integration Center, THE WHITE HOUSE (Feb. 25 2015),
https://www.whitehouse.gov/the-press-office/2015/02/25/fact-sheet-cyber-threat-intelli-
gence-integration-center (last visited Apr. 20, 2016). Further discussion regarding the CTIIC
is included in Part III.
SUMMER 2016] Common Law and Common Sense 909
3. Remaining Loopholes
150. Id.
151. Presidential Memorandum – Establishment of the Cyber Threat Intelligence Integration Center,
THE WHITE HOUSE (Feb. 25, 2016), https://www.whitehouse.gov/the-press-office/2015/02/
25/presidential-memorandum-establishment-cyber-threat-intelligence-integrat (last visited
Apr. 8, 2016).
152. Fact Sheet: Cyber Threat Intelligence Integration Center, THE WHITE HOUSE (Feb. 25,
2016), https://www.whitehouse.gov/the-press-office/2015/02/25/fact-sheet-cyber-threat-in-
telligence-integration-center (last visited Apr. 8, 2016).
153. Fact Sheet: Executive Order Blocking the Property of Certain Persons Engaging in Significant
Malicious Cyber-Enabled Activities, THE WHITE HOUSE (Apr. 1, 2015), https://www.whitehouse.
gov/the-press-office/2015/04/01/fact-sheet-executive-order-blocking-property-certain-per
sons-engaging-si (last visited Apr. 8, 2016).
154. Vikas Bajaj, To Catch a Hacker, N.Y. TIMES: TAKING NOTE (Apr. 1, 2015, 1:44 PM),
http://takingnote.blogs.nytimes.com/2015/04/01/to-catch-a-hacker/?_r=0.
155. See Teplinsky, supra note 139, at 276.
910 University of Michigan Journal of Law Reform [VOL. 49:4
156. For example, in 2001 Congress passed the Gramm-Leach-Billey Act, which com-
pelled security for financial institutions. Those financial institutions were to “implement a
comprehensive written information security program to: (1) ensure the security and confi-
dentiality of customer information; (2) protect against any anticipated threats or hazards to
the security or integrity of such information; and (3) protect against unauthorized access to
or use of such information.” Smedinghoff, supra note 4, at 110.
157. In 2003 Congress passed HIPAA Security Regulations, which “require covered enti-
ties to (1) ensure the confidentiality, integrity, and availability of electronic health
information, (2) protect against any reasonably anticipated threats or hazards to the security
or integrity of such information, and (3) protect against any reasonably anticipated uses or
disclosures of such information that are not permitted or required.” Id.
158. Teplinsky, supra note 139, at 276.
159. Cybersecurity Framework, NIST, http://www.nist.gov/cyberframework/ (last visited
Apr. 8, 2016).
160. Teplinsky, supra note 139, at 277–78.
161. See Presidential Memorandum – Establishment of the Cyber Threat Intelligence Integration
Center, supra note 151; Tom Risen, New Agency to Aid in Battle Against Hackers, U.S. NEWS &
WORLD REP. (Feb. 10, 2015, 4:25 PM), available at http://www.usnews.com/news/articles/
2015/02/10/new-cybersecurity-agency-to-aid-in-battle-against-hackers; Dustin Volz, What a
New $35 Million Agency Is Expected to Do for US Cyber Defense, DEF. ONE (Feb. 10, 2015), http://
www.defenseone.com/technology/2015/02/what-new-35-million-agency-expected-do-us-
cyber-defense/105048/.
162. See, e.g., West, supra note 3, at 130–32 (discussing the contemporary use of active
defense strategies and corporate hacking back).
163. See id. at 133.
164. See Messerschmidt, supra note 41, at 277 (describing how Google disclosed that it
hacks back); see also Huang, supra note 82, at 1246, 1251 (noting that “[a]mbiguous legal
standards . . . have not stopped security professionals from engaging in some legally question-
able tactics,” and that “[s]ecurity software vendors sell tools capable of real-time hackback”).
SUMMER 2016] Common Law and Common Sense 911
169. Consider, for example, the “retreat to the wall” principle of self defense. In fact,
even the right to defend one’s own life and limb has caveats, such as the duty to “retreat to
the wall.” This principle provides that “a man who, in the lawful pursuit of his business is
attacked by another, under circumstances which denote an intention to take away his life or
do him some enormous bodily harm, may lawfully kill the assailant, provided he uses all the
means in his power, otherwise to save his own life or prevent the intended harm; such as
retreating as far as he can.” 3A GILLESPIE MICH. CRIM. L. & PROC. § 91:51 (2d ed. 2014); see
also, e.g., Commonwealth v. Benoit, 892 N.E.2d 314, 326 (Mass. 2008). The “retreat to the
wall” principle has been abrogated in thirty-three states, however, under “stand-your-ground-
laws.” See AMERICAN BAR ASSOCIATION: NATIONAL TASK FORCE ON STAND YOUR GROUND LAWS,
PRELIMINARY REPORT AND RECOMMENDATIONS 10 (2014). Those laws eliminate the duty to re-
treat, but still require an objectively reasonable threat or perceived threat to life or limb. See
id. at 9.
170. See 3A GILLESPIE MICH. CRIM. L. & PROC. § 91:51.
171. RESTATEMENT (SECOND) OF TORTS § 80 (1977); see also Teel v. May Dep’t Stores Co.,
155 S.W.2d 74 (1941) (finding it reasonable for a department store owner to use reasonable
confinement in defense of property).
172. RESTATEMENT (SECOND) OF TORTS §§ 79, 80 (1977).
173. State v. Schloredt, 111 P.2d 128, 131–32 (Wyo. 1941).
174. Id. at 131.
175. Id.
SUMMER 2016] Common Law and Common Sense 913
176. WAYNE R. LAFAVE, 2 SUBSTANTIVE CRIMINAL LAW § 10.6 (2d ed. 2015); see also RE-
STATEMENT (SECOND) OF TORTS § 79 (1977) (explaining that use of deadly force for the
intrusion of property may only be justified if it is believed that the intruder may cause death
or serious bodily injury to the actor or a third party).
177. Katko v. Briney, 183 N.W.2d 657, 658 (Iowa 1979).
178. Id.
179. Id.
180. Id.; see generally Hooker v. Miller, 37 Iowa 613 (Iowa 1873); Wilder v. Gardner, 39 Ga.
App. 608 (Ga. Ct. App. 1929); State v. Beckham, 257 S.W. 817 (Mo. 1924).
181. WAYNE R. LAFAVE, 2 SUBSTANTIVE CRIMINAL LAW §10.6 (2d ed. 2015).
182. Id.
183. Id.
184. See The Offensive Approach to Cyber Security in Government and Private Industry, INFOSEC
INSTITUTE, http://resources.infosecinstitute.com/the-offensive-approach-to-cyber-security-in-
government-and-private-industry/ (last visited Apr. 8, 2016).
914 University of Michigan Journal of Law Reform [VOL. 49:4
B. Solutions
Because of these issues with active defense and hacking back, cor-
porations should instead rely on regulatory guidance regarding
permissible cyberdefense strategies. However, the problem is that
comprehensive regulatory guidance does not yet exist. The CTIIC
should utilize its expertise and functionality as an inter-agency data
repository to formulate regulations in conjunction with the FCC—
which has Congressionally delegated rulemaking authority—to clar-
ify the scope of permissible corporate cyberdefense strategies.
These regulations would have the capacity to evolve with the chang-
ing Internet landscape. This is because of the pliancy of regulations
relative to statutes. And a FCC regulatory process avoids vetogates,
as well as other complications of the political process. Critically,
closing legal loopholes will prevent corporations from relying on
risky self-help strategies and would require corporate defense strate-
gies to align with well-developed common law principles.
205. An Executive Assistant Director of the FBI, Richard McFeely noted that the “biggest
issue right now is getting the private sector to a comfort level where they can report anoma-
lies, malware, incidences within their networks. It has been very difficult with a lot of major
companies to get them to cooperate fully.” Michael D. Scott, 18 No. 2 Cyberspace Law 3, CYBER-
SPACE LAW. (March 2013).
206. Other commentators have noted the potential effectiveness of mandatory standards.
See Robert Gyenes, A Voluntary Cybersecurity Framework is Unworkable – Government Must Crack the
Whip, 14 U. PITTSBURGH J. TECH. L. & POL’Y 293, 310–13 (2014).
SUMMER 2016] Common Law and Common Sense 919
CONCLUSION