Robert Hansen (RSnake / ha.ckers.org / SecTheory) created a little challenge (pun intended) a couple of days ago titled "The Diminutive XSS worm replication contest":
The diminutive XSS worm replication contest is a week long contest to get some good samples of the smallest amount of code necessary for XSS worm propagation. I’m not interested in payloads for this contest, but rather, the actual methods of propagation themselves. We’ve seen the live worm code and all of it is muddied by obfuscation, individual site issues, and the payload itself. I’d rather think cleanly about the most efficient method for propagation where every character matters.
Kurt Wismer (anti-virus rants blog) thinks this is a lousy idea:
yes, folks... robert hansen (aka rsnake), the founder and ceo of sectheory, felt it would be a good idea to hold a contest to see who could create the smallest xss worm... ok, so there's no money changing hands this time, but that doesn't mean the winner isn't getting rewarded - there are absolutely rewards to be had for the winner of a contest like this and that's a big problem because lots of people want rewards and this kind of contest will make people think about and create xss worms when they wouldn't have before...
Here's where Kurt diverges from simply highlighting nominal arguments of the potential for misuse of the contest derivatives. He suggests that RSnake is being unethical and is encouraging this contest not for academic purposes, but rather to reap personal gain from it:
would you trust your security to a person who makes or made malware? how about a person or company that intentionally motivates others to do so? why do you suppose the anti-virus industry works so hard to fight the conspiracy theories that suggest they are the cause of the viruses? at the very least mr. hansen is playing fast and loose with the publics trust and ultimately harming security in the process, but there's a more insidious angle too...
while the worms he's soliciting from others are supposed to be merely proof of concept, the fact of the matter is that proof of concept worms can still cause problems (the recent orkut worm was a proof of concept)... moreover, although the winner of the contest doesn't get any money, at the end of the day there will almost certainly be a windfall for mr. hansen - after all, what do you suppose happens when you're one of the few experts on some relatively obscure type of threat and that threat is artificially made more popular? well, demand for your services goes up of course... this is precisely the type of shady marketing model i described before where the people who stand to gain the most out of a problem becoming worse directly contribute to that problem becoming worse... it made greg hoglund and jamie butler household names in security circles, and it made john mcafee (pariah though he may be) a millionaire...
I think the following exchange in the comments section of the contest forum offers an interesting position from RSnake's perspective:
Re: Diminutive XSS Worm Replication ContestPosted by: Gareth Heyes (IP Logged)Date: January 04, 2008 04:56PM
@rsnake
This contest is just asking for trouble :)
Are there any legal issues for creating such a worm in the uk?
------------------------------------------------------------------------------------------------------------
Re: Diminutive XSS Worm Replication Contest
Posted by: rsnake (IP Logged)Date: January 04, 2008 05:11PM
@Gareth Heyes - perhaps, but trouble is my middle name. So is danger. Actually I have like 40 middle names it turns out. ;) No, I'm not worried, this is academic - it won't work anywhere without modification of variables, and has no payload. The goal is to understand worm propagation and get to the underlying important pieces of code.
I'm not in the UK and am not a lawyer so I can't comment on the laws. I'm not suggesting anyone should try to weaponize the code (they could already do that with the existing worm code if they wanted anyway).
So, we've got Wismer's perspective and (indirectly) RSnake's.
What's yours? Do you think holding a contest to build a POC for a worm a good idea? Do the benefits of research and understanding the potential attacks so one can defend against them outweigh the potential for malicious use? Do you think there are, or will be, legal ramifications from these sorts of activities?
/Hoff
I'm far from being impartial on many topics -- I don't believe that anyone is truly impartial about anything -- but at the same time, I have an open mind and will gladly listen to points raised in response to anything I say. I may not agree with it, but I'll also tell you why.
What I have zero patience for, however, is when I get twisted semantic marketing spin responses. It makes me grumpy. That's probably why Rothman, Shimmy and I get along so well.
Some of you might remember grudge match #1 between me and Alex Niehaus, the former VP of Marketing for Astaro (coincidence?) This might become grudge match #2. People will undoubtedly roll their eyes and dismiss this as vendors sniping at one another. So be it. Please see paragraphs #1 and 2 above.
My recent interchange with Richard Stiennon is an extension of arguments we've been having for a year or so from when Richard was still an independent analyst. He is now employed as the Chief Marketing Officer at Fortinet.
Our disagreements have intensified for what can only be described as obvious reasons, but I'm starting to get as purturbed as I did with Alex Neihaus when the marketing sewerage obfuscates the real issues with hand-waving and hyperbole.
I called Richard out recently for what I believed to be complete doubletalk on his stance on UTM and he responded here in a comment. Comments get buried so I want to bring this back up to the top of the stack for all to see. Don't mistake this as a personal attack against Richard, but a dissection of what Richard says. I think it's just gobbledygook.
To be honest, I think it took a lot of guts to respond, but his answer makes my head spin as much as Anna Nicole Smith in a cheesecake factory. Yes, I know she's dead, but she loved cheesecake and I'm pressed for an analogy.
The beauty of blogging is that the instant you say something, it becomes a record of "fact." That can be good or bad depending upon what you say.
I will begin to respond to Richard's retort wherein he first summarily states:
I also assume that this means Richard hates the bit buckets that Firewall, IPS, NAC, VA/VM, and Patch Management (as examples) have become, too? This trend is the natural by-product of marketers and strategists scrambling to find a place to hang their hat in a very crowded space. So what.
UTM is about solving applied sets of business problems. You can call it what you like, but the only reason marketeers either love or hate UTM usually depends upon where they sit in the rankings. This intrigues me, Richard, because (as you mention further on) Fortinet pays to be a part of IDC's UTM Tracker, and they rank Fortinet as #1 in at least one of the product price ranges, so someone at Fortinet seems to think UTM is a decent market to hang a shingle on.
Hate it or not, Fortinet is a UTM vendor, just like Crossbeam. Both companies hang their shingles on this market because it's established and tracked.
You're right. Lumping Crossbeam with Fortinet and Astaro is the wrong thing to do. ;)
Arguing the viability of a market which has tremendous coverage and validated presence seems a little odd. Crafting a true strategy of differentiation as to how you're different in that market is a good thing, however.
So what you're saying is that you like the nebulous and ill-defined blob that is Gartner's view, don't like IDC, but you'll gladly pay for their services to declare you #1 in a market you don't respect?
You mean besides when you said:
Just in case you're interested, you can find that quote here. There are many, many other examples of you saying this, by the way. Podcasts, blog entries, etc.
Also, are you suggesting that Fortinet does not consider itself a UTM player? Someone better tell the Marketing department. Look at one of your news pages on your website. Say, this one, for example -- 10 articles have UTM in the title and your own Mr. Akomoto (VP of Fortinet, Japan) says "The UTM market was pioneered by us," says Mr. Okamoto, the vice-president of Fortinet Japan. Mr. Okamoto explains how Fortinet created the UTM category, the initial popularity of UTM solutions with SMBs..."
Yes, I understand how much you dislike IDC. Can you kindly show reference to where you previously commented on how Fortinet was executing on your vision for Secure Network Fabric? I can show you where you did for Crossbeam -- it was at our Sales Meeting two years ago where you presented. I can even upload the slide presentation if you like.
Richard, I'm not really looking for the renewal of your Crossbeam Fan Club membership...really.
Oh, now it's on! I'm fixin' to get "Old Testament" on you!
Just so we're clear, ISV applications that run on Crossbeam such as XML gateways, web-application firewalls, database firewalls and next generation network converged security services such as session border controllers are all UTM "legacy applications!?"
So besides an ASIC for AV, what "new" non-legacy apps does Fortinet bring to the table? I mean now. From the Fortinet homepage, please demonstrate which novel new applications that Firewall, IPS, VPN, Web filtering and Antispam represent?
It must suck to have to craft a story around boat-anchor ASICs that can't extend past AV offload. That means you have to rely on software and innovation in that space. Cobbling together a bunch of "legacy" applications with a nice GUI doesn't necessarily represent innovation and "next generation."
It's clear you have a very
deludedinteresting perspective on security applications. The "innovation" that you're suggesting differentiates what has classically been described as the natrual evolution of converging marketspaces. That over-played Snort analogy is crap. The old "signature" vs. "anomaly detection" argument paired with "deep packet inspection" is tired. Fortinet doesn't really do anything that anyone else can't/doesn't already do. Except for violating GPL, that is.I suppose now that Check Point has acquired NFR, their technology is crap, too? Marcus would be proud.
Oh come on, Richard. First of all, the answer to your question is that many, many large enterprises and service providers utilize a layered defense and place an IPS before or after their firewall. Some have requirements for firewall/IDS/IPS pairs from different vendors. Others require defense in depth and do not trust that the competence in a solutions provider that claims to "do it all."
Best of breed is what the customer defines as best of breed. Just to be clear, would you consider Fortinet to be best of breed?If you use a Crossbeam, by the way, it's not a separate device and you're not limited to just using the firewall or IPS in "front of" or "behind" one another. You can virtualize placement wherever you desire. Also, in many large enterprises, using IPS's and firewalls from separate vendors is not only good practice but also required.
How does Fortinet accomplish that?
Your "payload inspection" is leveraging a bunch of OSS-based functionality paired with an ASIC that is used for AV -- you know, signatures -- with heuristics and a nice GUI. Whilst the Cosine IP Fortinet acquired represents some very interesting technology for provisioning and such, it ain't in your boxes.
You're really trying to pick a fight with me about Check Point when you choose to also ignore the fact that we run up to 15 other applications such as SourceFire and ISS on the same platform? We all know you dislike Check Point. Get over it.
Really? So since you don't have separate products to address these (Fortinet sells UTM, afterall) that means you had nothing to offer them? Convergence is driving UTM adoption. You can call it what you want, but you're whitewashing to prove a flawed theorem.
...and what the heck is the difference between that and UTM, exactly? People don't buy IPS, they buy network level protection to defend against attack. IPS is just the product catagory, as is UTM.
I don't like Scotch, Richard. It leaves a bad taste in my mouth...sort of like your response ;)