808bits

nShield Solo XC F3 & nShield Solo XC F3 for nShield Connect XC and for nShield HSMi

FIPS 140-2 certificate #3766 · Entrust · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and initialized to Overall Level 2 per Security Policy. The protocol TLS shall not be used when operated in FIPS mode

Certificate

Certificate number3766
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorEntrust · website
Hardware versionsNC4035E-000 and NC4335N-000, Build Standard A
Firmware versions12.50.11

Module description

The nShield XC F3 PCIe card, sold as nShield XC F3 PCIe server-embedded hardware security modules (HSMs) and also used in the nShield Connect XC and nShield HSMi network appliance HSMs, are multi-tasking HSMs optimized for symmetric and asymmetric operations on protected keys. The nShield modules are FIPS 140-2 Level 2 embedded devices for applications including but not limited to PKI, SSL/TLS, Secure Manufacturing, Data Protection, Key Management and Provisioning.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Physical Security: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AESC1105
CKGvendor affirmed
CVLC1105
DRBGC1105
DSAC1105
ECDSA805, C1105
HMACC1105
KBKDFC1105
KTS
KTSvendor affirmed
RSAC1105
SHS3130, C1105
Triple-DESC1105

Allowed algorithms

Diffie-Hellman (CVL Cert. #C1105, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C1105, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC MQV (CVL Cert. #C1105, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2020-12-10InitialLightship Security, Inc.
2022-02-25UpdateLightship Security, Inc.

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2020-12-10, 2022-02-25

Source documents