Security should be visible in the operating model.
Qinsight’s security approach emphasizes design-time controls, least privilege, defense in depth and clear customer boundaries for cryptographic evidence.
Four principles that shape the platform
Security by design
Security requirements are treated as architecture inputs rather than controls added at the end of delivery.
Zero trust
Access is scoped and authenticated, with least-privilege expectations across product and operational workflows.
Defense in depth
Controls are layered so no single mechanism is expected to carry the entire security boundary.
Continuous monitoring
Logging, review and operational monitoring support detection, investigation and continual improvement.
Minimize what crosses the boundary
Qinsight's approach to data protection emphasizes encryption, access controls, minimal retention and auditability.
Encryption in transit
Protected transport for data exchanged with Qinsight services.
Encryption at rest
Stored information protected using appropriate platform controls.
Minimal retention
Collect and retain only what is needed for the service and agreed use case.
Access + audit
Controlled access with audit logging to support review and accountability.
Clear boundaries and shared responsibility
Transparency
Communicate material security practices, product boundaries and roadmap status without implying certifications that are not complete.
Shared responsibility
Document what Qinsight controls and what remains the customer’s responsibility in deployment, access and governance.
Regulatory support
Produce evidence that can support customer assurance and compliance work without claiming that the product itself certifies compliance.
