The text of the Privacy Continuous Monitoring Strategy
Approval #
The Senior Agency Official for Privacy (SAOP) approves this privacy document. The Chief Information Security Officer (CISO) concurs on the security controls it relies on.
| Role | Name | Signature |
|---|---|---|
| Senior Agency Official for Privacy (SAOP) | ||
| Chief Information Security Officer (CISO), concurring |
Revision History #
| Date | Version | Description | Reviewer |
|---|---|---|---|
| 2026-10-31 | 1.0 | Initial issuance | [Reviewer name] |
Review cycle: Every year, and after a change that affects privacy risk.
Mandate. Office of Management and Budget (OMB) Circular A-130, Appendix I, requires the SAOP to develop and maintain a privacy continuous monitoring strategy and program. Circular A-130 defines the strategy as a formal document that catalogs the privacy controls in place at the Organization. It assigns each control an assessment frequency that keeps the Organization compliant and manages privacy risk. This strategy works alongside the information security continuous monitoring strategy (PLAN-ISCM-001).
1. Purpose #
The privacy continuous monitoring program keeps the SAOP aware of privacy risks at all times. It watches for changes to systems and their environments that affect personally identifiable information (PII). It assesses privacy controls often enough to show that they work and that the Organization meets its privacy requirements.
2. Control Catalog and Assessment Frequency #
The SAOP keeps the full catalog of privacy controls in the governance, risk, and compliance (GRC) system. For each privacy control, the SAOP records whether it is a program management, common, system-specific, or hybrid control, and how often it is assessed. The frequencies below are the Organization’s defaults. The SAOP may set a shorter frequency for a system with higher privacy risk.
| Control group | Examples | Default assessment frequency | Assessed by |
|---|---|---|---|
| Privacy program management | PM-18, PM-19, PM-20, PM-27 | Every year | SAOP |
| PII inventory and minimization | PM-05(1), PM-22, PM-25, PT-07(1) | Every year | Chief Privacy Officer |
| Authority, purpose, notice, and consent | PT-02, PT-03, PT-04, PT-05 | Every year, and when a collection changes | Privacy officers |
| System of records notices and computer matching | PT-06, PT-06(1), PT-08 | Every year, and when a system of records changes | Privacy Act Officer |
| Privacy impact assessments | RA-08 | Every year, and before a significant change to a system | Privacy officers |
| Privacy controls carried out by systems | AU-03(3), SC-07(24), SI-12(1), SI-18 | As often as PLAN-ISCM-001 sets for the system’s security controls | Security control assessor, with the privacy officer |
| Breach response and privacy incident handling | IR-08(1), PLAN-BR-001 | Every year, through the tabletop exercise | SAOP |
3. Assessment Methods and Measures #
Assessors examine documents, interview the people who carry out each control, and test system controls, as National Institute of Standards and Technology (NIST) SP 800-53A describes. The SAOP tracks these measures every quarter:
- the share of systems that handle PII with a current privacy impact assessment (PIA);
- the share of systems of records with a current system of records notice (SORN) that carries the breach routine uses;
- the share of the workforce that completed privacy training on time;
- the number of breaches, and the time from discovery to the Cybersecurity and Infrastructure Security Agency (CISA) report and to notification;
- the number of open privacy weaknesses and how many are past due.
Entry criteria: A privacy control is due for assessment.
Exit criteria: Each control due has a recorded result.
| Step and actor | Action | Tool | Evidence | Controls |
|---|---|---|---|---|
| 1. SAOP | At the start of each fiscal year, list the privacy controls due for assessment, with the assessor for each. | The GRC system | Assessment schedule | PM-31, CA-07 |
| 2. Privacy officer | Examine the PIAs, SORNs, and privacy notices for each control due. | The document management system | Document review notes | RA-08, PT-05, PT-06 |
| 3. Privacy officer | Interview the people who carry out each control. Record what they said. | The GRC system | Interview notes | CA-02 |
| 4. Security Control Assessor | Test the privacy controls that systems carry out, as often as the information security continuous monitoring (ISCM) Strategy sets. | The GRC system | Test results | CA-02, CA-07 |
| 5. Privacy officer | Record each control’s result, with any weakness found. | The GRC system | Assessment results | CA-02, PM-31 |
The privacy officer gathers the measures at the end of each quarter.
Entry criteria: A quarter ends.
Exit criteria: The SAOP reviewed the measures and decided on any action.
| Step and actor | Action | Tool | Evidence | Controls |
|---|---|---|---|---|
| 1. Privacy officer | Count the systems that handle PII with a current PIA, and the systems of records with a current SORN that carries the breach routine uses. | The document management system | Document counts | PM-05(1), RA-08, PT-06 |
| 2. Privacy officer | Pull the share of the workforce that completed privacy training on time. | The learning management system (LMS) | Training completion report | AT-02, AT-03 |
| 3. The Security Operations Center (SOC) | Report the number of breaches, and the time from discovery to the CISA report and to notification. | The ticketing system | Breach report | IR-05, IR-08(1) |
| 4. Privacy officer | Count the open privacy weaknesses and the ones past due. | The GRC system | Weakness counts | CA-05, PM-04 |
| 5. SAOP | Review the measures each quarter and decide on any action. | The document management system | Quarterly measures report | PM-31 |
Evidence: the assessment schedule and results in the GRC system, the document review notes, the training completion report, the breach report, and the quarterly measures reports.
4. Watching for Change #
System Owners tell the privacy officer before any change that affects PII. Such changes include a new collection, a new use or sharing of PII, a new system or technology, or a change in the people whose PII the system holds. The privacy officer decides whether the change needs a new or updated PIA, SORN, or privacy notice. The CISO tells the SAOP about any incident, vulnerability, or monitoring finding that puts PII at risk.
Entry criteria: A System Owner plans a change that affects PII, or a finding puts PII at risk.
Exit criteria: The privacy documents match the change before it goes into production, and the SAOP knows of the finding.
| Step and actor | Action | Tool | Evidence | Controls |
|---|---|---|---|---|
| 1. System Owner | Before any change that affects PII, tell the privacy officer through the change request. | The ticketing system | Change request | CM-04, RA-08 |
| 2. Privacy officer | Within the change review, decide whether the change needs a new or updated PIA, SORN, or privacy notice. Record the decision in the change request. | The ticketing system | Privacy decision | CM-04, RA-08, PT-05 |
| 3. System Owner | Complete any document the privacy officer requires before the change goes into production. | The document management system | Updated PIA, SORN, or notice | RA-08, PT-05, PT-06 |
| 4. CISO | When an incident, vulnerability, or monitoring finding puts PII at risk, tell the SAOP on the day the CISO learns of it. | The ticketing system | Notice to the SAOP | IR-06, PM-31 |
Evidence: the change requests with the privacy decisions, the updated PIAs, SORNs, and notices, and the notices to the SAOP.
5. Reporting and Correcting Weaknesses #
Assessors record privacy control weaknesses in the GRC system. The System Owner opens a plan of action and milestones (POA&M) item for each weakness, as the POA&M Management Procedure (PROC-POAM-001) describes. The SAOP reviews open privacy weaknesses every quarter and reports privacy program status to the Agency Head every year. The SAOP uses the results in the annual Federal Information Security Modernization Act (FISMA) privacy report.
Entry criteria: An assessment finds a privacy control weakness.
Exit criteria: The weakness has a POA&M item, and the SAOP reported it in the quarterly review and the annual report.
| Step and actor | Action | Tool | Evidence | Controls |
|---|---|---|---|---|
| 1. Assessor | When an assessment finds a privacy control weakness, record it. | The GRC system | Weakness record | CA-02, PM-31 |
| 2. System Owner | Open a POA&M item for each weakness, as the POA&M Management Procedure describes. | The GRC system | Open item | CA-05 |
| 3. SAOP | Every quarter, review the open privacy weaknesses with the privacy officer and the System Owners. | The GRC system | Quarterly review notes | CA-05, PM-04 |
| 4. SAOP | Every year, report privacy program status to the Agency Head. | The document management system | Annual status report | PM-31 |
| 5. SAOP | Use the year’s results in the privacy section of the annual FISMA report. | The document management system | FISMA privacy report | PM-04, PM-31 |
Evidence: the weakness records and POA&M items in the GRC system, the quarterly review notes, the annual status report, and the FISMA privacy report.
6. Review #
The SAOP reviews this strategy every year and after a change in law, OMB policy, or the Organization’s systems that affects privacy risk.
7. References #
These are the sources this document cites, with a link to each official text.
- Federal Information Security Modernization Act of 2014 (44 U.S.C. § 3551 et seq.), December 18, 2014.
- NIST SP 800-53A Rev. 5: Assessing Security and Privacy Controls, January 2022.
- Privacy Act of 1974 (5 U.S.C. § 552a), December 31, 1974.