這算是 Google Cloud Platform 在補產品線，讓那些有強制使用 HSM 的需求的應用 (通常是遇到一定要 FIPS 140-2 的規範) 可以搬上雲端：「Introducing Cloud HSM beta for hardware crypto key security」。
從圖片上可以看到 LiquidSecurity，應該是「LiquidSecurity® General Purpose HSM Adapters and Appliances」這個產品：
如同 AWS 的 CloudHSM 服務，GCP 的 Cloud HSM 也是提供 FIPS 140-2 Level 3：
Cloud HSM allows you to host encryption keys and perform cryptographic operations in FIPS 140-2 Level 3 certified HSMs (shown below).
演算法上，支援 AES、RSA 與 ECC (NIST 的 P-256 與 P-384)：
In addition to symmetric key encryption using AES-256 keys, you can now create various types of asymmetric keys for decryption or signing operations, which means that you can now store your keys used for PKI or code signing in a Google Cloud managed keystore. Specifically, RSA 2048, RSA 3072, RSA 4096, EC P256, and EC P384 keys will be available for signing operations, while RSA 2048, RSA 3072, and RSA 4096 keys will also have the ability to decrypt blocks of data.
us-west1，另外價錢也比軟體服務版本的 Cloud KMS 貴不少：
|Billable item||For keys with protection level SOFTWARE||For keys with protection level HSM|
|Active AES-256 and RSA 2048 key versions||$0.06 per month||$1.00 per month|
|Active RSA 3072, RSA 4096 or Elliptic Curve key versions||$0.06 per month||$2.50 per month for the first 2,000|
$1.00 per month thereafter
|Destroyed key versions||Free||Free|
|Key operations: Cryptographic||$0.03 per 10,000 operations||$0.03 per 10,000 operations for AES-256 and RSA 2048 keys|
$0.15 per 10,000 operations for RSA 3072, RSA 4096, and Elliptic Curve keys
|Key operations: Admin||Free||Free|
AWS CloudHSM 推出了一些新功能：「AWS CloudHSM Update – Cost Effective Hardware Key Management at Cloud Scale for Sensitive & Regulated Workloads」。
其中比較特別的是從以前只支援 Level 2 變成支援 Level 3 了：
More Secure – CloudHSM Classic (the original model) supports the generation and use of keys that comply with FIPS 140-2 Level 2. We’re stepping that up a notch today with support for FIPS 140-2 Level 3, with security mechanisms that are designed to detect and respond to physical attempts to access or modify the HSM.
在維基百科裡面有提到 Level 2 與 Level 3 的要求：
Security Level 2 improves upon the physical security mechanisms of a Security Level 1 cryptographic module by requiring features that show evidence of tampering, including tamper-evident coatings or seals that must be broken to attain physical access to the plaintext cryptographic keys and critical security parameters (CSPs) within the module, or pick-resistant locks on covers or doors to protect against unauthorized physical access.
In addition to the tamper-evident physical security mechanisms required at Security Level 2, Security Level 3 attempts to prevent the intruder from gaining access to CSPs held within the cryptographic module. Physical security mechanisms required at Security Level 3 are intended to have a high probability of detecting and responding to attempts at physical access, use or modification of the cryptographic module. The physical security mechanisms may include the use of strong enclosures and tamper-detection/response circuitry that zeroes all plaintext CSPs when the removable covers/doors of the cryptographic module are opened.
主動式偵測以及銷毀算是 Level 3 比 Level 2 安全的地方。
Pay As You Go – CloudHSM is now offered under a pay-as-you-go model that is simpler and more cost-effective, with no up-front fees.
看到由 Google 主導的 BoringSSL 有計劃將其中一塊申請 FIPS 140-2 的驗證計畫 (BoringCrypto 的部份)：「FIPS 140-2」。
其中 FIPS 140-2 最有名的後門應該是 Dual_EC_DRBG (定義於 NIST SP 800-90A，被 FIPS 140-2 引用)，所以特地講清楚他們選擇哪個演算法：
FIPS 140-2 requires that one of its PRNGs be used (which they call DRBGs). In BoringCrypto, we use CTR-DRBG with AES-256 exclusively and RAND_bytes (the primary interface for the rest of the system to get random data) takes its output from there.
而且還花了不少篇幅解釋 PRNG 的細節。