FedRAMP High
SC - System and Communications Protection

FedRAMP High SC-1: Policy and Procedures

Develop, document, disseminate and review the policy for system and communications protection, and its procedures, on the FedRAMP-defined cadence: policy at least annually under High and at least every three years under Moderate, procedures at least annually and after significant changes under both.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 27 controls across 16 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 8 controls

  • 1.1.1 1.1.1 Requirement 1 policies and procedures governed
  • 1.1.2 1.1.2 Requirement 1 roles and responsibilities assigned
  • 10.1.1 10.1.1 Requirement 10 policies and procedures maintained and in use
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 4.1.2 4.1.2 Requirement 4 roles and responsibilities assigned
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 3.1.2 3.1.2 Assigned duties for Requirement 3 activities

C5 (Germany) · 3 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-08 Policies for data transmission
  • C5-CRY-01 Policy for the use of encryption procedures and key management
  • ASBv3-GS-3 Define and implement data protection strategy
  • ASBv3-GS-4 Define and implement network security strategy
  • CCM-CEK-01 Encryption and Key Management Policy and Procedures
  • CCM-IVS-01 Infrastructure and Virtualization Security Policy and Procedures

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 5.1 Policies for information security

ISO 27002:2022 · 1 control

  • 5.1 Policies for information security
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission
  • SC-1 SC-1 Policy and Procedures
  • SC-1 SC-1 Policy and Procedures
  • SC-1 SC-1 Policy and Procedures

SOC 2 · 1 control

  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SC - System and Communications Protection

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High SC-1 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.

Query this from an agent

The graph holds this control, the 27 it maps to, and the evidence behind each claim, over MCP and REST.