Published cases from the last few years. In each one, what was connected shaped what happened next.
Waymo and Anthony Levandowski
2016 to 2020
The path
A senior engineer with legitimate access downloaded about 14,000 confidential files before leaving.
What followed
He pleaded guilty to theft of trade secrets in 2020 and was sentenced to 18 months in prison.
The people with legitimate access are part of the risk.
Nvidia
February 2022
The path
A criminal group got into the company’s network.
What followed
Employee credentials and proprietary information, including source code, were taken and leaked online.
Source code is a target in its own right.
These cases show how connected work can be taken. They are not claims about what any single control would have prevented.
What it is
Your team needs working copies online. Your master copies do not have to stay there.
If only your master copies had no network path to them while nobody was using them.
Welcome to Offline Secure Storage®.
A new approach to data storage. Your data sits on your own drives, physically disconnected, until a named person opens it from their registered phone.
Controlled ConnectivityPhysically disconnected at Layer 1. No IP path exists until a session is authorised
Secured Offline AccessRequested from a registered phone, out of band, then sign-in and MFA
Secured Offline DataYour own dedicated drives, single-tenant, in a Firevault Bunker
What it gives you
Collaboration is not custody. Keep the definitive work separately.
Active repositories, project tools and everyday collaboration stay as they are. OSS keeps the definitive master physically offline, with named responsibility.
Choose a situation to see the difference.
Choose a situation
SituationA departing employee copies source and builds from the shared repository.
TodayOne place
LeaverValid access
RepositoryShared
Source and buildsCopied
Nobody can say which version is authoritative, or prove when it existed.
With OSSPhysically offline
Your working systemsStay connected
Physical disconnect
Retained masterData offline
Registered phoneSeparate, non-IP connection control
The dated master sits on a different access path. It won’t stop copying from the live repository, but you keep an authoritative record.
Offline
The retained data is physically disconnected. Your live systems stay connected and still need their own protection.
Illustrated Vault access cycle, not a live session. Only data retained in OSS is protected while physically disconnected.
A separate retained master.
Selected source, designs and research remain physically offline between authorised sessions.
Keep working as you do today.
Active repositories, project tools and everyday collaboration remain in place.
Named responsibility.
Agree custody, retention and access, and keep the evidence behind your ownership claim.
Who it’s for
Picture the moment your work becomes someone else’s opportunity.
Three illustrative situations. Working files stay online; selected master copies are held separately.
Switch between without and with OSS, or let each one turn by itself.
Meet Emily.
Engineering lead
Tuesday · 02:14
“A departing employee has copied work from the shared repository.”
The team needs to establish which source and build records are authoritative, from a repository the leaver could reach.
The working repository and the retained master have different access paths.
Protect the asset. Control the path.Offline Secure Storage® protects the work itself. Control by Firevault decides which network paths into your critical systems exist, and when.
No software to install and nothing to migrate. Your Vault sits alongside everything you already have.
01Order
02Request
03Open
04Offline
Identity checked
You
Your Vault
Choose your Vault.
Pick a size and order online. We check your identity and set your Vault up in a Firevault Bunker.
Requested from your phone
Registered phone
Request out of band
Your Vault
Open it from your phone.
Ask for access from your registered phone, then sign in with MFA. The request does not travel over your network.
Physical access granted
Your browser
Your Vault
Add or find files.
Work in your browser for up to 120 minutes. Share one file at a time. Every session is logged.
Offline again
Your network
Your Vault
It goes offline again.
When you finish, the connection is removed. Until next time, there is no path to it.
Worth knowing. A Vault keeps a copy offline, but it cannot check what you put in it. Keep your phone and sign-in safe, and check your files now and then.
See it for yourself
One Vault. Three states.
Step through a closed Vault, an open session and the moment it disconnects again.
Registered phoneSeparate request path, out of band
The normal state
Closed
Closed is the normal state. There is nothing on the network to find, search or sign in to.
Requested
No session requested.
Reported by the Vault
Vault physically disconnected at Layer 1.
On record
Last session closed Tue 16:42 by the engineering lead.
Concept illustration. The request path, the Vault’s reported state and the session record are shown separately because they are not the same thing.
Questions worth asking
Questions worth asking.
Want your project lead or legal adviser to see how retained masters are accessed? Book a demo.
No. Keep everything you have. A Vault adds one retained master that sits offline, so it doesn’t depend on any of it holding.
No. Repositories and project tools stay as they are. Only the holder learns one short routine: approve from their phone, sign in, add or find files.
No. A dated master and a log of every session support your evidence. Legal ownership depends on your agreements, registrations and professional advice.
No. Each Vault belongs to one named person. For larger archives, Storage gives several named people their own access.
Open the Vault, pick the file and send a link that expires, with a password sent separately. You can withdraw it at any time.
In a Firevault Bunker, with three independent entry checks, including biometrics, and 24/7 monitoring.