Skip to content

Program Management Decision Worksheet

Program Management Decision Worksheet template: Every decision the Program Management family of NIST SP 800-53 Rev. 5 forces, with typical values and who decides, for the whole organization, as a spreadsheet.

TypeProgram stageStatusTemplate versionNIST basis
Decision worksheetFoundationDraft1.0.0SP 800-53 release 5.2.0

Every decision the Program Management family asks your organization to make before its policy and procedures can be final: the family’s key questions, then each organization-defined parameter of every PM control, with a typical value where the Program Management Policy gives one. Download the spreadsheet, fill the “Your value” column with the people who decide, and carry the values into the policy’s highlighted fields.

Typical values are starting points, not recommendations for every system. “Who decides” defaults to the role accountable for the family policy; many organizations delegate system-level values to the system owner.

VariantSpreadsheet
Organization-wideCSV

38 decisions.

DecisionControlTypical valueWho decides
Who leads the security program, and who approves the program plan and sets the organization’s risk tolerance?PM-1, PM-2, PM-28The Chief Information Security Officer leads the program; the senior leader approves the plan and sets risk tolerance.Senior leader
Who leads the privacy program, and is it combined with another role?PM-18, PM-19A senior privacy official who reports to the senior leader. A small organization may give the role to its general counsel or compliance lead.Senior leader
Which PM controls do not apply, and why?PM-8, PM-17, PM-24PM-8 applies only to owners or operators of critical infrastructure, PM-17 only where the organization holds controlled unclassified information, and PM-24 only to organizations that run matching programs. Record each decision in the program plan.Chief Information Security Officer
The frequency at which to review and update the organization-wide information security program planPM-1AnnuallyChief Information Security Officer
Events that trigger the review and update of the organization-wide information security program planPM-1A significant change to the organization’s mission, structure, risk tolerance or systems, a major incident, or a finding from an assessment or audit of the programChief Information Security Officer
The frequency at which to update the inventory of organizational systemsPM-5Quarterly, and whenever a system is authorized, significantly changed or retiredChief Information Security Officer
The frequency at which to update the inventory of systems, applications, and projects that process personally identifiable informationPM-5(1)At least annually, and whenever a privacy impact assessment is completed or updatedChief Information Security Officer
Non-essential functions or services to be offloadedPM-7(1)Non-essential services, such as email, file sharing and public web hosting, on systems that support mission-essential functionsChief Information Security Officer
The frequency at which to review and update the risk management strategyPM-9AnnuallyChief Information Security Officer
The frequency at which to review and revise the mission and business processesPM-11Annually, and whenever the organization changes its mission, structure or major servicesChief Information Security Officer
The frequency at which to review and update the policyPM-17AnnuallyChief Information Security Officer
The frequency at which to review and update the proceduresPM-17AnnuallyChief Information Security Officer
The frequency of updates to the privacy program planPM-18AnnuallyChief Information Security Officer
The roles of a Data Governance BodyPM-23The chief data officer (chair), the chief information officer, the chief information security officer, the senior privacy official, the records manager and the owners of major data setsChief Information Security Officer
The responsibilities of a Data Governance BodyPM-23Setting data governance policy, approving data sharing agreements, and resolving data quality and access issuesChief Information Security Officer
The frequency for reviewing policies that address the use of personally identifiable information for internal testing, training, and researchPM-25AnnuallyChief Information Security Officer
The frequency for updating policies that address the use of personally identifiable information for internal testing, training, and researchPM-25Annually, and whenever the review finds a change is neededChief Information Security Officer
The frequency for reviewing procedures that address the use of personally identifiable information for internal testing, training, and researchPM-25AnnuallyChief Information Security Officer
The frequency for updating procedures that address the use of personally identifiable information for internal testing, training, and researchPM-25Annually, and whenever the review finds a change is neededChief Information Security Officer
The time period in which complaints (including concerns or questions) from individuals are to be reviewedPM-265 business daysChief Information Security Officer
The time period in which complaints (including concerns or questions) from individuals are to be addressedPM-2630 daysChief Information Security Officer
The time period for acknowledging the receipt of complaintsPM-263 business daysChief Information Security Officer
The time period for responding to complaintsPM-2630 daysChief Information Security Officer
Privacy reportsPM-27An annual privacy program report, summaries of privacy impact assessments, and breach reportsChief Information Security Officer
Privacy oversight bodiesPM-27The board of directors or its audit committee, and regulators where law requiresChief Information Security Officer
Officials responsible for monitoring privacy program compliancePM-27The senior leader, the chief information security officer and general counselChief Information Security Officer
The frequency for reviewing and updating privacy reportsPM-27AnnuallyChief Information Security Officer
The personnel to receive the results of risk framing activitiesPM-28Authorizing officials, system owners, information owners, the leaders of mission and business functions, the senior privacy official, and the senior accountable official for risk managementChief Information Security Officer
The frequency for reviewing and updating risk framing considerationsPM-28Annually, with the risk management strategyChief Information Security Officer
The frequency for reviewing and updating the supply chain risk management strategyPM-30AnnuallyChief Information Security Officer
The metrics for organization-wide continuous monitoringPM-31Systems with a current authorization, plan of action items past due, vulnerabilities remediated within the required times, and staff with current security awareness trainingChief Information Security Officer
The frequencies for monitoringPM-31Continuously for automated controls, and at least monthly for vulnerability, configuration and account dataChief Information Security Officer
The frequencies for assessing control effectivenessPM-31A third of each system’s controls each year, so every control is assessed at least every three yearsChief Information Security Officer
The personnel or roles for reporting the security status of organizational systems toPM-31The senior leader and the authorizing officialsChief Information Security Officer
The personnel or roles for reporting the privacy status of organizational systems toPM-31The senior leader and the authorizing officialsChief Information Security Officer
The frequency at which to report the security status of organizational systemsPM-31MonthlyChief Information Security Officer
The frequency at which to report the privacy status of organizational systemsPM-31QuarterlyChief Information Security Officer
The systems or system components supporting mission-essential services or functionsPM-32The systems and components that support mission-essential functions, as the business impact analysis identifies themChief Information Security Officer

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.