Skip to content

Plan of Action and Milestones (POA&M)

Plan of Action and Milestones (POA&M) template: The register of a system's known weaknesses and the planned actions, milestones and dates to fix them, as SP 800-53 CA-5 requires.

TypeProgram stageStatusTemplate versionNIST basis
Form or registerOperateDraft1.0.0SP 800-53 release 5.2.0

The register of a system’s known weaknesses and the planned actions, milestones and dates to fix them, as SP 800-53 CA-5 requires.

ControlTitle
CA-5Plan of Action and Milestones
CA-7Continuous Monitoring
PM-4Plan of Action and Milestones Process
VariantReady to adoptAnnotated
All baselinesWord · MarkdownWord · Markdown

The register as a spreadsheet: CSV, with one column per field.

SystemSystem ownerLast updatedUpdated by
Fill in: system name and identifierSystem ownerFill in: dateFill in: name and title
  • Add an item for each weakness or deficiency found in a control assessment, and for each known vulnerability the system has not yet fixed (CA-5a).
  • Update the register Fill in: the frequency at which to update an existing plan of action and milestones based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities Typical: at least monthly, and whenever an assessment, audit, scan or monitoring activity finds a new weakness, using the findings of control assessments, independent audits or reviews, and continuous monitoring (CA-5b).
  • Keep closed items, with their completion date and evidence, so the history supports the next assessment.
  • When the System owner proposes to accept a risk instead of fixing it, record the authorizing official’s decision and its date in the item.
FieldWhat to record
IDA unique, permanent identifier for the item
WeaknessA short name and a description of the weakness
SourceWhere it was found: assessment, scan, audit, incident or continuous monitoring, with the report reference
ControlsThe controls affected, such as AC-2 or SI-2
Affected componentsThe components or services where the weakness exists
Date identifiedWhen the weakness was found
Risk levelThe risk the weakness poses, using the organization’s risk scale
OwnerThe role responsible for fixing it
Resources requiredFunding, staff or tools needed, or “none”
MilestonesInterim steps, each with a planned date
Scheduled completionThe date the weakness will be fixed
StatusOpen, completed or risk accepted
Completion date and evidenceWhen it was fixed and where the evidence is
CommentsChanges to dates, with the reason and who approved them
IDWeaknessSourceControlsAffected componentsDate identifiedRisk levelOwnerResources requiredMilestonesScheduled completionStatusCompletion date and evidenceComments
Fill in: IDFill in: weaknessFill in: source and report referenceFill in: controlsFill in: componentsFill in: dateFill in: risk levelFill in: owner roleFill in: resourcesFill in: milestones and datesFill in: dateFill in: statusFill in: date and evidence locationFill in: comments

Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.