Secure communications framework
Secure communications is more than encrypted calls. The files and recordings that travel with those calls need the same discipline. This page shows how vFileLock's controls fit together as one framework, designed for defence, intelligence and government work, and which settings to use at each level.
vFileLock's levels and controls are aligned with South Africa's Minimum Information Security Standards. vFileLock is not certified or accredited under any scheme. Where you handle state-classified information, your own security authority decides which systems may carry it.
Six layers, one framework
Each layer answers one question. Together they decide who may see a file, and prove who did.
The ledger
Approvals
Need-to-know
Classification
Identity and devices
Planned approved-device keys.
Sovereign hosting
Planned inside your own network, with no call home.
Read from the foundation up: each layer rests on the one below it.
Settings for each level
These are vFileLock's default rules, with the choices that suit each level. The uses are design examples. Your own classification guide decides what belongs at which level.
| Level | Use it for | Who may receive it | Viewing and device | Opens and time | Approval | Choose |
|---|---|---|---|---|---|---|
| Public | Notices and documents cleared for release | Anyone named | The owner's choice | Up to 50 opens, or unlimited. Up to 30 days | None | The level alone is enough |
| Internal | Routine internal documents | Your own people, or a named outside person with a code | View only by default, with a watermark | Up to 50 opens, or unlimited. Up to 30 days | None | The Standard preset |
| Restricted | Drafts, and procurement documents shared with industry | Inside: people cleared for Restricted. Outside: a named person with a code | View only for outside recipients. Terms first. Watermark | Up to 50 opens. Up to 14 days | An approver, for outside recipients | The Standard preset, and an e-mail at every open |
| Confidential | Tender evaluations, personnel matters and case files | Cleared, named people. Outside only by exception | View only, no download. Terms first. Watermark. Forwarding blocked | Up to 5 opens. Up to 7 days | Inside: an approver. Outside: the Information Officer | The Confidential preset for the most sensitive files: 24 hours, open once, burn after reading |
| Secret | Operational material, and source or witness material | Cleared, named people inside your organisation only | View only, no download. Audio and video stream only. First device only | Up to 3 opens. Up to 72 hours | The Information Officer | The Secret preset: open once, burn after reading |
| Top Secret | The few files that could neutralise your work | Cleared, named people inside your organisation only | As Secret | Open once. Up to 24 hours. Burn after reading | Two different approvers, both cleared, neither the owner | A small, named pool of approvers. Check the chain after each share |
See the full table on Classification.
Need-to-know
- Files go to named people, one person per share. Each person gets their own link and their own key halves.
- Clearances for Restricted, Confidential, Secret and Top Secret come from your own sign-in groups. A higher clearance covers the lower ones.
- vFileLock checks the clearance when a person locks, opens or approves. A person who is not the named recipient is refused, and the attempt is recorded with their name.
- Secret and Top Secret stay inside your organisation.
- Every share that needs approval carries a purpose: why this person needs the file.
- Even the record follows need-to-know. At Top Secret, only the owner, the Information Officer and the two approvers may read it.
- Planned the recipient's clearance is checked already when the share is made.
- Planned in classified Repo folders, people without the clearance see no file names, no labels and not even a count.
Approvals and two-person control
- Restricted to an outside person: an approver. Confidential: an approver inside, the Information Officer outside. Secret: the Information Officer. Top Secret: two different approvers.
- Approvers hold a clearance at least equal to the level. Nobody approves their own share.
- A request nobody answers ends after 72 hours, and its key half is destroyed.
- Raising a level is immediate, and ends any live share that breaks the new level. Lowering a level needs approval, and two approvers when lowering from Top Secret.
Devices and keys
- Files are locked on the device, before they travel. A lost device shows nothing readable, and a share can be revoked at once.
- Personal keys are made on your own device. The private key never leaves it. A Backup card holds your key, itself locked with your passphrase.
- First device only is forced at Secret and Top Secret. The file opens on the first device and on no other. Clearing the browser counts as a new device.
- The device is recorded on every attempt, and a new device raises an alert to the owner.
- Planned approved-device keys. Each approved device makes its own key pair, and the private key stays on that device. Files are locked to all of a person's approved devices. A new device is approved from one that is already trusted.
The ledger as evidence
- Every lock, share, approval, open and refusal is recorded, with the person, the time, the IP address and the device.
- Each file has its own chain. Changing or deleting an entry breaks it, and the newest entry of every chain is lodged in POPIA Bridge.
- Breach attempts are recorded as such: the wrong clearance, a share the rules do not allow, a person who is not the named recipient, a second device, a forwarded link, a level lowered without approval.
- Reading the record is recorded too. Who looked at the evidence is evidence.
- The record exports as CSV and JSON with the chain proof, so another tool can check it without vFileLock.
More on POPIA Bridge.
Sovereign hosting and key custody
- vFileLock runs in South Africa, on VOIMAR's own network. People sign in through Voimar ID, VOIMAR's own sign-in service.
- VOIMAR's servers hold locked files only. They have no code that could decrypt one.
- With the signed waiver, VOIMAR cannot open your files at all.
- Coming optional key escrow and recovery under dual control, for organisations that want a way back when keys are lost.
- Planned the same software inside your own network. No call home, no telemetry and no outside scripts. It talks only to your own sign-in, mail, record and vault, and with escrow your recovery key stays in your own vault.
More on Deployment and Key escrow and recovery.
With vKOM-SECURE and vKONNECTOR
vKOM-SECURE is VOIMAR's secure communications platform for government, defence and enterprise, and vKONNECTOR is its app. vFileLock
comes with both. Calls and chat travel on the platform. Files travel as vFileLock shares, under the levels on this page.
Coming call recordings on the same levels and the same record. See vFileLock with vKOM and UCC.
Tuning the framework
A framework is only as good as its settings. These are the choices that matter most.
- Map your own markings to the six levels, and write down what belongs at each.
Keep clearance groups small
Put people in the group for the level they need, and review the groups when people move.- Name your Information Officer, your approvers and a second approver for Top Secret before the first file is locked.
- Set the floor for the switch "Ask me to lock when I share". Choose at least "Only for sensitive files" for everyone, and "Always" for units that handle classified material.
- Choose your recovery option with your security authority: a signed waiver, or, when it is switched on, key escrow under dual control.
- Have every person acknowledge the classification policy. It says plainly that every action is recorded.
- Check the record on a schedule. Verify the chains, read the breach list, and export the evidence you must keep.
Decide where it runs
hosted in South Africa by VOIMAR, or, planned, inside your own network.
What this framework does not claim
- vFileLock is aligned with South Africa's Minimum Information Security Standards, the US federal scheme and ISO/IEC 27001:2022. It is not certified or accredited under any of them.
- It records who holds a clearance. It does not vet people.
- Your own security authority decides which systems may carry state-classified information.
- No system can stop a photo of a screen. That is why sensitive files open view only, with the reader's name on every page, and why every open is on the record.
See vFileLock with your own files and rules
Bring your Information Officer, your security officer and your IT lead. Or open vFileLock and lock your first file.
