Skip to main content

Control Configuration Names

This article offers some guidelines on naming conventions for control configurations

Alan Winchester avatar
Written by Alan Winchester
Updated over 2 years ago

A common point of confusion that we see on the platform is naming configurations for the system or the control itself. A configuration name is best when it describes the security purpose of the configuration and the name should apply to multiple controls or systems. When a control is first created, it assumes the name: "Default." In general, this would be how most systems in an organization will have their controls configured. But sometimes certain systems pose a greater risk to the organization or operate in an environment that necessitates greater or lesser security. In those situations you may want to make the security features of the control more or less restrictive, depending upon the risk. Two good examples of Configuration Names might include "High Risk" or "Low Risk."

As a reference point, the overwhelming majority of customers on CyMetric have only one configuration name: "Default." The next largest number have two configurations: "Default" and "High." A very small number of customers have system specific configuration names. We do not recommend this approach as it could lead to the same control configuration having different names which could be quite confusing.

If you have questions about naming configuration, please feel free to call and speak to one of our specialists.

Did this answer your question?