• Technical report
    61 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    61 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document aims to provide an introduction to the topic of creating a conceptual model for storing multidimensional data which is received as XBRL instances that follow the rules defined by European taxonomies published by the European Banking Authority (EBA) or by the European Insurance and Occupational Pensions Authority (EIOPA).

  • Standard
    52 pages
    English language
    sale 15% off
  • Draft
    52 pages
    English language
    sale 15% off

This document provides guidelines for data point modelling for supervising experts. The main body consists of four sections. The interrogative form helps in choosing which section may best answer your question and lead you to a good understanding of the subject matter. After this first introductory section and the section containing terms and definitions, the main part starts to provide basic knowledge about different types of data models and data modelling approaches. The first and the second sections provide an overview of data models in general, in contrast to the third section that highlights the necessity of data modelling for supervisory data. This third section draws on the objectives and background information of the preceding sections. Furthermore, a paragraph classifies the Data Point Model introduced by the Eurofiling Initiative and elaborated by EIOPA and EBA, where many new terms related to DPM are introduced. Another paragraph explains the areas of application for the DPM. The third section concludes with a paragraph introducing a subset of the technical constrains that need to be considered in the creation process of the DPM. The fourth section gives step-by-step instructions on how to create a DPM. The paper concludes with remarks on the progress achieved so far, and provides an outlook on the software that is being developed at the moment to support you during the creation process.

  • Standard
    36 pages
    English language
    sale 15% off
  • Draft
    36 pages
    English language
    sale 15% off

This document defines the Data Point Methodology for the creation of Data Point Models in the context of European supervisory reporting. Data Point Models are published by a European supervisory authority. To reflect the defined structures in a machine-readable form, they can be accompanied by an XBRL taxonomy. It is also possible to extend the described methodology to other environments.

  • Standard
    18 pages
    English language
    sale 15% off
  • Draft
    18 pages
    English language
    sale 15% off

This document defines a common terminology to be used in the context of third-party payment (TPP). Next, it establishes two logical structural models in which the assets to be protected are clarified. Finally, it specifies security objectives based on the analysis of the logical structural models and the interaction of the assets affected by threats, organizational security policies and assumptions. These security objectives are set out in order to counter the threats resulting from the intermediary nature of TPPSPs offering payment services compared with simpler payment models where the payer and the payee directly interact with their respective account servicing payment service provider (ASPSP). This document assumes that TPP-centric payments rely on the use of TPPSP credentials and the corresponding certified processes for issuance, distribution and renewal purposes. However, security objectives for such processes are out of the scope of this document. NOTEÂ Â Â Â Â Â This document is based on the methodology specified in the ISO/IEC 15408 series. Therefore, the security matters that do not belong to the TOE are dealt with as assumptions, such as the security required by an information system that provides TPP services and the security of communication channels between the entities participating in a TPP business.

  • Standard
    40 pages
    English language
    sale 15% off
  • Draft
    40 pages
    English language
    sale 15% off

This document defines and describes the structure for the codes for an internationally valid system to classify financial instruments. The classification system applies to financial instruments negotiated internationally as well as to domestic instruments. The term “financial instruments” refers not only to classical securities and derivatives but also covers the innovative financial products that have emerged in different markets (a trend that is expected to continue in the future). This document is intended for use in any application in the trading and administration of financial instruments in the international securities business. Insofar as the trading and administration of securities do not affect other countries, the application of this document remains at the discretion of the responsible national bodies, such as stock exchanges, banks, brokers, regulatory bodies and other institutions active in the securities field. In principle, the CFI code reflects characteristics that are defined when a financial instrument is issued and that remain unchanged during its entire lifetime. However, a few events that can lead to a new CFI code for the same instrument are anticipated, such as the changing of voting rights or ownership restrictions by a stockholders' meeting.

  • Standard
    9 pages
    English language
    sale 15% off
  • Standard
    9 pages
    English language
    sale 15% off
  • Draft
    9 pages
    English language
    sale 15% off

