808bits

XSOC Cryptosystem

FIPS 140-2 certificate #4038 · XSOC Corp · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3080

Certificate

Certificate number4038
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorXSOC Corp · website
Software versions3.0.1

Module description

XSOC Cryptosystem ™ is a standards-based "Drop-in Compliance" cryptographic engine that enables the protection of data requiring absolute compliance with federal standards. The module delivers core cryptographic Suite-B functions to the layered architecture of XSOC's own proprietary security workflow and overall cryptosystem. Data that is enciphered or transformed by XSOC passes through XSOC Cryptosystem during every cycle of operation. XSOC Cryptosystem enables flexible modes of operation for encryption.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4702
CKGvendor affirmed
CVL1342, 1343, 1344, 1345
DRBG1600
DSA1244
ECDSA1160
HMAC3114
KAS130
KASvendor affirmed
KBKDF145
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSA2562
SHA-324
SHS3849
Triple-DES2494

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • CentOS 6 and OpenJDK 1.7 running on HP ProLiant DL360 G7 Server using an Intel Xeon X5670 (single-user mode)

Validation history

DateTypeLab
2021-09-27InitialAEGISOLVE, 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: 2021-09-27

Source documents