vFileLock with vKOM and UCC
VOIMAR's communications platforms carry calls, chat and files. vFileLock is the part that locks the files. It works the same way everywhere: the app hands the file to vFileLock, and vFileLock does the locking, the rules and the record. No VOIMAR app ever holds a key.
One lock, four ways to connect
The share pop-up
Coming the same screen when you attach, drag or right-click a file inside VOIMAR's apps.
coming inside the apps
The connector
The custody API
Signed webhooks
vKONNECTOR, vCOMMANDER, the Repo, or your own system. The person presses Share.
The share pop-up. The file is locked here, on the person's own device.
The link, the share's number, its state and its rules. Never a key.
“May this person do this?” asked before the action, and what was done written into the record.
Every event in the record, pushed to your endpoints, signed so the receiver can prove where it came from.
Platform by platform
vKONNECTOR
Coming attach or drop a file in a chat and the share screen opens, with the level and a sensible preset already set.
by link, pop-up coming
vKOM-SECURE
Coming the share pop-up in the console, and call recordings on the same levels and record.
by link, pop-up coming
vCOMMANDER
Coming the same share pop-up when you attach, drag or right-click a document.
by link, pop-up coming
The Repo
Coming "Lock with vFileLock" on every file, and classified folders with key entry. The vFileLock page the Repo opens, with its key-entry viewer, is live.
The Record Store
Coming each recording gets a level, an owner and its own record of every listen, download, share and refusal.
vFileLock is also an option for GYTE, Kesho and Heita.
The connector
The connector is how a web application hands a file to vFileLock without ever touching a key.
- The person clicks Share in the host application.
- The application opens vFileLock's page in a small window. The person is signed in with Voimar ID.
- vFileLock says it is ready, and tells the application the person's switch setting.
- The application hands over the file, with a suggested level and kind of file. The person can change both.
- vFileLock shows the share pop-up. The file is locked in that window, on the person's own device.
- vFileLock hands back the link, the share's number, its state and its rules. If the person asks, it also hands back a locked copy to keep next to the original.
What keeps it safe:
- Only the web addresses your organisation lists may use the connector. They are matched exactly, with no wildcards.
- Each side accepts a message only from the exact address and window it expects.
- The application never sees the second key half, the file key or the code.
- A second page lets people manage a share from inside the application: who opened it, revoke, extend, approve.
The custody API
The custody API is the server side. An application uses it to label what it holds, to ask before it acts, and to write down what it did.
- Register an item, such as a document, a folder or a recording. It gets a level, an owner and its own hash chain.
- Ask before acting: may this person open, share, download, print or export this item? The answer is yes, no, or needs approval, with the rules the level forces. Every no is recorded by vFileLock itself.
- Write events into the item's chain, and read and verify the ledger.
- The person's own sign-in token travels with the call, so no application can claim a clearance on someone's behalf.
- No key can make or open a share, receive a key half or touch recovery.
More on Deployment.
Signed webhooks Coming
Webhooks push the record outward. Every event, from every source, goes to the endpoints an organisation chooses.
- Each delivery is signed with HMAC-SHA256 over the time and the body, using the organisation's own secret.
- A delivery with an old time stamp is refused, and a repeated event is counted once.
- Failed deliveries are retried, from 1 minute up to 24 hours, with a delivery log and a redeliver button.
- The body never carries a key half, a code or anything inside a file. Recipient addresses are masked.
Call recordings and the Record Store Coming
Call recordings are sensitive files too. The Record Store will use the same levels, roles and record as documents.
- Each recording gets a level, an Information Owner (for example the call-centre manager), a Custodian and named Users.
- Before every listen, download, share or export, the Record Store asks the custody API. A no is shown with its reason, and is already on the record.
- Every listen is recorded, with the person, the time, the IP address and the device.
- The rules follow the level. Secret and Top Secret recordings stream only and are never downloaded. Each Top Secret listen is approved by the Information Owner.
- An honest difference: recordings are kept and played by the Record Store, so they are not locked end to end the way a vFileLock file is. vFileLock decides and records. The Record Store enforces.
One record across everything
Whatever the source, a document in the Repo, a file shared from a chat or a call recording, the events land in the same place: one hash-chained ledger per item, and POPIA Bridge. Your Information Officer sees one view. More on POPIA Bridge.
Your own tenant
Every organisation is its own tenant. Its files, records, keys, settings and list of allowed applications never mix with another organisation's. The same holds inside VOIMAR's platforms: a file shared from vKONNECTOR in one organisation does not exist for another.
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.
