FedRAMP High
SA - System and Services Acquisition

FedRAMP High SA-8: Security and Privacy Engineering Principles

Apply FedRAMP-defined systems security and privacy engineering principles in development.

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

What else in your programme already covers this

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

  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development
  • CCM-DSP-07 Data Protection by Design and Default
  • CCM-DSP-08 Data Privacy by Design and Default

PCI DSS 4.0 · 4 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.5.1 6.5.1 Change control procedure for production

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-P3.1 P3.1 Collecting personal information consistent with objectives

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles

NIST SP 800-218 · 3 controls

CIS Controls v8 · 2 controls

  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components

NIST SP 800-53 Rev 5 · 2 controls

  • NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
  • NIST800-SA-8 SA-8 Security and Privacy Engineering Principles

C5 (Germany) · 1 control

  • C5-DEV-01 Policies for the development/procurement of information systems
  • CFTC-SS-7 Generally Accepted Standards and Best Practices

CMMC 2.0 · 1 control

GDPR · 1 control

  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • 161R1-SA-8 Security and Privacy Engineering Principles
  • 03.16.01 Security Engineering Principles

NIST SP 800-172 · 1 control

  • 3.13.2e Introduce Unpredictability into System Operations
  • SA-8 SA-8 Security and Privacy Engineering Principles
  • SA-8 SA-8 Security and Privacy Engineering Principles
  • SA-8 SA-8 Security and Privacy Engineering Principles

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 SA - System and Services Acquisition

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

FedRAMP High SA-8 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 39 it maps to, and the evidence behind each claim, over MCP and REST.