United States: The SAFETY Act: Providing Critical Liability Protections For Cyber And Physical Security Efforts

Last Updated: April 22 2014
Article by Dismas Locaria, Brian M. Zimmet and Jason R. Wool

Since September 11, 2001, Americans have been keenly aware of the need to better protect both the people and assets of the United States from those who may be intent on doing us harm. We have seen, and largely accepted, increased physical security measures at airports, government facilities, and even sporting event venues. Requirements that once would have seemed a gross invasion of privacy are now commonplace. Some of these requirements were federally mandated; however, because the private sector owns and operates the vast majority of critical infrastructure, the government has been reluctant (or perhaps unable) to impose sweeping security measures across all swaths of life. Nevertheless, despite the cost of some of these measures, we have seen the private sector increase physical security efforts in an effort to better protect the public and manage the risk of liability that could arise from an attack. In some instances, these measures were also implemented to obtain a little-known government "carrot," namely liability protection under a federal statute referred to as the SAFETY Act (or "Act").

We have been recently bombarded with both fact and fiction about the vulnerabilities of our critical infrastructure to cyber intrusion and attack. Some in Congress have sought to adopt comprehensive cybersecurity regulation, but legislative efforts to adopt such regulation have fallen short. In lieu of mandatory regulation, the federal government has sought to encourage owners and operators of critical infrastructure to adopt baseline cybersecurity measures to protect their assets, primarily through the adoption of a new Cybersecurity Framework by the National Institute of Standards and Technology ("NIST"). In its promotion of the NIST Cybersecurity Framework, the government has sought to identify incentives for owners and operators of critical infrastructure to adopt the framework. The SAFETY Act is one of the few tools in the government's toolbox that can provide concrete, achievable benefits for owners and operators of critical infrastructure. In this context, the SAFETY Act may also serve not only to incentivize the improvement of an organization's cybersecurity, thereby better protecting its assets, but may also benefit the organization at-large, in non-terror contexts.


In the wake of 9/11, Congress passed the Homeland Security Act of 2002 with a little known section called the "Support Anti-Terrorism by Fostering Effective Technologies Act of 2002," or the "SAFETY Act."1 The purpose of the SAFETY Act was to encourage the development and deployment of anti-terrorism products and services (collectively referred to by the statute and herein as "technologies") by granting various risk management protections.

The SAFETY Act, when enacted, held tremendous promise for protecting sellers of new, as well as established, technologies that were needed to combat terrorism and remove impediments to bringing such technologies to and/or maintaining their place in the market. It did so by establishing two levels of protection from third-party liability – Designation and Certification – that may arise from injury, loss of life, or damage to property or businesses arising out of an act of terrorism where the technology was deployed in defense against, response to or recovery from such an act.

Importantly, in the final rule, the Department of Homeland Security ("DHS") recognized that to encourage industry to make new technologies would likely mean that some would require additional development, testing and evaluation before being available for deployment.2 As a result the final regulation implements a process whereby technologies in development may be afforded SAFETY Act Designation.3 This type of Designation is referred to as Developmental Testing and Evaluation ("DT&E") Designation. This is particularly significant to potential sellers of technologies that may be reluctant to enter the marketplace, or cannot find affordable insurance, for fear of massive liability. This process sees to it that promising technologies are not killed at the drawing board due to the enormity of liability arising from acts they are designed to prevent.

The Benefits of the SAFETY Act

The SAFETY Act offers substantial protections for sellers of technologies that receive Designation, or the higher-tiered protection, Certification. Designation (including DT&E Designation) most notably caps third-party liability at an approved level of insurance. The Act, however, also includes a myriad of additional risk management benefits along with Designation, such as exclusive jurisdiction in federal court for suits against sellers of a technology arising from acts of terrorism; a bar against punitive damages and prejudgment interest; a limitation on non-economic damages; and liability only in proportion to the responsibility of the seller.

