Security Package Formal Review Report

Note

Document header

[Your Module Name] Security Package Formal Review		status: draft security: YES safety: ASIL_B
tags: template realizes: wp__fdr_reports
doc__mod_temp_module_name_sec_pkg_fdr		Generic Document

Attention

The above directive must be updated according to your Module.

• Modify Your Module Name to be your Module Name

• Modify id to be your Module Name in upper snake case preceded by doc_ and succeeded by safety_package_fdr

• Adjust status to be valid

• Adjust safety and tags according to your needs

1. Purpose

The purpose of this review checklist is to report status of the formal review for the Security Package.

2. Checklist

See also the review concept for further information about reviews in general and inspection in particular.

Table 19 Security Package Checklist

Id	Security Package activity	Compliant to ISO SAE 21434?	Comment
1	Is a Security Package provided which matches the Security Plan (i.e. all planned work products referenced)?	[YES | NO ]	<Rationale for result>
2	Is the argument how security is achieved, provided in the Security Package, plausible and sufficient?	NO	The argument is intentionally not provided by the Project.
3	Are the referenced work products available?	[YES | NO ]	<Rationale for result>
4	Are the referenced work products in released state, including the Process Security Audit?	NO	Security Audit is currently not planned, tailored out.
5	If security related deviations from the process or security concept are documented, are these argued understandably?	[YES | NO ]	<Rationale for result>
6	Are the requirements for post-development available?	[YES | NO ]	<Rationale for result>