StateRAMP is based on the FedRAMP standard, which means that it uses a similar set of documents and requirements to assess and authorize cloud service providers. One of the key documents of both StateRAMP and FedRAMP is the System Security Plan (SSP), which represents the provider’s security controls, compliance perimeter, and capabilities. 

In Revision 5, StateRAMP has seemingly moved from the traditional SSP toward an “operational control matrix,” or systematized document outlining the same information. Here, we’ll cover the SSP/control matrix and what it represents for the provider during StateRAMP authorization. 

Read More

StateRAMP, much like FedRAMP, includes a series of documents that the cloud provider and their 3PAO must complete before they are fully authorized. These documents align with several stages of the assessment process and provide regulating authorities with the proof they need to see that the cloud offering meets requirements. 

Here, we summarize the documents you must complete as part of your StateRAMP assessment process.

Read More

Assessments for both StateRAMP and FedRAMP rely on the 3PAO’s understanding of the systems and people that will interact with a specific government agency. With this knowledge, it’s easier to determine where particular requirements begin and where they end. Across both of these frameworks, this concept is known as the “authorization boundary.” 

The authorization boundary serves as a (sometimes physical, sometimes logical, sometimes administrative) fence that delineates the scope of a cloud system’s operations, setting clear boundaries for where assessment and regulatory requirements begin and end. 

Whether you’re a cloud service provider or a government agency representative, this article will shed light on this essential concept and help you understand its impact on the landscape of cloud security.

Read More