*Precondition: A PC with HSM must be connected via PCIe and HSM driver has been installed correctly on the PC. * Input conditions / steps: OpenSSL's PKCS # 11 test software is run for AES ,Random number generation, key generation * Expected outcome: AES Average Encryption / decryption rate for HSM (less than a second for symmetric encryption for 10 MB data) True random number generation throughput result is obtained above 200Mpbs. Key generation speed result is obtained above 50 key per second."

*Precondition: ERARGE HSM has been established / connected under UC11. * Input conditions / steps: (True Randomness, unpredictability) 320 blocks of random data of 1 million bits are collected from TRNG. * Expected outcome: It is expected to pass NIST-800-22, Diehard and BigCrush Compliance tests.

*Precondition: The Secure Authentication device connects to a network computer running HSM and Secure Gateway. * Input conditions / steps: Enter the webauthn.io website and register with Secure authentication device. * Expected outcome: The webauthn.io website is entered, the login process is successful using secure authentication device.

*Precondition: HSM and Secure Gateway have been run on Otokar's system and verification has been completed. * Input conditions / steps: At least 20 users using the system are surveyed. Ease of use is asked. * Expected outcome: Mean opinion result expected to be 3.5 and above in 0(lowest) to 5(highest) range"

*Precondition: HSM and Secure Gateway devices have passed lab tests. * Input conditions / steps: Installation and functional tests, deployment, and system verification are carried out on Otokar system, which is available within the scope of UC11, all system is operated in a temperature range of -15 + 60C for 1-4 weeks. * Expected outcome: Installation and functional test takes time less than 4 hours. Deployment takes time minimum 1 maximum 3 days. System verification and lifecycle tests are completed in minimum 1 maximum 4 weeks

*Precondition: HSM and Secure Gateway have been run in Otokar's system and verification has been completed. * Input conditions / steps: Communication is listened from the ends of the network and data blocks are collected. Tampering is applied to HSM. MitM attack is organised. Unauthorised access is realised. * Expected outcome: It is verified that the data is integrated and encrypted from the end to the end in the network. Malicious people cannot access either the data transferred in the communication or the authentication keys

-Task Safety in faulty situation * preconditions: body inspection tasks are provided to operation stack. * input conditions / steps: Mutating operations with faulty situations. * expected results: System do not cause any unsafe movement or behaviour.

Fault injection to robotic system * preconditions: System should be operating normally without any fault. * input conditions / steps: Injecting faults and mutating source code of the operating system. * expected results: Robot system will handle errors and continue operating in normal mode.

-Task Safety in faulty situation * preconditions: body inspection tasks are provided to operation stack. * input conditions / steps: Manipulating data transfer nodes * expected results: System do not cause any unsafe movement or behaviour in cell.

-Fault injection to robotic system * preconditions: System should be operating normally without any fault. * input conditions / steps: Injecting fault that manipulates the robot camera stream. * expected results: Robot system will detect error and report situation.

- ML Techniques Preprocessing & Training: * Pre-condition: The system is up and running in operational mode. * Input conditions / steps: Data from the system is continuously collected and fed into ML process block. * Expected outcome: Pre-determined ML techniques and models are executed, output networks are generated and made available for inference step."

-Fault injection to robot system * Prerequisites: The system must have made image recordings while operating normally without any fault. * Input conditions / steps: Fault injection is performed on images recorded from robot cameras. * Expected results: The camera quality control system will detect the fault and report the situation.

Fault injection to robot camera system * Prerequisites: The system must have made image recordings while operating normally without any fault. * Input conditions / steps: Performing fault injections to robot cameras at different fault types and at different rates. * Expected results: The camera quality control system will detect which faults have been injected according to varying fault types and rates.

Fault Injection Tool for Robotic System * Prerequisites: System must be working properly. * Input conditions / steps: Robotic system files are testing to evaluation about their reliability. * Expected results: The detailed evaluation of the results that occur when the tested files are mutated, ensures that the user has information about the reliability of the tested file.