Overview
Hyver continuously keeps your maturity assessment up to date by recalculating scores whenever key inputs change. This article lists the specific actions that trigger a recalculation, ensuring that your maturity data always reflects the most current state of your findings, technologies, and processes.
What Triggers a Maturity Score Recalculation?
Changes to Findings
A finding is added to a subcategory
A linked finding is fixed, and its maturity level is updated
An automatically fixed finding is assigned maturity level 2, and this differs from its pre-fixed score
The maturity level of a finding is changed manually
The severity of a finding changes, altering its maturity level (for non-fixed, non-reopen, non-pre-open findings)
A finding is moved to Reopen status and the maturity level is changed
A finding is changed from Potential to Vulnerability type
A finding’s NIST subcategory is changed
A finding is marked as Not Relevant
A finding is deleted
Changes to Linked Assets
A technology asset is added and linked to a subcategory
A process asset is added and linked to a subcategory
Wrap-up / Next Steps
Maturity score recalculations happen automatically, so your assessment stays aligned with the latest state of your security posture. Keep in mind that even small changes—like updating a severity level or adding a new asset—can ripple across your maturity model.