POPIA Bridge
POPIA Bridge is VOIMAR's privacy service. With vFileLock it does three jobs. It checks a share against your policy before the share is made. It keeps an independent record of every event. And it gives your Information Officer a view of every document flow, with proof that nothing was changed.
2. A record of every event
Every event goes into POPIA Bridge's record: lock, level change, owner and custodian changes, share, approval asked, approved or declined, code sent, wrong code, terms accepted, open, refused open, forward attempt, revoke, extend, burn, expiry, and every time someone reads the record.
Each entry holds the time, who acted, the IP address and device, the file's type, size, level and category, the fingerprint of the locked file, the outcome and the reason, and whether it was a breach attempt.
What never goes into the record: either half of a key, the key itself, codes, or anything inside the file. The recipient's address goes in masked, with a keyed hash, so one person's events can be found without the record holding their address.
3. A hash-chained ledger
- Every file has its own chain. Each entry carries the SHA-256 hash of the entry before it.
- Changing or deleting an entry breaks the chain.
- The newest entry of every chain is lodged in POPIA Bridge's own tamper-evident record, so even a removed tail shows.
- Entries are only ever added. Revoking, burning and changing a level add entries. A burned file's record stays.
- Anyone who may read a file's ledger can verify it. Your Information Officer can verify every file at once.
- Reading the record is itself recorded. Who looked at the evidence is evidence too. Owners see who read the record of their files.
Recipients' acceptances of the terms keep their own chain, in the same way.
The Information Officer's view
- Every document flow in your organisation, with filters: person, owner, level, kind of file, POPIA category, event, dates and file.
- Exports as CSV and JSON with the chain check, so an auditor can recheck the chain from the export alone.
- The list of breach attempts.
- A chain-of-custody export for any document.
Planned as a signed PDF. - The approvals queue.
Who may read a file's record
| Reader | Public to Confidential | Secret | Top Secret |
|---|---|---|---|
| Information Owner | The full record | The full record | The full record |
| Custodian | Holding and admin events | Holding and admin events | None |
| Recipient (signed in) | Their own opens | Their own opens | None |
| Information Officer | Everything | Everything | Everything |
| Named auditors | Everything | Everything | None |
| The two approvers | The full record |
Built for POPIA's duties
vFileLock and POPIA Bridge turn several of POPIA's duties into working controls and evidence: accountability (section 8), security safeguards (section 19), dealing with security compromises (section 22), and a person's right to know who accessed their information (sections 23 to 25).
No product makes an organisation compliant on its own. Compliance also needs your policies, your Information Officer and your people. vFileLock makes their work visible and provable. See POPIA compliance for what supports each of POPIA's conditions, and what stays with you.
One record, more sources
Planned call recordings in the Record Store, and classified folders in the Repo, on the same levels, roles and record.
Planned other destinations for the record, such as a GDPR register or a security monitoring system, for organisations that need them.
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.
