The webinar, hosted by Keysight’s device security team, focused on helping organizations understand and prepare for an OCP SAFE review. S.A.F.E., which stands for Security Appraisal Framework Enablement, is a framework created by the Open Compute Project (OCP) to evaluate security in hardware and software components. Unlike certification schemes, S.A.F.E. is flexible and adaptable to specific products and environments, allowing researchers and labs to emphasize the most critical aspects of a device under review.
The session was led by Cameron Howell, Security Analyst, and Anjana Miyar, Senior Security Analyst, who covered the fundamentals of S.A.F.E., the three scopes of evaluation, and practical advice on navigating the review process efficiently.
What is OCP SAFE?
OCP SAFE is not a certification but a framework for structured security appraisal. Its purpose is to provide transparency about vulnerabilities, mitigations, and security posture across components commonly used in data centers. Companies such as Google and Microsoft already request S.A.F.E. reviews from suppliers.
S.A.F.E. consists of three scopes:
Scope 1 – Software/firmware design and architecture: Evaluates high-level and low-level design, code review, and compliance practices.
Scope 2 – Trust boundaries:
Focuses on communication between Trusted Execution Environments (TEE) and Rich Execution Environments (REE), attestation, and data separation.
Scope 3 – Hardware security: Evaluates physical resiliency against fault injection and side-channel attacks. S.A.F.E. emphasizes documentation-heavy evaluation—detailed design documents, code, threat models, and testing evidence are critical inputs.
Why S.A.F.E. Matters
The groups most invested in S.A.F.E. reviews include:
- Data center operators that require supplier transparency.
- Software developers and architects who document and design security mechanisms.
- Product owners who manage features and compliance.
- Security teams and component suppliers who want to demonstrate security robustness to large-scale customers.
- S.A.F.E. reviews help ensure that products meet industry expectations, mitigate vulnerabilities early, and streamline adoption by hyperscale operators.
The Review Process
The S.A.F.E. evaluation is iterative and involves close communication between labs and developers:
- Document and code collection – The review begins by gathering architecture diagrams, security implementation details, build systems, and code bases.
- Initial Q&A session – Developers and architects explain system operations, assumptions, and potential attack surfaces.
- Threat modeling – Either supplied by the client or developed with lab assistance, this models attacker goals, assets, and vulnerabilities.
- Review and feedback loop – Documentation and code are reviewed for vulnerabilities, with ongoing Q&A to refine understanding.
- Fixes and validation – Identified vulnerabilities are patched; labs re-review code and documentation to confirm fixes.
Reporting – Deliverables include:
- A long-form report (for internal client use) with details on assets, threat models, risks, and findings.
- A short-form report (potentially public) summarizing key vulnerabilities and mitigations, often requested by customers.
- Delta reviews are available for subsequent product versions, reducing effort by focusing only on changes.
Best Practices for Clients
Keysight experts highlighted strategies to make S.A.F.E. reviews more efficient:
- Comprehensive documentation: Clear, well-structured design docs and code references speed up analysis.
- Threat models: Preparing or co-developing threat models ensures focus on relevant attack vectors.
- Developer involvement: Direct communication with engineers prevents delays and misinterpretations.
- Testing artifacts: Providing test code, cryptographic vectors, and hardware devices (especially for Scope 3) strengthens review depth.
- Active communication: Quick responses to lab queries avoid bottlenecks in iterative reviews.
Scope-by-Scope Deep Dive
Scope 1 (Software & Firmware)
- Covers CPUs, GPUs, FPGAs, network controllers, accelerators, and storage devices.
- Relies on an OCP-recommended checklist covering architecture, documentation, code vulnerabilities, and compliance.
- Every production firmware version must undergo evaluation.
- Deliverables: detailed reports including CVSS scores, threat models, and findings.
- Keysight supports clients by holding scoping calls, reviewing documents, creating or validating threat models, mapping code bases, and conducting manual and automated reviews.
Scope 2 (Trust Boundaries)
- Assesses TEEs, REEs, attestation, and authenticated/encrypted I/O.
- Lacks an official OCP checklist but uses processes informed by Keysight’s experience with other certifications (e.g., EMVCo).
- Involves verifying physical or logical separation between trusted and untrusted environments, analyzing privilege escalation risks, and reviewing fuse/security configurations.
- Requires close collaboration with the OCP SAFE certification body to clarify evaluation details.
Scope 3 (Hardware Security)
- Focuses on resilience to fault injection and side-channel analysis.
- Keysight leverages its expertise in hardware evaluations and its proprietary Inspector toolkit to test cryptographic robustness.
- Builds on experience with EMVCo and Common Criteria certifications.
Q&A Highlights
During the Q&A session, several key points were clarified:
- Reuse of other certifications: Analysis from certifications like SESIP can sometimes be reused, though labs may revalidate portions.
- Patching during evaluation: Fixes are accepted and reviewed as part of the process.
- Initial scoping calls: Cover goals, target overview, relevant scopes, and timelines.
- Evaluation duration: Typically several months, depending on the speed of fixes.
- Validity of results: Findings remain valid until a new version of the product is released.
- Delta evaluations: Only required when significant security-related changes occur.
Conclusion
The webinar emphasized that OCP S.A.F.E. reviews are collaborative, documentation-driven, and iterative. Keysight positions itself as a partner that guides clients through scoping, documentation, threat modeling, vulnerability review, and reporting across all three scopes.
By preparing comprehensive documentation, engaging developers early, and maintaining clear communication, organizations can streamline their reviews, address vulnerabilities efficiently, and provide hyperscale customers with the assurance they demand.