Encryption Tools. The public/private key pair used for both encryption and signing are simply keys. They can’t do anything on their own. In order actually encrypt and sign messages/data you will need an encryption tool. Customers that wish to take advantage of SET will need to source a suitable encryption tool compliant with RFC4880 (e.g. PGP Desktop v9.5) which applies the appropriate keys for encryption and decryption. The Client will validate that the file(s) are correctly named and checked .• We will provide you with a username and password to connect to the Government Gateway.• We will ensure that endpoints (your location and our location) are recognised and validated (via mutual TLS Certificates).• We will ensure that the data transmission tunnel is encrypted.• We will provide you with our Public-Keys.• We will validate that all data is signed and encrypted.• We will ensure that the data file names are time stamped to ensure uniqueness.• We will guide you through the initial set-up process with our dedicated “onboarding” team and ensure that you are ready in good time before submission. • A Browser Interface running Internet Explorer v6.0 or higher connected to the internet. • An email facility to receive notifications. • A signing/encryption tool compliant with XXX 0000, such as PGP Desktop v9.5. • Tools to generate certificate signing requests (CSR’s) such as OpenSSL. • A nominated digital Certificate Authority (CA) where you would source your digital certificates. • A Public/Private Key Certificate for data signing • A Public/Private Key Certificate for data encryption. • Be able to install the client certificate for TLS authentication on their client machine(s). • Perimeter firewall(s) should be configured (if needed) to exchange encrypted traffic (HTTPS) with the GGW live environment. • Supply root and interim root certificates to enable Public Key verification.
Appears in 6 contracts
Samples: Framework Agreement, Framework Agreement, Framework Agreement
