Information Session on T2S User Connectivity



Similar documents
Data Migration Tool Requirements and Related Procedures

T2S Non Functional Tests

T2S financials: status update

Overview of Message Retrieval capabilities on SWIFTNet

ISO COMPLIANCE WITH OBSERVEIT

T2S General Technical Specifications

Control and management of privileged users

Cloud-based Managed Services for SAP. Service Catalogue

General Computer Controls

Strong authentication of GUI sessions over Dedicated Links. ipmg Workshop on Connectivity 25 May 2012

REGULATIONS FOR THE SECURITY OF INTERNET BANKING

Customized Cloud Solution

HIPAA: MANAGING ACCESS TO SYSTEMS STORING ephi WITH SECRET SERVER

DISASTER RECOVERY. Omniture Disaster Plan. June 2, 2008 Version 2.0

Electronic Document and Record Compliance for the Life Sciences

How To Ensure The C.E.A.S.A

Securing the Service Desk in the Cloud

itg CloudBase is a suite of fully managed Hybrid & Private Cloud Services ready to support your business onwards and upwards into the future.

Course Outline: Course 6317: Upgrading Your SQL Server 2000 Database Administration (DBA) Skills to SQL Server 2008 DBA Skills

Market Data + Services. Advanced outsourcing solutions. IT Hosting and Managed Services

CLOUD SERVICES FOR EMS

Blackboard Collaborate Web Conferencing Hosted Environment Technical Infrastructure and Security

Microsoft SQL Server 2008 R2 Enterprise Edition and Microsoft SharePoint Server 2010

Connectivity. Alliance Access 7.0. Database Recovery. Information Paper

ITIL A guide to Event Management

ITIL: Service Operation

T2S Non Repudiation of Origin (NRO)

San Francisco Chapter. Information Systems Operations

T2S PROGRAMME OFFICE. Connecting to T2S. Technical Session. June 25 th, Colt Telecom Group Limited. All rights reserved.

Agio Remote Monitoring and Management

UNIFIED MEETING 5 SECURITY WHITEPAPER INFO@INTERCALL.COM INTERCALL.COM

Dedicated Links Connectivity Specifications

Information security controls. Briefing for clients on Experian information security controls

Administering Microsoft SQL Server Databases

DISK IMAGE BACKUP. For Physical Servers. VEMBU TECHNOLOGIES TRUSTED BY OVER 25,000 BUSINESSES

Administering Microsoft SQL Server Databases

Fully Managed IT Support. Proactive Maintenance. Disaster Recovery. Remote Support. Service Desk. Call Centre. Fully Managed Services Guide July 2007

Intrado Inc. (as successor in interest to Connexon Telecom Inc) Support Policy

StreamServe Persuasion SP5 StreamStudio

Ongoing Help Desk Management Plan

Data Backup and Restore (DBR) Overview Detailed Description Pricing... 5 SLAs... 5 Service Matrix Service Description

Security Assessment Report

User Guide & Implementation Guidelines for using the Transaction Delivery Agent (TDA) 3.0

Troubleshooting BlackBerry Enterprise Service 10 version Instructor Manual

Upgrading Your SQL Server 2000 Database Administration (DBA) Skills to SQL Server 2008 DBA Skills Course 6317A: Three days; Instructor-Led

Network Monitoring. Chu-Sing Yang. Department of Electrical Engineering National Cheng Kung University

Draft Information Technology Policy

Connectivity. Alliance Access 7.0. Database Recovery. Information Paper

How To Create A Network Access Control (Nac) Solution

BMC s Security Strategy for ITSM in the SaaS Environment

System Description of the Date Center System Relevant to Security and Availability (SOC 3) November 1, 2011 through April 30, 2012

Troubleshooting and Maintaining Cisco IP Networks Volume 1

Administering Microsoft SQL Server Databases

SCHEDULE 1 SERVICE DESCRIPTION

CounselorMax and ORS Managed Hosting RFP 15-NW-0016

Course 20462C: Administering Microsoft SQL Server Databases

UC4 Software: HELPING IT ACHEIVE SARBANES-OXLEY COMPLIANCE

Security in Space: Intelsat Information Assurance

