Requirement Definition
Secure Development Starts Here
Fortifying component hardware, firmware, and software is critical to building more secure systems. The most effective way to build more secure products is to integrate security requirements into every phase of the development lifecycle, beginning with the product definition.
With our broad product portfolio, there’s no "one size fits all" solution to component-level security. Security requirements are driven by context and vary by component features, complexity, and risk level.
Examples of software and firmware requirements:
- Approved crypto algorithms and implementations (for components with crypto).
- Input validation and secure coding requirements.
- Static code analysis (SCA) of all Intel-developed code, with the SCA tool determined by programming language.
Examples of hardware security requirements:
- Access management requirements for protected or sensitive registers.
- Architecture reviews by a team of HW security experts.
- Security requirements for third-Party IP and components.
Standard security and privacy requirements include:
- Security and privacy validation
- Privacy assessments
- Security-focused reviews