QuantGuard™
Menu

The file, as it opens

system,owner,location,purpose,algorithm,key_storage,data_protected,confidential_years,upgrade_path
Online banking,Digital channels,www.example.com,key agreement,X25519,load balancer,customer sessions,10,configuration
Payments API,Payments,api.example.com,signature,RSA 2048,HSM,payment instructions,7,vendor
Mail gateway,IT operations,mail.example.com,key agreement,ECDHE P-256,file,client email,7,upgrade
Archive,Records,archive.example.internal,encryption,AES-256,cloud key store,identity files,10,none needed

Sample rows use example.com. Replace them with your own systems.

What each column asks

The last two decide your priorities.

system
The business system or service
owner
Who answers for it
location
Host name, account or code repository
purpose
Key agreement, signature, encryption or hashing
algorithm
As configured, with its key size
key_storage
HSM, cloud key store, file or code
data_protected
What the key protects
confidential_years
How long that data must stay secret
upgrade_path
Configuration, upgrade or vendor

Rather we filled it in?

The QuantGuard™ inventory builds this list from your code, servers and cloud.

Book a consultation

Every QuantGuard™ engagement is delivered by Dirhami Investment Technology Ltd.