This document specifies a general framework, including principles, requirements and guidance for assessing, measuring, monitoring and reporting on investments and financing activities in relation to climate change and the transition into a low-carbon economy. The assessment includes the following items: —   the alignment (or lack thereof) of investment and financing decisions taken by the financier with low-carbon transition pathways, adaptation pathways, and climate goals; —   the impact of actions through the financier’s investment and lending decisions towards the achievement of climate goals in the real economy, i.e. mitigation (greenhouse gas emissions) and adaptation (resilience); —   the risks to owners of financial assets (e.g. private equities, listed stocks, bonds, loans) arising from climate change. To support the financier’s assessment of the impact of investment and lending decisions, this document provides guidance for the financier on how to: —   set targets and determine metrics to be used for tracking progress related to the low-carbon transition pathways of investees; —   determine low-carbon transition and adaptation trajectories of investees; —   document the causality or linkage between its climate action and its outputs, outcomes and impacts. This document is applicable to financiers, i.e. investors and lenders. It guides their reporting activities to the following third parties: shareholders, clients, policymakers, financial supervisory authorities and non-governmental organizations.

  • Standard
    43 pages
    English language
    sale 15% off
  • Standard
    47 pages
    French language
    sale 15% off
  • Draft
    43 pages
    English language
    sale 15% off
  • Draft
    52 pages
    French language
    sale 15% off

This document provides a uniform structure for the identification of financial instruments as well as referential instruments (see Annex A) using a unique identification code and associated minimum descriptive data (see Annex B).

  • Standard
    15 pages
    English language
    sale 15% off
  • Standard
    15 pages
    English language
    sale 15% off
  • Draft
    15 pages
    English language
    sale 15% off

The standard defines the transfer of electronic documents between stakeholders in the insurance industry (for
example between insurer and intermediary).
The standard specifies:
 the semantic process for the transfer of documents (for example insurance policy, claim notification,
correspondence) that may be transferred as an attached file and
 a limited number of meta data describing the document (for example type of document, identification of
insurer, intermediary and client, policy number, claim number).

  • Standard
    65 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document describes the Registration Authority (RA) responsible for the registry of IBAN formats that conform with ISO 13616-1, the procedures for registering IBAN formats that conform with the ISO 13616 series and the structure of the registry.

  • Standard
    3 pages
    English language
    sale 15% off
  • Draft
    3 pages
    English language
    sale 15% off

This document specifies the elements of an international bank account number (IBAN) used to facilitate the processing of data internationally in data interchange, in financial environments as well as within and between other industries. The IBAN is designed for automated processing but can also be used conveniently in other media interchange when appropriate (e.g. paper document exchange). This document does not specify internal procedures, file organization techniques, storage media or languages to be used in its implementation, nor is it designed to facilitate the routing of messages within a network. It is applicable to the textual data which might be conveyed through a system (network).

  • Standard
    8 pages
    English language
    sale 15% off
  • Draft
    8 pages
    English language
    sale 15% off

This document specifies how to describe the characteristics of banking products or services (BPoS) from a customer's perspective. Characteristics of a BPoS can be observed from different facets, called key elements, which are divided into three groups: required, optional or voluntary elements. This document elaborates on the purpose, content and description approach for the required and optional key elements. Six levels of conformity are described in this document which are intended to allow a customer to assess the coverage of key elements in a BPoS. The logical and physical formats to express key elements are also defined. This document excludes requirements of a BPoS itself and specific value ranges of any key element are out of the scope. This document guides the provider of BPoS in describing their products or services with the intent to help customers understand or compare specific BPoS. It is not applicable to describing securities or insurance-related products or services. BPoS can be issued by banks and other institutions.

  • Standard
    51 pages
    English language
    sale 15% off

This document specifies the minimum elements of an unambiguous legal entity identifier (LEI) scheme to identify the legal entities relevant to any financial transaction. It is applicable to "legal entities", which include, but are not limited to, unique parties that are legally or financially responsible for the performance of financial transactions or have the legal right in their jurisdiction to enter independently into legal contracts, regardless of whether they are incorporated or constituted in some other way (e.g. trust, partnership, contractual). It includes governmental organizations, supranationals and individuals when acting in a business capacity[1], but excludes natural persons. It also includes international branches as defined in 3.5. The LEI is designed for automated processing. It can also be conveniently used in other media interchange when appropriate (e.g. paper document exchange). NOTE Examples of eligible legal entities include, without limitation: — all financial intermediaries; — banks and finance companies; — international branches; — all entities that issue equity, debt or other securities for other capital structures; — all entities listed on an exchange; — all entities that trade financial instruments or are otherwise parties to financial transactions, including business entities, pension funds and investment vehicles such as collective investment funds (at umbrella and sub-fund level) and other special purpose vehicles that have a legal form; — all entities under the purview of a financial regulator and their affiliates, subsidiaries and holding companies; — sole traders (as an example of individuals acting in a business capacity); — counterparties to financial transactions. [1] As stated by the LEI Regulatory Oversight Committee on 30 September 2015.

  • Standard
    8 pages
    English language
    sale 15% off

