Continuous monitoring

Authorization is a subscription, not a trophy. Once a service is FedRAMP Certified, the work shifts from a single assessment to a monthly and annual rhythm that never stops.

Last updated: 2026-11-22.

What ConMon is

Continuous monitoring, ConMon for short, is the ongoing proof that an authorized service is still as secure as the day it was certified. Systems change: code ships, dependencies update, configurations drift, new vulnerabilities are published. ConMon is the mechanism that catches that drift before it becomes a breach or a revoked authorization. The governing document is the ConMon Playbook v1.0, dated November 17, 2025.

The rhythm has three beats: monthly, annual, and event-driven. Monthly deliverables keep FedRAMP current on the service's security posture. The annual reassessment re-tests controls. And significant changes to the system, along with newly discovered vulnerabilities, trigger work outside the calendar.

Every month

Each month, an authorized CSP submits three things:

New findings from the monthly scans land on the POA&M with the same clocks as assessment findings: Critical and High in 30 days, Moderate in 90, Low in 180. The remediation page covers the clocks and the closure cycle in detail.

Every year

Once a year, the 3PAO comes back for the annual reassessment. The assessor re-tests a subset of controls plus one-third of the remaining controls each year, so the full baseline gets re-covered on a rolling basis rather than all at once. The reassessment also verifies closure of POA&M items the CSP marked fixed during the year.

Penetration testing runs on the same annual cadence: at least every 12 months for Moderate and High. (Low and LI-SaaS do not require it.) The initial pen test, the one done before the first SAR, must be no more than 6 months before SAR submission. Pen Test Guidance v3 (June 30, 2022) remains the binding version; v4.0 has been in draft since March 2024.

What it costs

Annual continuous monitoring, including the annual 3PAO reassessment, runs roughly $100K–$600K per year by level, commonly $200K–$500K per year for Moderate. That is a compiled industry range, not a published price. The figure covers the reassessment, monthly reporting, and annual penetration testing, and it recurs every year the service stays authorized. Budget it as a permanent operating cost. The cost guide puts it in context with the one-time authorization costs.

What happens if you lapse

Missing monthly deliverables or letting POA&M items go overdue does not trigger an immediate revocation. It triggers escalation. Under the ConMon Playbook, overdue items move through graduated levels: five or more high-impact findings aged past 30 days triggers one level, past 60 days a stricter one, and ten or more moderate findings past 90 or 120 days escalate similarly. At the end of the ladder, missing deadlines without an approved deviation request can end in suspension or revocation of authorization.

The practical lesson is that ConMon fails slowly and then suddenly. A missed month is recoverable. A pattern of missed months, with an aging POA&M, is how authorizations get lost.

Deviation requests. When a CSP cannot meet a requirement on schedule, it can ask FedRAMP for an approved deviation. FedRAMP will not approve a deviation for a High vulnerability, and high-risk vendor dependencies must be mitigated to Moderate through compensating controls within 30 days. A deviation buys time for lower-severity items; it is not a waiver.

How 20x changes monitoring

FedRAMP 20x pushes monitoring toward automation. Key Security Indicators are designed to be measured and validated against machine-readable evidence rather than described in narrative, and detection widens beyond scheduled scans to threat intelligence, bug bounties, supply-chain monitoring, and vulnerability disclosure. The remediation clocks change with it: a likelihood × impact matrix replaces the flat 30/90/180-day model, with evaluation within 2 days (High), 5 days (Moderate), or 7 days (Low) of detection. The direction is clear even where the details are still settling: monitoring becomes continuous in fact, not just in name.

Frequently asked questions

Does the annual reassessment test every control?

No. Each year the 3PAO re-tests a subset of controls plus one-third of the remaining controls, so coverage rotates across years rather than repeating the full assessment annually.

Is penetration testing required every year?

Yes, for Moderate and High: at least every 12 months. Low and LI-SaaS do not require pen testing.

How long does authorization last?

There is no fixed expiry date. Authorization lasts as long as continuous monitoring is maintained: monthly reporting, the annual 3PAO reassessment, and annual penetration testing. Let the monitoring lapse and the authorization is at risk.

ConMon is where the POA&M lives after authorization, so the remediation page is the natural companion to this one. And if the acronyms are piling up, the glossary covers them.