Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


12:00 AM

Can Spybots be Programmatically Defended Against?

An article in today's New York Times (A Company Promises the Deepest Data Mining Yet, by Louise Story, 3/20/08 page C3) talks about web activity monitoring by a company called Phorm. Phorm's claims it can monitor every single online action by working with data from an ISP. Clearly this raises privacy and security concerns and has already done do in Britain where Phorm is working with British ISPs.

The Phorm approach was only described as a cookie on the user's PC that used a random number to identify the user. The approach to monitoring web activity was not described but I would guess there is a spybot involved.

Web application security is a big concern of mine. Techniques like SSO user authentication, multifactor authentication, enforcement of roles, page reauthoriation, URL tamper protection, URL parameter checksums, and script insertion protection are standard security approaches I use in all my web applications. But these guard against unauthorized usage, and not from spying on authorized users.

The NYTimes article got me thinking about protection against spybots. They are an ever present performance hazard but they are also a serious security risk. A spybot found on a laptop that has Personally Identifiable Information (PII) like SSN, credit card numbers, and the like, even if the data is encrypted, constitutes a security breach. By law, the breach has to be reported, persons real or potentially affected notified plus other things like credit monitoring has to happen at a cost of $10-$184 per identity. No small dollar amount if many identities are stolen.

Spybots can be detected and immunized against. Search andDestroy is an excellent example of this and has saved my laptop many a time. The problem is the lag between identification and availability of immunication and countermeasures. Network security should be also a good control point but it seems that spybots are everywhere even on secure networks.

Is it possible to, in effect, build in spybot protection into a web application or is this more effectively done through a companion app - a counterbot? Could transparent encryption be used to make data visible to the user while the spybot sees the encrypted data? There could be real possibilities here or not, depending on feasibility and time.

Any approach needs to be general enough to be usable by web developers with the ideal approach transparent to the web application. My gut feeling is that having the protection as close to the application will provide the best protection.

I don't have a specific idea on feasibility yet. I know it is a serious security concern. I toss it out to you. I would appreciate your thoughts on feasibility and approach.



Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to memory exhaustion and denial of service. Sydent also does not limit response size for requests it mak...
PUBLISHED: 2021-04-15
Sydent is a reference Matrix identity server. Sydent can be induced to send HTTP GET requests to internal systems, due to lack of parameter validation or IP address blacklisting. It is not possible to exfiltrate data or control request headers, but it might be possible to use the attack to perform a...
PUBLISHED: 2021-04-15
Sydent is a reference matrix identity server. A malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example. This issue has been fixed in 4469d1d.
PUBLISHED: 2021-04-15
Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks. This requires WordPress installation to be using PHP 8. Access to internal files is possible in a successful XXE attack. This has be...
PUBLISHED: 2021-04-15
The project received a report that all versions of Apache OpenOffice through 4.1.8 can open non-http(s) hyperlinks. The problem has existed since about 2006 and the issue is also in 4.1.9. If the link is specifically crafted this could lead to untrusted code execution. It is always best practice to ...