The Log Mandate – Enabling Indian ISPs to adhere to DoT compliance rules

 In Cloud

The Indian ISPs have to adhere to the 2013 missives issued by the Department of Telecommunications (DoT). In its initiative to improve transparency, the DoT had mandated ISPs to maintain logs of Internet Protocol Detail Record (IPDR) and Network Address Translation (NAT). The directive also instructed storage of log data for one year.

 

ISPs need to maintain logs for the following parameters of IPDR
Name of Person / Organization
Address
Contact No
Alternate Contact No
Email Address
Landline / MSISDN / MDN / Leased Circuit ID for Internet Access
User ID for Internet Access based on authentication
IP Address Assigned
Static/Dynamic IP Address Allocation
Source port of the public IP address in case of NATING
IST Start Time of IP Address Allocation (hh:mm:ss)
IST End Time of IP Address Allocation (hh:mm:ss)
Start Date of IP Address Allocation (dd/mm/yyyy)
End Date of IP Address Allocation (dd/mm/yyyy)
Source MAC Address / Other Device Information Number
Parameter to be stored in SYS Log of Network Address Translation (NAT) for Internet Access
Start date (mm:dd:yyyy) and time (hh:mm:ss)
End date (mm:dd:yyyy) and time (hh:mm:ss)
Source IP Address
Source Port
Translated IP Address
Translated Port
Destination IP Address
Destination Port

 

As is known, the CER router generates massive amounts of log data (around 50GB a day) based on the number of users serviced and their browsing. Given an average of 3 devices per user – Mobile Phone, Laptop, Tab, PC, etc., one can imagine the amount of browsing history generated.

Each subscriber will have a router which can service multiple devices. Corporate customers get Static IP for the router but the retail customers do not get static IP. Therefore, the Static IP address changes in the router every time. It is important for the ISP to capture the subscribing user, the router and their browsing history based on the NAT log.

There are multiple ways in which this is is achieved. The traditional tools captures the log and maintains it in databases and the archive of these databases is maintained in the tape storage. Maintaining the log compliance data in traditional method involves higher levels of manual effort, longer retrieve data time and increased cost.  

CoreStack log management solves the problem by using a combination of Open source log management tools, indexing tools and Cloud Service providers. This is because, cloud object storage provides faster retrieval compared to maintaining the archival data in the tape storage.

Click here to learn more about our Log Life Cycle Management system.

CoreStack helps leading ISP comply to DoT rules

We recently implemented CoreStack’s Log Management feature for a leading Indian ISP, and are glad to share the solution mechanism designed to tackle this unique compliance requirement of the DoT.

 

This solution helped the ISP to effectively manage their log operations.

 

Recent Posts

Leave a Comment

Start typing and press Enter to search