This document specifies a standardised way of embedding the legal entity identifier (LEI) code, as represented in ISO 17442-1, in digital certificates, represented by the International Telecommunications Union (ITU) Recommendation X.509 and its ISO equivalent standard, ISO/IEC 9594-8. This document specifies the structure of a public key certificate conforming with ISO/IEC 9594-8 in which the LEI is embedded.

  • Standard
    5 pages
    English language
    sale 15% off

This document specifies the elements of an unambiguous scheme to identify a financial transaction uniquely whenever useful and agreed by the parties or community involved in the transaction. It does not specify the timing of assignment of who should be responsible for its generation, so as not to limit its usage or relevance, nor does it consider a need to establish a data record for the unique transaction identifier (UTI) itself.

  • Standard
    3 pages
    English language
    sale 15% off

This International Standard specifies the elements and structure of a universal identifier code, the business identifier code (BIC), for financial and non-financial institutions, for which such an international identifier is required to facilitate automated processing of information for financial services. The BIC is used for addressing messages, routing business transactions and identifying business parties. This International Standard applies to organizations and excludes individual persons.

  • Standard
    6 pages
    English language
    sale 15% off
  • Standard
    9 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document gives an overview of existing and currently used financial instrument identifiers. It shows which instrument identifiers, ticker symbols and proprietary codes are assigned via a standardized scheme to instruments of all asset classes. It focuses on providing an overview of the landscape and not on evaluating the schemes. Several aspects of the detailed trade cycle (a few examples being book building/primary, order entry management, execution management and trade confirmation matching) are excluded as their complexity would reduce the readability of the overview. Similarly, the level of complexity involved in properly representing the shifting perspectives of what is considered a financial instrument, based on a particular function being performed, is excluded.

  • Technical report
    4 pages
    English language
    sale 15% off

This International Standard provides a uniform structure for the identification of fungible and nonfungible
securities and financial instruments (see Annex A) using a unique identification number and
associated minimum descriptive data (see Annex B).

  • Standard
    11 pages
    English language
    sale 15% off
  • Standard
    16 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO/TR 21941:2017 reports the findings of research into the interface between third-party payment service providers (TPPs) and account servicing payment service providers (ASPSPs).

  • Technical report
    19 pages
    English language
    sale 15% off

ISO 20275:2017 specifies the elements of an unambiguous scheme to identify the distinct entity legal forms in a jurisdiction. Its aim is to enable legal forms within jurisdictions to be codified and thus facilitate the classification of legal entities according to their legal form. It is not the purpose of the document to give the comparison or alignment of entity legal forms across different jurisdictions, so as not to limit its usage and relevance.

  • Standard
    4 pages
    English language
    sale 15% off

ISO 12812-1:2017 defines the general framework of mobile financial services (payment and banking services involving a mobile device), with a focus on: a) a set of definitions commonly agreed by the international financial industry; b) the opportunities offered by mobile devices for the development of such services; c) the promotion of an environment that reduces or minimizes obstacles for mobile financial service providers who wish to provide a sustainable and reliable service to a wide range of customers (persons and businesses), while ensuring that customers' interests are protected; d) the different types of mobile financial services accessed through a mobile device including mobile proximate payments, mobile remote payments and mobile banking, which are detailed in other parts of ISO 12812; e) the mobile financial services supporting technologies; f) the stakeholders involved in the mobile payment ecosystems. ISO 12812-1:2017 includes the following informative annexes: - an overview of other standardization initiatives in mobile financial services (Annex A); - a description of possible mobile payment business models (Annex B); - a description of typical payment instruments which may be used (Annex C).

  • Standard
    33 pages
    English language
    sale 15% off

