WORM media types

I don't know of any other write-once media with storage in the 100GB range.

I can see two possible approaches to address your needs:

• Build a secure system that provides append-only access to dedicated storage. You could build a custom, single-purpose system that has a collection of computers (running dedicated software) and dedicated storage (e.g., dedicated hard disks), which exists only for the purpose of providing high-capacity write-once storage. The software running on those machines could be entrusted with enforcing the append-only/write-once property. If you keep the software on those machines simple enough, and protect the system from attack, then you may be able to get some assurance that there is no way for an attacker to modify data that has already been written.

• Use secure logging functionality. You may be able to store your bulk data on standard high-capacity media (e.g., hard disks, tape), and then keep a secure audit log of the data on write-once low-capacity media. If the audit log contains a hash of each large file written to the standard media, then this provides a way to detect (but not prevent) any modification/deletion/overwrite of the data stored on the high-capacity media. There are many sources for low-capacity write-once media, from line printers, to CD-R/DVD-R, to Sandisk's dedicated SD card with 1GB of write-once storage. See my answer elsewhere for more details.

I would also like to direct you to the following research paper, which I believe may be highly relevant to your needs:

• Radu Sion, "Strong WORM", International Conference on Distributed Computing Systems (ICDCS 2008).

Depending on your needs, you could use a standard SATA hard drive with a hardware write-blocker, e.g. bridge devices intended for use in computer forensics. For example, this device has three drive connections, each with a read-only/read-write switch. It's not strictly "write once", and magnetic media does suffer from the potential for damage. It won't work as a destination for streaming log messages, but it would work for applications where you plan on writing, say, a secure OS image and then forcing it to read-only so that rootkits can't persist across reboots. You can use the same scheme and avoid magnetic media reliability problems with a SATA SSD. Either approach would provide very high capacity. This strategy doesn't protect you from modification by someone with physical access (they can just flip the switch), but it does protect you from modification through online access.