Security & Isolation Overview
A public-safe explanation of how SGEN emphasizes site separation, governed access, managed configuration, and secure delivery boundaries.
Security theme
The public security model can be understood through a small set of themes that explain how SGEN protects site separation, access control, managed settings, and delivery boundaries within a shared platform foundation.
Site content and settings remain distinct within the shared platform model.
Administrative and operational access is governed by role and surface.
Sensitive settings are managed through controlled configuration practices.
Requests are handled through secure, controlled platform layers.
Security principles
SGEN is designed around platform control, site separation, and managed operational boundaries. Although the platform foundation is shared, site content and operating context are separated so that one site does not become another site’s data surface.
Site separation
Each site operates within its own site-specific context so that content, settings, and operational data remain distinct.
Controlled access
Administrative and operational access should remain governed, role-aware, and appropriate to the surface being used.
Managed configuration
Sensitive configuration should be handled through managed secret and environment controls, not embedded directly into public-facing code or documentation.
Secure delivery
The platform is structured to support secure request handling, controlled delivery, and consistent platform-level protections.
Public communication boundary
This page should explain the security model without disclosing implementation-sensitive information.