The second level of protection – Certification – confers all of the benefits of Designation as well as the marked addition of potential immunization from liability via the Government Contractor Defense.4 The assertion of this defense, however, can be rebutted by proving with clear and convincing evidence that fraud or willful misconduct occurred by the seller in submitting information to DHS. Certified technologies are also deemed "Approved Products for Homeland Security" by DHS.

Designation and Certification protections are awarded in five-year increments, which can be renewed in increments of five years thereafter. DT&E Designation limits the term of protection to 36 months (with no continuing survivorship for the life of the technology), and is terminable at will by DHS.

Perhaps the greatest benefit of either Designation or Certification, however, is that the Act itself provides that the only proper party defendant to a lawsuit arising out of an act of terrorism is the seller. Thus, customers, clients, subcontractors and vendors that either consume the technology or support the seller in deploying the technology are immune from liability. As one can imagine, providing customers and potential customers with the benefit of immunizing them from the potentially ruinous cost of terrorism liability is a tremendous market differentiator. Importantly, however, one does not have to provide the covered Technology to consumers to be considered a seller. Under the Act, an entity can provide a product or service to itself and still obtain Designation or Certification. In instances such as these, the entity would be a seller to itself.

An Act of Terrorism

The protections of the SAFETY Act are triggered by an "act of terrorism."5 By statute, an "act of terrorism" is an act, determined by the Secretary of DHS, that:

  1. [I]s unlawful;
  2. [C]auses harm to a person, property, or entity, in the United States, or in the case of a domestic United States air carrier or a United States-flag vessel (or a vessel based principally in the United States on which United States income tax is paid and whose insurance coverage is subject to regulation in the United States), in or outside the United States; and
  3. [U]ses or attempts to use instrumentalities, weapons or other methods designed or intended to cause mass destruction, injury or other loss to citizens or institutions of the United States.6

Importantly, the final rule to the SAFETY Act expands on the definition of "harm" to include "financial harm," either by nature or degree. This expansion of "harm" potentially broadens the applicability of the Act considerably by removing any need for physical damage.

Obtaining SAFETY Act Protections

SAFETY Act protections are sought through an application process. Designation must first be achieved to receive Certification, although applicants may seek both protections simultaneously as part of the same application submission. To receive Designation, applicants must demonstrate that a proposed technology meets various criteria, including:

  • That the technology has utility and is effective;
  • That the seller of the proposed technology has large or unquantifiable potential third-party liability risk exposure;
  • That it is likely that without the SAFETY Act's protections, the liability associated with the technology would prevent or curtail the proposed technology's deployment;
  • That there be a substantial potential risk exposure to the public should the technology not be deployed; and
  • Any other factors DHS deems relevant to the security of the United States.

For Certification, applicants must satisfy all of the criteria of Designation, as well as provide information evidencing that the technology can meet three additional criteria, that the technology: 1) performs as intended; 2) conforms to specifications; and 3) is safe for use.

Ten Years and Counting

The SAFETY Act had a slow start following its inception in late 2002 as DHS established its Office of SAFETY Act Implementation ("OSAI") and finalized its internal procedures and operating policies. Following the statute's enactment, a proposed rule was issued in July 2003,7 followed by an interim rule in October 2003.8 Also in October 2003, DHS issued the first iteration of the SAFETY Act Application Kit. However, DHS took almost two years to issue a final regulation and revised Application Kit.9

The processing of applications for the SAFETY Act's protections was initially slow as well – from October 2003, when the initial SAFETY Act Application Kit was first published, until June 18, 2004 – a period of eight months – just three technologies received Certification status. It took another eight months to double that number to six Designations and Certifications. Today, while over 900 technologies have received SAFETY Act protections, this amounts to less than 100 per year. Thus, while the SAFETY Act holds tremendous benefits for corporations of all kinds, it remains something of a secret.

The SAFETY Act Today

While the event that led to the creation of the SAFETY Act was an act of physical terror, there is no question that cyber-attacks can also have enormously destructive effects, especially in the context of critical infrastructure. Moreover, current and former officials of the FBI and DHS, as well as numerous members of Congress, agree that cyber-terrorism is a significant security concern.

