Design security classifications, levels, and information items

Classification describes business categories; levels describe sensitivity. Classification information items are reusable semantic concepts, not physical columns. Associate actual objects after recognition or manual review. Establish policy and framework first.

Design the hierarchy

1. Open Data Security > System Settings > Data Classification Design, also labeled Security Classification Design.
2. Set levels, names, and supported types. Data item support also supports information items.
3. Configure custom properties/icons and save.
4. Create nodes in Data Classification and Levels > Data Classification.

Once nodes exist, levels and supported types can increase, not decrease. Changing a property type clears values; making it required requires completion. Assess impacts first.

Reuse catalog structures

If approved, select one enabled catalog space and immediate or real-time synchronization. Its depth must be at least the security hierarchy depth. Existing attached assets/information items block synchronization. Enabling it prevents independent hierarchy edits.

Synchronization mainly copies names/descriptions, not all properties. Set default levels/importance or complete them afterward. Verify supported types:

Catalog support	Security support
Folders only	Folders
Folders/tables	Folders/tables
Folders/data items	Folders/data items
Standards, services, metrics, files, reports	Security table/data-item/view scope; those business types are not copied

Later synchronization follows changed source folder types. Verify hierarchy and eligible objects, not names alone.

Maintain information items

1. Create a named/described folder in Classification Information Items.
2. Create the item and save its properties.
3. Define custom properties through More > Custom Properties as needed.
4. Download import templates; choose automatic codes or provide codes.
5. Inspect progress, successes/failures, and search by name/code.

Attached items cannot be deleted; nonempty folders cannot be deleted. Export without selections covers all; with selections it covers selected items.

Maintain classifications

Create/edit nodes, add information items, and import/export templates in Data Classification, also called Security Classification. Existing items, assets, or approvals block deletion. Structure exports differ from asset exports, which include the current class and descendants.

Define levels and evidence

Maintain levels, importance references, and decision criteria in Data Levels. Built-in values are editable; referenced levels cannot be deleted. Upload legal files in Legal Provisions and verify downloads. Referenced provisions cannot be deleted. Uploading evidence alone does not establish compliance.

Next: Collaborative classification or Recognition.