Tag: government cybersecurity

Navigating FedRAMP’s 2024 Updates – What CSPs Need to Know

September 27, 2024 at 8:00 am by Amanda Canale

Since July 2024, the Federal Risk and Authorization Management Program, or FedRAMP, has undergone significant changes that will greatly impact the way cloud service providers (CSPs) are able to obtain authorization to work alongside the federal government and its agencies. 

Prior to the recent revision, the authorization process was conducted via one of two methods: Authorize to Operate (ATO) by way of agency authorization, and Provisional Authority to Operate (P-ATO) via the Joint Authorization Board (JAB). Both methods included a three-step process: Preparation, Authorization, and Continuous Monitoring. 

Now, there is a singular authorization process, ATO, making P-ATO no longer an option for CSPs. 

AI-created photo of the American flag that is made up of binary code.

Recent Changes to Authorization Process

As part of the revision, FedRAMP has introduced several measures that are aimed at speeding up the authorization process without sacrificing the necessary level of scrutiny.

Streamlined Authorization Process 

One of the notable changes involves the modernization of the process for achieving ATO. Previously, obtaining FedRAMP authorization was a complex and time-consuming process, involving multiple steps and significant investment from CSPs. However, with these new changes, FedRAMP is moving towards streamlining the authorization process while maintaining the integrity of security standards, meaning there will be only one authorization method for CSPs — ATO.

With FedRAMP’s new streamlined process, comes the dismantling of the JAB and the P-ATO process, and the implementation of the new governing body, the FedRAMP Board. The board will, “approve and help guide FedRAMP policies, bring[ing] together the federal community to create a robust authorization ecosystem,” said Eric Mill, the executive director for cloud strategy at the U.S. General Services Administration (GSA).

Due to the single authorization method, communication will become more fluid, ensuring that CSPs can address agency concerns in real time, which is expected to expedite approvals. The program has also emphasized more transparent guidelines, clarifying the steps needed to achieve compliance. This reduces the guesswork for cloud service providers and enables them to better align their security practices with federal requirements from the onset, rather than having to backtrack and make corrections during the authorization process. 

The goal of this new streamlined process is to get more CSPs through the authorization pipeline faster while still maintaining robust security standards, which is a stark difference from the P-ATO process that was only conducted during specific times of the year. This effort was created based on the feedback within the cloud service industry where companies voiced concerns about the length of time it takes to gain authorization, especially given the rapid pace at which technology changes.

Photo of a table displaying binary code and cybersecurity lock symbol. On top of the table is an iPad being held by two hands and the iPad has an American flag on it.
 
Emphasis on Automations

Among the most impactful changes is the increased emphasis on continuous monitoring and automation. The use of automated tools that can assess security controls in real-time allows cloud service providers to detect vulnerabilities swiftly and efficiently throughout the entire FedRAMP process. This shift towards automation aims to minimize human error, improve response times to threats, and ensure that cloud environments remain secure as they continue to grow and change. Continuous monitoring will now play a more central role in FedRAMP, allowing agencies and cloud providers alike to be better equipped to respond to cybersecurity threats.

This emphasis on automation is supported by a new technical documentation hub that was specifically designed to support CSPs during the authorization process. The automate.fedramp.gov website offers CSPs with all the necessary documentation to support them during the authorization process. This documentation includes detailed technical specifications, best practices, and guidance on managing their authorization packages. 

The intention of this new hub is to provide CSPs with quicker and more frequent documentation updates, improve the user experience for those implementing FedRAMP packages and tools, and to provide a collaborative workflow.

There are plans in place to expand the capabilities of the hub, with the intention to also integrate FedRAMP authorization submissions.

Implementation of Red Teaming 

Previous authorization methods included a three-step process: preparation, authorization, and continuous monitoring. In previous iterations, part of the preparation process for both methods was an initial assessment of the CSOs done by an independent third-party assessment organization (3PAO).

The appointed 3PAOs would conduct a thorough evaluation of the CSP’s security package, which included both a documentation review and testing of the cloud service’s implementation of their security controls. Additionally, CSPs were required to provide monthly and annual security assessments, vulnerability scans, and other documentation to prove their ability to protect federal data as part of their continuous monitoring.

With this new revision, FedRAMP has also introduced a new mandate surrounding red teaming, adding an additional layer of scrutiny for cloud security. Red teaming is an advanced form of ethical hacking where security experts simulate real-world attacks on cloud environments to uncover vulnerabilities that traditional testing methods might miss. This new mandate requires CSPs to undergo periodic red teaming assessments, ensuring that their systems can withstand sophisticated threats that are constantly evolving in the cybersecurity landscape.

By simulating these real-world attacks, red teaming identifies weaknesses before they can be exploited, giving CSPs the chance to proactively address potential threats. It’s a vital step in recognizing the importance of not just meeting baseline security standards but continuously improving security postures to keep pace with emerging threats. 

While this new requirement adds an additional layer to the authorization process, it also provides peace of mind for both the CSPs and government agencies, reinforcing the trust necessary for working with sensitive government data. 

Digital illustration of a government building surrounded by glowing data streams, representing modern technology and cybersecurity.
 

Conclusion

