Labels
Labels are the free-form tagging layer that cuts across CyberGuard’s object types. A label is nothing more than a word, but because the same word can be attached to a domain, an asset, a control, an evidence and an incident, labels let you slice the platform along an axis the data model does not have — a client name, a site, a regulation, a project code, a wave of work.
Where to find it
Section titled “Where to find it”Extra → Labels in the sidebar. Add label creates one.
Naming rules
Section titled “Naming rules”A label is a single token: letters, digits, underscores and hyphens, up to 36 characters, no spaces. The form rejects anything else with “Label must be alphanumeric and contain at most 36 characters”.
That constraint is deliberate — labels are meant to be typed and filtered, not written. Use pci-dss, site-lyon, wave-2, not PCI DSS scope (phase two).
Where labels apply
Section titled “Where labels apply”Objects that support labels show a Labels field in their creation and edit forms, and a Labels filter on their list view. They include:
- Organization — domains.
- Assets and operations — assets, applied controls and policies, evidences, task templates, incidents, documents.
- Risk — risk scenarios, vulnerabilities.
- Findings — findings and findings binders.
- Catalog — reference controls, metric definitions, custom dashboards.
- Third parties — entities, representatives, solutions, contracts.
- Privacy — processings.
- Project management — projects, collections, accreditations, responsibility matrices.
Not every object type carries labels, so if a form has no Labels field, that object simply is not taggable — filter it by domain, status or owner instead.
Using labels
Section titled “Using labels”Attach labels from the object’s own form: the Labels field is a multi-select that offers the existing vocabulary. Then, on any list view that supports them, open the filter panel and pick one or more labels to narrow the table. Combine a label filter with a status or domain filter to get to a working set quickly — “everything tagged wave-2 that is still To do”, for example.
Because labels are ordinary objects, they respect domain permissions like everything else, and editing or deleting a label from this page removes it everywhere it was applied. Review the list occasionally and merge the near-duplicates that inevitably appear.
Related
Section titled “Related”- Applied controls — filtering an action plan by label.
- Evidences — grouping supporting documents.
- Domains — labelling the folder tree itself.
