TRUST ATLAS WORKSHEET
Security target brief
EUCC product certification · Step 2 · Make claims and evidence traceable- Who prepares it
- Product architect + development team
- When to prepare it
- Before evaluator fieldwork
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Target and configuration
- Example cryptographic module v2.1, approved boot and hardware configuration only
- Threat
- Unauthorized modification of the module’s firmware
- Assumption
- Physical deployment and operating environment follow administrator guidance.
- Security claim and evidence
- Verified boot checks signed firmware. Link design and negative tests.
- Evaluation reference
- Record the scheme, assurance level and applicable protection profile.
Gather first
- Product boundary and configuration
- Applicable protection profile and evaluation scheme
- Security architecture and threat model
How to prepare it
- Identify the target of evaluation by version, components, users, operating environment and evaluated configuration.
- List threats, assumptions and claims, then trace them to functions, requirements and tests. Record protection profile claims and the selected assurance route where applicable.
- Review the brief with the evaluator before freezing the official security target. Match every scope and configuration statement across the supporting records.
Review
The target, claims and assumptions describe the exact product a buyer will deploy.
Handoff
Use the facility’s current security target guidance for the official submission.