Tenant isolation
Each organization's Forest data is kept separate from every other organization's.
Last updated June 1, 2026
Every organization in Forest is its own tenant. Your assessments, scores, capabilities, contracts, and recommendations belong to your tenant and are kept separate from every other organization on the platform.
Why isolation is the foundation
Forest holds a candid picture of each customer's security program. That picture is only safe to create if customers trust that no one else can reach it. Tenant isolation is the boundary that makes that trust reasonable. Requests are scoped to your tenant, so data from one organization is never returned to, or mixed with, another.
This separation is what lets Forest offer useful comparison without exposing anyone. You can see how your maturity compares to a peer average without ever seeing another organization's underlying data, and they never see yours.
What stays inside your tenant
Your CAMP assessment, criticality settings, and target maturity.
Your Org Score, Forest Score, and domain scores.
Your capabilities, tool mappings, contracts, and roadmap.
The recommendations the Forest Intelligence Service generates for you.
Isolation and comparison are not in tension. Forest can show you a peer benchmark precisely because the raw data behind it stays locked inside each tenant.
Isolation defines the outer boundary. Inside it, Role-based access control governs who on your team sees what. For how comparison stays safe across tenants, see Benchmark privacy.