At its core, FedRAMP allows federal agencies to leverage modern cloud technologies while maintaining the necessary security protocols. However, as technology evolves and cybersecurity threats become more sophisticated, FedRAMP has had to adapt to ensure CSPs can remain flexible while still adhering to the government’s stringent security requirements. 

These significant changes reflect not only the evolving world of cybersecurity threats, but also the increasing complexity of cloud environments. This revision highlights the program’s adaptability and commitment to maintaining a high level of security across all federal cloud environments. The foundation laid by these updates will help streamline the authorization process, enhance monitoring capabilities, and ultimately provide greater assurance that government data remains protected in an ever-changing threat landscape.

As these recent changes continue to take effect, they are set to shape the future of cloud security for federal agencies, creating a more secure and efficient path forward for cloud adoption across the U.S. government. SEM will be closely following the ongoing evolution of the FedRAMP process and will continue to provide you with the latest updates and guidance to help you navigate the authorization process effectively.

FISMA Requirements: Are You Compliant?

May 2, 2019 at 6:55 pm by Heidi White

All US-based organizations and agencies, whether public or private, must comply with certain information security measures when it comes to data storage and disposal. For government agencies and affiliated organizations, information security is paramount because of the sensitive nature of the information housed within these parties. To ensure the protection of proprietary United States data, legislation to regulate proper data and information security management was passed as part of the Electronic Government Act of 2002.

FISMACalled the Federal Information Security Management Act (FISMA), this law focuses on the importance of data security as it relates to the economic and national security interests of the US. As such, FISMA stipulates that all government agencies, government contractors, and any organization that exchanges data directly with a government system must safeguard all of their information technology (IT) systems, including stored data, by developing, documenting, and implementing an information security program.

In 2014, this law was amended to the Federal Information Security Modernization Act (FISMA 2014) to bolster the authority of the Department of Homeland Security (DHS) to administer, implement, and provide technical assistance with policies for information security for non-national (civilian) security federal Executive Branch systems. FISMA 2014 also updated and clarified the oversight authority of the Office of Management and Budget (OMB) and its ability to eliminate inefficient and wasteful reporting of any organization under FISMA. It also sanctions DHS’ role in assisting OMB with this responsibility.

FISMA: Who It Affects and Why It’s Important

The purpose of FISMA is to protect government information, assets, and operations against natural threats and criminal activity, whether from within the US or outside. Therefore, any US organization directly related to or doing business with the US government, including federal- and state-level government agencies and contractors, state government departments, military subcontractors, and even data clearinghouses fall under FISMA regulations.

FISMA-cybersecurityFISMA, FISMAFailure to pass a FISMA inspection by DHS or OMB can result in unfavorable publicity for your organization and a cut to your IT budget, as well as significant administrative ramifications to your organization. However, failure to comply with FISMA, especially when it comes breach-avoidance and proper data destruction, can have much grander and more catastrophic implications for you and your organization. Should any of your private, secured federal data be compromised and your organization was found to be noncompliant, there are serious civil and criminal federal consequences.

How to Comply with FISMA

C-suite executives like chief information officers, information security officers, senior agency officials, and agency program officials are all responsible and held accountable for ensuring compliance of FISMA within their respective organization.

cybersecurity-governmentAs stated in FISMA, these federal or otherwise federally-affiliated organizations must develop, implement, and accurately manage an information security program to safeguard the IT systems and any ensuing data that is collected stored, and transferred. This includes documentation of both the security systems and access granted to stored federal information.

The National Institute of Standards and Technology (NIST) outlines steps that these individuals should take to comply with FISMA:

  1. Track and categorize all information and media devices that must be protected.
  2. Set baseline security controls. Implement and document their use in the appropriate security system.
  3. Regularly refine these controls using a defined risk-assessment procedure as part of an annual review process.
  4. Authorize the IT system for processing within the selected group of authorized personnel and monitor the systems on a regular basis.

Complying with FISMA also extends into data destruction and device disposal practices. Full data destruction requirements can be found under the Federal Information Processing Standards (FIPS) Publication 200: Minimum Security Requirements for Federal Information and Information Systems. According to FIPS, organizations under FISMA must: i) set and enforce policies for protecting all data and information systems, whether on paper or in digital format, ii) appoint authorized personnel for sole access of the IT systems and federal information and iii) ensure complete and total destruction of both the data and the media in which it is stored upon reaching end-of-life.

When it comes to the disposal of this federally-protected private data, FIPS also states that the organization must develop and enforce a set of policies for how the data and media should be destroyed, and accurately document every data disposal event, most easily accomplished by using an audit-friendly media tracking system such as SEM’s iWitness. It’s recommended to purchase on-site data destruction machinery and limit access to the data and the data destruction machinery to a small group of authorized personnel.

media-tracking
SEM’s iWitness media tracking system provides audit-friendly compliance with FISMA’s documentation requirements

Furthermore, when it comes to the data end-of-life cycle, the device in which the data is housed must also be destroyed via degaussing, incinerating, melting, or pulverizing machinery so that neither device nor data can be read or otherwise reconstructed. And, you want to choose a vendor like SEM that has NIST- and NSA-approved data destruction machinery.