ISO/TS 12812-3:2017 specifies the interoperable lifecycle management of applications used in mobile financial services. As defined in ISO 12812‑1, an application is a set of software modules and/or data needed to provide functionality for a mobile financial service. This document deals with different types of applications which is the term used to cover authentication, banking and payment applications, as well as credentials. Clause 5 describes the basic principles required, or to be considered, for the application lifecycle management. Because several implementations are possible with impacts on the lifecycle, this document describes the different architectures for the location of the application and the impacts of the different scenarios regarding the issuance of the secure element when present (see Clause 6), the different roles for the management of the application lifecycle and the domains of responsibilities (see Clause 7). It also specifies functions and processes in the application lifecycle management (see Clause 8) and describes scenarios of service models and roles of actors (see Clause 9).

  • Technical specification
    12 pages
    English language
    sale 15% off

ISO/TS 12812-5:2017 focuses on mechanisms by which a person ("consumer", "payer" or "business") uses a mobile device to initiate a payment to a business entity ("merchant" or "payee"). Such a payment may use the traditional merchant point of interaction (POI) system, where the manner of settling the payment follows well-established merchant services paradigms. Additionally, there are other ways for a consumer to make a payment to a merchant, using the mobile device to initiate, authorize and process transactions outside of traditional payment networks using secure payment instruments. Accordingly, this document supports both "push" and "pull" payments (i.e. transactions that are pushed or transmitted from a mobile device into a POI or pulled or received into a mobile device or POI), which are initiated and/or confirmed by a consumer to purchase goods and or services, including proximate payments, remote secure server payments, as well as mobile payments that leverage other technologies [e.g. cloud computing, quick response ("QR") codes, biometrics, geo-location and other methods to authenticate and authorize the transaction]. One of the most important aspects of the MFS environment is mobile payments to businesses. There are many ways a consumer, or a business as a consumer, can make a payment to a merchant. ISO 12812 provides a comprehensive standard for using the mechanisms involved in mobilizing the transfer of funds regardless of who is involved in the process. This document is intended to be used by potential implementers of mobile retail payment solutions, while ISO 12812-4 is intended for potential implementers of solutions for mobile payments to persons. NOTE ISO 12812‑1:2017, 5.4 explains the differences in the use of these terms. As such, the ISO 12812 (all parts) seeks to support all possible technologies and is not designed to highlight or endorse specific technologies in the competitive marketplace. Although this document deals with mobile payments made by a consumer or a business acting as a consumer, which transactions are subject to a variety of consumer protection requirements, in terms of the relationship to the MFSP, the consumer (or business) is the customer of the MFSP. Nevertheless, this document will use the term "consumer."

  • Technical specification
    55 pages
    English language
    sale 15% off

ISO/TS 12812-4:2017 provides comprehensive requirements and recommendations, as well as specific use cases for implementation of interoperable mobile payments-to-persons. The emphasis is placed on the principles governing the operational functioning of mobile payments-to-persons systems and processes, as well as the presentation of the underlying technical, organizational, business, legal and policy issues, leveraging legacy infrastructures of existing payment instruments (see ISO 12812‑1:2017, Annex C). ISO/TS 12812-4:2017 includes the following items: a) requirements applicable to mobile payments-to-persons; b) recommendations regarding mechanisms involved in the operation of interoperable mobile payments-to-persons; c) a description of the different use cases for mobile payments-to-persons; d) a generic interoperability model for the provision of different mobile payments-to-persons; e) recommendations for the technical implementation of the generic architectures for the mobile payments-to-persons program; f) recommendations for mobile remittances; g) use cases with the corresponding transaction flows; h) discussion of the financial inclusion of unbanked and underbanked persons (Annex A); i) some legal aspects to consider for mobile payments-to-persons (Annex B). ISO/TS 12812-4:2017 is structured as follows: - Clause 6 sets forth the requirements that a mobile payments-to-persons program must comply with. - Clauses 7, 8 and 9 provide the different levels of implementation for the interoperability of mobile payments-to-persons. - Clause 7 describes the interoperability principles for mobiles payments-to-persons. - Clause 8 describes: a three-layer high-level architecture for mobile payments-to-persons programs; payments instruments sustained by these programs; processing details for a series of significant use cases of mobile payments-to-persons using these payment instruments. - Clause 9 provides a step-by-step data flow description for different mobile payments-to-persons implementations: bank-centric, non-bank centric and card-centric. They can be mapped into the processing use cases of Clause 8, where abstraction is made in the nature of the payment service providers.

  • Technical specification
    36 pages
    English language
    sale 15% off

