Trustity Steel

Why Trustity Steel?

• Air-gapped by design. The kiosk does not use the network to cleanse a file. The microVM has no network interface. It receives the file over a local channel, rebuilds it, and is destroyed.
• The file stays the file. A PNG comes out as a PNG. A Python script comes out as a Python script. Office files with macros are rebuilt as the modern Office format without the macros. Nothing is converted to PDF just to be “safe.”
• Programs stay on the source drive. Executables are listed and marked not copied. There is no way to add them to the clean set. The originals remain on the USB that came in.
• A different drive on the way out. After the source USB is removed, the clean set goes to one place: a different USB, a folder on a network drive that was prepared on the appliance, or a disc when one is in the burner. The operator types the folder name. The share opens with the service account already on the machine. A rewritable disc that already holds data is erased before the write. The same physical USB is refused.
• A scan report, not a verdict from an antivirus engine. The report records what was kept and what was left out of each rebuilt file. It can be written next to the clean files as trustity-scan.txt.

Trustity Steel V 1.0. The on-screen badge reads Trustity Core because this is the Core air-gapped CDR mode. Operator documentation is at trustity.co/kb/steel.