What the heck is shared responsibility in CMMC?
Most Department of Defense (DoD) contractors, especially small businesses, rely on the help of External Service Providers (ESP) for their operational needs. Whether for day-to-day IT
Most Department of Defense (DoD) contractors, especially small businesses, rely on the help of External Service Providers (ESP) for their operational needs. Whether for day-to-day IT
For Department of Defense (DoD) contractors that are pursuing Cybersecurity Maturity Model Certification (CMMC) compliance, you may have heard recent buzz of “organization-defined parameters” (ODP)
Federal government contractors that handle Controlled Unclassified Information (CUI) must implement the National Institutes of Standards and Technology (NIST) Special Publication 800-171. NIST 800-171 lists
All federal government contractors handle Federal Contract Information (FCI) in some form or another. We cover the definition of FCI in a previous post, but
Federal government contractors that handle Controlled Unclassified Information (CUI) must implement the National Institutes of Standards and Technology (NIST) cybersecurity standard 800-171. In May 2024,
Between the DoD’s publication of the FedRAMP equivalency memo, the subsequent discussion amongst the CMMC community, and more small businesses providing cloud-based services to the
Federal contractors required to implement the cybersecurity controls in NIST SP 800-171 may be confused when addressing safeguards involving the protection of “sessions”, particularly user
Microsoft. When you hear this word, what goes through your mind? Is it joy? Perhaps frustration? Maybe it’s robust features like Azure. What about Azure Virtual
US Department of Defense (DoD) contractors that handle Controlled Unclassified Information (CUI) are required to secure that CUI by implementing the National Institutes of Standards