Platform module
Sensitive operations, compartmentalised and logged.
Run covert investigations, integrity testing and polygraph sessions on a need-to-know basis — with restricted access, a full audit trail and POPIA-aligned handling of every subject record.
Need-to-know case files · Restricted access roles · Polygraph session logs tied to investigations · Full audit trail · POPIA-aligned
The problem
Sensitive work leaks when it lives outside the system.
Covert operations handled on spreadsheets, personal phones and email threads expose subjects, sources and the business itself.
Everyone can see everything
Without compartmentalisation, a covert file is one shared drive away from tipping off the subject and collapsing the operation.
No defensible record
Polygraph results and integrity findings kept off-system can’t be tied to a case, a date or an examiner — and won’t survive scrutiny.
Privacy exposure
Handling subject data without lawful basis, consent tracking or retention control creates real POPIA and reputational risk.
How it works
From authorisation to closure, on a need-to-know footing.
Authorise. A covert case is opened under restricted access — only named, cleared roles can see it exists.
Compartmentalise. Evidence, sources and notes sit in the case with role-based visibility, so contributors see only their slice.
Examine. Polygraph sessions are booked and logged against the investigation, with examiner, consent and outcome captured.
Escalate. Findings feed the investigation and, where warranted, an incident — without ever widening the circle.
Close. The case closes with a complete, timestamped audit trail and a retention rule applied to subject data.
Capabilities
Built for the operations you can’t talk about.
Compartmentalised case files
Need-to-know structure keeps each covert operation sealed to the people cleared for it.
Restricted access roles
Granular, role-based permissions govern who can open, view, edit or even discover a case.
Polygraph session logs
Every session is tied to an investigation with examiner, date, consent and result recorded.
Full audit trail
Immutable, timestamped history of every view, edit and export — defensible after the fact.
POPIA-aligned handling
Lawful-basis notes, consent capture and retention rules for sensitive subject data.
Tied to investigations
Covert findings link cleanly into case management and incidents without breaking compartmentalisation.
On the data spine
One record, shared only where it should be.
Covert operations sit on the same data spine as the rest of MiMs, but under stricter walls. A polygraph result can escalate into an investigation and an incident, and every hop is logged — while access stays locked to cleared roles across all your sites.
What feeds it
- Investigation case management
- Incident reports flagged sensitive
- Restricted user roles and clearances
- Polygraph examiner schedules
What it feeds
- Investigation case management
- Incident management (on escalation)
- The document library (sealed evidence)
- The audit trail and reporting
Where it’s used
Integrity work across high-risk sectors.
“We can finally run a covert operation without half the team knowing it exists. The polygraph logs sit with the case, and the audit trail means the outcome holds up when it matters.”
Attribution withheld under NDA to protect ongoing operations.
FAQ
Covert operations & polygraph, answered.
Who can see a covert case?
Only named roles you clear for it. Compartmentalised case files are invisible to everyone else — they can’t view, edit or discover that the case exists.
Are polygraph sessions recorded in the system?
Yes. Each session is logged against its investigation with the examiner, date, consent and outcome, so results are always tied to a case rather than floating in isolation.
How does this stay POPIA-aligned?
Sensitive subject data carries lawful-basis notes, consent capture and retention rules, and every access is written to an immutable audit trail. MiMs is POPIA-aligned by design.
Can a covert finding become a formal incident?
When warranted, a finding escalates into an investigation or incident. The escalation is logged and access stays compartmentalised — the circle only widens when you decide it should.
Does it work across multiple sites?
Yes. Restricted roles and clearances apply consistently across every site on your data spine, so a national operation stays sealed end to end.