Cryptography and cyber security

We also bring supporting knowledge of technologies a system test often depends on. A feature that talks over TLS, seals a key in a TPM, or uses a SAM is not testable until that environment is prepared and understood. We can stand that environment up so the trial can proceed.

We are practised in TLS, hardware security such as TPM and SAM, and the encryption that sits with them. The aim is not a lecture on cryptography. It is a lab in a known state: certificates, trust stores, keys, and modules named in the protocol, so testers are proving the product rather than fighting an unfinished crypto stack.

1. 01

   TLS

   Transport security as the product actually uses it: certificates, trust, versions, and what must fail if the handshake is wrong.

2. 02

   TPM

   Trusted Platform Module work — sealed keys, measured state, and whether the software under test is talking to the module it thinks it is.

3. 03

   SAM

   Secure Access Module and related host-device security, including estates that already use NFC or a smart-card reader.

4. 04

   Encryption around them

   Keying, wrapping, and the difference between a test key and a live one. Complex crypto environments prepared so system testing can be undertaken, not deferred.

This work sits beside System Testing: the protocol names the kit; this page is how we get the crypto environment into a known state first.