OSS® for customer dataData protection and storage
Held off the network until you need it.
Customer records, identity documents, contracts, payment evidence and support histories. Keep the working copies where your teams need them and move the archive that does not need to stay online into physically disconnected storage.
Offline Secure Storage®OSS® for customer data- Protects
- The records you could not recreate
- Hardware
- Dedicated, except LUV
- When closed
- No standing network path
- Access
- Authorised, out of band, time-bound
- Hosted in
- Firevault Bunkers: Europe live, US and Middle East next
A simple governance question
If your systems were breached tonight, how much customer data would be reachable?
Most organisations keep every customer record permanently connected. Very little of it needs to be. The problem is not only attackers. It is how much customer data is reachable at all times.
- Encryption does not reduce reach
Encrypted records that remain online are still discoverable, still copyable and still governed by keys held in the same estate.
- A path that does not exist cannot be used
When the vault is disconnected there is no share, no console and no credential for an intruder to abuse.
- Minimisation is a physical act
Data protection law asks you to limit exposure. Moving retained records offline does that in practice rather than on paper.
- Evidence comes from state, not policy
A regulator can be shown where the data lives, when it was reachable and who retrieved it.
- An account is compromised.
Scenario 1
- Ransomware reaches the archive.
Scenario 2
- A supplier is breached.
Scenario 3
- The regulator asks a question.
Scenario 4
See the difference
The same stolen login. Two places to keep your records.
Choose a state to see what an intruder can reach.
Contracts, accounts and recovery copies share one connected estate. One stolen login, one supplier or one mistake reaches all of it.
The records you could not recreate sit on dedicated hardware with no standing network path. Access begins outside the normal network, on an authorised out-of-band request, for a time-bound session.
The principle
Changing the connection state changes what any breach can expose.
Most organisations keep every customer record permanently connected because that is how systems are built, not because the business needs it. If retained customer data sits physically outside the connected estate, a compromised credential has no route to it.
- Your important data
- Your network
- Security tools
- Still reachable
- Stolen, locked or changed
What businesses protect
The records customers trust you with.
First-pass inventory
- Customer identity files
- Signed agreements
- Payment evidence
- Case histories
- Closed accounts
- Consent records
First-pass inventory
Decide what has to stay reachable.
The aim is not to take the business offline. It is to identify the customer data that is most damaging to expose and least often used, then change its state.
- Identity
- Contracts
- Payments
- Support
- Archive
- Evidence
- Verification documents
- Onboarding evidence
- Address records
What belongs offline
Connected for the work. Offline for the archive.
Everyday and connected
- Active customer accounts
- Live support cases
- Current billing and orders
- Working documents in progress
- Everyday collaboration
- Closed and dormant accounts
- Identity and verification archives
- Retained payment evidence
- Historic case records
Who can reach it
The right person can reach the right record.
The verified owner controls everyday access. Selected files can be shared without exposing the whole vault. Every retrieval is recorded.
- Verified owner
- Authorised colleague
- Auditor or regulator
- Succession route
- Access is linked to a verified individual rather than a shared company account.
One vault per user
- Release the specific record an auditor or regulator needs, for a defined window.
Share a file, not the vault
- Every retrieval is recorded, so handling can be demonstrated later.
Recorded retrieval
Use cases
This is not only about the worst day.
Six everyday reasons to give retained customer data a different state.
- Prove where customer data lives.
Location
- Recover from copies kept off the network.
Recovery
- Retire legacy systems safely.
Legacy
- Reduce what a third party can hold.
Third parties
- Answer requests without exposure.
Requests
- Show a control an insurer understands.
Insurance
The products
Offline Secure Storage®, then the product that fits the volume.
Offline Secure Storage holds selected customer records on dedicated hardware. What changes between products is capacity and how access opens.
- Physically offline between sessions.
Vault
- Ask from your registered phone and confirm it is you.
Open a session
- Work with your files for up to 120 minutes.
File Manager
- Opens on a day you choose each week, for 12 hours.
LUV
- From 20TB, growing in 20TB steps.
Storage
Why Firevault
Physics, not promises.
Every Offline Secure Storage® instance is built on the same four physical principles.
- Physical storage
Offline Secure Storage instances are held on dedicated physical hard drives, not in S3 cloud buckets, shared storage pools or multi-tenant infrastructure. Your selected data is assigned to real hardware, with dedicated RAID 1 drives providing resilience.
- Physical ownership
Each Offline Secure Storage instance is allocated to a specific customer, with dedicated physical capacity and clearly defined ownership. Your data is not pooled, commingled or held within a shared storage estate.
- Physical control
Access begins outside the normal network path. An authorised out-of-band command, such as SMS, controls the physical Layer 1 connection to your #OSS instance. When access is not required, that network path is physically disconnected.
- Physical security
Your #OSS hardware is housed in carefully selected, professionally managed data centres with layered physical security, resilient power and environmental controls. Access is tightly controlled using three-factor authentication, including biometric identification, supported by 24/7 monitoring, restricted access zones and a complete audit trail.
Evidence
What the regulator and the NCSC expect.
Offline Secure Storage can help support these obligations. It does not make you compliant on its own.
- Appropriate measures, judged by risk
ICO
- Security appropriate to the risk
UK GDPR Article 32
- A copy out of an attacker’s reach
NCSC
Your next step
Protect the records that matter most.
Start with the records you could not recreate. Keep everything else where it works best.