## 5 Security Evaluation Using Virtual Machine-Linked Simulation Environment
### Security Evaluation Scenarios
#### 5.1.1 Security Evaluation Scenario 1  
Scenario 1 is for verifying the data conformity, certificate, and certificate digest of the components of BSM. Table 5 shows the test sequence of Scenario 1.  
Scenario 1 is verifying the BSM's validity and certificate digest value. The verdict is \"pass\" only if the data and digest of the BSM are valid. It is a \"fail\" if any one item is not satisfied. To execute Evaluation Scenario 1, a certificate that the evaluation target node could use was generated. Two types of certificates were generated: trusted and untrusted. Figure 13 shows the information of trusted/untrusted certificates created through CANoe.  
When the evaluation target node sends BSMs using a trusted and untrusted certificate, the verification node receives the BSMs. It verifies their validity through the standard  
\begin{table}
\begin{tabular}{c l} \hline \hline
**Item** & **Description** \\ \hline TP ID & The unique identifier of TP \\ Test object & A simple description of the test objective and goal \\ References & Reference standards for conformity requirements \\ Test configuration & Test configuration type of TP \\ Pre-test conditions & The initial conditions that the IUT must apply to apply TP \\ Test sequence & Test procedure \\ Stimulus & Refers to an event generated to allow the IUT to perform a specific task \\ Check & Determining whether the conditions are appropriate \\ Configuration & Refers to the IUT operation in the test stage \\ Verify & Verifying whether the IUT operates as expected. Classified as pass/fail \\ Procedure & A specific action is instructed, e.g., Repeat steps 1 to 4 \\ \hline \hline \end{tabular}
\end{table}
Table 4: Description of each item in TP.  
\begin{table}
\begin{tabular}{c l c c} \hline \hline
**No.** & **Description** & & **Reference** \\ \hline
**Scenario 1** & BSM conformance and certificate validation test & SAE J2735 [19] & 6.10 DF\_BSMcoreData \\  & & IEEE 1609.2 [10] & 6.3 Secured protocol data units \\ \hline \hline \multirow{4}{*}{**Scenario 2**} & & SAE J2735 [19] & 7.221 DE\_VehicleEventFlags \\  & & Table 17 - SAE J2735 requirements \\  & & SAE J2945/1 [36] & 6.3.1 BSM Contents (BSMCONT) \\  & & & 6.3.6.15 DE\_VehicleEventFlags \\ \hline \multirow{3}{*}{**Scenario 3**} & & UN Regulation 155 [1] & 7.2.24 Specifications \\  & & ISO/SAE 21434 [3] & 10.4.2 Integration verification [RC-10-12] \\ \cline{1-1}  & & ISO/SAE 21434 [3] & 11 Cybersecurity validation [RQ-11-01] \\ \hline
**Scenario 4** & Certificate type validation test in event situation & SAE J2945/1 [36] & 6.5.2 BSM Signing (BSMSIGN) \\ \hline \hline \end{tabular}
\end{table}
Table 3: Description of proposed scenarios.  
conformity of the BSM core data and the digest values of the certificate. If both items are valid, the verdict is \"pass\"; if not, the verdict is \"fail\" as shown in Figure 14.  
Through this scenario, a driving vehicle can verify BSMs and certificates received from other vehicles. When Scenario 1 is executed, it is possible to perform SAE J2735 BSM standard conformance and IEEE 1609.2-based certificate validity verification for messages received from neighboring vehicles at once.