EasyManuals Logo

Entrust nShield User Manual

Entrust nShield
90 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #77 background image
You are not able to access any keys that you previously used in a deleted Security
World
It is recommended that you reformat any standard nShield cards that were used as
Operator Cards within this Security World before you delete it.
Except for nShield Remote Administration Cards, if you do not reformat
the smart cards used as Operator Cards before you delete your
Security World, you must throw them away because they cannot be
used, erased, or reformatted without the old Security World key.
You must reformat, reuse or destroy the smart cards from a deleted Security World’s
ACS. If these cards are not overwritten or destroyed, then an attacker with these smart
cards, a copy of your data (for example, a weekly backup) and access to any nShield
HSM can access your old keys.
11.5. Module failure
If a module fails and cannot be factory reset then application keys protected by Module
keys or NVRAM keys are potentially vulnerable to attack. In this instance procedural and
technical access controls should be deployed to protect the module until secure
destruction of the module occurs as described in Decommission and Disposal.
11.6. Tamper incident
Physical Security provides guidance on the physical security controls available on the
different nShield platforms and the procedural controls required to maintain those
physical security controls across the product’s lifecycle.
If a tamper incident is observed the guidance in Security Incident and Response should
be followed to manage the incident. The investigation will determine the extent of the
attack. Once an HSM has been confirmed as being tampered its integrity can no longer
be assured and it should be decommissioned and disposed ofsee Decommission and
Disposal for more information.
However, there are two instances where it is possible to recover the module from a
tamper event. These are:
nShield Solo XC tamper events - see nShield Solo XC physical security controls for
more information.
nShield Connect lid is either open or closed - see Tamper event for guidance on how
to investigate the tamper and the criteria required to recover from the tamper. The
occurrence of the event should be recorded and recovery authorized in accordance
with the Customer’s Security Incident and Response Policy.
nShield® Security Manual 77 of 90

Table of Contents

Other manuals for Entrust nShield

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Entrust nShield and is the answer not in the manual?

Entrust nShield Specifications

General IconGeneral
TypeHardware Security Module (HSM)
Cryptographic AlgorithmsAES, RSA, ECC, SHA, DES, 3DES
CertificationFIPS 140-2 Level 3, Common Criteria EAL4+
InterfacesEthernet, USB, PCIe
Form FactorNetwork-attached, PCIe card, USB device
Remote ManagementYes, via web interface or CLI
Tamper ResistanceTamper evident, tamper resistant
Operating Temperature0°C

Related product manuals