SECURITY & TRUST

Clear boundaries. Accountable operations.

Understand how application isolation, secrets, access, and release history fit together in the Orisite hosting design.

Security is part of the deployment model

A hosting panel should make responsibility visible. Orisite separates the customer workspace, the deployment control plane, and the runtime node so that each action has an owner and a defined boundary.

Isolate each application

Every website has its own runtime boundary. Shared capacity must not mean shared application credentials or unrestricted access to neighbouring workloads.

  • Rootless execution and a non-root application user
  • Explicit CPU, memory, process, and storage limits
  • Read-only application image with designated writable mounts
Keep credentials out of releases

A release identifies the code and runtime configuration. Secret values belong in protected storage and are resolved only for an authorized operation.

  • Opaque secret references instead of raw API keys
  • No credentials in browser responses or application artifacts
  • Separate references for staging and production
Make privileged actions traceable

Workspace identity and scope define who can inspect or request a change. Runtime execution must pass its own checks before a node acts.

  • IAMC identity and least-privilege scopes
  • Actor, request, release, and tenant correlation
  • Append-only audit evidence for sensitive changes
Verify domain ownership before traffic

Domain ownership, DNS configuration, and TLS status are distinct checks. A saved domain request alone does not prove a secure live endpoint.

  • Ownership verification before activation
  • Separate desired and observed TLS state
  • Health checks before a traffic switch

Control the paths into and out of the runtime

An application should expose only the endpoints required to serve traffic. Database, storage, and provider connections need a documented destination and permission boundary. The runtime contract specifies deny-by-default network egress; node enforcement must be verified before production use.

TLS protects a connection to the verified domain. It does not replace application authorization, database permissions, input validation, or patching. Those controls remain necessary inside the application.

Prepare for credential exposure and incidents

If a credential may be exposed, revoke or rotate it at the issuing provider, replace the protected reference, and identify every affected environment. Review access and deployment history before restoring normal operation.

Preserve timestamps, affected release references, and a minimal description of the incident. Do not paste raw credentials or customer records into general support messages. A verified private reporting channel must be published before sensitive reports are accepted.

  • Identify the workspace and impacted application
  • Contain access before making a new release
  • Validate recovery and record the final outcome
Shared responsibility
AreaOrisite responsibilityApplication owner responsibility
Runtime boundaryIsolation policy, deployment controls, node healthCompatible application code and required extensions
CredentialsProtected references and access checksCredential rotation and minimum provider permissions
Application dataStorage boundaries and recovery controlsData classification, retention, and application authorization
YOUR APPLICATION. YOUR WORKFLOW.

Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.