Security and trust boundaries

Keep secrets, identities, data and service entry points within their necessary boundaries.

Secrets and deployment

Inject secrets through a protected environment, not source, public browser variables, URLs or logs. Services receive only dedicated derived secrets. Preserve data and encryption keys, use HTTPS and restrict raw service ports.

Different entries, different identities

Same-origin public Zones are not untrusted-script sandboxes. Third-party administration uses opaque iframe isolation and short-lived delegated identities rather than platform administrator credentials. Verify both signed Gateway context and business authorization.

Content, media and reporting

Article HTML is sanitized server-side, and references do not make private media public. Check content and secret boundaries before publication. Never attach credentials to public reports. The private vulnerability-reporting channel is not yet finalized; a public issue is not private.