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.

Perimeter

5/21/2009
04:55 PM
Gadi Evron
Gadi Evron
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Lessons From Fighting Cybercrime, Part 2

In this article we'll examine three basic guidelines on how to implement solutions into social systems, learned from the fight against spam.

In this article we'll examine three basic guidelines on how to implement solutions into social systems, learned from the fight against spam.Last week I blogged about two spam-fighting ideas: email stamps and blocking port 25. We've shown that while security and cybercrime are filled with reactive solutions doomed to failure, it is possible to gain strategic advantage while implementing them.

Email stamps is a good example of a solution doomed to failure. Why do solutions like this fail?

Avoiding resistance from users is the first key to success. Email stamps make sending email more complicated. They also take something that was free and add a price tag to it.

Taking something that is already widely implemented and adding counter-intuitive terms to its use is always going to encounter resistance. Users don't want additional complexity added to email.

Much the same, taking something and raising its cost, or worse, making something previously free cost money, is one of the reasons so many Internet start-ups failed the past ten years (if we are to listen to social psychology). People do not like feeling cheated out of something that is already theirs.

Needlessly added complexity and making something previously free, cost, especially in a competitive marketplace where users can just switch providers, are paths to failure.

Tying it together, these lead us to the concept of naivete. How practical is the system to reach, be accepted, and then implemented by professionals?

The technology for email stamps requires a large part of the world to implement it before it works. The world is a multi-valence of complex inter-connected systems, and expecting everyone, or a large part of everyone, to do as you ask (if you can even reach them) is simply not plausible.

My second example from the previous blog, blocking port 25--a very different approach--worked immediately for those who did implement it.

Anti-spam introduced the world to the FUSSP, or sarcastically, the "perfect solution": You Might Be An Anti-Spam Kook If... http://www.rhyolite.com/anti-spam/you-might-be.html

It enumerates ways by which "new" and "amazing" suggestions on solving the spam problem go wrong... If only "everyone" (or most people) used their solution or "forced users" to act counter intuitively (and similar truisms), spam would be "gone". It is well worth a read.

Trying to map how some solutions work while others can't even get off the ground and seeing how communities and social systems change is fascinating. The examples above and many other lessons of fighting cybercrime are illuminating. Especially when we consider they are mostly derived from failures of technical solutions to solve a human problem, a common design fallacy this day and age.

In my next blog in this series, we discuss security by obscurity as used by attackers.

Follow Gadi Evron on Twitter: http://twitter.com/gadievron

Gadi Evron is an independent security strategist based in Israel. Special to Dark Reading. Gadi is CEO and founder of Cymmetria, a cyber deception startup and chairman of the Israeli CERT. Previously, he was vice president of cybersecurity strategy for Kaspersky Lab and led PwC's Cyber Security Center of Excellence, located in Israel. He is widely recognized for ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17452
PUBLISHED: 2020-08-09
flatCore before 1.5.7 allows upload and execution of a .php file by an admin.
CVE-2020-17451
PUBLISHED: 2020-08-09
flatCore before 1.5.7 allows XSS by an admin via the acp/acp.php?tn=pages&sub=edit&editpage=1 page_linkname, page_title, page_content, or page_extracontent parameter, or the acp/acp.php?tn=system&sub=sys_pref prefs_pagename, prefs_pagetitle, or prefs_pagesubtitle parameter.
CVE-2020-17447
PUBLISHED: 2020-08-09
MyBB before 1.8.24 allows XSS because the visual editor mishandles [align], [size], [quote], and [font] in MyCode.
CVE-2020-16248
PUBLISHED: 2020-08-09
** DISPUTED ** Prometheus Blackbox Exporter through 0.17.0 allows /probe?target= SSRF. NOTE: follow-on discussion suggests that this might plausibly be interpreted as both intended functionality and also a vulnerability.
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.