Overview
Processes play a key role in shaping your cybersecurity maturity. In Hyver, you can link structured security processes—like alert handling or postmortems—to specific NIST subcategories. These linked processes help improve your maturity score when used appropriately.
What Is a Process Asset?
A process is a collection of structured activities or tasks designed to achieve a security-related outcome. Examples include:
Two-factor authentication enforcement
Incident postmortem reviews
Vulnerability triage workflows
In Hyver, these are added as assets and linked to NIST subcategories to reflect their contribution to your security posture.
How Process Assets Affect Maturity Scoring
Linked processes are assigned a default maturity level of 3
This value is editable
The score is only used if it increases the current subcategory maturity score
Example: If a subcategory’s score is 2.5, a process score of 3 will help raise it
If the score is already above 3, the process asset is ignored to avoid lowering the score
Changing a process’s maturity level updates all subcategories it’s linked to
⚠️ If a process provides partial coverage, or requires additional processes to be effective, create a finding to reflect that gap.
How to Add a Process Asset
Option 1: Add a Suggested Process
If a subcategory is missing a mapped process, Hyver will suggest relevant ones:
Click the + button (if you have asset creation permissions):
Fill in the asset details:
Process type
Process name
Engagement
Primary NIST subcategory (required)
Click Create
Option 2: Add a Process You Define
If no suggestions appear, you can create a custom process
In the Asset creation screen, click + New next to the type dropdown
Follow the same steps to define and save the asset
You can only add one process asset at a time, but the same asset can apply to multiple subcategories.
Managing Process Assets
Go to the Assets page
Use the Unmapped Framework filter to find process assets not linked to NIST CSF
To view or edit linked subcategories:
Wrap-up / Next Steps
Processes are a powerful way to reflect real-world implementation of security practices. By mapping them to the right subcategories, you ensure that maturity scores align with what’s actually being done — not just what's on paper.





