Skip to content
MSO CloudDocumentation

Security disclosure policy

On this page

How to report a suspected vulnerability in MSO Cloud and what happens after you do. The mechanisms that keep one organization out of another's data are explained in Tenancy and security; the internal threat model is not published.

Reporting a vulnerability#

Item Policy
Contact security@younetgroup.com
Include The steps to reproduce, the affected page or endpoint, and the scope you tested
Scope Only organizations you are a member of; never test other tenants
Handling Acknowledged within two business days, then triaged by severity
Priority A confirmed tenant-isolation issue takes priority over all other work

Guarantees a report is judged against#

Guarantee Where it is explained
A request reads only its own organization's rows, enforced in the database Tenancy and security
The request host decides the organization, not the session cookie Tenancy and security
Credentials are envelope-encrypted, never logged, returned or archived Tenancy and security
Identifying names are masked at display according to the organization's settings Identity masking
Mutating, authentication and webhook endpoints are rate-limited Tenancy and security
A high-severity dependency advisory blocks a release Quality gates

Controls not yet automated#

Each open item has a named owner and a review date in the internal register.

Control Compensating control today
Encryption-key retirement with checkpointed rewrap Every historical key version is retained; only new writes move
Point-in-time and off-site recovery drill Host snapshots and tenant exports where available
Enforced content security policy A report-only policy ships, and violation reports are collected

Durable telemetry with service-level objectives, build-artifact provenance and signing, and migration lock budgets are not yet automated either.