Module
A Module represents an external data source or system that supplies asset data to the registry. It acts as the bridge between the Asset Registry and your IT ecosystem — connecting platforms like AWS, Azure, ServiceNow, or internal systems so that assets can be imported, synchronized, and kept up to date.
Core concepts
Why Modules matter
Modules turn the Asset Registry into a dynamic, living system that stays in sync with your broader IT environment. They let you:
- Automatically populate the registry with accurate, real-time asset data from external systems
- Track asset provenance — know exactly which system each asset came from
- Map data from various systems to a common structure using Element Types
- Organize data sources into logical hierarchies (e.g., separate Modules for
AWS_ProdandAWS_Staging)
Example
| Module | Provides Elements for |
|---|---|
AWS | Servers (EC2 instances), storage, networking |
ServiceNow | Applications, databases, ITSM records |
These Modules feed asset data into the registry, where each asset is classified under the correct Element Type and assigned to the appropriate Domain.
How Modules connect to other concepts
- Type Functions and Type Units are associated with a Module, scoping them to specific data sources
- Each Element can be traced back to the Module that supplied it
- Modules feed data through Blueprint integrations, where incoming assets are classified using Element Types and assigned to Domains
Built-in Module
The Asset Registry ships with one built-in Module:
| Module | Description |
|---|---|
| Canonical Business Context | The data source for the BCM model. Connects technical assets (applications, packages, vulnerabilities) to business concepts (products, customers, revenue) and impact assessments (legal, reputational, financial) |
This Module is pre-configured and cannot be edited or deleted. All built-in Type Functions, Type Units, and Element Types are scoped to this Module.
Creating a Module
Navigate to Modules in the top navigation bar and click + New Module.
Settings
| Toggle | Default | Description |
|---|---|---|
| Active | On | Whether the Module is available for use |
| Built In | Off | Marks the Module as system-defined. Built-in Modules cannot be edited or deleted |
Details
| Field | Type | Required | Description |
|---|---|---|---|
| Module Name | Text | Yes | A unique name for this Module. Duplicates are rejected with a validation error |
| Description | Text (multiline) | No | A brief explanation of the data source this Module represents |
| Parent Module | Dropdown | No | An optional parent for building hierarchical Module structures (e.g., Cloud_Sources > AWS). The dropdown excludes self and descendants to prevent circular references |
Viewing and editing
Click any row in the Modules table to open it in view mode. From there:
- Click the edit icon to switch to edit mode
- Click the delete icon to remove the Module (with confirmation)
Built-in Modules display a warning banner and cannot be edited or deleted.
Best practices
- Use clear naming conventions that reflect the system and environment (e.g.,
AWS_Prod,ServiceNow_EU) - Create separate Modules for different environments of the same system to keep production and staging data distinct
- Review Module mappings regularly to stay aligned with changes in upstream source schemas