1. Introduction
Good security practice requires procedural as well as technical measures to provide a
comprehensive security environment for the protection of your cryptographic keys and
data.
This guide provides advice to you on the secure operation of the product. It identifies
procedural measures that should be deployed to support the secure operation of the
nShield. The guidance should be used in the development of your Security Operating
Procedures for your systems incorporating the nShield.
1.1. Who should read this document?
The guide should be used by the following people:
•
Those responsible for the security policy and procedures for your systems
incorporating the nShield
•
Those responsible for commissioning the nShield
•
Those responsible for administering the nShield
•
Those responsible for auditing the nShield.
1.2. Products covered by this manual
The guide covers the following product variants:
•
nShield Edge
•
nShield Solo+
•
nShield Solo XC
•
nShield Connect+
•
nShield Connect XC.
In this manual, guidance given for nShield Solo applies to both the
Solo+ and Solo XC product variants. Similarly, guidance given for
nShield Connect applies to both the Connect+ and Connect XC product
variants.
1.3. Product security objective
The nShield range of products provide protection against technical and physical attacks
on keys used to protect your data in use, in motion and at rest. This provides
confidentiality, integrity and availability* of user data up to FIPS 140-2 Level 3 and
nShield® Security Manual 5 of 90