Electronic fee collection - Security framework
Introduction: Reader’s guide The development process for a security concept and implementation to protect any existing electronic fee collection (EFC) system normally includes several steps as follows: — definition of the security objectives and policy statements in a security policy; — threat analysis with risk assessment to define the security requirements; — development of the security measures followed by the development of security test specifications. Figure 1 — Development path for the security documents In the second step, each actor in an existing EFC system has to implement the defined security measures and supervise the effectiveness. Security measures which do not work or work incorrectly need to be improved. The development of the EFC security framework follows this approach as closely as possible. The used methodology needs to consider following limitations: — No security policy exists: The security policy can only be defined by the responsible stakeholders and its freedom is only limited by laws and regulations. Nonetheless, this Technical Specification provides basic examples of possible security policies (in Annex E to Annex F). — No risk assessment possible: The risk assessment compares the possible loss for the stakeholder and the required resources (e.g. equipment, knowledge, time, etc.) to perform an attack. It is the trade-off evaluation of the cost and benefit of each countermeasure which is only possible for an implemented system. — No specific system design or conf
Scope: The overall scope of this Technical Specification is an information security framework for all organizational and technical entities of an EFC scheme and in detail for the interfaces between them, based on the system architecture defined in ISO 17573. The security framework describes a set of requirements and associated security measures for stakeholders to implement and thus ensure a secure operation of their part of an EFC system as required for a trustworthy environment according to its security policy. The scope of this Technical Specification comprises the following: — definition of a trust model (Clause 5); Basic assumptions and principles for establishing trust between the stakeholders. — security requirements (Clause 6); — security measures — countermeasures (Clause 7); Security requirements to support actual EFC system implementations. — security specifications for interface implementation (Clause 8); These specifications represent an add-on for security to the corresponding standards. Figure 5 above shows the relevant interfaces and the corresponding relevant interface standards, as illustrated in Figure 6. — key management (Clause 9); Covering the (initial) setup of key exchange between stakeholders and several operational procedures like key renewal, certificate revocation, etc. — security profiles (Annex A); — implementation conformance statement (Annex B) provides a checklist to be used by an equipment supplier, a system implementation, or an actor of a role declaring his conformity to this Technical Specification; — general information security objectives of the stakeholders (Annex C) which provide a basic motivation for the security requirements; — threat analysis (Annex D) on the EFC system model and its assets using two different complementary methods, an attack-based analysis, and an asset-based analysis; — security policy examples (Annex E and Annex F); — recommendations for privacy-focused implementation (Annex G); — proposal for end-entity certificates (Annex H). TECHNICAL SPECIFICATION ISO/TS 19299:2015(E) © ISO 2015 – All rights reserved ISO/TS 19299:2015(E) Figure 6 — Scope of EFC security framework for secure communication The followi