Information Technology Branch Access Control Technical Standard

Administering Microsoft SQL Server Databases

State of Wisconsin DET File Transfer Protocol Service Offering Definition (FTP & SFTP)

ITIL A guide to event management

Simple Software for a Business Continuity Plan and a Disaster Recovery Plan (BCP DRP) pdf ppt

Clarity in the Cloud. Defining cloud services and the strategic impact on businesses.

Administering Microsoft SQL Server Databases

Introducing Cisco Voice and Unified Communications Administration Course ICOMM v8.1; 5 Days, Instructor-led

Feature and Technical

SUPPLIER SECURITY STANDARD

OX Guard Product Guide v1.0 V1.0

Administering Microsoft SQL Server Databases

NETWORK SERVICES WITH SOME CREDIT UNIONS PROCESSING 800,000 TRANSACTIONS ANNUALLY AND MOVING OVER 500 MILLION, SYSTEM UPTIME IS CRITICAL.

ETSI TS V2.1.1 ( ) Technical Specification

Department of Industry and Science

NASA Consolidated Active Directory Overview ( August 20, 2012 ) Les Chafin Infrastructure Engineering HPES

Evaluation Guide. Powerful & Immediate Business Web Security via the Cloud

ENABIL Managed Services

Capacity Management Plan

BroadCloud PBX Customer Minimum Requirements

Data Center Colocation - SLA

VODAFONE G-CLOUD SMS-SERVICE

T2S Special Series I Issue No 1 I April 2012 I T2S benefits: much more than fee reductions

2014 Cash management in TARGET2-Securities with the Banque de France Blueprint Version 1 February 2014

Adopting Cloud Computing with a RISK Mitigation Strategy

BlackShield ID Agent for Terminal Services Web and Remote Desktop Web

Transcription:

Information Session on T2S User Connectivity Technical and Operational criteria for the selection of T2S Network Providers Silvio Orsini T2S Infrastructure Co-ordinator Frankfurt,14 July 2010 1

Disclaimer The following slides summarise the main aspects of the current considerations of the Eurosystem with respect to technical criteria on the basis of which the T2S Network Providers will be selected. Although some of the issues presented can be considered fairly stable and will most likely be part of the final decision, others are not, and might therefore be dropped or substantially altered. Consequently, these slides should by no means be used by any T2S Actor or potential T2S Network Provider to make any decisions or investments with respect to connectivity in T2S. Although this presentation has been delivered to a number of CSDs that have - together with the Eurosystem - signed the T2S Memorandum of Understanding, they have been published on the ECB website in order to give all economic actors equal and simultaneous information about the status of the T2S connectivity discussions. 2

Summary 1. Introduction 2. Volumetric assumptions 3. Selection criteria 4. Organization, operation and plan 3

1. Introduction The T2S platform The T2S platform widens over three Regions: Region 1 Italy Region 2 Germany Region 3 France The remote access to the platform is enabled by VANs Region 1 and region 2 are directly connected to the VANs Region 3 relies on the accesses to VANs at region 1 & 2 (using the internal 4CB network) 4

1. Introduction Responsibility T2S s responsibility ends at connection point P The network interface at T2S platform and user domain are technically decoupled How the user interface is defined is not specified by T2S Notary log middleware T2S platform domain P GW VAN VAN VAN U GW Users domain The gateway (GW) is the VAN termination-end under the VAN providers responsibility 5

1. Introduction Connectivity architecture The VANs are connected to the 4 sites avoiding any single point of failure The VANs take into account workload management and periodic swaps (i.e. rotation, recovery) Users do not perceive in which Region a module is running Rotation/recovery is transparent (no changes in user configuration is requested) T2S platform domain Site 1 Region 2 Region 1 Site 2 Site 3 Site 4 Gateway Gateway Gateway Gateway VAN domain network user domain T2S actor (user or application) 6

2. Volumetric assumptions Volume of transactions With reference to: T2S General Technical Specifications - General Technical Design version 2.2.0 7

2. Volumetric assumptions 2014 volume breakdown The following figures show the estimated volumes to be managed by T2S core system (the mainframe) and the archiving platform in the first year of production 8

