Millions of users of SBI Left Banking are unprotected online. Report

The State Bank of India has emerged as the center of information security scandal since Wednesday's media report claimed that India's largest bank has released a server whose banking data has not been protected. Then it is reported that the server was backed up, but the existence of an alleged defective server causes serious questions about the bank's security experience that manages the sum of more than 42 major Indian customers.

According to TechCrunch's report, the alleged defective server of the State Bank of India was deployed in the Mumbai Data Center and included two months' data from SBI Quick, a corporate banking customer service. SBI Quick insists that its consumers are easy and inappropriate to receive basic information about their accounts with the bank. Consumers can ask for their balance, mini announcement, demand book, and more.

The SBI server is not explicitly protected by a password, thus giving someone who knows where to look - accessing millions of bank data, including cell phone numbers, partial account numbers, account balances, recent deals, and more. TechCrunch notes that the leak detected a security researcher who wants to remain anonymous.

The report explains that the server is based primarily on the SBI Quick Service backbone and includes millions of messages that are sent to consumers in response to their inquiries. It added that they can learn how text messages are sent in real time. The site states that it has confirmed the identity of the server trying to use a security researcher in India to use the SBI Quick Service and in seconds it may actually see the investigator's number as well as the response to the password shortage.

TechCrunch notes that the server has detected that on Monday the bank sent more than three million text messages to consumers. With malicious data such as two months, the malicious side can greatly hurt the consumers of the Indian state bank.

We have addressed to SBI for a statement on this issue but did not receive a response at the time of publication.

<! -

->

.