Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The NIS Regulations were enacted in May 2018 to implement the EU Directive to achieve NIS compliance.

Just like any compliance or set of regulations, FedRAMP uses many acronyms and key terms to describe processes, standards, and regulations. This article explains key terminology that is used in the FedRAMP framework. You may already be familiar with some of these compliance terms and acronyms from other security frameworks.

Google adopted its cloud infrastructure, Google Cloud Platform (GCP), to be compliant with FedRAMP. GCP earned a FedRAMP High authorization to operate (ATO) for several cloud products in a handful of locations and has uplifted the current FedRAMP Moderate services to more products and locations. Government agencies can now work with the highest level of classified information using GCP.

The current FedRAMP Authorization process is a struggle. First, you must manage multiple regulatory standards and frameworks, which change over time. Second, regulatory standards and frameworks overlap in scope and can often conflict and be difficult to manage together. And, lastly, information systems continue to increase in size and complexity.

For a Cloud Service Provider (CSP) to be FedRAMP accredited, it must complete the following six phases. They are diagnostic assessment, boundary and architecture review, documentation, technical remediation, testing preparation & residual risk, and Final Authorization to Operate.

The federal government enacted the FedRAMP regulation in December 2011 to enable executive agencies and departments to use an assessment method based on risk and cost-effectiveness when adopting cloud technologies. A FedRAMP readiness assessment is mandatory for cloud products and solutions providers seeking to receive an Authorization to Operate (ATO). FedRAMP ATO indicates that a provider’s hosted information and systems meet FedRAMP requirements.