2. Volumetric assumptions Network workload (2) Each VAN provider shall size its infrastructure based on its expected market share (theoretically it can also be equal to 100%) and shall size the infrastructure to ensure it meets performance and volume requirements Capacity planning breakdown data shall be provided to T2S administrator every year (for sizing and monitoring purpose) 9

3. Selection criteria The VAN services T2S connectivity services shall support file and message transfer, real-time (A2A) file and message transfer, store-and-forward (A2A) web access to T2S platform (U2A) 10

3. Selection criteria Message and file differentiation Message is a data structure containing a single financial instruction or information based on ISO20022 standard (maximum message length will be defined) File is a data structure containing two or more messages, (maximum message length will be defined) 11

3. Selection criteria Real-time file/message transfer T2S and Users are able to exchange messages and files A real-time message exchange (request-response) shall be completed within few seconds; If no response is received in this timeframe a timeout message shall be generated by the VAN and sent to the sender 12

3. Selection criteria Store and forward file/message transfer The sender can transmit message or file even when the receiver is not available The message/file is delivered by the VAN as soon as the receiver becomes available VAN shall provide to the sender a delivery notification failure after a maximum number of failed retries when the receiver is available after a number of days in case the receiver is not reachable 13

3. Selection criteria T2S Business Continuity support VANs shall support T2S Business continuity without any user intervention or impact on user configuration in case of intra-region recovery, between primary and secondary site in the same region, on request of 4CB staff, VANs are requested to switch the traffic in few minutes in case of inter-region recovery, between the two Regions, on request of 4CB staff, VANs are requested to switch the traffic in few minutes on periodic rotation occurrence (e.g. almost every six months), the VAN provider must switch the traffic between the two Region, on request of 4CB staff, during a week-end, in few minutes (planned operation) 14

3. Selection criteria Restart after disaster 1. Usage of VAN message retrieval service VANs resend instructions, settlement confirmations, static data changes, and maintenance instructions the same account positions can be rebuild with a reasonable likelihood (but no guarantee) 2. As an alternate option the users should resend messages and files the operational risk would significantly increase because of the needed interaction with many parties a huge co-ordination effort is needed in relation to testing message recovery 15

3. Selection criteria Recovery of the VAN The VAN shall automatically manage its recovery, exploiting the redundancies, to assure the service continuity T2S is not going to rotate in case of the regional disaster of a single VAN (users of that VAN will not be able access T2S platform) Recovery from one VAN to another is a user responsibility 16

3. Selection criteria Security features VAN shall provide the technical infrastructure to exchange messages in compliance with strict security requirements Confidentiality Integrity User identification and access control Non repudiation 4CB staff shall decide who is allowed to access the T2S domain monitor the technical operations at the T2S interface of the VAN manage all the encryption keys from T2S used in the VAN administer all the T2S credentials used by the T2S actors 17

4. Organization, operation and plan Service catalogue and manuals The VAN shall provide a catalogue of connectivity services for its customers as part of the T2S overall service catalogue Jointly with the 4CB staff, the VAN shall provide and maintain two reference manuals: Operations manual, that describes the network related components installed in the premises of the Service Provider and contains the complete list of monitored elements Escalation manual, that formalises the escalation process in normal and abnormal conditions 18

4. Organization, operation and plan Support and Incident/Problem management Support Team: the VAN providers shall offer to 4CB and the T2S actors a Service Desk service the 4CB Teams shall be able to contact the VAN providers Support Teams 24 hours seven days a week during all year Trouble ticketing system: the VAN providers shall record all actions, as well as the timestamp (time and date) at which the actions occur, in its central Trouble ticketing system this information shall be made available to the 4CB upon request and as part of the periodic incident review activity The VAN providers shall provide: initial response time for blocking problems: a maximum will be defined first status update time for blocking problems: a maximum will be defined 19

4. Organization, operation and plan Implementation requirements The VAN providers shall preliminary implement a proof of concept; the PoC infrastracture will remain as internal test environment for the 4CB (INTEG, IAC) The VAN providers shall support for implementing and executing integration and acceptance tests of the services 20

Information Session on T2S User Connectivity Thank you for your attention Frankfurt,14 July 2010 21