ISO 12812-2:2017 describes and specifies a framework for the management of the security of MFS. It includes - a generic model for the design of the security policy, - a minimum set of security requirements, - recommended cryptographic protocols and mechanisms for mobile device authentication, financial message secure exchange and external authentication, including the following: point-to-point aspects to consider for MFS; end-to-end aspects to consider; security certification aspects; generation of mobile digital signatures; - interoperability issues for the secure certification of MFS, - recommendations for the protection of sensitive data, - guidelines for the implementation of national laws and regulations (e.g. anti-money laundering and combating the funding of terrorism (AML/CFT), and - security management considerations. In order to avoid the duplication of standardization work already performed by other organizations, this document will reference other International Standards as required. In this respect, users of this document are directed to materials developed and published by ISO/TC 68/SC 2 and ISO/IEC JTC 1/SC 27.

  • Technical specification
    56 pages
    English language
    sale 15% off

ISO 18774:2015 defines and describes rules for an internationally valid system for building short names of any kind of financial instrument within a defined structure. This International Standard is intended for use in any application in the trading and administration of securities globally. The FISN has been developed after taking into account the need of human-readability as well as interoperability with existing standards and systems.

  • Standard
    12 pages
    English language
    sale 15% off

ISO 4217:2015 specifies the structure for a three-letter alphabetic code and an equivalent three-digit numeric code for the representation of currencies. For those currencies having minor units, it also shows the decimal relationship between such units and the currency itself. The scope of this International Standard also includes funds and precious metals. ISO 4217:2015 also includes basic guidelines for its maintenance. ISO 4217:2015 is intended for use in any application of trade, commerce and banking, where currencies and, where appropriate, funds are required to be described. It is designed to be equally suitable for manual users and for those employing automated systems.

  • Standard
    5 pages
    English language
    sale 15% off

ISO 9362:2014 specifies the elements and structure of a universal identifier code, the business identifier code (BIC), for financial and non-financial institutions, for which such an international identifier is required to facilitate automated processing of information for financial services. The BIC is used for addressing messages, routing business transactions and identifying business parties. This International Standard applies to organizations and excludes individual persons.

  • Standard
    6 pages
    English language
    sale 15% off
  • Standard
    9 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 20022-4:2013 was prepared to complement the ISO 20022 Metamodel, as specified in ISO 20022-1:2013, with the XML syntax transformation rules to be applied by the ISO 20022 Registration Authority in order to translate an ISO 20022 compliant MessageDefinition into an XML Schema for the description and validation of XML Messages. It specifies the transformation rules from level 3 to level 4. It is a deterministic transformation, meaning that the resulting XML Schema is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation.

  • Standard
    22 pages
    English language
    sale 15% off

ISO 20022-5:2013 was prepared to complement ISO 20022-1:2013. The reverse engineering guidelines explain how to extract relevant information from existing IndustryMessageSets in order to prepare the submission to the ISO 20022 Registration Authority of equivalent, ISO 20022 compliant BusinessTransactions and MessageSets. The ISO 20022 Repository will contain all ISO 20022 compliant BusinessTransactions and MessageSets, as outlined in ISO 20022-1:2013.

  • Standard
    36 pages
    English language
    sale 15% off

ISO 20022-8:2013 describes the transformation rules to generate ASN.1 abstract syntax from an ISO 20022 compliant MessageDefinition. The generated abstract syntax is for the description and validation of Messages. The transformation rules are a transformation from Level 3 to Level 4. It is a deterministic transformation, meaning that the resulting ASN.1 is completely predictable for a given MessageDefinition. There is neither manual input to the transformation itself nor manual adjustment to the result of the transformation. ISO 20022-8:2013 is the ASN.1 equivalent of ISO 20022-4:2013. In ISO 20022-4:2013 the abstract syntax generated is XML Schema; in ISO 20022-8:2013 it is ASN.1. In ISO 20022-4:2013 the only encoding supported is UTF-8 XML; in ISO 20022-8:2013 there are multiple encodings supported for ASN.1. These include all the standard encodings, but in addition the ability to register custom encodings in ECN.

  • Standard
    25 pages
    English language
    sale 15% off

ISO 20022-1:2013 consists of: the overall description of the modelling approach; the overall description of the ISO 20022 Repository contents; a high-level description of the input to be accepted by the Registration Authority to feed/modify the Repository's DataDictionary and BusinessProcessCatalogue; a high-level description of the Repository output to be made publicly available by the Registration Authority. BusinessTransactions and Message Sets complying with ISO 20022 can be used for electronic data interchange among any industry participants (financial and others), independently of any specific communication network. Network-dependent rules, such as message acknowledgement and message protection, are outside the scope of ISO 20022.

  • Standard
    152 pages
    English language
    sale 15% off

ISO 20022-3:2013 describes the modelling workflow, complementing ISO 20022-1:2013 and ISO 20022-2:2013. The modelling workflow describes the required steps a modeller follows in order to develop and maintain standardized BusinessTransactions and MessageSets. ISO 20022-3:2013 is not intended to describe what will be the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022-7). Examples are provided only to illustrate the modelling methodology and are not normative.

  • Standard
    24 pages
    English language
    sale 15% off

