An independent assessor accredited to evaluate a cloud service against FedRAMP requirements. A 3PAO tests the controls and reports what it found; it does not grant the authorization.
Why it matters: Its report is the independent view an authorizing official relies on when deciding.
Source: [8]How GovSecure AI handles this →
The senior federal official with the authority to accept risk for a system and sign its authorization.
Why it matters: The package is written for this person, so evidence has to answer their questions.
Source: [1]
A senior official's formal decision that a system may operate, accepting the risk that remains. It is a risk decision about one system, not a certificate a vendor earns once.
Why it matters: A federal system generally may not process agency data in production without one.
Source: [1]
All the components that are authorized together as one system. Separately authorized systems it connects to sit outside the boundary.
Why it matters: The boundary decides which controls and evidence are in scope. Drawn too wide or too narrow, it distorts both.
Source: [1]
The set of documents an authorizing official reviews to make the decision. It typically includes the system security plan, the assessment report and the plan of action and milestones.
Source: [1]
An approach where an authorization stays current because controls are monitored and risk is reviewed on an ongoing basis, instead of being decided again from scratch every few years. NIST guidance describes the underlying idea as ongoing authorization.
Why it matters: It moves the work from a periodic documentation sprint to keeping evidence current all the time.
Sources: [1], [5]How GovSecure AI handles this →
The gap that opens when a system's actual settings move away from its approved, documented configuration.
Why it matters: Drift that goes unnoticed means the system being operated is no longer the system that was authorized.
Source: [2]How GovSecure AI handles this →
Keeping ongoing awareness of a system's security posture, vulnerabilities and threats so that risk decisions rest on current information.
Why it matters: An authorization is only as trustworthy as the monitoring that follows it.
Source: [5]How GovSecure AI handles this →
A predefined starting set of controls for a system at a given impact level: Low, Moderate or High. Organizations then tailor it to their system.
Why it matters: The baseline sets the size of the job: how many controls must be implemented, documented and evidenced.
Source: [4]
The written explanation in a security plan of how one control is met for this system: who does what, with which tools, and how often. Often called a control narrative.
Why it matters: Assessors test the system against these statements, so vague ones invite findings.
Sources: [2], [1]How GovSecure AI handles this →
Relying on a control that another authorized provider or the wider organization already implements, such as physical security in a cloud provider's data center. The inheriting system still records where the protection comes from.
Why it matters: Inherited controls reduce work, but only when the split of responsibility is written down clearly.
Sources: [1], [2]
Government information that is not classified but that law, regulation or government-wide policy requires to be protected or limited in how it is shared.
Why it matters: Whether a system handles CUI affects which requirements apply and where the data may live.
Source: [10]
The records that show a control is in place and working: configurations, logs, screenshots, scan results, policies and similar artifacts.
Why it matters: A control without current evidence is hard to defend in an assessment.
Source: [3]How GovSecure AI handles this →
The U.S. government-wide program that sets a standard approach to security assessment, authorization and continuous monitoring for cloud services used by federal agencies.
Why it matters: Agencies generally expect a cloud service to hold a FedRAMP authorization before it handles federal data.
Source: [8]
The U.S. law that requires federal agencies to run risk-based information security programs for their systems, including systems operated by contractors on their behalf.
Source: [9]
A rating of Low, Moderate or High for how much harm a loss of confidentiality, integrity or availability would cause. It comes from categorizing the information the system handles.
Why it matters: The impact level determines which control baseline applies.
Source: [6]
The person responsible for keeping a system's day-to-day security posture in order on behalf of the system owner. In practice they maintain the documentation, gather evidence and track open findings.
Source: [1]
The catalog of security and privacy controls published by the National Institute of Standards and Technology and used across U.S. federal systems. Controls are grouped into families such as Access Control (AC) and Configuration Management (CM).
Why it matters: Most other terms on this page refer back to this catalog.
Source: [2]
A set of machine-readable formats from NIST for control catalogs, baselines, security plans, assessment results and plans of action, expressed in JSON, XML or YAML.
Why it matters: Machine-readable documents can be validated and exchanged by tools instead of being retyped.
Source: [7]How GovSecure AI handles this →
The running list of known weaknesses in a system, with the planned fix and target dates for each.
Why it matters: Authorizing officials read it to judge whether the remaining risk is actually being worked down.
Source: [1]
NIST's seven-step process for managing security and privacy risk in a system: prepare, categorize, select, implement, assess, authorize and monitor.
Why it matters: An ATO is the output of the authorize step, and monitoring keeps it valid.
Source: [1]
The assessor's written results: which controls were tested, how they were tested, and which were found satisfied or not.
Sources: [1], [3]
A safeguard, technical or procedural, that protects a system and its information. Each control has an identifier, such as AC-2 for account management.
Source: [2]
The document that describes a system, its boundary, and how each required control is implemented.
Why it matters: It is the core of the authorization package and the reference assessors test against.
Source: [1]How GovSecure AI handles this →