The potential liability from a successful cyber-terrorist attack is substantial. Disruption to a company's operations alone can result in lost business, negative customer reaction, financial harm, government investigations, contract breaches, shareholder lawsuits, and more. In some instances, a cyber-attack could also result in physical destruction and harm, which could expose the victim to tort liability. For owners and operators of information technology systems, the ramifications of a cyber-attack can extend to large swaths of third parties (think of a major power outage, lack of telecommunications, or broken ATMs).

Owners of such systems should explore the possibility of seeking SAFETY Act coverage as a way to complement cybersecurity insurance policies and other risk-mitigation tools. Such consideration would include:

  • Reviewing your cyber-attack risks and potential liabilities to determine whether obtaining SAFETY Act coverage would benefit your business;
  • Examining whether any of your security systems, business continuity, physical and cyber-related defense/mitigation plans, or other products and services qualify for coverage under the SAFETY Act;
  • To the extent possible, procuring SAFETY Act-approved products and services to take advantage of the liability flow downs, or working with your business partners to encourage them to obtain SAFETY Act coverage; and
  • Including SAFETY Act requirements in all of your security product and service procurements.

Any entity that sells cybersecurity solutions to owners of information technology systems should consider applying for SAFETY Act protection for such products or services. First, such sellers should review or seek advice on whether your products and services are likely to qualify for coverage under the SAFETY Act. If your products or services do not currently qualify for coverage, keep the SAFETY Act in mind, because it may be a significant way to differentiate your future products and services from those of your competitors.

Put simply, the SAFETY Act represents a win/win for both the government and private industry. By taking advantage of the program, private industry can help protect the country from cyber-attack while also lowering insurance costs and mitigating liability risks. Even in the absence of a terrorist attack, SAFETY Act coverage serves as a stamp of approval from the federal government that a Technology – which, again, includes security services that a company provides to itself – is an effective tool for preventing, detecting, or responding to cyber-attacks. Coverage is therefore not only a market differentiator, but also significant evidence of commercial reasonableness in legal proceedings not associated with an act of terrorism. As a result, any company facing cyber-risk should carefully consider how a SAFETY Act Designation or Certification could protect its interests and elevate its standing in the marketplace.


1. Homeland Security Act of 2002, Pub. L. No. 107-246, §§ 861-865, 116 Stat. 2135 (2002) (Title VII, Subtitle G) (codified at 6 U.S.C. §§ 441-444). The Department of Homeland Security issued the final rule, implementing the SAFETY Act on June 8, 2006 (71 Fed. Reg. 33,147 et seq. (June 8, 2006, Final Rule), which codified the Act's implementing regulations at 6 C.F.R. Part 25.

2. 71 Fed. Reg. 33,147, 33,156 (June 8, 2006, Final Rule).

3. 6 C.F.R. § 25.4(f).

4. The Government Contractor Defense arose out of a landmark case, Boyle v. United Technologies Corporation, 487 U.S. 500 (1988), whereby the U.S. Supreme Court determined that a defense contractor manufacturing a military product in accordance with precise government specifications may not be held liable for claims resulting from use of the manufactured product. With respect to the SAFETY Act, DHS limits the defense to that which existed on the day of the SAFETY Act's enactment (November 25, 2002), meaning that future judicial developments in the government contractor defense would not apply. Hence, the considerable body of law growing out of Boyle, and its progeny up to the enactment of the SAFETY Act (November 25, 2002), are essentially frozen in time.

5. 6 U.S.C. § 444(2).

6. Id.

7. 68 Fed. Reg. 41,420 et seq. (July 11, 2003, Proposed Rule).

8. 68 Fed. Reg. 59,684 et seq. (October 16, 2003, Interim Rule).

9. 71 Fed. Reg. 33,147 et seq. (June 8, 2006, Final Rule).

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.