BS ISO 22381:2018
$142.49
Security and resilience. Authenticity, integrity and trust for products and documents. Guidelines for establishing interoperability among object identification systems to deter counterfeiting and illicit trade
Published By | Publication Date | Number of Pages |
BSI | 2018 | 30 |
This document gives guidelines for establishing interoperability among independently functioning product identification and related authentication systems, as described in ISO 16678. The permanent transfer of data from one system to another is out of the scope of this document.
It also gives guidance on how to specify an environment open to existing or new methods of identification and authentication of objects, and which is accessible for legacy systems that may need to remain active.
It is applicable to any industry, stakeholder or user group requiring object identification and authentication systems. It can be used on a global scale, or in limited environments. This document supports those involved in planning and establishing interoperation.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
6 | Foreword |
7 | Introduction |
9 | 1 Scope 2 Normative references 3 Terms and definitions |
10 | 4 Abbreviated terms 5 Planning, implementing and controlling systems’ interoperability 5.1 Identify stakeholders and their needs |
11 | 5.2 Organize stakeholders 5.2.1 Identify lead stakeholder 5.2.2 Define roles and responsibilities 5.2.3 Develop a contractual framework |
12 | 5.2.4 Set up an onboarding and leaving process 5.3 Plan architecture 5.3.1 General principles |
13 | 5.3.2 Identify participating OIASs and functional blocs to form the constituents of the I-OP |
14 | 5.3.3 Study types and ownership of attributes to be handled 5.3.4 Specify TEPs for secure I-OP access |
15 | 5.3.5 Specify access rules for users 5.3.6 Define and improve trust levels |
16 | 5.3.7 Outline or delimit the usage of participating OIASs and their functional units 5.3.8 Draft an I-OP architecture 5.3.9 Return information back to the source |
17 | 5.4 Plan and implement operations 5.4.1 Define data exchange formats 5.4.2 Establish trust into the service behind a particular UID 5.4.3 Delimit data inputs and outputs |
18 | 5.4.4 Define storage and custodianship of data inputs and outputs 5.4.5 Define operational responsibilities 5.4.6 Prepare for systems failures 5.4.7 Negotiate alarm responses of common interest |
19 | 5.4.8 Run pilots 5.5 Review and improve 5.5.1 General 5.5.2 Revisit stakeholders’ expectations 5.5.3 Review operations 5.5.4 Review security |
20 | 5.5.5 Review technology |
21 | Annex A (informative) Typical stakeholder interests in an I-OP |
26 | Annex B (informative) The role of trusted entry points for user groups |
27 | Annex C (informative) Types of information exchanged in I-OP architectures |
28 | Bibliography |