United States: New DOD Cybersecurity Rule Continues Onslaught Of Federal Regulations For Government Contractors

The last few months have been busy ones for contractors as the U.S. government continues to rapidly issue new requirements in an attempt to catch up in the cybersecurity arena. While the government has not yet realized its goal of establishing a uniform baseline for protecting government data in the private sector, it continues to make progress. In the past few months, the government has updated guidelines establishing baseline requirements for contractors and has given direction to agencies regarding actions that should be taken in working with contractors. While these efforts continue to move toward harmonization, agencies, for the time being, are still approaching cybersecurity on an ad hoc basis, as demonstrated by the Department of Defense's ("DOD") recent interim rule. In this Commentary, we describe these rules and anticipated future developments.

Updated Standards and Direction to Agencies

In 2010, the U.S. government designated the National Archives and Records Administration ("NARA") as the executive agency responsible for developing a government-wide program for the protection of controlled unclassified information ("CUI"). In May 2015, NARA issued a proposed rule establishing requirements for federal agencies that handle CUI. The proposed rule also authorizes these agencies to impose requirements regarding safeguarding CUI on contractors working with them. NARA indicated that it is formulating a standard Federal Acquisition Regulation ("FAR") containing CUI requirements that should be used in all federal procurement contracts. NARA expects to publish this FAR provision in 2016.

As part of establishing required protection for CUI, NARA worked with the National Institute of Standards and Technology ("NIST") to create a set of security guidelines to be used by contractors working with CUI. NIST released these guidelines in June 2015 in NIST Special Publication 800-171 ("SP 800-171"). These guidelines build on standards previously established by NIST that regulate the protection of CUI on government information systems (found in NIST Special Publication 800-53 ("SP 800-53")). NIST and NARA developed the new guidelines with the understanding that certain standards in SP 800-53 would not be appropriate for privately owned and operated contactor networks. Importantly, the SP 800-171 guidelines are tailored for nonfederal information systems that contactors already have in place, with a goal of attempting to avoid requiring contractors to completely replace legacy information systems.

The SP 800-171 guidelines identify 14 security requirement families that draw from the requirements for federal systems found in SP 800-53 and the Federal Information Processing Standard Publication 200. These set the minimum level of information security a contractor should maintain in information systems processing, storing, or transmitting CUI. The SP 800-171 guidelines do not prescribe specific controls, tasks, or system requirements. Instead, the standards contain a set of requirements that are intended to overlap with contractors' existing security processes. Contractors can use a variety of solutions to satisfy these requirements. Further, the guidelines specify that contractors may implement alternative, but equally effective, security measures to satisfy a particular requirement. These alternative measures should be based on existing and recognized security standards. To assist contractors in implementing appropriate measures or identifying appropriate alternatives, Appendix D of the NIST Guidelines maps the CUI security requirements to similar already established security controls in ISO/IEC 27001/2 or NIST SP 800-53.

As mentioned above, the new NIST standards do not automatically apply to government contracts. Rather, they are designed to provide federal agencies with recommended requirements to include in agreements with nonfederal entities. NARA has directed agencies, however, to apply the new standards in future contracts, and it is anticipated that SP 800-171 will form much of the basis of the FAR clause NARA will soon propose. As such, contractors should review the requirements in SP 800-171 and determine whether they need to update their information security practices now, as opposed to waiting for the upcoming FAR clause.

The Office of Management and Budget ("OMB") has also issued draft guidance designed to provide direction to agencies in what they should require of their contractors in connection with CUI. Like the NARA proposed rule, OMB's draft guidance recommends that agencies require their contractors to meet the SP 800-171 guidelines. In addition to the baseline security requirements, however, the OMB draft guidance also requires agencies to include contractual mandates that contractors report "cyber incidents" (including both actual compromises and potential adverse effects) that affect CUI.

The OMB draft guidance also directs agencies to conduct their own assessments of contractors' information security to confirm that they are meeting required standards. To allow for this, the guidance recommends that agencies include in contracts provisions granting access to facilities, installations, operations, documentation, databases, IT systems, devices, and the personnel used in the performance of a contract. Agencies also are advised to seek certification and confirmation of sanitization of government and government-activity-related files and information at contract closeout.

