Secuware Security Framework - Crypt4000 Module
Caveat: When obtained, built, installed, protected and initialized as assumed by the Crypto Officer role and specified in Section 8.2 of the provided Security Policy. Section 8.2 of the provided Security Policy specifies the complete set of source files of this module. There shall be no additions, deletions or alterations of this set as used during module build. All source files shall be obtained via secure FTP. Any deviation from the specified verification, protection, installation and initialization procedures will result in a FIPS 140-2 non-compliant module.
Certificate
| Certificate number | 1079 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Secuware · website |
| Software versions | 4.0 |
Module description
The SCM is a function library implementing crypto services which is delivered to the final user as a SW cryptographic object module, running on Windows operating system in a General Purpose Computer. The logical cryptographic boundary for the SCM is the discrete block of object code containing the machine instructions and data generated from the SCM FIPS source, which will be allocated continuously in a main memory address space, as used by the calling application.
Approved algorithms
Tested configurations
- Microsoft Windows XP SP2 (single user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2008-12-24 | Initial | atsec information security corporation |
| 2009-01-26 | Update |
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: 2008-12-24, 2009-01-26