Tenant isolation
Customer records and files must be isolated at the data layer, not simply hidden in the interface.
Trust by design
Operational readiness data needs controlled access, traceability and recovery.
ReadyOps is being designed around multi-company isolation, least privilege, private evidence, auditable decisions and clear customer data responsibilities.
Role controls
Administrators, coordinators, supervisors, field users and viewers receive only necessary access.
Private evidence
Controlled storage, time-limited access, version history and appropriate medical-data minimisation.
Recovery
Backups, restoration tests, incident processes, monitoring and release controls before production.
Security principles
ReadyOps production controls are intended to include secure authentication, MFA for privileged users, least-privilege permissions, customer isolation, encryption in transit, protected document storage, audit history, secrets management, rate limiting, monitoring and controlled releases.
Privacy and POPIA-aware processing
Customers remain responsible for determining lawful processing and the operational information required for employees and contractors. ReadyOps should minimise personal and medical information and process it under appropriate contractual and technical controls.
Medical information: The operational requirement is normally fitness status, restrictions, issue date, expiry and authorised evidence—not a complete clinical history.
Production assurance
- Requirements-based quality assurance
- Tenant-isolation and permission testing
- Secure file and notification testing
- Backup and restoration exercises
- Independent penetration testing at appropriate scale
- Documented residual risks and approvals
Shared responsibilities
| ReadyOps | Customer |
|---|---|
| Operate and secure the platform according to approved controls. | Nominate authorised users and approve role access. |
| Provide export, support and incident processes. | Maintain source-data authority and accuracy. |
| Protect private records and customer separation. | Use the system as part of a controlled operational process. |
| Communicate material changes and providers. | Determine legal, employment, safety and customer obligations. |
Important limitations
ReadyOps supports structured operational and ISO-aligned processes. It does not itself certify an organisation, guarantee legal compliance, replace competent professional judgement or guarantee workplace safety. Final deployment and exception decisions remain the responsibility of authorised customer personnel.
Need the security assurance pack?
Qualified prospects can request the current architecture, test and provider summaries under appropriate confidentiality controls.