A maker of measuring instruments has its IT looked after by a small IT service company that accesses all servers via remote maintenance. Attackers take over the service company’s remote maintenance tool and use it over one weekend to encrypt the systems of several customers. The service company did not appear in the manufacturer’s asset register, and nobody had asked how its access was protected. The supply chain brings services into the organization, and with them the risks of the suppliers.
Hardly any organization works alone today. Raw materials, software, cloud services, payroll and transport come from outside, and providers often have deep access to data and systems. Asset category AC11 brings suppliers and your own logistics together so that you can name them in the asset register, assign them to a responsible person and rate them by their protection needs.
What belongs to it?
The catalogue splits the category into two asset classes. One covers who supplies, the other how goods move through the organization and on to customers.
- Suppliers and vendors. Raw material suppliers, for example for steel, active ingredients or yarn, service providers such as an external payroll bureau, a managed service provider or a law firm, technology vendors for software, network hardware and cloud, and product vendors who supply goods for resale, private label products or white-label devices.
- Logistics. Distribution networks of retail partners, fulfilment centres or wholesalers, transport routes such as fixed truck tours, air freight and rail connections, and warehousing systems from the warehouse management system through barcode-based stock tracking to the automated high-bay warehouse.
The warehousing systems show how closely the category is tied to IT: if the warehouse management system fails, shipping stops, even with every parcel sitting on the shelf.
Why the category matters
ISO/IEC 27005 distinguishes primary assets, meaning information and processes with value of their own, from supporting assets on which these rest. The catalogue lists suppliers and vendors as supporting assets and allows your own logistics to be primary assets. The standard’s own example of dependencies between assets already includes an IT maintenance service through which a risk is passed on to the business process.
The standard becomes even clearer in the event-based approach. In Annex A.2.4.1 it describes the organization’s ecosystem, which besides clients and partners explicitly includes service providers, subcontractors and suppliers, and it points out that attackers increasingly exploit the weakest link within it. A supplier with privileged access is therefore often the easiest route to your business assets. Its protection needs follow from the information, systems and processes it can reach or carries.
Typical threats
- G 0.11 Failure or Disruption of Service Providers: insolvency, a strike or an attack at the supplier paralyses your own service.
- G 0.23 Unauthorised Access to IT Systems: attackers use a service provider’s remote maintenance or interface access.
- G 0.20 Information or Products from Unreliable Sources: counterfeit components, software from dubious sources.
- G 0.21 Manipulation of Hardware or Software: tampered deliveries or compromised updates from a vendor.
- G 0.19 Disclosure of Sensitive Information: a service provider loses the data entrusted to it.
- G 0.16 Theft of Devices, Storage Media or Documents: cargo theft in transit or at a transhipment warehouse.
In practice: recording assets in the asset register
Rate by criticality. Create important suppliers and logistics assets as entries and assign category, class and type (→ Asset Register in the Starter Kit). Rate each supplier by the access it has and by what its failure would mean; the details go in the → Supplier Register.
Link access. Link each supplier to the information, systems and processes it can reach. That way it inherits the right protection needs, and you see which requirements belong in the contract.
Check contracts and evidence. Security requirements, notification duties, audit rights and certificates belong in the agreement. The → Supplier Security Policy defines what is required for each rating.
Plan alternatives. For critical suppliers, record whether there is a second source and how a switch would work.
Relations to other categories
In the catalogue, the supply chain generates AC01 Information, such as delivery notes and shipment data, and is controlled by AC02 Software. It supplies software and AC03 Hardware, is administered by people (AC04 Human) and is stored in or delivered to physical assets. It is financed by financial assets and influences them, uses licences for intellectual property and is administered and assessed by the organization. Legal requirements regulate it, the environment (AC10 Environmental) restricts it, and in turn it affects the environment. It constitutes AC12 Relationships, enables and influences the AC13 Market and provides the input for AC14 Processes, which it also triggers.
Effective controls
- A.5.9 Inventory of Information and Other Associated Assets: important suppliers and logistics assets in the register, with a responsible person.
- A.5.12 Classification of Information: the classification of shared data determines the requirements for the supplier.
- A.5.19 Information Security in Supplier Relationships and A.5.20 Addressing Information Security Within Supplier Agreements: define requirements and agree them by contract.
- A.5.21 Managing Information Security in the ICT Supply Chain: manage risks from software, hardware and IT subcontractors.
- A.5.22 Monitoring, Review and Change Management of Supplier Services: keep an eye on services and changes at the supplier.
- A.5.23 Information Security for Use of Cloud Services: govern selection, use and exit for cloud providers.
Sources
- ISO/IEC 27005:2022, Annex A.2.2: Assets, and Annex A.2.4.1: Ecosystem
- ISO/IEC 27002:2022, clauses 5.9, 5.12 and 5.19 to 5.23
- BSI IT-Grundschutz Compendium: elementary threats G 0.11 to G 0.23