Overview
To get the most meaningful and complete maturity assessment in Hyver, it’s not enough to rate subcategories manually. This article outlines the recommended order for contributing data — from technologies and processes to findings and manual ratings — so you can improve both coverage and scoring accuracy.
Recommended Order for Maturity Scoring
1. Add Technology Assets Mapped to Subcategories
Click the + button to add suggested technologies already in use at your organization
Linked technologies help validate and improve maturity scores automatically
Use the Unmapped Framework filter on the Assets page to find technology assets that aren’t yet mapped
2. Add Process Assets Mapped to Subcategories
Click the + button to add applicable processes your organization has implemented
Mapped processes contribute directly to subcategory scoring
Again, use the Unmapped Framework filter on the Assets page to identify gaps
3. Identify NIST Functions with No Score
Go to the Maturity page
Use filters to identify functions and subcategories without scores
Focus next steps on filling in those gaps
4. Manually Score Unrated Subcategories
Use the No maturity score or Unknown filter to isolate unrated subcategories
Select a maturity level (1–5), or mark as Unknown or Not relevant
You can also link findings during this step to enhance scoring
Elements That Influence Maturity Scoring
To ensure balanced and accurate results, your maturity score should ideally include input from all four of the following:
Element | How It Contributes |
Technologies | Add real tools (e.g., EDR, IAM) linked to subcategories |
Processes | Link active security practices (e.g., patching, monitoring) |
Findings | Automatically included if mapped to a subcategory during creation |
Manual Ratings | Direct scoring based on user knowledge and documentation |
Use filters on the Findings page to locate findings not yet mapped to a framework:
Wrap-up / Next Steps
Using a structured approach to maturity scoring helps ensure your results reflect the real state of your security posture — not just a snapshot. Adding mapped assets and strategically filling in missing scores brings clarity, credibility, and momentum to your improvement efforts.