CBEC Partner Connectivity Protocol

Central Board of Excise & Customs

Department of Revenue, Ministry of Finance, Government of India

CBEC Partner Connectivity Protocol – Solution for CBEC field formations managed by Custodians (under the HCCAR, 2009) requiring IT infrastructure and connectivity with CBEC Data Centre

Version 2.0

March 2017

Document Control

CBEC Partner Connectivity Protocol – Solution for CBEC field formations managed by Custodians (under the HCCAR, 2009) requiring IT infrastructure and connectivity with CBEC Data Centre

Reference: Reference is invited to CBEC Notification No. 26/2009-Customs(N.T.) dated 17^th March 2009 bringing into effect the “Handling of Cargo in Customs Areas Regulations 2009” (referred in short as ‘Regulations’) and Circulars Nos. 13/2009-Customs dated 23^rd March 2009 and No. 21/2009-Customs dated ₄th August 2009. Reference is also invited to CBEC’s Circular No.4/2011-Customs dated 10th January 2011

The above Regulations/Circular issued by CBEC prescribe, inter-alia, that the networking, communication equipments, Uninterrupted Power Supply System, desktops, servers, printers other computer peripherals and secure connectivity to the CBEC Data Centres as specified by the Directorate General of Systems shall also be provided by the custodians. It has further been provided that these instructions apply to all the Custodians of ports, airports, Inland Container Depots (ICDs), Container Freight Stations (CFSs), Integrated Check posts (ICPs), Land Customs Stations (LCSs), the major ports notified under the Major Ports Act 1963 and the airports notified under the Airports Authority of India Act, 1994.

Overview: This Document provides the current revised technical details for network connectivity and IT infrastructure at ICDs/CFSs/ICPs etc. which are covered under HCCAR 2009, requiring access to CBEC’s Data Centres for accessing CBEC’s Customs applications. This document/specifications herein may be revised from time to time in terms of the above cited Regulations.

Requirements:

a) The Custodian would be required to provide MPLS connectivity for access to the Data Centre. M/s BSNL and M/s TCL are the authorized service providers of CBEC for primary connectivity and alternate connectivity respectively and therefore already have presence at the Data Centres. However, connectivity can also be taken from any other MPLS Service provider who has presence at CBEC’s Data Centres.

b) It is mandatory for the Custodian to take MPLS connectivity to the Data Centre-Delhi as well Data Centre – Chennai to ensure business continuity in the event of a contingency as well as disaster recovery. This would help the location to be connected to the services at the time of non-availability of Primary Data Centre at New Delhi.

c) The bandwidth provided should be of either 4, 8, or 16 Mbps through Optical Fiber Cable depending on the number of users. A bandwidth estimate of about 150 kbps per user should be used while calculating the bandwidth requirement.

d) The Custodian shall ensure that the last mile connectivity to the Custodian site and to Data Centres would be on Optical Fiber Cable. The Custodian shall ensure that the underground fiber laid should have proper ducting and the routes taken by the fiber shall avoid digging prone areas thereby ensuring minimum or no disruption to CBEC services. Refer to Annexure 1 for various options of Connectivity to the Data Center.

e) The Custodian would be required to provide all requisite infrastructure including office space and furniture, Local Area Network (LAN) Infrastructure including Desktops, File & Print servers, Printers (including Line Printers as may be required), Routers, LAN Switches, air-conditioning, backup power and UPS. Specifications of equipment (as deployed by CBEC) are detailed at Annexure 2. The infrastructure supplied must conform to these specifications or higher. The annual maintenance and proper upkeep of these equipments would also be the responsibility of the Custodian.

f) The WAN and LAN equipment provided by Custodians shall conform to CBEC’s IT Infrastructure Design and secure access policy. The local infrastructure would have to integrate with CBEC’s Central End Point Protection (Anti-Virus & HIDS) gateway, Network Access Control (NAC), Active Directory, CBEC’s Content Filtering Solution, Data Leakage Prevention (DLP) and Centralized Patch Management systems etc. This is important since any violation would impact the connectivity to the data List of all software agents required to be installed on Desktops are provided in Annexure 3. The agents which are required to be mandatorily integrated with CBEC’s centralized security controls are marked as Mandatory and will be provided to the Custodian by CBEC.

g) The Custodian would be required to provision Resident Engineers (R.E.) as per their working hours who would be responsible for day to day support and maintenance of the Local IT Infrastructure. Minimum qualification of E.s (as deployed by CBEC) is provided in Annexure 4.

h) The Custodian should ensure that CBEC LAN is segregated for security and not connected to the CFS/ICD own LAN. The LAN/WAN implementation would be required to conform to the Information Security Policy of CBEC, which will be shared by CBEC with the Custodian after they have executed the required Non-Disclosure Agreement.

i) Custodian would be required to sign a “Non Disclosure Agreement” on a stamp paper with the Jurisdictional Commissioner of Customs. The format of this agreement is enclosed at Annexure 5. Once the infrastructure is ready, the custodian is required to fill up the Infrastructure checklist enclosed at Annexure 6, and have it verified by the Customs officer located at the site. The Non Disclosure Agreement and Infrastructure checklist in original is required to be submitted to the Jurisdictional Commissioner of Customs.

The System Manager or Alternate System Manager would in turn forward a scan copy of the signed Infrastructure checklist and NDA to CBEC for issue of LAN I P pool (cbec.lanwan@icegate.gov.in)

Annexure