Built as if the audit were tomorrow.
This page describes the architecture, not aspirations. Everything below is a property of how KSN Suite is built — demonstrable in a live tenant — and where we do not hold a certification, we say so plainly.
Your data shares a platform. Never a row.
Multi-tenant does not mean commingled. Isolation in KSN Suite is a structural property of the schema and the permission model, enforced on every read and every write.
Every row is tenant-scoped
Every table in the platform carries a mandatory tenant column, and every query runs inside the tenant context established by your session. There is no shared pool of records with a filter bolted on top — the scoping is structural, and our own test suite includes checks that deliberately omit the tenant predicate to prove they return zero cross-tenant rows.
Permission-first access
Every screen, endpoint and action — down to editing a storefront banner or viewing a cost field — sits behind a granular permission. Your administrators compose roles from those permissions; nobody at your company sees anything an admin has not granted, and the same model governs the API.
An audit trail on every mutation
Every create, update and deactivation writes an audit record with the actor, the timestamp, and the full before-and-after state of the row. Writes flow through controlled database procedures rather than ad-hoc statements, so no code path can change data without leaving the trail.
Fewer ways in. Fewer ways to get it wrong.
Protection comes from narrowing the paths data can travel, then watching the paths that remain.
Encrypted in transit
All traffic between browsers, mobile devices and the platform runs over TLS. Storefronts, portals and the API present no unencrypted endpoints.
Credentials done properly
Passwords are stored only as salted hashes using a modern memory-hard algorithm — never in plain text, never reversibly. Sessions are token-based and expire.
Controlled write paths
Application code cannot write to tables directly: mutations go through stored procedures that enforce validation and audit logging in one place. Reads flow through curated views.
Separated environments
Development, staging and production run as separate estates with separate databases and credentials. Customer data lives only in production.
A backup that has never been restored is a hope.
Production databases are backed up on a schedule, and restore procedures are exercised rather than assumed — a restore is only trusted after its object counts and contents have been compared against the source. Backups are retained under the same tenant isolation guarantees as live data.
GDPR-ready by design, honest about certifications.
KSN Suite is operated from Canada and designed to support your obligations under PIPEDA and the GDPR: your business owns its data, records can be exported, corrected and erased on request, and the audit trail documents every change along the way. We act as a processor of the personal data your tenant holds — we do not sell it, mine it, or use it to train anything.
Plainly: we do not currently hold SOC 2 or ISO 27001 certification. Where this page uses words like “aligned” or “designed to support”, it describes architecture we can demonstrate in a live tenant — not an audit we have purchased. If a certification is a hard requirement for your evaluation, tell us; we would rather lose the deal honestly than win it with a vague claim.
Found something? Tell us first.
If you believe you have found a security vulnerability in KSN Suite, any of its storefronts, or this website, please email security@ksnsuite.ca with steps to reproduce, the affected hostname, and any relevant request or response details. Please do not access data that is not yours, degrade the service, or disclose the issue publicly before we have had a chance to fix it.
We acknowledge reports within two business days, keep you informed while we investigate, and will not pursue action against good-faith research conducted within these guidelines.
Verify it yourself.
The trial tenant runs the same isolation, permissions and audit trail as production — because it is production. Kick the tires with your own security checklist.
14 days · every module · no card