This page was not yet optimized for use on mobile devices.
SAFE-Key Device
Certificate details
| Certificate ID | #3186 |
|---|---|
| Status | historical |
| Historical reason | Moved to historical list due to sunsetting |
| Validation dates | 24.05.2018 |
| Standard | FIPS 140-2 |
| Security level | 3 |
| Type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Caveat | When utilizing a Trusted Path as specified in the Security Policy |
| Exceptions |
|
| Description | The SAFE-Key device is a USB-based hardware security token; its primary purpose is two-factor authentication. The device supports three modalities: web-based two-factor authentication (patented), two-factor authentication for protected file decryption and two-factor authentication for digital signature generation. The two factors are something you have (i.e. a specific SAFE-Key device) and something you know (i.e. a password). It also supports one-factor, something you have (i.e. a specific SAFE-Key device) authentication. |
| Version (Hardware) | 1.4 |
| Version (Firmware) | Boot 1.2.0.0, PEM 1.2.0.0, BIOS 1.2.0.0 |
| Vendor | BiObex, LLC http://www.biobex.com |
| Lab | CYGNACOM SOLUTIONS INC |
| Algorithms | |
| References | This certificate's webpage directly references 0 certificates, transitively this expands into 0 certificates. |
Security policy
Extracted keywords
Symmetric Algorithms
AES, AES-256, AES256, HMACAsymmetric Algorithms
RSA-2048, RSA-OAEPHash functions
SHA-256, PBKDFSchemes
Key exchange, Key Exchange, Key agreement, Key AgreementProtocols
SSLRandomness
DRBG, RNGBlock cipher modes
CBCSecurity level
level 3, Level 2, Level 3Standards
FIPS 140-2, FIPS 197, FIPS 186-4, FIPS 198-1, FIPS 180-4, SP 800-38A, SP 800-38F, SP 800-133, SP 800-90A, SP 800-56B, SP 800-132, PKCS #1Automated analysis
Automated inference - use with caution
All attributes shown in this section (e.g., links between certificates, products, vendors, and known CVEs) are generated by automated heuristics and have not been reviewed by humans. These methods can produce false positives or false negatives and should not be treated as definitive without independent verification. This applies equally to the Cross-references section below. If you want to know more about how this data is computed and how reliable it is, see our documentation on automated analysis. If you believe any information here is inaccurate or harmful, please submit feedback.No automatically derived data are available in this section.
Cross-references
No references are available for this certificate.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate data changed.
-
The certificate was first processed.
{
"_type": "sec_certs.sample.fips.FIPSCertificate",
"cert_id": 3186,
"dgst": "2eae7050dee6b674",
"heuristics": {
"_type": "sec_certs.sample.fips.FIPSCertificate.Heuristics",
"algorithms": {
"_type": "Set",
"elements": [
"#1839",
"SHS#4313",
"#2080",
"#4313",
"#5373",
"DRBG#2080",
"HMAC#3561",
"KTS#5373",
"RSA#2874",
"#3561",
"AES#5373",
"CVL#1839",
"#2874"
]
},
"cpe_matches": null,
"direct_transitive_cves": null,
"extracted_versions": {
"_type": "Set",
"elements": [
"1.4",
"1.2.0.0"
]
},
"indirect_transitive_cves": null,
"module_processed_references": {
"_type": "sec_certs.sample.certificate.References",
"directly_referenced_by": null,
"directly_referencing": null,
"indirectly_referenced_by": null,
"indirectly_referencing": null
},
"module_prunned_references": {
"_type": "Set",
"elements": []
},
"policy_processed_references": {
"_type": "sec_certs.sample.certificate.References",
"directly_referenced_by": null,
"directly_referencing": null,
"indirectly_referenced_by": null,
"indirectly_referencing": null
},
"policy_prunned_references": {
"_type": "Set",
"elements": []
},
"related_cves": null,
"verified_cpe_matches": null
},
"pdf_data": {
"_type": "sec_certs.sample.fips.FIPSCertificate.PdfData",
"br1_deviations": 43,
"br1_tables": null,
"is_br1_format": false,
"keywords": {
"asymmetric_crypto": {
"RSA": {
"RSA-2048": 1,
"RSA-OAEP": 1
}
},
"certification_process": {},
"cipher_mode": {
"CBC": {
"CBC": 1
}
},
"cplc_data": {},
"crypto_engine": {},
"crypto_library": {},
"crypto_protocol": {
"TLS": {
"SSL": {
"SSL": 3
}
}
},
"crypto_scheme": {
"KA": {
"Key Agreement": 1,
"Key agreement": 1
},
"KEX": {
"Key Exchange": 5,
"Key exchange": 1
}
},
"device_model": {},
"ecc_curve": {},
"eval_facility": {},
"fips_cert_id": {
"Cert": {
"#1": 1,
"#1839": 2,
"#2080": 1,
"#2874": 1,
"#3561": 1,
"#4313": 1,
"#5373": 2
}
},
"fips_certlike": {
"Certlike": {
"#2080 DRBG": 1,
"#2874 RSA": 1,
"#3561 HMAC": 1,
"#4313 SHS": 1,
"#5373 AES": 2,
"AES-256": 1,
"AES256": 1,
"CVL #1839": 2,
"PKCS #1": 2,
"SHA- 256": 2,
"SHA-256": 17
}
},
"fips_security_level": {
"Level": {
"Level 2": 1,
"Level 3": 2,
"level 3": 1
}
},
"hash_function": {
"PBKDF": {
"PBKDF": 3
},
"SHA": {
"SHA2": {
"SHA-256": 17
}
}
},
"ic_data_group": {},
"javacard_api_const": {},
"javacard_packages": {},
"javacard_version": {},
"os_name": {},
"pq_crypto": {},
"randomness": {
"PRNG": {
"DRBG": 21
},
"RNG": {
"RNG": 1
}
},
"side_channel_analysis": {},
"standard_id": {
"FIPS": {
"FIPS 140-2": 6,
"FIPS 180-4": 1,
"FIPS 186-4": 2,
"FIPS 197": 2,
"FIPS 198-1": 1
},
"NIST": {
"SP 800-132": 1,
"SP 800-133": 1,
"SP 800-38A": 1,
"SP 800-38F": 2,
"SP 800-56B": 6,
"SP 800-90A": 1
},
"PKCS": {
"PKCS #1": 1
}
},
"symmetric_crypto": {
"AES_competition": {
"AES": {
"AES": 15,
"AES-256": 1,
"AES256": 1
}
},
"constructions": {
"MAC": {
"HMAC": 2
}
}
},
"tee_name": {},
"tls_cipher_suite": {},
"vendor": {},
"vulnerability": {}
},
"module_algorithms": {
"_type": "Set",
"elements": [
"SHS#4313",
"DRBG#2080",
"HMAC#3561",
"KTS#5373",
"RSA#2874",
"AES#5373",
"CVL#1839"
]
},
"policy_algorithms": {
"_type": "Set",
"elements": [
"#1839",
"#2080",
"#4313",
"#5373",
"#3561",
"#2874"
]
},
"policy_metadata": {
"/Author": "ajoyce",
"/CreationDate": "D:20180515150328-04\u002700\u0027",
"/Creator": "Microsoft\u00ae Word 2010",
"/ModDate": "D:20180515150328-04\u002700\u0027",
"/Producer": "Microsoft\u00ae Word 2010",
"pdf_file_size_bytes": 817257,
"pdf_hyperlinks": {
"_type": "Set",
"elements": [
"http://csrc.nist.gov/groups/STM/cavp/documents/dss/rsanewval.html",
"http://csrc.nist.gov/groups/STM/cavp/documents/shs/shaval.html",
"http://csrc.nist.gov/groups/STM/cavp/documents/drbg/drbgnewval.html",
"http://csrc.nist.gov/groups/STM/cavp/documents/components/componentnewval.html",
"http://csrc.nist.gov/groups/STM/cavp/documents/mac/hmacval.html",
"http://csrc.nist.gov/groups/STM/cavp/documents/aes/aesval.html"
]
},
"pdf_is_encrypted": false,
"pdf_number_of_pages": 29
}
},
"state": {
"_type": "sec_certs.sample.fips.InternalState",
"module": {
"_type": "sec_certs.sample.document_state.DocumentState",
"convert_ok": true,
"download_ok": true,
"extract_ok": true,
"json_hash": null,
"source_hash": null,
"txt_hash": null
},
"policy": {
"_type": "sec_certs.sample.document_state.DocumentState",
"convert_ok": true,
"download_ok": true,
"extract_ok": true,
"json_hash": "5c15801ce1ed3e211d52e4f0d0af67e0f6abf431b379c398935a86b0642e5bcb",
"source_hash": "ab34a69781820be0430d72066c0513c3386f229bf935b6188a704b46335443bc",
"txt_hash": "f6de70965a04b3a8f98bd73affd17378ea754afbab387ae174940a16d5d97893"
}
},
"web_data": {
"_type": "sec_certs.sample.fips.FIPSCertificate.WebData",
"caveat": "When utilizing a Trusted Path as specified in the Security Policy",
"certificate_pdf_url": "https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/May2018consolidated.pdf",
"date_sunset": null,
"description": "The SAFE-Key device is a USB-based hardware security token; its primary purpose is two-factor authentication. The device supports three modalities: web-based two-factor authentication (patented), two-factor authentication for protected file decryption and two-factor authentication for digital signature generation. The two factors are something you have (i.e. a specific SAFE-Key device) and something you know (i.e. a password). It also supports one-factor, something you have (i.e. a specific SAFE-Key device) authentication.",
"embodiment": "Multi-Chip Stand Alone",
"exceptions": [
"Mitigation of Other Attacks: N/A"
],
"fw_versions": "Boot 1.2.0.0, PEM 1.2.0.0, BIOS 1.2.0.0",
"historical_reason": "Moved to historical list due to sunsetting",
"hw_versions": "1.4",
"level": 3,
"mentioned_certs": {},
"module_name": "SAFE-Key Device",
"module_type": "Hardware",
"revoked_link": null,
"revoked_reason": null,
"standard": "FIPS 140-2",
"status": "historical",
"sw_versions": null,
"tested_conf": null,
"validation_history": [
{
"_type": "sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry",
"date": "2018-05-24",
"lab": "CYGNACOM SOLUTIONS INC",
"validation_type": "Initial"
}
],
"vendor": "BiObex, LLC",
"vendor_url": "http://www.biobex.com"
}
}