This technote is a compilation of documents that describe the steps for creating checks in the Control Compliance Suite 11.0 Standards module. Basic knowledge of CCS standard module and CCS queries is required to ensure that the parameters of the checks are changed accordingly for the standards to run successfully.
Please refer to the attached documents for guidelines on creating Control Compliance Suite (CCS) 11.0 checks. A standard can be broken into following components:
In essence a standard is comprised of a collection of checks that can be executed on a target system. CCS installs a number of standards during the installation of the Application Server. CCS provides predefined standards that customers can use out of the box to check for compliance within the organization. The standards support xml checks for simple evaluation on assets such as checking for the existence of a particular register key, etc. The standards also support complex C# checks for complex evaluation on assets. The complex checks for values that are stored in the dlls and are not easily accessible through normal means. The reason being is that the check editor makes a system call to a dll. So it returns the message "This is a complex check and modifying it is not supported through the check editor”. The simple and the complex checks in the Table pane are tagged differently. You can differentiate between the simple and complex checks visually by the icon. The icon that indicates the complex checks has a red mark on the upper left corner. This Red circle on the check indicates that it is a complex check that normally has some type of code or complex algorithm that is not exposed in the check builder UI. Normally there is no way to edit these checks. You may be able to modify the parameters in that tab and accomplish the customization, but otherwise you will need to use the check as it is or try to determine a way to build it from scratch within the check builder UI.