Another missing file
Security No Comments »According to Christopher Gormley, chief operating officer at Tiversa Inc., a Cranberry Township, Pasadena-based P2P network monitoring firm: On average, about 1.5 billion searches take place on P2P (peer to peer) networks daily compared with 180 million on Google, and that a growing number of the searches are being done for malicious purposes. Gormley also said that Tiversa also has noticed the emergence of several data aggregators whose sole purpose seems to be collecting information on P2P networks for their own illegal uses or to resell to other miscreants.
1.5 billion compared to 180 million is almost 10 times as many searches. And given they are being done on P2P networks, this means that these searches are uncovering the files stored on individual computers connected to the Inernet, computers which vary from individuals at home right through to computers in the heart of large corporations. And direct access to information on these computers could reveal a lot more than the person intended - P2P software often allows access to many of the folders on the computer on which it is installed by default rather than by permission. This means that the person who installed the P2P software often unwittingly exposes all the data on their computer to the rest of the world, and this can include password files, personal information, private lists and much more.
Numerous organisations have suffered data leaks as a result of such carelessness. Last year, for instance, the personal data of about 17,000 Pfizer employees was exposed after an employee installed unauthorized P2P software on her laptop. And at a US Senate hearing last year, lawmakers heard testimony from several witnesses about the abundance of classified government and military documents as well as corporate data freely available on P2P networks.
The data said to be available included a full diagram of the Pentagon’s secret backbone network infrastructure, complete with IP addresses and password-change scripts; contractor data on radio-frequency manipulation techniques for dealing with improvised explosive devices in Iraq; the complete minutes of a board meeting held at a large financial services company; and the detailed launch plan of a start-up company, complete with growth targets and other business forecasts.
Naturally, the immediate reaction is to not allow P2P software and so remove the risk of this happening. But people are creative and find ways around the rules which means P2P software will creep in and the risk resurface. And while the main threat comes from public P2P software (e.g. Limewire, Kazaa), P2P technology is also being used as a business enabler in many organisations.
So, the big question is how do we mitigate against confidential data loss? One thought is to focus attention on network monitoring to see which files are being sent in and out of corporate networks. However, I am not sure how this benefits us as it doesn’t directly prevent illegal transmission versus legal transmission - it simply gives us an audit trail we can dissect when the proverbial excrement hits the fan.
However, there may be a more straightforward solution … most connected systems use specific port numbers over which they transmit data. A corporate network should have a know port topology - ie we should be able to define exactly which ports are needed for communication with the outside world, and in which direction that communication should be. So, for example, if we needed port 6346 to be open (which is Limewire’s default communication port), we could easily define which direction traffic was allowed. We could block outbond traffic with a simple rule in the firewall and so stop all outbound traffic dead in its tracks. We could work through all the ports (OK there are a lot) and define a full firewall map and so manage corporate network traffic exactly as we needed to. The remaining ports could be monitored if required, but this would be a more manageable task.
Quick reference lists of common port numbers abound, and so a network administrator would be able to quickly present a route-map to securing their corporate network and earn a few brownie points from their CIO. Of course, implementing or even suggesting such a plan of action might be met with blank stares because few people are fully aware of the risk to their sensitive data from unctontrolled P2P applications.
IRC Beginners Reference
List of Common TCP/IP numbers (PDF)
Let’s hope this article helps IT departments get a head start on securing their networks, or at least raising awareness of the issue to the execs.
Article inspired by: File-sharing breach at investment firm highlights dangers of P2P networks — again