[ Applies to ] StorageGuard 9.2.9 and later / All supported target systems / Baseline Configuration
Custom Check Fields let administrators and risk owners capture organization-specific metadata on checks and risks, directly in StorageGuard. You can define fields such as “SLA (days)”, “Compliance Tag”, or “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.
In this article
Key concepts
| Concept | Description |
|---|---|
| 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. It applies to all the check's findings unless overridden at the risk level. |
| Risk-level value | The value on a specific finding (risk). It overrides both the global default and the check-level value. |
Note: When more than one value is set, the most specific one wins: risk value, then check-level default, then global default.
Supported value types:
- Text
- Number
- Boolean
- Date
- Enum (predefined list of selectable values)
Manage custom fields
You manage field definitions under Baseline Configuration > Settings > Custom fields.
Add a custom field
- Go to the Baseline Configuration tab, select Settings, and then select Custom fields from the left panel.
- Click (+) Add field.
- In the Add Custom Field dialog, enter:
- Name: the label that appears on risks and in reports.
- Type: Text, Number, Boolean, Date, or Enum.
- Default value: the initial value applied to all checks.
- Click OK to save the field.
The new custom field is now available on checks, risks, and finding reports.
Edit a custom field
- Go to the Baseline Configuration tab, select Settings, and then select Custom fields from the left panel.
- Select the custom field from the list.
- Click Edit field.
- Update the field name, type, or default value as needed.
- Click OK to save your changes.
Note: Changes to the default value do not override values already set on checks or risks.
Delete a custom field
- Go to the Baseline Configuration tab, select Settings, and then select Custom fields from the left panel.
- Select the custom field from the list.
- Click Delete field.
- Confirm the deletion.
Caution: Deleting a field removes it from all checks, risks, and reports.
Set field values on checks and risks
Change the default value for one or more checks
Use this when a specific check should have a different default value than the global field default.
- Go to the Baseline Configuration tab, select Checks, and then select Knowledge Base from the left panel.
- Select one or more checks.
- Right-click the selected checks to open the context menu.
- Select Edit custom fields.
- In the dialog, do either of the following:
- Change the default value for one or more custom fields.
- To revert a value to the global default, click (R) Reset to default.
- 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
- Go to the Baseline Configuration tab and select Risks from the left panel.
- Double-click the risk to open its details.
- In the Attributes pane, locate the custom field.
- Change the field value.
This value applies only to the selected risk.
Change a custom field value for multiple risks
- Go to the Baseline Configuration tab and select Risks from the left panel.
- Select one or more risks.
- Right-click the selected risks to open the context menu.
- Select Edit custom field.
- Enter the new value.
- Click OK.
The value is applied to all selected risks.
Permissions and access
The permission to view or modify custom fields is controlled through user roles. It follows the permission for managing checks under Baseline Configuration.
Example use cases
| Field | Purpose |
|---|---|
| SLA (Days) | Defines the required remediation timeframe, for example, 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, such as
Ops: OwnerorGRC: Control ID, to keep long lists organized. - Enum discipline: Define clear, mutually exclusive values. Avoid overlapping terms, such as “Prod” and “Production”, to prevent reporting fragmentation.
Troubleshooting and FAQs
What takes precedence: the global default, the check default, or the risk value?
The risk value, then the check-level default, then the global default.
How do I reset a check-level value back to the global default?
Go to Baseline Configuration > Checks > Knowledge Base, open Edit custom fields for the check, and click (R) Reset to default. See Change the default value for one or more checks.
[ Still need help? ]
Our support team is here for you. Submit a request and we'll get back to you.
Comments
0 comments
Please sign in to leave a comment.