Overview
Not all organizations use off-the-shelf security processes. If an internal process has been developed — such as a unique audit protocol or custom compliance workflow — it can be represented in the Cye Exposure Management Platform by creating a custom process asset. This article explains how to add and link custom processes so they contribute to maturity scoring.
When to Use a Custom Process
Use a custom process when:
The security process is specific to the organization
It's not listed among predefined process types
It still needs to be 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 internal best practices are represented in the maturity score — even if they don't follow a template. Map them to the right subcategories to ensure they are included in maturity calculations.
For the full list of processes Cye supports out of the box and their NIST mappings, see the Appendix: Supported Mitigations and Their NIST Mapping.






