StorageGuard Custom Check Fields

Applies to: StorageGuard 9.2.9 and later

Overview

Custom Check Fields let administrators and risk owners capture organization specific metadata on checks and risks—directly in StorageGuard. You can define fields (e.g. “SLA (days)”, “Compliance Tag”, “Severity Override Reason”) and have them appear:

• In Findings on the Risks page
• In reports showcasing Checks and Findings

Each field has a name, value type, and default value. Defaults can be refined at the check level (affecting all findings generated by that check) and further overridden at the individual risk (finding) level.

Key Concepts

Custom Field: A user-defined attribute assigned to checks and visible on their findings.

Default Value: The system-wide initial value configured at the field definition level.

Check-Level Override: A default value tailored to a specific check (applies to all its findings unless overridden at risk level).

Risk-Level Value: The value on a specific finding (risk) that can override both the global default and the check-level value.
 

Value Types Supported:

• Text
• Number
• Boolean
• Date
• Enum (predefined list of selectable values)

Using Custom Check Fields

Add a Custom Field

Use this to define your custom check fields:

1. Navigate to the Baseline Configuration tab, select Settings, and then Custom fields from the left panel.
2. Click the (+) Add field button.
3. In the Add Custom Field dialog, enter: 
   • Name – the label that will appear on risks and in reports
   • Type – select one of Text, Number, Boolean, Date, Enum
   • Default value – the initial value applied to all checks
4. Click OK to save the field.

The new custom field is now available on checks, risks, and finding reports.

Edit a Custom Field

Use this to edit one or more of your custom check fields:

1. Navigate to the Baseline Configuration tab, select Settings, and then Custom fields from the left panel.
2. Select the custom field from the list.
3. Click Edit field.
4. Update the field name, type, or default value as needed.
5. Click OK to save changes.

NOTE: Changes to the default value do not override values already set on checks or risks.

Delete a Custom Field

Use this to delete a custom field that is unused or no longer required:

1. Navigate to the Baseline Configuration tab, select Settings, and then Custom fields from the left panel.
2. Select the custom field from the list.
3. Click Delete field.
4. Confirm the deletion.

Note that deleting a field removes it from all checks, risks, and reports.
Change the Default Field Value for One or More Checks

Use this when a specific check should have a different default value than the global field default:

1. Navigate to the Baseline Configuration tab, select Checks, and then Knowledge Base from the left panel.
2. Select one or more checks.
3. Right click the selected check(s) to open the context menu.
4. Select Edit custom fields.
5. In the dialog: 
   • Change the default value for one or more custom fields.
   • To revert a value to the global default, click (R) Reset to default.
6. Click OK to apply the changes.

The updated values become the default for all findings generated by the selected checks.

Change a Custom Field Value for a Single Risk

Use this to override the value for a specific finding:

1. Navigate to the Baseline Configuration tab and select Risks from the left panel.
2. Double click the risk to open its details.
3. In the Attributes pane, locate the custom field.
4. Change the field value.

This value applies only to the selected risk.

Change a Custom Field Value for Multiple Risks

Use this to update many findings at once:

1. Navigate to the Baseline Configuration tab and select Risks from the left panel.
2. Select one or more risks.
3. Right click the selected risks to open the context menu.
4. Select Edit custom field.
5. Enter the new value.
6. Click OK.

The selected value is applied to all chosen risks.

Permissions & Access

The permission to view or modify custom fields is controlled through user roles. It is aligned and controlled through the permission defined for managing checks under Baseline Configuration.

Example Use Cases

• SLA (Days): Defines the required remediation timeframe (e.g., critical issues resolved within 7 days).
• Score: Represents an internally calculated risk score or priority used to rank findings.
• Depends On: Identifies other findings that must be addressed before this finding can be addressed.

Best Practices

Naming Conventions: Use consistent prefixes or patterns (e.g., Ops: Owner, GRC: Control ID) to keep long lists organized.

Enum Discipline: Define clear, mutually exclusive values. Avoid overlapping terms (e.g., “Prod” vs “Production”) to prevent reporting fragmentation.

Troubleshooting & FAQs

Q1. What takes precedence—global default, check default, or risk value?

A: Precedence: Risk value → Check-level default → Global default.

Q2. How do I reset a check-level value back to the global default?

A: Use (R) Reset to default in Edit custom fields under checks → knowledge-base.