Finally, the OMB directs the General Services Administration to develop a "business due diligence" service that will provide access to risk information that will include data collected from voluntary contractor reporting, public records, publicly available data, and commercial subscription data. At this point, it is unclear how this new service will drive requests for information from contractors to build the database, but it seems likely that agencies will use their supply chain risk management authority to impose requirements for information to be included in the due diligence system.

DOD Interim Rule

The DOD has been in the vanguard of imposing cybersecurity requirements on contractors, primarily through contract clause requirements in the DFARS. Citing "urgent and compelling reasons" to issue an Interim Rule that is effective immediately, the DOD has, among other things, expanded the scope of its existing DFARS cybersecurity provisions, strengthened its reporting requirements, and updated it to account for NIST's development of SP 800-171. As this clause is a mandatory flow-down clause, it carries ramifications for all prime contractors and subcontractors working in the defense industry.

In revising DFARS 252.204-7012, DOD expanded the scope of the information covered by the clause. The clause now protects all Covered Defense Information ("CDI"), which is defined to include information provided to the contractor by the government, or obtained by the contractor in performance of the contract, that is:

  • Controlled technical information
  • Critical information for operational security
  • Export control information
  • Any other information marked or otherwise identified in the contract as requiring safeguarding or dissemination restrictions.

The scope of these categories proves somewhat expansive. For example, export control CDI includes technology controlled by the International Traffic in Arms Regulations, the Export Administration Regulations, and sensitive nuclear technology information, as might be expected. But the clause also requires safeguarding of a contractor's export license applications as CDI. It also expands CDI beyond the concept of "information." It expressly applies to "items" and "commodities," apparently requiring contractors to report an adverse effect on export-controlled items as a cyber incident. Finally, the catch-all category seemingly expands CDI to cover any information properly marked by DOD, and it could require the reporting of incidents affecting privacy data and even proprietary business information. In addition to expanding the scope of coverage, DOD updated the DFARS clause to reference SP 800-171 as a baseline for information security standards a contractor must meet, as opposed to SP 800-53, which the prior version referenced.

The DOD incident reporting requirements have been redoubled as well. The deadline to report remains 72 hours from the time that the contractor discovers a cyber incident, as does the requirement to conduct a further review of the incident for evidence of compromised CDI across the contractor's network. Subcontractors are now required to report a cyber incident both to the government directly and "up the chain" to its higher-tier contractors, ultimately reaching the prime contractor. The provision also retains the obligation of contractors to maintain an image of all known affected information systems for 90 days. In addition to preserving the damage assessment information and providing it to the government, contractors will be required, upon request, to grant DOD access to "additional information and equipment that is necessary to conduct a forensic analysis." This provision could prove quite intrusive, and although the clause places limits on the dissemination of contractor information not created by or for DOD, the exceptions are quite broad and vaguely defined (e.g., "entities with missions that may be affected by such information") and may be difficult to enforce.

Cyber incident reports must be filed online at the DOD-DIB Cyber Incident Reporting & Cyber Threat Information Sharing Portal. Reporting an incident requires a medium assurance certificate that must be acquired from an External Certification Authority. Although most prime contractors likely have such a certificate already, some small business subcontractors may not. Contractors at all tiers should obtain a medium assurance certificate in advance as part of their cybersecurity plans.

Conclusion

Contractors working with the government should become familiar with the security requirements of the NIST Guidelines in SP 800-171 as the government is moving in the direction of using these criteria to establish baseline requirements for information security. Further, contractors must understand their monitoring and reporting requirements for cyber incidents, as these are also fast becoming staples in cybersecurity contract provisions. The recent actions by NARA, OMB, and DOD give clear indication as to the government's priorities in the cybersecurity arena, and those that do business with the government will gain the most competitive advantage by proactively offering solutions that are in line with these priorities.

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.

Authors
J. Andrew Jackson
Mauricio F. Paez
Richard J. Johnson
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
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
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
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.

Disclaimer

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.

Registration

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.

Cookies

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.

Links

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.

Mail-A-Friend

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.

Security

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.