Beyond Compliance: DFARs 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting: A Matter of National Security

The DOD Guidance provides additional information on how they might penalize business partners who fail to adhere to new security rules, including penalties and not being awarded new contracts. Aside from the obvious competitive business reasons to immediately implement the NIST 800-171 security requirements this latest theft of project Sea Dragon data is reminder of the implications to national security. Most of NIST 800-171 is just good cybersecurity hygiene that at a minimum will make contractors harder targets for hostile nation states.

Are You Fully Compliant with DOD’s New Cybersecurity Standards?

The December 31, 2017 deadline for achieving compliance with NIST 800-171 has come and gone. If you’re still not compliant, you’re at risk for penalties, and chances of winning future contracts and bids are at great risk. The good news is it’s not too late!

How to Enable Applications Teams to Secure Code (part 2)

It’s more important than ever to make sure your applications are secure. What tools are available to help in this effort – and what are the pros, cons, features, and benefits of these enablement tools?

Applying NIST 800-171 Rev. 1 in a Manufacturing Environment

Are you a U.S. manufacturers who supply products within supply chains for the DOD? If you are it’s likely that you are required to ensure adequate security by implementing NIST SP 800-171 as part ensuring compliance with DFARS clause 252.204-7012. Achieving NIST SP 800-171 Rev. 1 compliance for a manufacturing a business has its own unique challenges.

How to Ensure NIST 800-171 Subcontractor Compliance

The December 31, 2017 deadline for creating your SSP and POA&Ms aligned with NIST special publication 800-171 requirements has passed. If you are a DOD prime contractor, now it’s time to focus subcontractor compliance.