What to expect

A design partnership is a working relationship, not a one-time setup. You get early access to capabilities, and Forest gets direct feedback from security leaders running real programs. This page sets expectations on both sides.

The arc of the engagement

Your first weeks center on building a baseline through the CAMP assessment. Once capabilities are scored, the Forest Intelligence Service produces your Org Score, Forest Score, domain scores, and an initial set of recommendations. Because FIS is deterministic, every number traces back to inputs you provided, and the same inputs always produce the same result.

From there, the work shifts to interpretation. You review where current maturity sits below target, where criticality raises priority, and how your performance compares to a privacy-preserving peer average. A peer delta is a performance difference, not a gap in your program.

Recurring reviews

Expect a regular review cadence. As you close gaps and update maturity, scores move and recommendations re-derive. Roadmap projections shift accordingly.

A peer delta tells you how you compare. A gap, the distance between current and target maturity, tells you what to fix. Treat them differently.

What we ask of you

As a design partner, you are expected to keep assessments reasonably current and share candid feedback through the feedback process. When something breaks or blocks you, use the support process.