FedRAMP High PL-2: System Security and Privacy Plans
Develop SSP that aligns with FedRAMP template; review and update annually.
What else in your programme already covers this
This control maps to 57 controls across 28 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
12.1.1 An overall information security policy is: • Established. • Published. • Maintained. • Disseminated to all relevant personnel, as well as to relevant vendors and business partners
12.1.2 The information security policy is: • Reviewed at least once every 12 months. • Updated as needed to reflect changes to business objectives or risks to the environment
12.5.2 PCI DSS scope documented and confirmed annually
12.5.2.1 Service provider scope confirmed every 6 months
2.1.1 All security policies and operational procedures that are identified in Requirement 2 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
You are reading one control. How much of FedRAMP High have you already done?
FedRAMP High PL-2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.