Overview
Not all organizations use off-the-shelf security processes. If you’ve developed your own internal process—such as a unique audit protocol or custom compliance workflow—you can represent it in Hyver by creating a custom process asset. This article explains how to add and link custom processes so they contribute to your maturity scoring.
When to Use a Custom Process
Use a custom process when:
The security process is specific to your organization
It’s not listed among predefined process types
You still want it reflected in the maturity assessment
How to Create a Custom Security Process
Option 1: From the Assets Page
Option 2: From the Maturity Screen
Completing the Asset Form
Select "Security Process" as the asset type
Enter a process name (e.g., "Quarterly Access Review Workflow"):
Choose the appropriate engagement
Assign the asset to a NIST subcategory under the primary framework
Click Create
Once saved, the custom process appears as a linked process for the selected subcategory in the maturity screen:
Wrap-up / Next Steps
Custom processes ensure your internal best practices are represented in your maturity score — even if they don’t follow a template. Just make sure they’re mapped to the right subcategories to be included in maturity calculations.






