When managing information security and privacy, it's important to understand how vendors, IT systems, and information assets are connected. Together they form the foundation of your organisation's digital ecosystem, and they shape the context of your security and privacy work.
You register each of them once and reuse them everywhere: in risk assessments, processing activities, business processes, incidents and as evidence for framework controls.
| Menu group | Register | Read more |
|---|---|---|
| Vendors, Systems & Processes | Vendors | Parties and customers |
| Customers | Parties and customers | |
| IT Systems | This page | |
| Business Processes | Business processes and BIA | |
| Dependencies | Dependencies | |
| Assessments | Pre-assessments | |
| Operational risk | Business Assets | This page |
| Cyber security | Information assets | This page |
Vendors, customers and IT systems are available when the Cyber security or Privacy module is active. Asset registries belong to the Operational risk and Cyber security modules. What you see also depends on your role. See Role-based access control.
The Vendors register keeps track of the external parties that provide services, software, infrastructure or support, and that may affect your information security or privacy compliance. For example:
The register has two tabs: Suppliers, the parties you have an agreement with yourselves, and Subcontractors, the parties that work for your suppliers. Each supplier can be given a supplier security assessment that calculates a risk score.
Why it matters: Vendors often have access to your systems or data, or process data on your behalf. Their security practices directly affect your organisation's risk.
The IT Systems register gives you an overview of the digital systems your organisation uses, whether they are internal platforms, cloud services or vendor-supplied tools. For example:
Select Add IT system to register a system. Important fields include the system owner, the Vendor that provides it and its subcontractors, how important the system is (1–5), the mode of operation, personal data, third-country transfer, availability requirements, the lifecycle status and Is this an AI system?. Each system can be given an IT system security assessment, and AI systems also an AI Act pre-assessment. See Pre-assessments.
What each system depends on (hosting, login, data flows) is mapped in Dependencies. To register many systems at once, use Import IT systems, see Bulk import.
Why it matters: These systems store, process or transmit your organisation's information assets. Any vulnerabilities in these systems can expose data to unauthorised access or loss.
Assets are registered in two registers, one per module:
IT systems are registered in their own register, not as assets. An asset can be linked to the IT systems that manage it. The asset registries list all the assets you can see, and can be sorted, filtered and searched like other lists. The asset types available are set per module in Settings.
Why it matters: Protecting information assets is at the heart of both information security (confidentiality, integrity, availability) and privacy compliance (e.g. GDPR).
Assets are rated for:
The confidentiality, integrity and availability levels are configured under Settings > Asset classification, and the scale applies to every module. See Settings.