The record of federal cyber governance, checked every day

FedXchange keeps every binding rule a federal security program follows, from the Privacy Act of 1974 to this morning's watch, and says what changed and why it matters in plain English. With a free account, it writes the policies that name the tools your agency actually runs.

Governance sources in force today, by the year they were issued

Show the numbers

	Sources in force
Before 2016	28
2016	13
2017	8
2018	6
2019	5
2020	9
2021	7
2022	7
2023	8
2024	8
2025	19
2026	25

Federal cyber governance is changing faster than agencies can absorb it

October 18, 2026 · Federal governance

We counted the binding cyber governance issued to civilian agencies by source and year since 2015. The total more than doubled, FedRAMP became the most prolific issuer, and the next ten months are the heaviest stretch yet.

Read the analysis

Documents: 831
In effect: 484
Proposed: 40
No longer in effect: 307

The record as of October 19, 2026. Open to anyone, with no account.

From the blog: what the record shows

All analysis

One provider, 91 agencies: the many-to-one problem in federal cloud
October 18, 2026 · FedRAMP
Providers have scale, system knowledge, and repeatability. Each agency has one bespoke instance per offering and no standard way to share the work. Marketplace data shows why, and how the 2026 FedRAMP rules make it worse.
Read the analysis
FedRAMP moved the risk to agencies. Here is where it landed.
October 18, 2026 · FedRAMP
Sixteen FedRAMP changes since 2022, scored for whether they move risk toward or away from agency authorizing officials. Twelve move it toward agencies; the vulnerability rules and quarterly reports move it away.
Read the analysis

The record, open to anyone

FedXchange reads 16 groups of federal sources, most of them every day, and a person reviews what the watch finds before it reaches the record. Nothing here needs an account.

Governance trackerOpen to anyone: Every law, executive order, OMB memorandum, CISA directive, NIST publication, FedRAMP rule, and contract clause that binds a federal security program, from the Privacy Act of 1974 to today, each with its status, its required agency actions, and the source.
Open the governance tracker
Marketplace trackerOpen to anyone: Every FedRAMP Marketplace listing, which agencies use it, and what changed stage this month.
Open the Marketplace tracker
Feeds and a spreadsheetOpen to anyone: Any tracker view as an Atom or JSON feed, or a CSV download, so the record can sit in your own reader or risk register.
Follow the whole record by Atom feed
Newsletter and alertsOpen to anyone: A short email each Friday with what the watch found that week, and an alert on the day it finds something new, if you want one.
Sign up below

What the watch checks, and how often

Then put the record to work: policies that name what your agency actually runs

Most policy templates say “the organization employs an automated tool.” Staff can't follow that, and assessors ask which tool you mean. FedXchange reads your agency's FedRAMP Marketplace authorizations, suggests a service for each of 18 security functions, and writes 67 plain-language policies, procedures, and plans that name the services and titles you confirm.

Works todayFree account

Step 1: Name your agency
FedXchange finds the cloud products your agency has authorized on the FedRAMP Marketplace and suggests one for each security function, such as identity management or vulnerability scanning.
How we pick each suggested service
Step 2: Confirm your choices
Confirm a service for each of 18 functions, including services the government runs, and set your own titles for 50 offices and roles.
See the functions
Step 3: Get your documents
FedXchange writes 67 policies, procedures, and plans that name what you confirmed. Download each one as a Word file.
How the documents are made
Step 4: Stay current
The governance watch checks federal sources every day and tells you which of your documents a change touches.
What the watch checks

Suggested services

Example

Identity provider
Your authorization
Matched to your Marketplace authorization
SIEM and log management
Your platform
Covered by your cloud platform's authorization
Vulnerability disclosure
Shared service
CISA Vulnerability Disclosure Policy Platform
Learning management
Generic name until you choose
“the learning management system”

Nothing is used until you confirm it.How we pick each suggested service

Incident Response Plan, section 4

Example

The Security Operations Center watches alerts from your log management service around the clock.
When an alert may be an incident, the analyst opens a ticket in your ticketing service and tells the Information System Security Officer within one hour.

The highlighted words come from your answers: the services you confirmed and the titles your agency uses.

67 documents, written in plain language

28 policies · 23 procedures · 9 plans · 7 templates, rules of behavior, and references

Information Security Program Plan
Incident Response Plan
Information Security Continuous Monitoring (ISCM) Strategy
Post-Quantum Cryptography Migration Plan
Rules of Behavior — Privileged Users
and 62 more

Your names, not placeholders. Where a template says “the organization employs an automated tool,” yours names the service you confirmed and the office that runs it.
Every real option, side by side. For each function, FedXchange lists the FedRAMP Marketplace products that fit it (157 listings in all, as of October 19, 2026), your agency's own first, and the 9 services the government runs itself in 8 of the 18 functions, which never appear among your authorizations. See the functions and the shared services
Checked before you see them. Each document cites the federal sources it rests on and passes a fixed series of checks, from source currency to a review board of 16 reviewer roles. They are drafts: nothing is final until a person at your agency approves it.
Word files you can edit, written again when you change an answer. Each comes with your agency's cover and a filled table of contents. Pick a new service or retitle an office, and the next draft says so everywhere it matters.
No AI writes them. A fixed generator writes every document, so the same answers always give the same text. Your own AI assistant can connect over the Model Context Protocol to review suggestions and record choices; every change waits for your yes. How assistants connect
Coming nextDrafted updates: when a source changes, FedXchange proposes new wording for a person to approve.

Each Friday, a short email lists what the watch found that week: new documents, changes in status, and comment deadlines, and, if you follow the Marketplace tracker, products that changed stage on the FedRAMP Marketplace. Add instant alerts if you want them. No account needed, and a one-click unsubscribe.

A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.

Free to use. FedXchange is built by Varry LLC, which also makes RMF Coach, hands-on courses and an authorization simulation for learning NIST RMF and FedRAMP.

Start with the record. Write your policy set when you're ready.

The trackers, feeds, and newsletter need no account. Anyone can sign up free with a work email or Google account.

Open the governance tracker Sign up free

The record of federal cyber governance, checked every day

Federal cyber governance is changing faster than agencies can absorb it

From the blog: what the record shows

One provider, 91 agencies: the many-to-one problem in federal cloud

FedRAMP moved the risk to agencies. Here is where it landed.

The record, open to anyone

Then put the record to work: policies that name what your agency actually runs

Step 1: Name your agency

Step 2: Confirm your choices

Step 3: Get your documents

Step 4: Stay current

67 documents, written in plain language

Get what changed in the record by email

Sign up

Who runs FedXchange

Start with the record. Write your policy set when you're ready.