Security control baselines, tailoring, and implementation priorities
ChangedWhat changed
Rev. 4 says baselines are selected in RMF Step 2 from Appendix D as low/moderate/high impact initial security control baselines, with controls assigned priority codes (P1, P2, P3, P0) for implementation sequencing: "Priority Code 1 means implement first, Priority Code 2 next, Priority Code 3 last, and Priority Code 0 means the control is not selected in any baseline." Rev. 5 does not give those baseline contents or sequencing codes in SP 800-53; instead it says "the baselines themselves and the tailoring guidance have been moved out of SP 800-53 and into SP 800-53B" and that Appendix C "does not imply prioritization, level of importance, or implementation order," while only identifying "impact-level prioritization" in RA-2(1). Rev. 4 also frames tailoring against the security control baseline alone, while Rev. 5 frames it as baseline selection and tailoring for "security and privacy" plans and says system security and privacy plans must identify relevant control baselines or overlays if applicable.
Why it matters
A reader relying on Rev. 4 would expect the catalog itself to tell them which controls are initially selected for low/moderate/high baselines and how to sequence implementation using P1/P2/P3/P0. Under Rev. 5, they must go to SP 800-53B for the baseline/tailoring detail and cannot treat catalog order or Appendix C markings as an implementation sequence; they also need to account for privacy being included in the baseline-selection and tailoring framework.