The Federal Information Security Modernization Act (FISMA) of 2014 establishes reforms and enhancements to the original 2002 FISMA legislation, which establishes the purpose of establishing a foundation of requirements that strengthen the security posture of information systems servicing the federal government. When most agencies (and their vendors) discuss establishing “FISMA compliance,” they are usually referring to meeting the controls identified in NIST SP 800-53, “Security and Privacy Controls for Information Systems and Organizations.” The law is enforced through various processes, as described by the Office of Management and Budget Circular (OMB) A-130. OMB A-130 establishes definitions, processes, and requirements for federal agencies to follow. FISMA (through A-130) recommends guidance issued by NIST, such as FIPS 199, FIPS 200 for impact-level categorization (low, moderate, or high-impact systems), and NIST 800-53A for the selection and implementation of security controls based on the system impact level. The control selection, implementation, and testing are where the rubber meets the road for many IT professionals responsible for “FISMA compliance,” especially when meeting compliance is essential to receiving an authority to operate (ATO) by government agencies.
FedRAMP is a result of the ”Cloud First” policy issued in Feb. 2011 (with more recent updates and enhancements), and OMB memo Security Authorization of Information Systems in Cloud Computing requiring the use of FedRAMP authorized cloud services by agencies in an effort to reduce costs on underutilized IT infrastructure and to streamline the IT procurement process. The FedRAMP Authorization Act of 2023 codified the program as the authoritative standard to security assessment and authorization for cloud computing products and services that process unclassified federal information. The core purpose of FedRAMP is to provide a standard for Cloud Service Providers (CSPs) to comply with federal cybersecurity requirements, validate meeting those requirements via a FedRAMP third party assessment organization (3PAO) and obtain a provisional ATO. Any commercial cloud vendor that provides cloud services to the federal government must achieve a FedRAMP P-ATO. FedRAMP is FISMA for the cloud as it inherits the NIST baseline of controls but is tailored for the cloud. Like FISMA, FedRAMP follows guidance established in NIST 800-53. In addition, the FedRAMP Program Management Office (PMO) has developed and published additional security control requirements for implementation and testing as part of the FedRAMP program. These additional controls and security test cases for a FedRAMP security assessment can be found on FedRAMP.gov.
Serving the unique needs of the Department of Defense (DoD), the FedRAMP+ leverages the FedRAMP baseline and adds specific security controls and requirements necessary to meet and assure DoD’s critical mission requirements. The DoD Security Requirements Guide (SRG) was developed by the Defense Information Systems Agency (DISA) for DoD agencies and DoD Mission Owners. The “plus” in FedRAMP+ signifies the additional security requirements that DISA has built on top of what FedRAMP as a program establishes for a risk-based approach in standardizing the adoption and use of cloud services by the federal government. The SRG establishes Impact Levels 2, 4, 5 and 6 based on information system sensitivity and security requirements. For CSPs with DoD customers, meeting the SRG requirements are a component to achieving a DoD Provisional Authorization (PA).