Federal FISMA audit readiness
Federal FISMA audit readiness: build evidence that survives the annual review
An operator’s playbook for preparing a federal agency information-security program for its annual Inspector General review. It turns the ten FISMA domains into an evidence production system: named owners, repeatable populations, testable controls, dated artifacts, findings and corrective actions. Contractors can use the same method to support agency customers, while keeping the agency accountable for its statutory program.
- Issuing authority
- U.S. Congress, OMB, CISA and agency Inspectors General
- Timing
- Run the work as a year-round control cycle. Start the annual readiness sprint 120 to 180 days before the IG’s fieldwork or evidence freeze, then maintain monthly evidence, quarterly risk and POA&M reviews, and a year-end reconciliation to the applicable metric instructions. For FY 2026 IG evaluations, CISA directed agencies to continue using the FY 2025 IG metrics because no replacement IG set was issued. Confirm the version and evidence window with the IG before work begins. The audit’s fiscal-year end is not a safe date to begin collecting evidence.
- Reviewed
- Inside this guide
- 7 steps · 7 templates
Who it applies to
Applies to U.S. federal agencies developing and operating agency-wide programs to protect federal information and systems. The annual IG evaluation uses current CISA reporting metrics and agency evidence. It is not a FedRAMP authorization, a security certification for a vendor, or a substitute for the agency risk-management framework. Confirm the current fiscal-year metric set, reporting instructions, system inventory and sensitive-information handling rules with the agency CISO and IG before starting.
What you’ll produce
An approved audit charter and boundary; reconciled system and control populations; evidence that can be reproduced from authoritative systems; tested control narratives and samples; a management-validated response; and a corrective-action plan with accountable executives, proof of closure and retest criteria.
FY 2026 evaluations continued to use the FY 2025 IG metrics. They cover ten domains: governance, supply chain risk, risk and asset management, configuration management, identity and access, data protection and privacy, security training, continuous monitoring, incident response and contingency planning. The maturity scale runs from ad hoc through defined, consistently implemented, managed and measurable, and optimized. A high-level policy statement does not prove a control operated. Public FY 2026 examples show why: NSF’s report said six of ten domains were effective, four were not, eight earlier findings remained incompletely remediated and one new finding was identified. NARA’s FY 2026 report listed six open recommendations. EAC assessed its program as effective at maturity level 3, closed four of ten open recommendations from its FY 2024 and FY 2025 audits, and reported one new finding. These are different agencies, scopes and report dates, not a sector-wide pass rate. Treat them as practical signals to test closure evidence, asset completeness and control operation, not as a ranking.
Run the project
Go to the roadmapDecisions for leadership
- What applies to each entity, product and activity?
- Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
Federal FISMA audit readiness kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Charter the review and lock its versioned scope · CISO + IG liaison + Internal audit + Program executive [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- Is a FISMA audit a certification?
- Who owns the evidence and final audit response?
- Can a contractor close an agency finding?
Worked scenario
A federal program says its privileged accounts are reviewed quarterly. The audit team selects the population from the identity platform, compares it with the authoritative system and contractor roster, selects a reproducible sample, and checks dated reviewer decisions, removal tickets and completion evidence. One sample includes a departed contractor whose access was disabled only after the review. The team does not quietly remove the exception from the population: it traces the cause, checks whether the issue affects other systems, records the agency response and tests the corrective action against a fresh population before recommending closure.
What to read next
- FedRAMP
Use when the service itself is a cloud offering seeking a federal authorization path.
- NIST Risk Management Framework
Use to connect security categorization, control selection, assessment and authorization work.
Official milestones
See the deadline calendar- 120–180 days before fieldwork
Start evidence-readiness sprint
Confirm exact IG dates and fiscal-year metric version; this is a planning target, not a government-wide statutory date.
Official reference (opens in a new tab) - Monthly
Reconcile systems, evidence and corrective actions
Retain dated source populations and report open gaps to accountable owners.
Official reference (opens in a new tab) - Before the IG response deadline
Approve agency management response
Use the deadline in the actual audit notice and internal counsel/IG liaison calendar.
Official reference (opens in a new tab) - Quarterly
Executive POA&M and repeat-finding review
Review overdue, recurring and risk-accepted items with the CIO and CISO.
Official reference (opens in a new tab)
- 01Charter the review and lock its versioned scope, CISO + IG liaison + Internal audit + Program executive, about 14 days
- 02Reconcile the inventory before testing controls, Enterprise architecture + System owners + Asset management + Acquisition, about 21 days
- 03Convert each metric into an evidence and test plan, CISO control owners + Privacy + Supply chain + Independent audit lead, about 21 days
- 04Collect source evidence and preserve its lineage, Control operators + System owners + Evidence custodian, about 30 days
- 05Test populations, samples and exceptions, Independent assessors + Internal audit + Control owners, about 30 days
- 06Draft management response and measurable corrective actions, Agency CISO + CIO + Finding owner + Counsel + IG liaison, about 21 days
- 07Verify closure and keep the program audit-ready, CISO governance + POA&M manager + Independent validation owner, about 14 days
Step by step
Checklist, instructions and 7 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Charter the review and lock its versioned scope | CISO + IG liaison + Internal audit + Program executive | 120 to 180 days before fieldwork, then update when systems or guidance change | Set a start date | Approved audit charter, evidence calendar and boundary register | Open |
| Reconcile the inventory before testing controls | Enterprise architecture + System owners + Asset management + Acquisition | First month; refresh at least monthly through the audit | Set a start date | Signed system inventory reconciliation and system-to-control coverage matrix | Open |
| Convert each metric into an evidence and test plan | CISO control owners + Privacy + Supply chain + Independent audit lead | Before evidence collection; approve test design before samples are selected | Set a start date | Ten-domain evidence map, metric crosswalk and approved test program | Open |
| Collect source evidence and preserve its lineage | Control operators + System owners + Evidence custodian | Monthly, with a 30-day evidence freeze before submission where feasible | Set a start date | Evidence index, immutable source artifacts and provenance log | Open |
| Test populations, samples and exceptions | Independent assessors + Internal audit + Control owners | During the agreed audit period and before management certification | Set a start date | Completed workpapers, exception log and validated findings | Open |
| Draft management response and measurable corrective actions | Agency CISO + CIO + Finding owner + Counsel + IG liaison | Set internal review dates ahead of the IG response deadline | Set a start date | Management response, risk acceptance record and funded corrective-action plan | Open |
| Verify closure and keep the program audit-ready | CISO governance + POA&M manager + Independent validation owner | Monthly POA&M review; quarterly executive review; year-round operation | Set a start date | Retest package, closure approval and next-year readiness backlog | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Charter the review and lock its versioned scope
Obtain the IG audit notice, fiscal-year metric version, evidence dates, reporting templates and secure transfer method. Define agency and system boundaries, fiscal-year cutoff, sampled populations, exclusions, contractor dependencies, points of contact and decision rights. Create a question log and escalation path. Mark every scope change with its date, rationale, approver and affected evidence.
What to produce
Approved audit charter, evidence calendar and boundary registerAudit charter and calendar
Gather first
- IG audit notice
- Current fiscal-year metrics
- System inventory
- Agency audit policy
- Secure evidence-transfer instructions
How to prepare it
- Record the notice date, fieldwork window, evidence cutoff, report response deadline and reporting version. Add an internal due date for every artifact that precedes the IG deadline.
- Define covered agency, systems, fiscal year, control population, exclusions, contractors, inheritance and reporting boundary. Name the official who approves changes.
- Maintain one row per request with question ID, owner, source system, custodian, due date, reviewer, sensitivity, status, links and escalation. Keep a dated change log.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional request
- IG request F-12 covers privileged access from October 1 through September 30. Identity Operations owns the authoritative export; Security Governance validates scope; delivery is due ten business days before the external date.
- Fictional scope change
- A cloud service is added after a boundary review. The register records the approval, fiscal-year relevance, affected controls and evidence already submitted.
Check before handing it over
Every request has one accountable owner, a source of truth, safe handling instructions and enough lead time for review.
Give approved scope and request tracker to system owners and the IG liaison.
- 02
Reconcile the inventory before testing controls
Export the authoritative system inventory and reconcile it to cloud accounts, applications, data flows, authorization packages, contracts and known shadow services. Record system owner, impact level, data types, hosting, interconnections, control inheritance, last assessment, open POA&Ms and status. Investigate every unmatched record. Freeze a dated population snapshot and have a second owner attest to completeness.
What to produce
Signed system inventory reconciliation and system-to-control coverage matrixReconciliation workbook
Gather first
- Authoritative system inventory
- Cloud account exports
- Application catalog
- Data-flow register
- Authorization packages
- Contracts
- Control inheritance records
How to prepare it
- Take dated extracts from each source. Normalize system identifiers without deleting the original values. Join on stable IDs first, then document any name-based matches.
- Classify each source row as matched, unmatched, duplicate, retired, newly discovered or out of scope. Assign each exception an owner and evidence-supported disposition.
- Map every in-scope system to an owner, impact level, data types, hosting, authorization status, inherited controls, latest assessment and open POA&Ms. Obtain a second-person completeness attestation.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional exception
- A procurement catalog lists a cloud service absent from the authorization inventory. Mark it newly discovered, identify the agency data owner, determine data sensitivity and route it for a documented scope decision.
- Reconciliation measure
- Report match rate as matched in-scope records divided by all in-scope records, plus the raw unmatched count and unresolved age. Never hide unresolved items in the percentage.
Check before handing it over
A reviewer can reproduce the joins, see all unmatched assets and trace each system to owners and assessed controls.
Send signed inventory and unresolved high-risk exceptions to the CISO and audit lead.
- 03
Convert each metric into an evidence and test plan
For each in-scope metric, write the criterion, responsible official, operating process, system of record, period, population, sample method, evidence artifacts, exceptions and rating rationale. Separate design effectiveness from operation. Identify inherited controls, compensating controls and dependencies. Document how each maturity claim maps to observable results; do not infer an optimized practice from a policy alone.
What to produce
Ten-domain evidence map, metric crosswalk and approved test programControl test plan
Gather first
- Current CISA IG metrics
- System boundary
- Agency policies
- Prior findings
- Risk register
- POA&Ms
- Prior-year test results
How to prepare it
- Create a row for every applicable metric and requirement. Record exact source paragraph, applicability rationale, control owner, process, system of record, period and evidence artifact.
- Specify the test objective, population, population source, sample method, selected period, expected attributes, exception criteria, assessor and reviewer. Distinguish design testing from evidence that the control operated.
- For maturity ratings, define the observable basis for the selected level and the gap to the next level. Have an independent reviewer challenge unsupported claims before fieldwork.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional control
- For quarterly access reviews, define the population as all privileged accounts active at quarter-end, source it from the identity platform, include contractor identities, and test reviewer authority, review date, disposition and removal completion.
- Maturity check
- A policy may support a defined process; a consistently implemented rating also needs operating evidence across the relevant population and period.
Check before handing it over
Each rating and conclusion maps to a current criterion and repeatable procedure.
Approve test design with Internal Audit and the IG liaison before selecting samples.
- 04
Collect source evidence and preserve its lineage
Pull exports from the authoritative platform or ticket system. Capture query, filters, timestamp, time zone, date range, record count, source owner and export digest. Link each artifact to one or more control tests and retain the native file read-only. For screenshots, include the full page, environment, URL or system name and capture date. Redact sensitive fields in a controlled copy; preserve originals under agency handling rules. Never manufacture a backdated approval or replace an operational record with a newly written narrative.
What to produce
Evidence index, immutable source artifacts and provenance logEvidence register
Gather first
- Control procedures
- Native system exports
- Ticket records
- Configuration snapshots
- Approval records
- Approved secure repository
How to prepare it
- Capture evidence from the authoritative source. Record system, query, filters, timestamp and time zone, period, row count, exporting owner and file digest.
- Link artifacts to metric, system, control, request number and test step. Preserve originals read-only; create a separately labeled redacted copy when allowed.
- For screenshots, include environment and capture date. Record collection, transfer and access events. Do not recreate missing historic evidence as if it were contemporaneous.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional evidence row
- Artifact E-104 is a read-only identity export generated October 3 at 14:05 UTC with filter “privileged=true,” 186 rows and SHA-256 digest recorded. Its owner explains the one excluded emergency account in a linked exception note.
Check before handing it over
An assessor can establish authenticity, period, source, completeness and the link from evidence to conclusion.
Transfer through the agency-approved channel and retain under agency evidence-handling policy.
- 05
Test populations, samples and exceptions
Reproduce the population from source data. Record selection method, sample size rationale, selected IDs, evidence dates and any missing item. Test whether each control occurred when required and whether the reviewer had authority and enough information. Log failures as found, including late approvals, stale access, missing assets and untested recovery plans. Expand testing when the pattern or risk warrants it. Have control owners explain facts, but keep the assessor’s conclusion independent.
What to produce
Completed workpapers, exception log and validated findingsAudit workpapers
Gather first
- Approved test program
- Population snapshot
- Evidence index
- Sample selections
- Interview notes
- Prior findings
How to prepare it
- Reproduce the population from its source and retain the query and reconciliation. Record completeness checks, exclusions and the accountable system owner.
- Select and document samples using the approved method. For each selected item, record expected attributes, evidence reviewed, result, reviewer and any exception.
- Validate exceptions against the source and the applicable period. Trace the cause, assess prevalence and impact, and expand testing if risk, pattern or control design warrants it.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional sample result
- One departed contractor remains active for two days after the quarterly review. Record the account ID in the restricted workpaper, removal ticket and timestamps, determine whether the exception is isolated, then inspect related populations before concluding.
Check before handing it over
Findings are fact-based, scoped, reproducible and supported by evidence rather than verbal assurances.
Provide validated findings and factual questions to the finding owner through the audit liaison.
- 06
Draft management response and measurable corrective actions
For each finding, state whether the agency agrees, partially agrees or disagrees and cite evidence. Separate immediate containment from durable root-cause correction. Give each action one accountable executive, funding source, milestones, due date, interim risk acceptance, dependencies, success measure and independent retest. Identify whether the fix affects other systems. Route disputed facts through the agreed audit channel and retain version history; do not promise closure solely because a policy or ticket was created.
What to produce
Management response, risk acceptance record and funded corrective-action planCorrective action plan
Gather first
- Validated finding
- Root-cause analysis
- Risk assessment
- Interim controls
- Budget forecast
- Agency response deadline
How to prepare it
- State the agency position and reference factual evidence. Separate disagreement about facts, criteria and risk significance.
- For every agreed action, assign one executive owner, root cause, affected systems, implementation steps, dependencies, interim protection, funding and dated milestones.
- Define the closure evidence and independent retest in advance. Specify what population, observation period and success threshold will prove the issue is fixed. Record residual risk acceptance separately with authority and expiry or review date.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional action
- The finding concerns late contractor deprovisioning. Procurement updates the termination feed, Identity Operations implements daily reconciliation, and the CIO assigns a 60-day completion target. Closure requires a fresh 30-day sample with zero unexplained late removals and independent review.
Check before handing it over
The plan can be funded, tracked and retested; creating a policy or closing a ticket alone does not count as remediation.
Route the response for CISO, CIO, counsel and agency approval before the deadline.
- 07
Verify closure and keep the program audit-ready
Require evidence that the remediation was implemented, operated over a sufficient period and worked on a fresh population. Reopen actions when failures recur or evidence is incomplete. Update the POA&M and risk register, resolve cross-system causes and report aging, repeat findings, overdue milestones and residual exposure to leadership. Feed lessons into the next fiscal-year metrics and budget cycle.
What to produce
Retest package, closure approval and next-year readiness backlogClosure dossier
Gather first
- Approved corrective action
- Updated control evidence
- Fresh population
- Independent validation plan
- POA&M status
- Executive review record
How to prepare it
- Verify implementation and collect evidence that the changed control operated over the agreed period. Use a fresh population rather than relying only on the sample that exposed the issue.
- Reperform the original test, compare expected and observed results, investigate every exception and assess whether the same cause affects other systems.
- Obtain closure approval from the authorized agency official, update POA&M and risk records, retain the rationale and carry remaining work into the next audit calendar.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional closure
- The updated feed is live. An independent reviewer selects a new population after 30 operating days, traces terminations to disabled accounts and documents the one approved emergency-account exception separately.
Check before handing it over
Closure demonstrates sustained effectiveness and has an authorized decision, retest and record update.
Give executives a quarterly view of overdue actions, repeat findings, age and accepted residual risk.
Official sources
- GAO · FISMA reports and annual agency reporting (opens in a new tab)
- CISA · FY 2025 Inspector General FISMA metrics used for FY 2026 evaluations (opens in a new tab)
- GAO · Cybersecurity Program Audit Guide (opens in a new tab)
- NARA OIG · FY 2026 FISMA audit and open recommendations (opens in a new tab)
- NSF OIG · FY 2026 FISMA report (opens in a new tab)
- EAC OIG · FY 2026 FISMA audit (opens in a new tab)
- GAO · Federal Information System Controls Audit Manual (FISCAM) (opens in a new tab)