How score history works

Score history shows how your scores move over time. A single snapshot tells you where you stand today. History tells you whether you are improving, holding, or slipping, which is the more important question for most security programs.

What history records

As your assessment changes, Forest captures how your scores stood at each point. Because every score is deterministic, each historical value reflects the exact inputs in place at that moment. You can trace any point back to the maturity scores, criticality ratings, targets, and scope behind it.

That traceability is what makes the trend honest. A rising Org Score means real maturity improved on capabilities that carry weight. A rising coverage component in your Forest Score means you assessed more of the relevant surface. The line moves for reasons you can name.

Reading the trend carefully

Not every movement reflects performance. If you widen scope or raise your targets, scores can shift even though nothing in your program changed. Keep these factors in mind when you interpret a slope.

Before reading a drop as decline, check whether scope or targets changed in that period. A larger scope or a higher target bar can lower a score without any real regression.

Why it matters

History turns Forest from a snapshot into a record you can take to leadership. You can show progress against a roadmap, justify investment by pointing to closed capability gaps, and demonstrate that movement is tied to specific, explainable inputs rather than to a number that drifts on its own.