FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W77239191> ?p ?o ?g. }

• W77239191 startingPage "349" @default.
• W77239191 abstract "TABLE OF CONTENTS INTRODUCTION I. LIABILITY SCENARIOS FOLLOWING A CYBER ATTACK A. Scenario One 1. Claims Against the Chemical Company a. Negligence Claims b. Strict Liability Claims c. Contract Claims 2. Claims Against Other Entities a. Design Defect Claims b. Failure-to-Warn Claims B. Scenario Two 1. Claims Against the Chemical Company 2. Claims Against Other Entities C. Scenario Three 1. Claims Against the Chemical Company 2. Claims Against the Cyber Security Vendor a. Claims by the Chemical Company b. Claims by other Parties D. Scenario Four 1. Claims Against the Chemical Company 2. Claims Against Other Entities E. Scenario Five 1. Claims Against the Chemical Company 2. Claims Against Other Entities II. APPLICATION OF THE SAFETY ACT TO LIABLITY RESULTING FROM A TERRORIST ATTACK A. Background of the SAFETY Act B. SAFETY Act Protections Available to Customers and Other Entities C. Application of SAFETY Act Protections to Cyber Security Vendors and Their Customers CONCLUSION INTRODUCTION Liability for a cyber attack is not limited to the attackers. An attack may be foreseeable in some circumstances, and the failure of the target or the other entities to take steps to prevent the attack can constitute a breach of duty to injured victims. in the absence of the protections provided by the Support Anti-Terrorism By Fostering Effective Technologies (SAFETY) Act, a cyber attack on a chemical facility could give rise to a number of common-law tort and contract claims (1) against the target of the attack and other entities, potentially including the target's cyber security vendors. This article discusses claims that might arise in various cyber attack scenarios and the effect of the SAFETY Act on these potential claims. (2) The SAFETY Act is a tort liability management statute that was passed as part of the Homeland Security Act of 2002. (3) Under the SAFETY Act, entities that sell or otherwise deploy products that can be used to deter, defend against, respond to, mitigate, or otherwise combat acts of terrorism are eligible to receive liability protections. These liability protections can take the form of jurisdictional defenses, a cap on liability, or a presumption of immediate dismissal of third-party liability claims. As discussed above, this article will review several scenarios to examine whether liability could be found against companies that make cyber security tools or against entities that purchase such tools. The article will then examine how the SAFETY Act could be utilized to mitigate or eliminate such liability. I. LIABILITY SCENARIOS FOLLOWING A CYBER ATTACK Cyber attacks are a well-recognized threat in today's world. (4) Companies are regularly subjected to breach attempts by individuals, organized crime, and even nation-states. These attacks have various motives, ranging from the theft of financial information or intellectual property to the disruption or destruction of operations, data, or physical facilities. (5) Below are several scenarios describing potential cyber attacks and an examination about the potential liability resulting from each. A. Scenario One A company that stores dangerous chemicals in large multi-thousand gallon tanks purchases cyber security software and hardware (physical devices attached to IT systems as a cyber security measure) to prevent outsiders from breaking into their industrial control systems. Through news reports and government-furnished intelligence, the company is well aware that, while it is not being specifically targeted by cyber-attackers, hackers have been breaking into chemical companies and seeking to take control of industrial control systems. …" @default.
• W77239191 created "2016-06-24" @default.
• W77239191 creator A5052021769 @default.
• W77239191 creator A5091810022 @default.
• W77239191 date "2013-01-01" @default.
• W77239191 modified "2023-09-27" @default.
• W77239191 title "Litigation Following a Cyber Attack: Possible Outcomes and Mitigation Strategies Utilizing the SAFETY Act" @default.
• W77239191 hasPublicationYear "2013" @default.
• W77239191 type Work @default.
• W77239191 sameAs 77239191 @default.
• W77239191 citedByCount "0" @default.
• W77239191 crossrefType "journal-article" @default.
• W77239191 hasAuthorship W77239191A5052021769 @default.
• W77239191 hasAuthorship W77239191A5091810022 @default.
• W77239191 hasConcept C10138342 @default.
• W77239191 hasConcept C108827166 @default.
• W77239191 hasConcept C144133560 @default.
• W77239191 hasConcept C162853370 @default.
• W77239191 hasConcept C200635333 @default.
• W77239191 hasConcept C2777338717 @default.
• W77239191 hasConcept C2777834853 @default.
• W77239191 hasConcept C2779517930 @default.
• W77239191 hasConcept C38652104 @default.
• W77239191 hasConcept C41008148 @default.
• W77239191 hasConcept C71745522 @default.
• W77239191 hasConceptScore W77239191C10138342 @default.
• W77239191 hasConceptScore W77239191C108827166 @default.
• W77239191 hasConceptScore W77239191C144133560 @default.
• W77239191 hasConceptScore W77239191C162853370 @default.
• W77239191 hasConceptScore W77239191C200635333 @default.
• W77239191 hasConceptScore W77239191C2777338717 @default.
• W77239191 hasConceptScore W77239191C2777834853 @default.
• W77239191 hasConceptScore W77239191C2779517930 @default.
• W77239191 hasConceptScore W77239191C38652104 @default.
• W77239191 hasConceptScore W77239191C41008148 @default.
• W77239191 hasConceptScore W77239191C71745522 @default.
• W77239191 hasIssue "3" @default.
• W77239191 hasLocation W772391911 @default.
• W77239191 hasOpenAccess W77239191 @default.
• W77239191 hasPrimaryLocation W772391911 @default.
• W77239191 hasRelatedWork W1481449633 @default.
• W77239191 hasRelatedWork W1561227960 @default.
• W77239191 hasRelatedWork W2101563345 @default.
• W77239191 hasRelatedWork W2103276759 @default.
• W77239191 hasRelatedWork W2173301970 @default.
• W77239191 hasRelatedWork W2253489503 @default.
• W77239191 hasRelatedWork W2338492429 @default.
• W77239191 hasRelatedWork W2487784979 @default.
• W77239191 hasRelatedWork W2563243935 @default.
• W77239191 hasRelatedWork W2766332463 @default.
• W77239191 hasRelatedWork W2949878041 @default.
• W77239191 hasRelatedWork W2967436886 @default.
• W77239191 hasRelatedWork W2998352765 @default.
• W77239191 hasRelatedWork W3034467091 @default.
• W77239191 hasRelatedWork W3123248919 @default.
• W77239191 hasRelatedWork W3124193089 @default.
• W77239191 hasRelatedWork W3156189339 @default.
• W77239191 hasRelatedWork W3161697898 @default.
• W77239191 hasRelatedWork W3183968355 @default.
• W77239191 hasRelatedWork W2187377832 @default.
• W77239191 hasVolume "30" @default.
• W77239191 isParatext "false" @default.
• W77239191 isRetracted "false" @default.
• W77239191 magId "77239191" @default.
• W77239191 workType "article" @default.