808bits

Apple iOS CoreCrypto Module, v3.0

FIPS 140-2 certificate #1963 · Apple Inc. · 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. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number1963
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-chip standalone
VendorApple Inc. · website
Software versions3.0
Hardware versionsA4 and A5

Module description

The Apple iOS CoreCrypto Module is a software cryptographic module running on a multi-chip standalone mobile device and provides services intended to protect data in transit and at rest.

Approved algorithms

AlgorithmCAVP certificate
AES2072, 2073, 2074, 2075, 2076, 2077, 2100, 2102
DRBG209, 210, 223, 225
ECDSA309, 311
HMAC1257, 1258, 1275, 1277
PBKDFvendor affirmed
RSA1076, 1077
SHS1805, 1806, 1824, 1826
Triple-DES1336, 1338

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (non-compliant); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 160 bits of encryption strength); ECDSA (Curves P-192, P-224 and P-521; non-compliant); DES; MD2; MD4; MD5; RIPEMD; CAST5; Blowfish; BitGen1; BitGen2; BitGen3; RC2; RC4; OMAC (non-compliant)

Tested configurations

  • iOS 6.0 running on an iPad (single-user mode)
  • iOS 6.0 running on an iPhone4
  • iOS 6.0 running on an iPhone4S

Validation history

DateTypeLab
2013-06-14Initialatsec information security corporation

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: 2013-06-14

Source documents