Your Top Five Cyber Risks in Five Clicks with the Free Cyber Risk Analysis

FREE RISK ANALYSIS
Request Demo

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

Top Cybersecurity Predictions for ...
on January 21, 2025

Cybersecurity in 2025: Key Predictions As we approach 2025, the cybersecurity landscape is poised for significant shifts. Experts predict a move towards more practical AI ...

A Pocket Guide to Cyber Risk ...
on January 16, 2025

Cybersecurity is no longer just about firewalls and antivirus software. In today's data-driven world, effectively managing cybersecurity risk requires quantification: turning ...

Choosing the Right Cyber Risk ...
on December 27, 2024

Selecting a cyber risk management solution is a critical decision for any organization. The process requires careful consideration of your needs, how a platform can meet them, and ...

How to Streamline Your ...
on December 24, 2024

Many industry regulations require or promote cybersecurity risk assessments to bolster incident response, but what is a cybersecurity risk assessment? For example, cyber risk ...

Alison Furneaux
CISO Reporting Structure ...
on December 23, 2024

The Changing Landscape of CISO Reporting The Chief Information Security Officer (CISO) role has evolved dramatically in recent years. Traditionally reporting to the Chief ...

How to Leverage the FAIR Model ...
on December 19, 2024

In light of the Colonial Pipeline cyberattack, measuring risk is on everyone’s minds. However, quantifying risk is often not easy. So many factors go into determining and ...

Kyndall Elliott