It's especially fun when you work for a contract manufacturer, like the company I work for, where some of our customers are under the compliance requirements and some aren't.
CUI wise, there is a CUI Registry, https://www.archives.gov/cui/registry/category-detail/controlled-technical-info.html, that gives at least some decent guidelines on what should and shouldn't be considered controlled unclassified information, but it's still supposed to be up to the prime to be clearly labeling their data accordingly. Half the time THEY don't even know what is and isn't CUI.
We were working on CMMC Level 3, but now with the most recent changes we're shifted down to Level 2. In theory it should be easier to implement now, but we'll see. At least we're now allowed to have a POAM under CMMC.
Joeatheist wrote:
MikeRigsby wrote:
It might also help for those of us having to deal with NIST 800-171, DFARS, and CMMC to figure out exactly what type of data from LANSweeper would be beneficial.
Agreed. It would also be nice if the CMMC accreditation board would make up their minds as to what will actually be required of us. From what I have read there are expected changes to CMMC ver 2.0 already. Not to mention that genuine CUI does not yet exist. If you remember we were told that older contracts will not be modified and therefore we will not be required to meet the compliance standards "Retro-actively", and that any CUI we receive in the future will be clearly labeled as such. To this day our company has yet to see anything, that according to the DoD, that has been labeled at both the top and bottom of the document with the markings that would identify it as Controlled Unclassified Information.
Kind regards,
Joe Schwartz
IT / Cybersecurity Manager
Ciao Wireless, Inc.