How it works

The short version

A lake of security data that no one can rewrite

We continuously collect open threat intelligence and security telemetry, normalize it to a common schema (OCSF), and store it as Apache Iceberg tables. The tables live on Myota cyberstorage, so every record is encrypted, split into fragments, and spread across multiple clouds the instant it lands. The result: a history you can query as of any past date, that an attacker cannot encrypt, delete, or alter, and that rewinds to a clean state in an instant.

The architecture

One lake, two surfaces

Two data sources flow into the same lake. The protected system of record lives on Myota; a read-only mirror serves the public site, because the Myota storage layer authenticates every request and never hands out whole objects.

Open threat intel and real sandbox attack telemetry normalize to OCSF, land in Iceberg on Myota, and surface via a public mirror plus a bring-your-own-logs example.

• Open threat intel — CVE, CISA KEV, GitHub Advisories, OSV, Certificate Transparency, and openly licensed feeds. This powers the public Time Machine.
• Your own logs — the same lake, pointed at security and audit logs, with a live attack-and-rewind demonstration.
• Apache Iceberg — immutable snapshots give the lake time travel: query it as of any date, diff two dates, trace an indicator across its whole life.

How Myota protects it

Shard and Spread™

Myota makes security intrinsic to the data itself, at the moment it is written. This is what makes the archive trustworthy rather than just convenient.

Encrypt at write time, secret-share into fragments, spread across clouds. Reconstruct from a subset, attacker gets meaningless fragments, instant rewind to any point.

• Encrypted at write time. Every record is encrypted the instant it lands. Security is part of the data, not a layer added later.
• Secret-shared and spread. The data, its metadata, and its keys are split into cryptographic shards and spread across multiple clouds. No single location holds anything whole.
• Ransom immunity. An attacker who reaches a storage location gets computationally meaningless fragments. There is nothing whole to encrypt or hold hostage.
• Resiliency without redundancy. The lake reconstructs from a subset of its shards, even if a location is lost, without keeping full duplicate copies.
• Instant rewind. Every write is a new shard set, so rewinding to an earlier point in time is a pointer move, not a slow restore.

Why it matters for your logs

The record an attacker tries to erase

The first thing many intruders do is delete or encrypt the logs to cover their tracks, and compliance regimes require those logs to stay tamper-evident. When the lake lives on Myota, a tamper attempt fails: the logs are immutable, and the lake rewinds to the moment before the attack while still showing exactly what happened.

Trust the record, not the hope that no one touched it

When an adversary tampers with the storage, the archive rewinds itself to the moment before. That is ransom immunity and instant rewind, powered by Myota Shard and Spread™.