# PM-04 Plan of Action and Milestones Process

NIST SP 800-53 control. Family: PM Program Management. Function: preventative. Baselines: privacy. Mapping licence: CC BY-SA 4.0.

Statement: a. Implement a process to ensure that plans of action and milestones for the information security, privacy, and supply chain risk management programs and associated organizational systems: 1. Are developed and maintained; 2. Document the remedial information security, privacy, and supply chain risk management actions to adequately respond to risk to organizational operations and assets, individuals, other organizations, and the Nation; and 3. Are reported in accordance with established reporting requirements. b. Review plans of action and milestones for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.
Guidance: The plan of action and milestones is a key organizational document and is subject to reporting requirements established by the Office of Management and Budget. Organizations develop plans of action and milestones with an organization-wide perspective, prioritizing risk response actions and ensuring consistency with the goals and objectives of the organization. Plan of action and milestones updates are based on findings from control assessments and continuous monitoring activities. There can be multiple plans of action and milestones corresponding to the information system level, mission/business process level, and organizational/governance level. While plans of action and milestones are required for federal organizations, other types of organizations can help reduce risk by documenting and tracking planned remediations. Specific guidance on plans of action and milestones at the system level is provided in CA-05.

## Patterns that use it (1)
- Important (1): SP-035 Offensive Security Testing

## Clauses by framework (38 frameworks)
- iso_27001_2022: 6.1, 6.1.3, 6.2, 7.5, 8.3, 9.3, 10.2. OSA's own, not in NIST's crosswalk: 6.1.3
- nist_csf_2: GV.OV-03, GV.PO-02, ID.IM-01, ID.IM-02, ID.IM-03, ID.RA-06. OSA's own, not in NIST's crosswalk: GV.PO-02, ID.IM-01, ID.RA-06
- apra_cps_234: Para 26
- pra_op_resilience: PS6/21-1.1
- rbi_csf: Annex1.18, ITGRCA.26
- fisc: FISC.O1
- lgpd_bcb: BCB.Art.5, BCB.Art.19, LGPD.Art.49
- mlps_2: 8.1.10.3
- dnb_good_practice: DNB.4.3
- cbb_tm: TM-4, TM-11
- cbuae: CR-14
- nca_ecc: 1-5
- qatar_nia: RM
- bog_cisd: CISD-COMP, CISD-III, CISD-IV
- bom_ctrm: 1.5, 5.4
- cbe_csf: GOV-3
- cbn_csf: Part1.3, Part2.2, Part6.1, Part6.2, Part7.2
- sa_js2: JS2-5, JS2-9
- bcbs_239: Principle 13
- bot_cyber: Ch1.3
- cpmi_pfmi: CG.LE, PFMI.P3
- eba_ict: 3.3.4
- ecb_croe: CROE.2.2.1, CROE.2.8.1
- ffiec_is: Appendix A, II.C.1, II.C.3, II.C.4
- iosco_cyber: LE-2
- nydfs_500: 500.2
- sebi_cscrf: RC.IM, RS.IM
- tsa_psd: SD-1 Sec 4
- doe_c2m2: PROGRAM
- cbest: CBEST.6
- tiber_eu: TIBER.CLOSE, TIBER.REM
- fca_sysc_13: SYSC 13.G.4
- fda_cyber: 524B-2, INC-3, VR-2
- hitrust_csf: 03.b, 11.b
- naic_ds: 4, 4E
- pra_ss1_23: P4.5
- solvency_ii: Art.46
- basel_sco60: SCO60.5, SCO60.82
OSA's mapping for iso_27001_2022 and nist_csf_2 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/PM-04
- Clauses only: /api/v1/controls/PM-04?fields=mappings
- Page for people: /controls/pm-04/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.