Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Your organization just won a federal contract. During the celebratory pizza party, the CXO cust in, “though the data is not confidential, it is controlled.” Simply put, this means you’re handling sensitive government data (also known as Controlled Unclassified Information or CUI), which requires safeguarding or dissemination controls for critical information that falls just short of classified status, triggering compliance with NIST SP 800-171.

When it comes to cybersecurity, even “routine” actions like applying patches can introduce risk. An update meant to fix one vulnerability can sometimes open the door to another, disrupt operations, or create compliance headaches.

In April, I had the amazing opportunity to participate in a unique AI security event put on by the National Cybersecurity Center of Excellence (NCCoE). The April event was all about getting the community together to discuss what a Cyber AI Profile should look like as an overlay to the NIST Cybersecurity Framework (CSF) 2.0.