SA-8 Security and Privacy Engineering Principles
Control
Apply the following systems security and privacy engineering principles in the specification, design, development, implementation, and modification of the system and system components: [Assignment: organization-defined systems security and privacy engineering principles].
Discussion
Systems security and privacy engineering principles are closely related to and implemented throughout the system development life cycle (see [SA-3](#sa-3) ). Organizations can apply systems security and privacy engineering principles to new systems under development or to systems undergoing upgrades. For existing systems, organizations apply systems security and privacy engineering principles to system upgrades and modifications to the extent feasible, given the current state of hardware, software, and firmware components within those systems.
The application of systems security and privacy engineering principles helps organizations develop trustworthy, secure, and resilient systems and reduces the susceptibility to disruptions, hazards, threats, and the creation of privacy problems for individuals. Examples of system security engineering principles include: developing layered protections; establishing security and privacy policies, architecture, and controls as the foundation for design and development; incorporating security and privacy requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that developers are trained on how to build secure software; tailoring controls to meet organizational needs; and performing threat modeling to identify use cases, threat agents, attack vectors and patterns, design patterns, and compensating controls needed to mitigate risk.
Organizations that apply systems security and privacy engineering concepts and principles can facilitate the development of trustworthy, secure systems, system components, and system services; reduce risk to acceptable levels; and make informed risk management decisions. System security engineering principles can also be used to protect against certain supply chain risks, including incorporating tamper-resistant hardware into a design.
Control enhancements (33)
- SA-8(1)Clear Abstractions
- SA-8(2)Least Common Mechanism
- SA-8(3)Modularity and Layering
- SA-8(4)Partially Ordered Dependencies
- SA-8(5)Efficiently Mediated Access
- SA-8(6)Minimized Sharing
- SA-8(7)Reduced Complexity
- SA-8(8)Secure Evolvability
- SA-8(9)Trusted Components
- SA-8(10)Hierarchical Trust
- SA-8(11)Inverse Modification Threshold
- SA-8(12)Hierarchical Protection
- SA-8(13)Minimized Security Elements
- SA-8(14)Least Privilege
- SA-8(15)Predicate Permission
- SA-8(16)Self-reliant Trustworthiness
- SA-8(17)Secure Distributed Composition
- SA-8(18)Trusted Communications Channels
- SA-8(19)Continuous Protection
- SA-8(20)Secure Metadata Management
- SA-8(21)Self-analysis
- SA-8(22)Accountability and Traceability
- SA-8(23)Secure Defaults
- SA-8(24)Secure Failure and Recovery
- SA-8(25)Economic Security
- SA-8(26)Performance Security
- SA-8(27)Human Factored Security
- SA-8(28)Acceptable Security
- SA-8(29)Repeatable and Documented Procedures
- SA-8(30)Procedural Rigor
- SA-8(31)Secure System Modification
- SA-8(32)Sufficient Documentation
- SA-8(33)MinimizationPRIVACY
Related controls
Need SA-8 implemented and evidenced?
We assess where you stand against this control, document the gap, and build the remediation plan your auditor and your board will both accept.
Control catalog and framework text on this page is reproduced from official NIST publications — a public-domain work of the U.S. Government (17 U.S.C. §105). Maverc commentary, groupings, and readiness guidance are our own and are not part of any NIST publication.
