Settings

The Control Model settings page lets you configure charter approval workflows and manage the classification system used to categorize Steering Committees. Navigate to Control Model → Settings to access four configuration tabs: Charter, Scope, Domain, and Region.

Charter tab

The Charter tab configures the default approval workflow for Security Charters at the tenant level.

Setting the tenant default workflow

Select an active workflow template of type CHARTER from the dropdown to set it as the organization-wide default. When a charter is submitted for approval and has no entity-level override, this default workflow is used.

You can remove the tenant default at any time. Individual charters can override the tenant default with a charter-specific workflow configured on the charter’s detail page.

Permissions

Managing the charter workflow configuration requires the security-charter:manage permission.

Scope tab

Committee scopes define the operational context of a Steering Committee. Each scope has a name, description, unique code, and active/inactive status.

Default scopes

SecureHive provides five predefined scope classifications. Click Create from Defaults to populate them in one step:

Managing scopes

Use the classification table to create custom scopes, edit existing ones, or deactivate scopes that are no longer needed. The table supports search by name or code and filtering by active/inactive status with pagination.

Each scope requires a unique code within your tenant. Codes should follow an uppercase naming convention (e.g., EXECUTIVE, PROJECT_BASED).

Domain tab

Committee domains categorize the cybersecurity focus area of a Steering Committee. SecureHive includes 21 predefined domains organized across five categories.

Default domains

Click Create from Defaults to populate all predefined domains:

Core Security Domains — Cloud Security, Data Protection, Product Security, Identity & Access, Network Security, Security Architecture.

Operations & Response — Security Operations, Incident Response, Threat Intelligence, Security Engineering, Security Testing & Validation.

Governance & Risk — Risk Management, Compliance, Security Governance, Security Program Management.

Third-Party & Supply Chain — Vendor Risk, Supply Chain Security.

People & Process — Security Awareness & Training, Business Continuity & Disaster Recovery.

Physical & Infrastructure — Physical Security, Security Automation & Orchestration.

Managing domains

Like scopes, domains are managed through the classification table with search, status filtering, and CRUD operations. Create custom domains for areas specific to your organization (e.g., OT_SECURITY for operational technology or AI_SECURITY for AI/ML security).

Region tab

Committee regions define the geographic context of a Steering Committee. This is particularly useful for organizations with distributed operations that need region-specific governance.

Default regions

Click Create from Defaults to populate five standard regions:

Managing regions

Add custom regions to match your organization’s geographic structure (e.g., ANZ for Australia & New Zealand, DACH for the DACH region). Regions follow the same management pattern as scopes and domains — each requires a unique code, supports active/inactive status, and can be searched and filtered.

Permissions

Managing committee classifications (Scope, Domain, Region) requires the steering-committee:manage permission. Managing charter workflow settings requires the security-charter:manage permission. Users without these permissions see a read-only view.