Request Demo

DFARS

Taking Charge of DFARS Compliance

down-arrow

If your company generates Department of Defense(DoD) related revenue, you likely fall under DFARS. If you want your DoD contracts to continue after the end of 2017, you need to take a close look at the Defense Federal Acquisition Regulation Supplement (DFARS) clause 225.204-7012. The regulation gives all the government contractors a deadline of December 31, 2017 to implement NIST Special Publication (SP) 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations. The fastest, most thorough solution available that you can use to complete your assessment for the lowest cost (experts provided) is available here. Otherwise, keep reading on.

What is the DFARS mandate?

The federal government is relying on external services to help carry out a wide range of federal missions as well as business functions. Many federal contractors and subcontractors “routinely process, store, and transmit sensitive federal information in their information systems to support the delivery of essential products and services to federal agencies.” With that being said, the contractor community has to provide assurance to DoD that their IT system can offer a high level of security to protect this sensitive information. If any contractor fails to do so, they can inevitably lose their contracts.

The document details requirements for protecting Controlled Unclassified Information (CUI) when:

  • The CUI is resident in nonfederal information systems and organizations

  • The information systems where the CUI resides are not used or operated by contractors of federal agencies or other organizations on behalf of those agencies

  • Where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or governmentwide policy for the CUI category or subcategory listed in the CUI Registry

In practical terms, although companies that work with the DoD already apply rigorous controls over classified data, now the protection is extended to the unclassified systems that include covered defense information, which creates wider-reaching consequences for the contractors. Being compliant can determine the future of businesses.

Who is impacted by NIST 800-171?

The requirements apply to all components of nonfederal information systems and organizations that process, store, or transmit CUI, or provide security protection for such components, which can be found in the CUI category list. The CUI requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.

Making the Business Decision

While implementing those requirements might seem arduous, it is important to know that these NIST standards are best practice standards that your company could have already implemented as part of maintaining a good security system. Each requirement on the list can help your firm stay away from different cyber events and safeguard CUI.

Even though there are a lot of aspects a company needs to consider, such as budget and resources, keep in mind that achieving compliance is the only option you have if you to win fugure contracts, and the clock is ticking.
 

Get on the right path:

  • Run a Security Assessment: this can help to have a clear vision of where your organization stands, and if you are in compliance with all the requirements.
  • Implementation: once you identified all the deficiencies in your IT system, you need to create a plan to help you complete the implementation. It should protect all the sensitive defense information as well as strengthen your system. Your POAM & SSP are crucial to documenting this step.
  • Partner with a third party: finding a trustworthy and experienced company to run your assessment, ease the process, and monitor and document continuing compliance. NIST SP 800-171 compliance is a dynamic process and there is only weeks left until the deadline. Reaching compliance, for now, is just the start, but maintaining the compliance is key.

Reach out to us for more information on how to get your assessment, complaince documents and policies in order before the deadline, and certainly before you try and win contracts in the future. We will help you weight the cost-impact of complying to DFARS and give you the most effective path to success available.

You may also like

Contextualize Quantified Cyber ...
on April 11, 2019

Now more than ever, CISO’s are being tasked with delivering hard metrics around an enterprise’s technology and digital risk. While this is nothing new for seasoned IT ...

NYDFS Implementation Grace Period ...
on April 9, 2019

Following the Equifax breach and growing concerns about the posture of the financial industry, New York State Department of Financial Services (NYDFS) released the initial ...

CEO's - Do You Know Where That ...
on April 5, 2019

It is no secret that cybersecurity has mystified many members of the C-suite since the function was introduced. With headlines dominated by breaches and hearings of information ...

Jerry Layden
Carbon Black Report Indicates ...
on April 2, 2019

In their third Global Incident Response Threat Report our Massachusetts neighbor, Carbon Black, illustrates not only the top industries for cyber attack but a deeply concerning ...

Legacy GRC And The Sunk Cost ...
on March 28, 2019

Last month, we covered how legacy GRC products and new integrated risk management (IRM) solutions can co-exist and in fact compliment each other. That said, in order for them to ...

Alison Furneaux
What To Expect From The Imminent ...
on April 6, 2019

While the NIST Privacy Framework may be the headliner for the most anticipated new publication from the National Institute of Standards and Technology, there are two imminent ...