ISO 20022-2:2013 defines the UML Profile for ISO 20022. In essence, it defines how to use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1:2013. In so doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of additional concrete syntaxes for the Metamodel, such as a textual concrete syntax. The Profile defines how to represent in UML each of the Metamodel's Scope Level Elements (Level 1), Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements that are scoped across the levels. Therefore, the Profile covers all of the Metamodel's Packages, except for the following: · ISO20022::Metamodel::ConceptualLevel::MessageTransport · ISO20022::Metamodel::LogicalLevel::Reversing · ISO20022::Metamodel::LogicalToPhysicalTransformation · ISO20022::Metamodel::PhysicalLevel The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some dependencies. ISO 20022-2:2013 is only applicable when UML is used.

  • Standard
    71 pages
    English language
    sale 15% off

ISO 20022-7:2013 specifies the responsibilities of the following bodies, which are involved in the registration and maintenance of the ISO 20022 Repository. The Registration Authority (RA) is the operating authority responsible for the registration and maintenance of the ISO 20022 Repository and for providing access to the information described in ISO 20022-1:2013. The RA is assisted by different Standards Evaluation Groups (SEG), i.e. groups of industry experts responsible for specific Business Areas of the Repository. A Technical Support Group (TSG) advises the SEGs, the RA, developers and communities of users on the technical implementation of ISO 20022. The Registration Management Group (RMG) is the governing body of the overall registration process and the appeal body for the communities of users, Submitting Organisations, the RA, the SEGs and the TSG. It monitors the registration process performance.

  • Standard
    5 pages
    English language
    sale 15% off

ISO 20022-6:2013 specifies the characteristics of the MessageTransportSystem required for an ISO 20022 BusinessTransaction and MessageDefinition. Changes to the value of the MessageTransport Characteristics can affect the BusinessTransaction and MessageDefinition. Each BusinessTransaction in the ISO 20022 Repository is associated with a MessageTransportMode. The MessageTransportMode specifies the values for the MessageTransportCharacteristics.

  • Standard
    7 pages
    English language
    sale 15% off

ISO 10383:2012 specifies a universal method of identifying exchanges, trading platforms, regulated or non-regulated markets and trade reporting facilities as sources of prices and related information in order to facilitate automated processing. It is intended for use in any application and communication for identification of places where a financial instrument is listed (place of official listing), where a related trade is executed (place of trade), and where trade details are reported (trade reporting facility).

  • Standard
    5 pages
    English language
    sale 15% off

ISO/TR 14742:2010 provides a list of recommended cryptographic algorithms for use within applicable financial services standards prepared by ISO/TC 68. It also provides strategic guidance on key lengths and associated parameters and usage dates. The focus is on algorithms rather than protocols, and protocols are in general not included in ISO/TR 14742:2010. ISO/TR 14742:2010 deals primarily with recommendations regarding algorithms and key lengths. The categories of algorithms covered in ISO/TR 14742:2010 are: block ciphers; stream ciphers; hash functions; message authentication codes (MACs); asymmetric algorithms; digital signature schemes giving message recovery, digital signatures with appendix, asymmetric ciphers; authentication mechanisms; key establishment and agreement mechanisms; key transport mechanisms. ISO/TR 14742:2010 does not define any cryptographic algorithms; however, the standards to which ISO/TR 14742:2010 refers may contain necessary implementation information as well as more detailed guidance regarding choice of security parameters, security analysis, and other implementation considerations.

  • Technical report
    31 pages
    English language
    sale 15% off

