CERBERUS

Vulnerabilities Threats Countermeasures

Document Security

FIPS PUB 140-1
DOD 5220.22-M
NCSC TG-25
FIPS PUB 81
FIPS PUB 180-1
DOD 5200.28-STD

INFOSEC
Cryptosystems
Passphrases
Windows® Leaks
System Settings

QUESTIONS?

NOTE: Our individually licensed software cryptosystems incorporate high-grade ciphers (specifically, CBC-mode triple-DES with 168-bit keys). They do not incorporate either overt Law Enforcement Access Fields or covert channels to leak keying information. They are thus considered "encryption items" - Category EI in the Commerce Control List, 15 CFR 774, subject to the Export Administration Act, 50 USC 2401. The penalty for their export from the United States without a BXA license, except to Canada is a fine, not to exceed $1,000,000 and/or a prison term, not to exceed 10 years, for each offense.

DEMONSTRATOR PACKAGES

These demonstrators have been compiled without the private masterkey generating function necessary for security. They include all the other cryptographic functions of the full products, but documents they encrypt can be unconditionally decrypted by anyone with a demonstrator. Their zeroized masterkeys let you examine the "look and feel" of their user interfaces and test how fast the encryption functions will execute on your system, while letting us comply with US export controls.

The demonstrators are available in self-contained installer/uninstallers that will not meddle with your system settings. Our products do, of course, automatically analyze your system configuration for potential security leaks, and will warn you of advisable modifications that they can perform for you, if you choose to authorize them to do so. Since we believe that these features uniquely differentiate our products, the demonstrators include all such capabilities for your evaluation.

These demonstrators are designed to cleanly uninstall, while any files encrypted with them can easily be made secure by the Licensed version's automatic re-encryption of all encryption keys with the private masterkey generated from your passphrase.

NOTE: The uninstall requirements of WinNT, Win4x and those for Win3x systems differ substantially. We wanted to ensure your ability to completely free your system of our products, if you concluded that they're not for you. Consequently, we've provided separate installer/uninstaller packages for Win95/98/NT and Win3.x systems, even though 32-bit demonstrators which will run on either Win32 or Win3.x-plus-Win32s platforms. These InstallShield® installer packages also include system DLLs appropriate to each platform.

PLATFORM VERSIONS

Our products' functions are strictly limited to ANSI C and single-threaded Win32 API function calls to statically-linked libraries. They include neither virtual device drivers operating between layers of the operating system (like disk encryptors) nor Visual whatever Dynamically Linked Libraries (whose absence of leaks we cannot verify).

This to ensure multiplatform cryptographic compatibility between Win 3x (Windows 3.1, 3.11 and WFW3.11), Win 4x (Windows 95, Windows 98, Windows 98SE and Windows ME) and NT (NT 4.0, NT 5.0/Windows2K and NT 5.1/WindowsXP) systems.

As a user convenience, our products include system reconfiguration utilities that replace the need for the user to individually change various Windows system settings to more secure configurations, and built-in warning functions to alert the user to the need for such reconfigurations. Unlike the cryptographic functions, however, these utility functions are platform-dependent and automatically respond differently on each.

NOTE: Windows 4.9/Windows ME will not permit the installation of 16-bit TSRs, such as Microsoft's own RAM disk from Windows 4.0/Windows 95 and Windows 4.1/Windows 98. As our built-in utility for optionally configuring TEMP space as a RAM drive on non-NT platforms relies on Microsoft's RAMDRIVE.SYS, that option will be unavailable under ME. (There are third party 32-bit RAM drives that some of our users are using instead, but our products' configuration utilities don't automate their set-up.)

Our 32-bit products will not only run under Win4x and NT, but even under Windows 3.1 or 3.11, or Windows for Workgroups 3.11 - as long as you have installed Microsoft's free Win32s upgrade. (Do not attempt to install Win32s on a Win4x or NT system.)

Please be sure to have Win32s (version 1.3) installed on any of these Win3x systems before installing 32-bit demonstrators. Win32s is available for free download from the Microsoft Software Library as pw1118.exe ( 2.5 MB ).

We believe that all customers should, therefore, be able to use our 32-bit products. However, we are making the slower 16-bit versions available on the chance that your individual circumstances may not permit you to install Win32s. We have, of course, ensured that documents and inventory files encrypted with 16-bit versions can be decrypted by the corresponding 32-bit versions, and vice versa.

NOTE: DOD 5220.22-M Sanitizing is not possible via 16-bit software under Win4x, unless you disable your system's write-behind caching. (It cannot reliably overwrite files through Win95's version of VCACHE, which just deletes them.) We don't think any product should require you to cripple basic system functions that other products may need, and we refuse to sell encryption products that Windows® data leaks will bypass. For that reason, the 16-bit versions of our products are programmed to refuse to run on Win4x systems. Therefore, we only provide 16-bit demonstrators in 16-bit installer/uninstaller packages.

DOCUMENT SECURITY MANAGER™

If you have Win4.0 (Windows 95), Win4.1 (Windows 98), NT4/SP3+ or NT5 (Windows 2000/XP) please download docmgr32.exe, a 32-bit installer for the 32-bit demoversion Document Security Manager™ v2.9.22.32 (1,101,166 bytes).

If you have Windows 3.1 or 3.11, or Windows for Workgroups 3.11, please download docmgr3x.exe, a 16-bit installer/uninstaller containing the 32-bit demonstrator for Document Security Manager™ v2.9.22.32 ( 987,937 bytes).