Final Government Contractor Basic Data Security Rule Issued

by WilmerHale

On May 16, 2016, the Federal Acquisition Regulations (“FAR”) Council published the final FAR rule on Basic Safeguarding of Contractor Information Systems.1 The rule is intended to prescribe “the most basic level” of safeguards, “reflective of actions a prudent business person would employ.”2


The rule, which includes a new contract clause, will apply to all acquisitions by any federal executive agency, beginning June 15, 2016, when a contractor's information system may contain “Federal contract information,” including acquisitions below the simplified acquisition threshold and for commercial items other than commercially available off-the-shelf (“COTS”) items.3

A key factor in applying the new rule is whether a contractor's information system contains “Federal contract information.” That term is defined intentionally broadly as “information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the Government, but not including information by the Government to the public (such as that on public websites) or simple transaction information, such as that necessary to process payments.”4The safeguarding requirements apply to all “covered contractor information systems,” namely, those information systems owned or operated by a contractor that process, store, or transmit Federal contract information.5

The substance of the contract clause prescribed by the rule must be flowed down in all subcontracts, other than contracts for COTS items, in which the subcontractor may have Federal contract information residing in or transiting through its information systems.6


The contract clause requires contractors to implement fifteen specified safeguards, including access control; identification and authentication safeguards; media, physical, system, and communication protection; and system and information integrity. The fifteen safeguards are listed at the end of this discussion. Each of the listed safeguards is drawn from the National Institute of Standards and Technology (“NIST”) Special Publication (“SP”) 800-171,7 which was intended to apply to more sensitive “Controlled Unclassified Information” (“CUI”).

This is not the first time that NIST SP 800-171 has been used to impose requirements on federal contractors. Department of Defense (“DoD”) contractors and subcontractors handling “Covered Defense Information” have until December 31, 2017 to fully implement all NIST SP 800-171 requirements on their covered systems pursuant to the recently implemented interim final DoD FAR Supplement (“DFARS”) rule on Network Penetration Reporting and Contracting for Cloud Services.8Unlike the DFARS rule, the new FAR rule does not impose all NIST SP 800-171 requirements on covered entities, but instead draws upon the requirements of NIST SP 800-171 with the intent of reflecting basic good cyber practices.  As such, many contractors and subcontractors are likely to be in compliance with the new FAR rule's requirements, particularly those contractors who are subject to the DFARS rule and are implementing NIST SP 800-171.

However, some safeguards mandated by the new FAR rule may present challenges for some contractors who do not currently have significant security safeguards. For example, contractors with information systems processing, storing, or transmitting Federal contract information will be required to:

  • “Monitor . . . organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.”9
  • “Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.”10
  • “Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.”11

While there are a variety of ways to implement these requirements, some companies subject to the rule may not meet these requirements and will have to upgrade their security practices accordingly.

One of the requirements is to “[i]dentify, report, and correct information and information system flaws in a timely manner.”12 In response to comments on the proposed rule suggesting imposing additional requirements, including an incident detection, reporting, and response requirement, the Federal Register notice states that “[t]his rule establishes minimum standards for contractors' information systems that process, store, or transmit Federal contract information where the sensitivity/impact level of the Federal contract information being protected does not warrant a level of protecting necessitating . . . detecting, reporting, and responding to security incidents . . .”13 The scope of the requirement to report information and information systems flaws is unclear, but these official comments suggest that the requirement may be an internal reporting requirement and not a requirement to report flaws to the contracting agency.

Looking Forward

  • Focus on Information Systems Rather than Information. The most significant change between the final rule and the proposed rule, published in 2012,14 was the shift in focus from protecting specific types of information to protecting the systems processing, storing, or transmitting that information. This is consistent with the construct in the DFARS rule, and may reflect a new government approach that will be carried through in future rulemaking, including pending rules from the National Archives and Records Administration (“NARA”), discussed below.
  • Compliance and Enforcement. The new rule does not include any new compliance or monitoring mechanisms. However, contractors failing to comply with the rule could be subject to liability under existing laws and regulations, such as the False Claims Act. Notably, one of the comments on the proposed rule expressed concern that an inadvertent release of information “could be turned into not only an information security issue but also a potential breach of contract.” In response, the Federal Register notice states that, “[g]enerally, as long as the safeguards are in place, failure of the controls to adequately protect the information does not constitute a breach of contract.”15
  • Other Contractor Data Security Rules and Requirements. The Federal Register notice notes that this rule is being issued as “just one step in a series of coordinated regulatory actions being taken or planned to strengthen protections of information systems.”16 The notice specifically highlights the draft Office of Management and Budget (“OMB”) guidance issued last summer regarding the protection of CUI (which recommended requiring contractor compliance with all of NIST SP 800-171 for contractors handling CUI),17 a rule addressing CUI being finalized by NARA, eventual FAR Council coordination and implementation when the OMB guidance and NARA rule are finalized, and the DFARS interim rule.18 As such, this rule establishes a baseline, and “does not relieve [] contractor[s] of any specific safeguarding requirement[] specified by Federal agencies and departments as it relates to covered contractor information systems generally or other Federal requirements for safeguarding [CUI].”19 Contractors should continue monitoring other developments, as well as reviewing any clauses regarding the protection of information or data security requirements that may be included in their contracts.

Full List of Safeguards

The rule requires covered contractor information systems to include, at a minimum, the following security controls:

  • Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems);
  • Limit information system access to the types of transactions and functions that authorized users are permitted to execute;
  • Verify and control/limit connections to and use of external information systems;
  • Control information posted or processed on publicly accessible information systems;
  • Identify information system users, processes acting on behalf of users, or devices;
  • Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems;
  • Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse;
  • Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals;
  • Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices; 
  • Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems; 
  • Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks;
  • Identify, report, and correct information and information system flaws in a timely manner; 
  • Provide protection from malicious code at appropriate locations within organizational information systems;
  • Update malicious code protection mechanisms when new releases are available; and
  • Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.20

1 81 Fed. Reg. 30439 (May 16, 2016), available here.

2 Id. at 30440-41.

3 FAR § 4.1902.

4 Id. §§ 4.1901, 52.204-21(a).

5 Id.

6 Id. § 52.204-21(c).

7 NIST SP 800-171 is available here.

8 80 Fed. Reg. 81472 (Dec. 30, 2015), available here. For more information on the DoD interim final rule, see our previous alert, available here.

9 FAR § 52.204-21(b)(x).

10 Id. §52.204-21(b)(xi).

11 Id. § 52.204-21(b)(xv) (emphasis added).

12 Id. § 52.204-21(b)(xii) (emphasis added).

13 81 Fed. Reg. at 30443-44.

14 77 Fed. Reg. 20881 (Aug. 24, 2012), available here.

15 81 Fed. Reg. at 30444.

16 Id. at 30440.

17 The draft guidance is available here. For more information about the draft guidance, view the recording and materials from the recent installment of our Cybersecurity, Privacy and Communications Webinar Series: Recent Data Security Developments for Government Contractors, available here.

18 81 Fed. Reg. at 30440.

19 Id.

20 FAR § 52.204-21(b).


DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© WilmerHale | Attorney Advertising

Written by:


WilmerHale on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.


JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at:

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.