ISO 11649:2009 specifies the elements of a structured creditor reference (RF Creditor Reference) used to facilitate the processing of data in data interchange and in the financial services, as well as between other business domains. The RF Creditor Reference is designed for use in an automated processing environment, but can also be implemented in other media interchanges (e.g. paper document exchange). ISO 11649:2009 does not specify internal procedures, file organization techniques, storage media, languages, etc. to be used in its implementation. It is applicable only to the textual data that can be conveyed through a system or network.

  • Standard
    7 pages
    English language
    sale 15% off

ISO 22307:2008 recognizes that a privacy impact assessment (PIA) is an important financial services and banking management tool to be used within an organization, or by “contracted” third parties, to identify and mitigate privacy issues and risks associated with processing consumer data using automated, networked information systems. ISO 22307:2008 describes the privacy impact assessment activity in general, defines the common and required components of a privacy impact assessment, regardless of business systems affecting financial institutions, and provides informative guidance to educate the reader on privacy impact assessments. A privacy compliance audit differs from a privacy impact assessment in that the compliance audit determines an institution's current level of compliance with the law and identifies steps to avoid future non-compliance with the law. While there are similarities between privacy impact assessments and privacy compliance audits in that they use some of the same skills and that they are tools used to avoid breaches of privacy, the primary concern of a compliance audit is simply to meet the requirements of the law, whereas a privacy impact assessment is intended to investigate further in order to identify ways to safeguard privacy optimally. ISO 22307:2008 recognizes that the choices of financial and banking system development and risk management procedures are business decisions and, as such, the business decision makers need to be informed in order to be able to make informed decisions for their financial institutions. ISO 22307:2008 provides a privacy impact assessment structure (common PIA components, definitions and informative annexes) for institutions handling financial information that wish to use a privacy impact assessment as a tool to plan for, and manage, privacy issues within business systems that they consider to be vulnerable.

  • Standard
    28 pages
    English language
    sale 15% off

ISO 19092:2008 describes the security framework for using biometrics for authentication of individuals in financial services. It introduces the types of biometric technologies and addresses issues concerning their application. ISO 19092:2008 also describes the architectures for implementation, specifies the minimum security requirements for effective management, and provides control objectives and recommendations suitable for use by a professional practitioner. The following are within the scope of ISO 19092:2008: usage of biometrics for the authentication of employees and persons seeking financial services by: verification of a claimed identity; identification of an individual; validation of credentials presented at enrolment to support authentication as required by risk management; management of biometric information across its life cycle comprised of the enrolment, transmission and storage, verification, identification and termination processes; security of biometric information during its life cycle, encompassing data integrity, origin authentication and confidentiality; application of biometrics for logical and physical access control; surveillance to protect the financial institution and its customers; security of the physical hardware used throughout the biometric information life cycle. ISO 19092:2008 provides the mandatory means whereby biometric information may be encrypted for data confidentiality or other reasons.

  • Standard
    77 pages
    English language
    sale 15% off

ISO 18774:2005 defines and describes rules for an internationally valid system for building short names of any kind of financial instrument within a defined structure. The FISN applies to both international and domestic financial instruments as covered by ISO 10962. The term "financial instruments" refers not only to classical securities, it also covers the innovative financial products that have emerged in different markets - a trend that is expected to continue in the future. ISO 18774:2005 is intended for use in any application in the trading and administration of securities globally.

  • Draft
    8 pages
    English language
    sale 15% off
  • Draft
    14 pages
    English language
    sale 15% off
  • Draft
    18 pages
    French language
    sale 15% off
  • Draft
    11 pages
    English language
    sale 15% off
  • Draft
    14 pages
    French language
    sale 15% off
  • Draft
    14 pages
    English language
    sale 15% off
  • Draft
    16 pages
    French language
    sale 15% off