<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[[SecurityRatty] tag: mature]]></title>
    <link>http://securityratty.com/tag/mature</link>
    <description></description>
    <pubDate>Tue, 05 Aug 2008 04:46:27 +0000</pubDate>
    <generator>iRatty Engine</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Is PCI DSS "Too Prescriptive"?]]></title>
      <link>http://securityratty.com/article/3dfc59dd4876349ed35372715a67d3d7</link>
      <guid>http://securityratty.com/article/3dfc59dd4876349ed35372715a67d3d7</guid>
      <description><![CDATA[I did this fun panel on PCI compliance at SecureWorld Bay Area the other week. What is interesting is that almost every time there is a discussion about PCI DSS, somebody crawls out of the woodwork...]]></description>
      <content:encoded><![CDATA[<p>I did this <u><a href="http://secureworldexpo.com/events/index.php?id=255">fun panel on PCI compliance at SecureWorld Bay Area</a></u> the other week. What is interesting is that almost every time there is a discussion about PCI DSS, somebody crawls out of the woodwork and utters the following: &quot;<strong>PCI is too prescriptive!</strong>&quot;, as if it is a bad thing (e.g. I mentioned it before <a href="http://chuvakin.blogspot.com/2008/04/rsa-impressions-2-compliance.html">here</a>)</p>  <p>I used to react to this with &quot;<em>Are you stupid?!</em> PCI being prescriptive is the best thing since sliced cake :-) Finally, there is some specific guidance for people to follow and be more secure!&quot; BTW, in many cases end users who have to comply with PCI DSS <strong>still</strong> think it is &quot;too fuzzy&quot; and &quot;not specific enough&quot; (e.g. see <u><a href="http://chuvakin.blogspot.com/2008/02/must-do-logging-for-pci.html">&quot;MUST-DO Logging for PCI&quot;</a></u>); and they basically ask for&#160; &quot;<strong>a compliance TODO list</strong>.&quot; (also see <a href="http://chuvakin.blogspot.com/2008/08/few-more-words-on-dlp-and-compliance.html">this</a> and especially <a href="http://securosis.com/2008/08/18/dont-sell-compliance-if-it-isnt-a-checkbox/">this</a> on compliance checklists)</p>  <p>But every time it happens, I can't stop but think - why do people even utter such utter heresy? :-) And you know what?&#160; I think I got it!</p>  <p>When people say &quot;PCI is too prescriptive,&quot; they actually mean that it engenders &quot;<u><a href="http://chuvakin.blogspot.com/2008/04/rsa-impressions-2-compliance.html">checklist mentality</a></u>&quot; and leads to following the letter of the mandate blindly, without thinking about WHY it was put in place (to protect cardholder data, share risk/responsibility, etc). For example, it says &quot;use a firewall&quot; and so they deploy a shiny firewall with a simple &quot;ALLOW ALL&lt;-&gt;ALL&quot; rule (an obvious exaggeration - but you get the point!) Or they have <u><a href="http://chuvakin.blogspot.com/2008/09/dumb-luck-is-strategy.html">a firewall with a default password unchanged</a></u>... In addition, the proponents of &quot;PCI is too prescriptive&quot; tend to think that fuzzier guidance (and, especially, prescribing the desired end state AND not the tools to be installed) will lead to people actually thinking about the best way to do it.</p>  <p>So the choices are:</p>  <ol>   <li><strong>Mandate the tools</strong> (e.g. &quot;must use a firewall&quot;) - <strong>and risk</strong> &quot;checklist mentality&quot;, resulting in BOTH insecurity and &quot;false sense&quot; of security. </li>    <li><strong>Mandate the results</strong> (e.g. &quot;must be secure&quot;) -&#160; <strong>and risk</strong> people saying &quot;eh, but I dunno how&quot; - and then not acting at all, again leading to insecurity. </li> </ol>  <p>Take your poison now?! Isn't compliance fun? What is the practical solution to this? I personally would take the pill #1 over pill #2 (and that is why I like PCI <a href="http://chuvakin.blogspot.com/2007/08/free-pci-compliance-book-chapter-on.html">that much</a>), but with some pause to think, for sure.&#160; I think organizations with less mature security programs will benefit at least a bit from #1, while those with more mature programs might &quot;enjoy&quot; #2 more...</p>  <p>BTW, this post was originally called &quot;Isn't Compliance Fun?!&quot;&#160; I had a few fierce debates with some friends and all of them&#160; piled on me to convince me that &quot;compliance is boring, while security is fun!&quot; The above does illustrate that there are worthy and exciting intellectual challenges in the domain of regulatory compliance. It is not [only] a domain of minimalists (who just &quot;want the auditor to go away&quot;) and <u><a href="http://securityincite.com/blog/mike-rothman/rise-up-against-mediocrity">mediocrity</a></u>, as some think. What makes security fun - the people aspect, the ever-changing threat landscape, cool technology, high uncertainty, even risk - also apply to compliance ...</p>  <p>So, need a cool marketing slogan BUT <u></u><a href="http://securityincite.com/blog/mike-rothman/pragmatic-cso-podcast-10-its-so-easy">hate &quot;making compliance easy&quot;</a>?&#160; Go for &quot;Making Compliance Fun!&quot; :-)</p>  <p><u><a href="http://chuvakin.blogspot.com/search/label/PCI">All posts on PCI</a></u> - some are fun:-)</p>  <div class="blogger-post-footer">About me: http://www.chuvakin.org</div><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=eFI6L"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=eFI6L" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=dQYpL"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=dQYpL" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?a=GGp5L"><img src="http://feeds.feedburner.com/~f/AntonChuvakinPersonalBlog?i=GGp5L" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~4/400214601" height="1" width="1"/>]]></content:encoded>
      <pubDate>Mon, 22 Sep 2008 11:43:00 +0000</pubDate>
      <category domain="http://securityratty.com/tag/pci">pci</category>
      <category domain="http://securityratty.com/tag/pci dss">pci dss</category>
      <category domain="http://securityratty.com/tag/compliance">compliance</category>
      <category domain="http://securityratty.com/tag/compliance fun">compliance fun</category>
      <category domain="http://securityratty.com/tag/pci compliance">pci compliance</category>
      <category domain="http://securityratty.com/tag/compliance checklists">compliance checklists</category>
      <category domain="http://securityratty.com/tag/fun">fun</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <category domain="http://securityratty.com/tag/regulatory compliance">regulatory compliance</category>
      <source url="http://feeds.feedburner.com/~r/AntonChuvakinPersonalBlog/~3/400214601/is-pci-dss-prescriptive.html">Is PCI DSS "Too Prescriptive"?</source>
    </item>
    <item>
      <title><![CDATA[From the Executive Women's Forum on Information Security]]></title>
      <link>http://securityratty.com/article/f2976566aba2a7d7042931766a835f14</link>
      <guid>http://securityratty.com/article/f2976566aba2a7d7042931766a835f14</guid>
      <description><![CDATA[The theme of the 2008 Executive Women's Forum on Information Security, Risk Management &amp; Privacy is &quot;risk convergence is inevitable.&quot; The risks associated with information security, privacy, physical...]]></description>
      <content:encoded><![CDATA[The theme of the 2008 Executive Women's Forum on Information Security, Risk Management & Privacy is "risk convergence is inevitable." The risks associated with information security, privacy, physical security and so forth are converging such that an integrated management approach is required from within the firm. <br />
<br />
Interestingly enough, business continuity management was not a key risk area mentioned by all panelists of the session titled "Convergence: The Good, The Bad & The Ugly." There were two pieces of strategic program management advice from the panelists. The first point is that you have to partner with all of your lines of business and corporate support areas. Since risk is related to the delivery of the business, no one department can address all of the issues. And, you might find that there are good practices already in place within your firm, so that you are not reinventing the wheel - leverage the good stuff throughout the firm. The second point is to focus on the budget issue - how many risk-related activities are already in place in your organization that could be combined, and possibly duplicated, so that more work gets done with less money spent? Pooling of already limited budgets can go a long way toward developing a program that is more mature, delivers more benefit to the organization and eliminates a lot of duplicative work. <br />
<br />
But all of this convergence comes at a price - mainly in fear, uncertainty and doubt of the workforce. Some feel that they will lose authority (especially in siloed risk approaches); others might lose their jobs as a result of the convergence. This human aspect was mentioned as the key challenge of an integrated approach. Therefore, communicating not only up within the firm but down to the workforce is critical to achieving a well-run and integrated program. <br />
<br />
And finally, for those areas that just don't want to "play the game," use your internal audit department as the "stick" that can get them to act. When I was an IT risk manager, I always said that I was management's best friend - let me tell you the gaps in your risk program rather than having them come from the audit department, which then become part of the records of the firm.]]></content:encoded>
      <pubDate>Thu, 18 Sep 2008 15:29:34 +0000</pubDate>
      <category domain="http://securityratty.com/tag/risk">risk</category>
      <category domain="http://securityratty.com/tag/risk approaches">risk approaches</category>
      <category domain="http://securityratty.com/tag/risk program">risk program</category>
      <category domain="http://securityratty.com/tag/risk management">risk management</category>
      <category domain="http://securityratty.com/tag/management">management</category>
      <category domain="http://securityratty.com/tag/management approach">management approach</category>
      <category domain="http://securityratty.com/tag/key risk">key risk</category>
      <category domain="http://securityratty.com/tag/audit department">audit department</category>
      <category domain="http://securityratty.com/tag/internal audit department">internal audit department</category>
      <source url="http://blog.gartner.com/blog/security.php?x=0&amp;itemid=3879">From the Executive Women's Forum on Information Security</source>
    </item>
    <item>
      <title><![CDATA[Summarizing August's Threatscape]]></title>
      <link>http://securityratty.com/article/01c05fcd5f209b7515be2cee57a93c9b</link>
      <guid>http://securityratty.com/article/01c05fcd5f209b7515be2cee57a93c9b</guid>
      <description><![CDATA[Following the previous summaries of June's and July's threatscape based on all the research published during the month, it's time to summarize August's threatscape

August's threatscape was dominated...]]></description>
      <content:encoded><![CDATA[<div style="text-align: left;"></div><div class="separator" style="clear: both; text-align: center;"></div><a href="http://1.bp.blogspot.com/_wICHhTiQmrA/SL_ZoXre4vI/AAAAAAAACJ0/LKtKpSt0igQ/s1600-h/ddanchev_august.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://1.bp.blogspot.com/_wICHhTiQmrA/SL_ZoXre4vI/AAAAAAAACJ0/Phtgyl6rLXQ/s200-R/ddanchev_august.png" /></a>Following the previous summaries of <a href="http://ddanchev.blogspot.com/2008/07/summarizing-junes-threatscape.html">June's</a> and <a href="http://ddanchev.blogspot.com/2008/08/summarizing-julys-threatscape.html">July's threatscape</a> based on all the research published during the month, it's time to summarize August's threatscape.<br />
<br />
August's threatscape was dominated by a huge increase of rogue security software domains made possible due to the easily obtainable templates for the sites, several malware campaigns targeting popular social networking sites, Russian's organized cyberattack against Georgia with evidence on who's behind it pointing to "everyone" and a few botnets dedicated to the attack making the whole process easy to outsource and turn responsibility into an "open topic", several new web based botnet management kits and tools found in the wild, evidence that the 76service may in fact be going mainstream since the concept of cybercrime as a service is already emerging, and, of course, a peek at India's CAPTCHA solving economy, where the best comment I've received so far is that every site should embrace reCAPTCHA, so that while solving CAPTCHAs and participating in the abuse of these services in question, they would be also digitizing books. As usual, August was a pretty dynamic month for the middle of summer, with everyone excelling in their own malicious field.<br />
<br />
<b>01.</b> <a href="http://ddanchev.blogspot.com/2008/08/mcafees-site-advisor-blocking-nruns-ag.html">McAfee's Site Advisor Blocking n.runs AG - "for starters"</a><br />
False positives are rather common, especially when you're aiming to protect the end user from himself and not let him gain access to "hacking tools", but you're flagging security tools as badware and missing over half the SQL injected domains currently in the wild due to the fact that SiteAdvisor's community still haven't reviewed them - that's not good<br />
<br />
<b>02.</b> <a href="http://ddanchev.blogspot.com/2008/08/twitter-malware-campaign-wants-to-bank.html">The Twitter Malware Campaign Wants to Bank With You</a><br />
Twitter, just like every Web 2.0 application, isn't and shouldn't be treated as a unique platform for dissemination of malware, since it's dissemination of malware "as usual". This particular malware campaign was not just executed by a lone gunman, but also, was taking advantage of a flaw allowing the author to add new followers potentially exposing them to the malicious links serving banker malware. For the the time being, MySpace, Facebook and Twitter accounts are the very last thing a malicious attacker is interesting in puchasing accounting data for, but how come? It's all due to the oversupply of automatically registered accounts at other popular services, whose ecosystem of Internet properties empower cybercriminals with the ability to launch, host and distribute malware in between abusing the very same company's services for the blackhat SEO campaign and redirection services. Theoretically, a distributed network build upon the services provided by a single company is faily easy to accomplish due to the single login authentication applied everywhere. A singly bogus Gmail account results in a blackhat SEO hosting blogspot account, flash based redirector hosted at Picasa, and a couple of thousands of spam emails sent automatically sent through Gmail in order to abuse it's trusted email reputation<br />
&nbsp; <br />
<b>03.</b> <a href="http://ddanchev.blogspot.com/2008/08/compromised-web-servers-serving-fake.html">Compromised Web Servers Serving Fake Flash Players</a><br />
If aggressiveness matter, this campaign consisting of remotely injected redirection scripts at legitimate sites next to on purposely introduced malware oriented domains, was perhaps the most aggressive one during the month. Fake flash players, fake windows media players and fake youtube players are prone to increase as a social engineering tactic of choice due to the template-ization of malware serving sites for the sake of efficiency<br />
<br />
<b>04.</b> <a href="http://ddanchev.blogspot.com/2008/08/pinch-vulnerable-to-remotely.html">Pinch Vulnerable to Remotely Exploitable Flaw</a><br />
With Zeus vulnerable to a remotely exploitable flaw allowing cybercriminals to hijack other cybercriminal's Zeus botnet, private exploits targeting the still rather popular at least in respect to usefulness Pinch malware are leaking, allowing everyone including security researchers to take a peek at a particular campaign running unpatched Pinch gateway<br />
<br />
<b>05.</b> <a href="http://ddanchev.blogspot.com/2008/08/phishers-backdooring-phishing-pages-to.html">Phishers Backdooring Phishing Pages to Scam One Another</a><br />
Backdooring phishing pages is perhaps the most minimalistic approach a cybercriminal wanting to scam another cybercriminal is going to take. The far more beneficial approach that I've encountered on a couple of occassions so far, would be to backdoor a proprietary web malware exploitation kit, release it in the wild, let them put the time and efforts into launching the campaigns, then hijack their botnet. In fact, the possibilities for backdooring copycat web malware exploitation kits in order to take advantage of the momentum while introducing a non-existent kit has always been there at the disposal of malicious attackers. One thing's for sure - there's no such thing as a free web malware exploitation kit, just like there isn't such thing as a free phishing page<br />
<br />
<b>06.</b> <a href="http://ddanchev.blogspot.com/2008/08/email-hacking-going-commercial-part-two.html">Email Hacking Going Commercial - Part Two</a><br />
In between the scammers promising the Moon and asking for anything between $20 to $250 to hack into an email account, there are "legitimate" services taking advantage of web email hacking kits consisting of each and every known XSS vulnerability for a particular service in an attempt to increase the chances of the attacker. And given that the majority of these have been patched a long time ago, social engineering comes into play. Do these services have a future? Definitely as more and more people are in fact looking for and requesting such services, in fact, they're willing to pay a bonus considering how exotic it is for them to have any email that they provide hacked into and the accounting data sent back to them<br />
<br />
<b>07.</b> <a href="http://ddanchev.blogspot.com/2008/08/russia-vs-georgia-cyber-attack.html">The Russia vs Georgia Cyber Attack</a><br />
Event of the month? Could be, but just like every "event of the moth" everyone seems to be once again restating their "selective retention" preferences. What is selective retention anyway? Selective retention is basically a situation where once Russian is attacking another country's infrastructure, you would automatically conclude that it's Russian FSB behind the attacks and consciously and subconsciously ignore all the research and articles telling you otherwise, namely that the FSB wouldn't even bother acknowledging Georgia's online presence, at least not directly. Moreover, talking about the FSB as the agency behind the cyberattacks indicates "selective retention", talking about FAPSI indicates better understanding of the subject.<br />
<br />
In times when cybercrime is getting ever easier to outsource, anyone following the news could basically orchestrate a large scale DDoS attack against a particular country in order to forward the responsibility to any country that they want to. In Russia vs Georgia, you have a combination of a collectivist society that's possessing the capabilities to launch DDoS attacks, knows where and how to order them, and that in times when your country is engaged in a war conflict drinking beer instead of DDoS-sing the major government sites of the adversary is not an option.<br />
<br />
Selective retention when combined with a typical mainstream media's mentality to "slice the threat on pieces" instead of turning the page as soon as possible, is perhaps the worst possible combination. Furthermore, coming up with <a href="http://intelfusion.net/wordpress/?p=398">Social Network analysis of the cyberattacks</a> would produce nothing more but a few fancy graphs of over enthusiastic Russian netizen's distributing the static list of the targets. The real conversations, as always, are <a href="http://blogs.nyu.edu/blogs/agc282/zia/2008/08/intelfusions_sna_of_russian_cy.html">happening in the "Dark Web" limiting the possibilities for open source intelligence</a> using a data mining software. Things changed, OPSEC is slowly emerging as a concept among malicious parties, whenever some of the "calls for action" in the DDoS attacks were posted at mainstream forums, they were immediately removed so that they don't show up in such academic initiatives<br />
<br />
<b>08.</b> <a href="http://ddanchev.blogspot.com/2008/08/76service-cybercrime-as-service-going.html">76Service - Cybercrime as a Service Going Mainstream</a><br />
The reappearance of the 76Service allowing everyone to log into a web based interface and collect all the accounting and financial data coming from malware infected hosts across the globe for the period of time for which they've bought access, indicates that what used to be proprietary services which were supposedly no longer available, are now being operated in a do-it-yourself fashion. Goods and products mature into services, so from a cost-benefit analysis perspective, outsourcing is naturally most beneficial even when it comes to cybercrime <br />
<br />
<b>09.</b> <a href="http://ddanchev.blogspot.com/2008/08/whos-behind-georgia-cyber-attacks.html">Who's Behind the Georgia Cyber Attacks?</a><br />
If it's the botnets used in the attacks, they are known, if it's about who's providing the hosting for the command and control, it's the "usual suspects", but just like previous discussion of the Russian Business Network, it remains questionable on whether or not they work on a revenue-sharing basis, are simply providing the anti-abuse hosting, or are the shady conspirators that every newly born RBN expert is positioning them to be.<br />
<br />
Cheap conversation regarding the RBN ultimately serves the RBN, and just for the record, there's a RBN alternative in every country, but the only thing that remains the same are the customers, tracking the customers means exposing the RBN and the international franchises of their services, making it harder to identify their international operations. And given that the "tip of the iceberg", namely RBN's U.S operations remain in tact, talking about taking actions against their international operations in countries where cybercrime law is still pending, is yet another quality research into the topic building up the pile of research into the very same segments of the very same ISPs.<br />
<br />
Just for the record - these "very same ISPs" are regular readers of my blog, and if you analyze their activities, they're definitely reading yours too, ironically, surfing through gateways residing within their netblock that are so heavily blacklisted due to the guestbook and forum spamming activities that their bad reputation usually ends up in another massive blackhat SEO campaign exposed.<br />
<br />
<b>10.</b> <a href="http://ddanchev.blogspot.com/2008/08/guerilla-marketing-for-conspiracy-site.html">Guerilla Marketing for a Conspiracy Site</a><br />
Conspiracy theorists may in fact have a new wallpaper to show off with<br />
<br />
<b>11.</b> <a href="http://ddanchev.blogspot.com/2008/08/banker-malware-targetting-brazilian.html">Banker Malware Targeting Brazilian Banks in the Wild</a><br />
When misinformed and not knowing anything about a particular underground segment, a potential cybercriminal would stick to using such primitive compared to the sophisticated banker malware kits currently in the wild. These sophisticated banker malware kits are often coming in a customer-tailored proposition, with their price increasing or decreasing based on the specific module to be included or excluded. For instance, a module targeting all the U.S banks that has been put in a "learning mode" long before it was made available to the customers can be requested and is often available with the business model build around the customer's wants&nbsp; <br />
<br />
<b>12.</b> <a href="http://ddanchev.blogspot.com/2008/08/compromised-cpanel-accounts-for-sale.html">Compromised Cpanel Accounts For Sale</a><br />
Despite the massive SQL injection attacks, accounting data for Cpanel accounts coming from malware infected hosts seems to be once again coming into play, which isn't surprising given the filtering capabilities and log parsing tools today's botnet masters are empowered with. These very same compromised Cpanel accounts and the associated domains often end up so heavility abused that it's tactics like these that are driving the underground multitasking mentality, namely, abusing a single compromised account for each and every malicious online activity you can think of - even hosting banners for their blackhat SEO services <br />
<br />
<b>13.</b> <a href="http://ddanchev.blogspot.com/2008/08/diverse-portfolio-of-fake-security.html">A Diverse Portfolio of Fake Security Software - Part Two</a><br />
In August we saw a peek of fake security software, neatly typosquatted domains whose authors earn revenue each and every time someone installs the software. The vendors behind this software are forwarding the entire process of driving traffic to those excelling in aggregating traffic and abusing it. As anticipated, underground multitasking started taking place within the fake security software domains, with the people behind them introducing client-side exploits in order to improve the monetization of the traffic coming to the sites<br />
<br />
<b>14.</b> <a href="http://ddanchev.blogspot.com/2008/08/diy-botnet-kit-promising-eternal.html">DIY Botnet Kit Promising Eternal Updates</a><br />
There's no such thing as a (quality) free botnet kit. What's for free is often the leftovers from a single feature of a more sophisticated proprietary botnet kit. This one in particular is however trying to demonstrate that even a plain simple GUI botnet command and control software can achieve the results desired by an average script kiddie, and not necessarily satisfy the needs of the experienced botnet master<br />
<br />
<b>15.</b> <a href="http://ddanchev.blogspot.com/2008/08/diverse-portfolio-of-fake-security_20.html">A Diverse Portfolio of Fake Security Software - Part Three</a><br />
As far as trends and fads are concerned, the majority of the domains are currently parked at up to four different IPs, with most of them going into a stand by mode once they get detected and reappear back couple of weeks later<br />
<br />
<b>16.</b> <a href="http://ddanchev.blogspot.com/2008/08/fake-celebrity-video-sites-serving.html">Fake Celebrity Video Sites Serving Malware - Part Two</a><br />
Due to the template-ization of fake celebrity video sites, and simple traffic management tools combined with blackhat SEO tactics, these sites are also prone to increase in the next couple of months<br />
<br />
<b>17.</b> <a href="http://ddanchev.blogspot.com/2008/08/web-based-botnet-command-and-control.html">Web Based Botnet Command and Control Kit 2.0</a><br />
It's releases like these that remind us of the amount of time, efforts and personal touch that a malicious attacker would put into such a management kit, currently acting as a personal benchmark as far as complexity and features indicating the coder's experience with botnets is concerned. What's he's failing to anticipate is that this kit is sooner or later going to turn into the "MPack of botnet management"<br />
<br />
<b>18.</b> <a href="http://ddanchev.blogspot.com/2008/08/diverse-portfolio-of-fake-security_25.html">A Diverse Portfolio of Fake Security Software - Part Four</a><br />
Keep it coming, we'll keep it exposing until we end up getting down to the "fake software vendor" itself<br />
<br />
<b>19.</b> <a href="http://ddanchev.blogspot.com/2008/08/automatic-email-harvesting-20.html">Automatic Email Harvesting 2.0</a><br />
Email harvesting is slowly maturing into a vertically integrated service provided by vendors of managed spamming services. This email harvesting module is aiming to close the page on text obfuscation in respect to fighting spam, and is successfully recognizing and collecting such publicly available emails. From a psychological perspective though, the end users who bothered to obfuscate their emails are less likely to fall victims into phishing scams, with the obfuscation speaking for a relatively decent situational awareness on how they emails end up in a spammer's campaign<br />
<br />
<b>20.</b> <a href="http://ddanchev.blogspot.com/2008/08/fake-porn-sites-serving-malware-part.html">Fake Porn Sites Serving Malware - Part Three</a><br />
As a firm believer in sampling in order to draw conclusions on the big picture, an approach that has proven highly accurate in modeling historical and upcoming tactics and behavior, a single fake porn site serving malware campaign usually exposes a dozen of misconfigured redirectors, which thanks to their misconfiguration despite the evasive features available within the kits, expose another dozen of malware campaigns<br />
<br />
<b>21.</b> <a href="http://ddanchev.blogspot.com/2008/08/facebook-malware-campaigns-rotating.html">Facebook Malware Campaigns Rotating Tactics</a><br />
With no particular flaw exploited other than the social engineering tactic of using already compromised Facebook accounts who would automatically spam all their friends with links to flash files hosted at legitimate services, the more persistent the campaign is, the higher the chance that it will scale enough. This campaign in particular is mainly relying on rotation of tactics, namely different messages, different services and file extensions used in order to trick someone's friend into visiting the URL. With the number of users increasing, the most popular social networking sites are naturally going to be permanently under attacks from cybercriminals<br />
<br />
<b>22.</b> <a href="http://ddanchev.blogspot.com/2008/08/fake-security-software-domains-serving.html">Fake Security Software Domains Serving Exploits</a><br />
Despite that it's a single brand, namely the International Virus Research Lab that's introducing client-side exploits within it's portfolio of domains, the opportunity for abuse may be noticed by the rest of the brands pretty fast<br />
<br />
<b>23.</b> <a href="http://ddanchev.blogspot.com/2008/08/exposing-indias-captcha-solving-economy.html">Exposing India’s CAPTCHA Solving Economy</a><br />
Taking into consideration the mentality surrounding a particular country's cybercriminals, how they think, how they operate, what do they define as an opportunity, and how much personal efforts are they willing to put into their campaigns, I wouldn't be surpised if a Russian vendor offering 100,000 bogus Gmail accounts for sale has in fact outsourcing the account registration process to Indian workers, paid them pocket change and is then reselling them ten to twenty times higher than the price he originally paid for them. <br />
<br />
The text based CAPTCHAs used at the major Internet portals and services, are so efficiently abused by this approach that continuing to use is directly undermining the trust these email providers and services often come with as granted<div class="feedflare">
<a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=VdcSL"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=VdcSL" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=2dvxL"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=2dvxL" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=hYvml"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=hYvml" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=YfcJl"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=YfcJl" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=WUVJL"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=WUVJL" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=jRCTL"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=jRCTL" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?a=KYkll"><img src="http://feeds.feedburner.com/~f/DanchoDanchevOnSecurityAndNewMedia?i=KYkll" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~4/388609194" height="1" width="1"/>]]></content:encoded>
      <pubDate>Wed, 10 Sep 2008 02:57:32 +0000</pubDate>
      <category domain="http://securityratty.com/tag/malware">malware</category>
      <category domain="http://securityratty.com/tag/facebook malware campaigns">facebook malware campaigns</category>
      <category domain="http://securityratty.com/tag/usefulness pinch malware">usefulness pinch malware</category>
      <category domain="http://securityratty.com/tag/banker malware kits">banker malware kits</category>
      <category domain="http://securityratty.com/tag/malware campaigns">malware campaigns</category>
      <category domain="http://securityratty.com/tag/botnet">botnet</category>
      <category domain="http://securityratty.com/tag/diy botnet kit">diy botnet kit</category>
      <category domain="http://securityratty.com/tag/distribute malware">distribute malware</category>
      <category domain="http://securityratty.com/tag/banker malware">banker malware</category>
      <source url="http://feeds.feedburner.com/~r/DanchoDanchevOnSecurityAndNewMedia/~3/388609194/summarizing-augusts-threatscape.html">Summarizing August's Threatscape</source>
    </item>
    <item>
      <title><![CDATA[Modelling Air Traffic Control]]></title>
      <link>http://securityratty.com/article/7f9e569822e0521bce9615d70124032f</link>
      <guid>http://securityratty.com/article/7f9e569822e0521bce9615d70124032f</guid>
      <description><![CDATA[Today I will discussa general approach to model air traffic control (ATC)using our CEP/EP reference architecture which is an application of the mature JDL multisensor data fusion model
ATC is an...]]></description>
      <content:encoded><![CDATA[<p>Today I will discuss a general approach to model air traffic control (ATC) using our <a href="http://www.thecepblog.com/what-is-complex-event-processing/" target="_blank">CEP/EP reference architecture </a>which is an application of the mature <a href="http://www.data-fusion.org/article.php?sid=70" target="_blank">JDL multisensor data fusion model</a>.</p>
<p>ATC is an excellent working example of complex event processing.   Radar and GPS provide the basic sensory information to accurately track and trace the position of each aircraft in the area of responsibility (AOR) of a particular control tower/zone.     Naturally,  sensory information is preprocessed and formatted in such a way that the data can be processed upstream by multiple real-time applications.</p>
<p>Before we look at complex ATC scenarios, such as &#8220;potential collision&#8221; or &#8220;aircraft off approach vector&#8221; we must trace and trace individual objects, aircraft-objects, accurately with very high confidence.    In addition to tracking aircraft-objects, there is a database of information about the aircraft (ideally), such as make, model, age, range, passengers and other properties about the aircraft-object.      In addition, there is a state-model for each aircraft, for example the aircraft might be &#8220;on the ground&#8221;, &#8220;approaching the runway&#8221;, &#8220;cleared for takeoff&#8221;, &#8220;cruising altitude&#8221;, &#8220;approaching runway&#8221;, &#8220;final decent&#8221; etc.  </p>
<p>Tracking and tracing individual aircraft is what is generally referred to as &#8220;object refinement&#8221; in our CEP/EP reference architecture.   The reason we call this function &#8220;object refinement&#8221; is that system engineers are focused on optimizing the situational knowledge about individual objects.     Sometimes we refer to this function as &#8220;track and trace&#8221; because that is what we are doing to  each object in the model.  In Marc Adler&#8217;s recent <a href="http://www.thecepblog.com/2008/09/07/modelling-shoplifting/" target="_blank">shoplifting scenario</a>, Marc was interested in tracking and tracing people in a store using imaging processing techniques to estimate their behavioral patterns.  In the same way, before we can process for scenarios such as &#8220;potential shoplifter&#8221; or &#8220;suspicious criminal gang activity&#8221; we must be able to accurately process (track and trace) individual object, such as people or merchandise.</p>
<p>Back to aircraft and ATC, the &#8220;complex event processing&#8221; begins when we are looking about object-object relationships, in this model, aircraft-to-aircraft, but this is an overly simplistic model, as we have not yet added (to our model) ground features (towers, buildings, power lines), weather (storm cells, wind) and other flying objects (known migratory bird paths, swarms of insects) to our simple model.  </p>
<p>Complex event processing occurs when we are processing multiple objects in our model looking for threats in real-time.     Practically speaking, all ATC applications are CEP applications.  This means that vendors and integrators who build ATC applications are also CEP vendors.   </p>
<blockquote><p>Editorial Note: CEP/EP has been around for a long time and was not recently invented in the past decade as some &#8220;inventors&#8221; would like for us to believe. </p></blockquote>
<p>As you can imagine, there is considerable &#8220;complex event processing&#8221; that goes on &#8220;behind the scenes&#8221; to provide air traffic controllers and pilots situational knowledge into the &#8220;friendly skies&#8221;.   As you might further imagine, the situation is more complex when the skies are &#8220;not so friendly&#8221;, for example, in air combat situations.   </p>
<p>Processing myriad objects is not the end of the processing &#8220;chain&#8221;.  For example, decisions are being made constantly about potential damage, alternative airports, and more.    In our reference model, we refer to this, generally speaking, as &#8220;impact assessment&#8221; because we must take an estimated detected complex event, for example &#8220;aircraft collision,&#8221; and estimate potential damage based on numerous factors such as, the amount of jet fuel in the aircrafts and the location of the aircrafts (over a large city or rural area, near a hospital and emergency services).   Regardless of the scenario, an impact assessment is normally required before optimal decisions can be made.</p>
<blockquote><p>This is true, by the way, for our <a href="http://www.thecepblog.com/2008/09/07/modelling-shoplifting/" target="_blank">shoplifting example</a> (the impact is different if a piece of gum is stolen versus a $1,000,000 diamond necklace or weapons-grade nuclear material) and other scenarios and models.  Static data (information about objects) is required for accurate decision processing.  </p></blockquote>
<p>Impact assessment is not the end of the &#8220;knowledge chain&#8221;.    Decisions are constantly being made that effect resources.  For example, suggestion an alternative route for an aircraft is a resource management decision.    Turning on and off radar or switching to alternative tracking devices is a resource management function.  In our CEP/EP reference model (based on the JDL data fusion model), we call this &#8220;resource management&#8221;.   This function includes contacting emergency services and directing them to a potential crash location or sending out a message to instruct all aircraft to stay off a certain radio frequency.  Resource management is critical.</p>
<p>Our simple ATC model today is by no means complete, it just scratches the surface.  In fact, I have a very close friend, <a href="http://www.linkedin.com/pub/0/b45/b16" target="_blank">Mark Secrist</a>, who is a former Marine fighter pilot and currently a senior captain for <a href="http://www.aa.com" target="_blank">American Airlines</a>.   I have asked Mark to read this post and help me further refine this crude &#8220;laymans&#8221; ATC model (Thanks Mark!).</p>
]]></content:encoded>
      <pubDate>Mon, 08 Sep 2008 09:27:26 +0000</pubDate>
      <category domain="http://securityratty.com/tag/model">model</category>
      <category domain="http://securityratty.com/tag/crude laymansatc model">crude laymansatc model</category>
      <category domain="http://securityratty.com/tag/state-model">state-model</category>
      <category domain="http://securityratty.com/tag/simple atc model">simple atc model</category>
      <category domain="http://securityratty.com/tag/complex">complex</category>
      <category domain="http://securityratty.com/tag/isconsiderable complex event">isconsiderable complex event</category>
      <category domain="http://securityratty.com/tag/overly simplistic model">overly simplistic model</category>
      <category domain="http://securityratty.com/tag/complex event">complex event</category>
      <category domain="http://securityratty.com/tag/simple model">simple model</category>
      <source url="http://www.thecepblog.com/2008/09/08/modelling-air-traffic-control/">Modelling Air Traffic Control</source>
    </item>
    <item>
      <title><![CDATA[More on Why Routing is Not Complex Event Processing]]></title>
      <link>http://securityratty.com/article/b2a2132904db8b6f400e9dc6e9ba65b1</link>
      <guid>http://securityratty.com/article/b2a2132904db8b6f400e9dc6e9ba65b1</guid>
      <description><![CDATA[Interestingly, CEP is Not BPM, BAM, BRE, BRMS or SOA stimulated many great comments andthe rebuttal Smart Order Routing and CEP - Made for Each Other . James Taylor responded with Business rules,...]]></description>
      <content:encoded><![CDATA[<p>Interestingly, <a href="http://www.thecepblog.com/2008/08/27/cep-is-not-bpm-bam-bpm-brms-or-soa/">CEP is Not BPM, BAM, BRE, BRMS or SOA</a> stimulated many great comments and the rebuttal <a href="http://streambase.typepad.com/streambase_stream_process/2008/09/smart-order-routing-and-cep.html">Smart Order Routing and CEP - Made for Each Other</a>.  James Taylor responded with <a href="http://www.ebizq.net/blogs/decision_management/2008/08/business_rules_decisions_and_e.php">Business rules, decisions and events</a>.   I followed up with <a href="http://www.thecepblog.com/2008/09/03/cep-is-not-low-latency-messaging-eai-or-esb/">CEP is Not Low Latency Messaging, EAI or ESB</a> and James replied in turn with <a href="http://www.ebizq.net/blogs/decision_management/2008/09/still_more_on_event_processing.php" target="_blank">Still More on Event Processing</a>.  It&#8217;s great to see the blogosphere doing so well.  Continuing, I would like to discuss smart order routing (SOR) a bit more and why routing is not CEP.</p>
<p>First of all, let&#8217;s ground the discussion a bit by translating &#8220;smart order routing&#8221; to &#8220;rule-based message routing&#8221; since in this application &#8220;smart&#8221;  translates to &#8220;using rules&#8221; and &#8220;order&#8221; translates to &#8220;message&#8221;.    Basically, Mark (and other &#8220;new on the routing scene&#8221; stream processing players) argue that rule-based message routing is CEP.  I will argue that routing is not even close to CEP.  Here is why,</p>
<p>Let&#8217;s take a look at a router on the backbone of the global Internet.   A backbone router has very sophisticated software developed over many decades.   These routers run sophisticated, mature algorithms to determine how to route messages (packets) and use these algorithms to build complex routing tables. </p>
<p>In addition, these routers process messages (packets) from countless sources and route messages (packets) to countless destinations.  Using some of the terms in early posts (above), there is a great &#8220;confluence of events&#8221; processed by routers.    Futhermore, there are normally quite complex authentication, authorization and other security parameters managed in a router, all in real time.   Routers do much more, but I don&#8217;t want to get too deep into routing in this post.</p>
<p>My point is that, without any doubt, global Internet routers process very &#8220;cloudy&#8221; &#8220;confluence of events&#8221; with much more sophistication than order routing applications.    However, we do not call Internet routing &#8220;CEP&#8221;, regardless of how many connections are processed or how much sophisticated processing occurs.  The reason is because the &#8220;C&#8221; in &#8220;CEP&#8221; defines a complexity that is at a higher abstraction than messaging and routing.</p>
<p>If you study the literature on CEP, some of which I posted recently, CEP was envisioned to solve complex event processing problems &#8220;on top of the routing layer&#8221; because the routing layer is a mature technology layer.  We can route, pure and simple.  Of course, we are always seeking faster, more scaleable and more secure routing. </p>
<p>I admire some of the startups in the CEP/ESP/EP space for working hard to make money and for aggressively positioning their products and attempting to build market share.   However, issues surface when these same companies seem to believe they are the first companies to work in the event processing or message routing space and that they can define whatever they want as &#8220;complex event processing&#8221; as long as it benefits their sales targets.</p>
<p>There is no doubt that a router does much more sophisticated event processing than the new rule-based stream processing systems running continuous queries across streaming data.  There is no doubt that a router processes a complex &#8220;confluence of events&#8221;.   However, we don&#8217;t call routers &#8220;CEP&#8221;. </p>
<p>We do not call routers &#8220;CEP&#8221; because CEP is about a higher level of knowledge processing.  CEP was created to detect the &#8220;complex events&#8221; that happen above the mediation and routing layer.     The literature and original examples on CEP are quite clear on this.</p>
<p> </p>
]]></content:encoded>
      <pubDate>Thu, 04 Sep 2008 05:38:58 +0000</pubDate>
      <category domain="http://securityratty.com/tag/complex">complex</category>
      <category domain="http://securityratty.com/tag/complex event">complex event</category>
      <category domain="http://securityratty.com/tag/solve complex event">solve complex event</category>
      <category domain="http://securityratty.com/tag/upwith cep">upwith cep</category>
      <category domain="http://securityratty.com/tag/cep">cep</category>
      <category domain="http://securityratty.com/tag/event">event</category>
      <category domain="http://securityratty.com/tag/cep defines">cep defines</category>
      <category domain="http://securityratty.com/tag/call routers cep">call routers cep</category>
      <category domain="http://securityratty.com/tag/call">call</category>
      <source url="http://www.thecepblog.com/2008/09/04/more-on-why-routing-is-not-complex-event-processing/">More on Why Routing is Not Complex Event Processing</source>
    </item>
    <item>
      <title><![CDATA[The Kum Bai Ya of Event Processing]]></title>
      <link>http://securityratty.com/article/498ae6976f44f86c66a91c8c3ef77d62</link>
      <guid>http://securityratty.com/article/498ae6976f44f86c66a91c8c3ef77d62</guid>
      <description><![CDATA[Kindred spirit Marc Adler mentions being abitturned off by thesniping back-and-forthin the CEP/EP blog-o-sphere.This was exactly how I felt in early 2006 whenfolks were sniping back and forth about...]]></description>
      <content:encoded><![CDATA[<p>Kindred spirit Marc Adler <a href="http://magmasystems.blogspot.com/2008/08/brief-thoughts-on-standardized.html" target="_blank">mentions</a> being a bit &#8221;turned off&#8221; by the sniping back-and-forth in the CEP/EP blog-o-sphere.  This was exactly how I felt in early 2006 when folks were sniping back and forth about SQL standards and event stream processing (ESP).  A group of vendors had created some stream processing engines and all were in &#8220;power positioning&#8221; mode with the acronyms &#8220;ESP&#8221; and &#8221;CEP&#8221;, hoping to ride what they perceived as a future event processing <a href="http://en.wikipedia.org/wiki/Gravy_train" target="_blank">gravy train</a>.</p>
<p>My goal at that time was to show everyone that there was a very mature (functional) reference architecture with decades of maturity that applies to (complex) event processing, adapted from the <a href="http://www.data-fusion.org/article.php?sid=70" target="_blank">JDL model for information fusion.</a>  <em><a href="http://en.wikipedia.org/wiki/Kumbaya" target="_blank">Kum Bai Ya</a>.</em></p>
<p style="text-align: center;"><img src="http://www.silkroad-asia.com/blogimgs/jdl2.jpg" alt="Event Processing Reference Architecture" width="440" height="240" /></p>
<p style="text-align: left;">There is plenty of room for everyone in this model.  <em>Kum Bai Ya.</em></p>
<p style="text-align: left;">The model is inclusine not exclusive.<em> Kum Bai Ya.</em></p>
<p style="text-align: left;">The JDL model is based on years of operational maturity.  <em>Kum Bai Ya.</em></p>
<p style="text-align: left;">The model is functionally and technically accurate.  <em>Kum Bai Ya.</em></p>
<p style="text-align: left;">Everyone at the first event processing symposium (March 2006) seemed to agree with this model, at least publicly, because there was no &#8220;push back&#8221; at the symposium.  <em>Kum Bai Ya.</em></p>
<p>Professor David Luckham did not discuss architecture in his book, <em>The Power of Events.  Kum Bai Ya</em>.</p>
<p>David&#8217;s research at Stanford, some CEP related, was funded by DARPA, who also support the JDL information fusion model.  <em>Kum Bai Ya.</em></p>
<p>TIBCO Software adopted the JDL model (Note: I worked for TIBCO the time.) <em>Kum Bai Ya</em>.</p>
<p>We built a functional reference architecture around this mature model.  <em>Kum Bai Ya</em>.</p>
<p>We did not claim we invented it.  <em>Kum Bai Ya</em>.</p>
<p>We did not patent the model, only shared it. <em>Kum Bai Ya</em>.</p>
<p>The model is free and open for everyone to use.  <em>Kum Bai Ya</em>.</p>
<p>The folks in the military and government totally agree with this model for CEP/EP.  <em>Kum Bai Ya</em>.</p>
<p>Complex operational problems are addressed every day with this model. <em>Kum Bai Ya</em>.</p>
<p>Air traffic control uses this model.  <em>Kum Bai Ya</em>.</p>
<p>Missile defense uses this model to protect us from harm everyday.  <em>Kum Bai Ya</em>.</p>
<p>Intrusion detection and network management now use this model (Note: I published an ACM paper on adapting this model for cybersecurity 10 years ago). <em>Kum Bai Ya</em>.</p>
<p>Oh, blog-o-sphere.  <em>Kum Bai Ya</em>.</p>
]]></content:encoded>
      <pubDate>Mon, 01 Sep 2008 08:58:40 +0000</pubDate>
      <category domain="http://securityratty.com/tag/kum bai">kum bai</category>
      <category domain="http://securityratty.com/tag/model">model</category>
      <category domain="http://securityratty.com/tag/mature model">mature model</category>
      <category domain="http://securityratty.com/tag/jdl model">jdl model</category>
      <category domain="http://securityratty.com/tag/patentthe model">patentthe model</category>
      <category domain="http://securityratty.com/tag/event">event</category>
      <category domain="http://securityratty.com/tag/functional reference architecture">functional reference architecture</category>
      <category domain="http://securityratty.com/tag/reference architecture">reference architecture</category>
      <category domain="http://securityratty.com/tag/asa future event">asa future event</category>
      <source url="http://www.thecepblog.com/2008/09/01/the-kum-bai-ya-of-event-processing/">The Kum Bai Ya of Event Processing</source>
    </item>
    <item>
      <title><![CDATA[Mainframe Mindset]]></title>
      <link>http://securityratty.com/article/fd258564c92d60a0ba9f7e4c10df7ee6</link>
      <guid>http://securityratty.com/article/fd258564c92d60a0ba9f7e4c10df7ee6</guid>
      <description><![CDATA[You might think a mature industry like mainframes means low growth, but IBM is still selling mainframes like hotcakes. IBM said its mainframe business rose 32% in the second quarter compared to...]]></description>
      <content:encoded><![CDATA[<p>You might think a mature industry like mainframes means low growth, but IBM is still selling mainframes like hotcakes. IBM said its mainframe business rose 32% in the second quarter compared to overall sales growth of 13%. How many 1960s technologies are putting up these numbers in 2008? The reality is that what mainframes do, they do well. While some companies invest 8 figures in moving to a supposed latest and greatest ERP or CRM solution, many would be better served by putting a Web services gateway in front of the mainframe to address the mainframe&#39;s chief weakness - distribution.</p><br /><div>From a security point of view, mainframes are interesting because they were designed for a closed environment. Their advocates generally talk about the beauty of RACF and so on, and that is all well and good until people go and put them on the web! Approaches vary, but it usually amounts to MQ Series with not authentication, sitting in front of the mainframe with a J2EE server talking to the queues. What happens then is a major shift, because the mainframe security model is designed (rightly for its time) to be focused on the resource owner (remember the R in RACF). There is a minimal effort on securing the subject, the claim and so on.</div><br /><div>Again the mindset is fine when its your own employees in a room using a terminal, but its another thing altogether when you are integrating with a distributed system. This is where we need more focus on securing the subject and the claim, not just the resource. This is of course where new standards and technologies &#160;such as SAML and Information Cards come in. Its not enough to protect the object resource and assume a benign controlled (or controllable) subject and claim, you have to add layers of protection to the subject and claim as well.&#160;</div>]]></content:encoded>
      <pubDate>Wed, 13 Aug 2008 17:18:17 +0000</pubDate>
      <category domain="http://securityratty.com/tag/mainframe">mainframe</category>
      <category domain="http://securityratty.com/tag/mainframe security model">mainframe security model</category>
      <category domain="http://securityratty.com/tag/mainframe business">mainframe business</category>
      <category domain="http://securityratty.com/tag/object resource">object resource</category>
      <category domain="http://securityratty.com/tag/resource">resource</category>
      <category domain="http://securityratty.com/tag/subject">subject</category>
      <category domain="http://securityratty.com/tag/claim">claim</category>
      <category domain="http://securityratty.com/tag/web services gateway">web services gateway</category>
      <category domain="http://securityratty.com/tag/security">security</category>
      <source url="http://1raindrop.typepad.com/1_raindrop/2008/08/mainframe-mindset.html">Mainframe Mindset</source>
    </item>
    <item>
      <title><![CDATA[EPTS: An Event Processing Marketing Society (EPMS)]]></title>
      <link>http://securityratty.com/article/4e5f9a576dd94f69f8da4a0f60aa3870</link>
      <guid>http://securityratty.com/article/4e5f9a576dd94f69f8da4a0f60aa3870</guid>
      <description><![CDATA[A number of months ago we posted Some Comments on the EPTS Member Agreement where we concluded, in summary
I have quite a few other concerns the with EPTS Member Agreement. Basically, the agreement...]]></description>
      <content:encoded><![CDATA[<p>A number of months ago we posted <a title="Some Comments on the EPTS Member Agreement" rel="bookmark" href="http://www.thecepblog.com/2008/04/06/comment-on-the-epts-member-agreement/"><span style="color: #105cb6;">Some Comments on the EPTS Member Agreement</span></a> where we concluded, in summary:</p>
<blockquote><p><em>&#8220;I have quite a few other concerns the with EPTS Member Agreement.   Basically, the agreement needs to be written with an eye toward a more flexible, open and inclusive process that puts the future of the EPTS square into the hands of the event processing community, not a small group of well intended folks who represent a small part of the overall event processing community and worldview.&#8221;</em></p></blockquote>
<p>Opher&#8217;s reply was to just dismiss these comments, a bit surprising since I served the CEP/EP community on the EPTS steering committee; worked quite hard as a matter of fact, for a number of years.   Opher&#8217;s appreciation for the years of work is to just off-handly dismiss my comments.</p>
<p>Then in <a href="http://epthinking.blogspot.com/2008/08/on-faithfull-representation-and-other.html"><span style="color: #2583ad;">On faithfull representation and other comments</span></a> and <a href="http://epthinking.blogspot.com/2008/08/on-top-down-and-bottom-up.html"><span style="color: #2583ad;">On Top Down and Bottom Up</span></a> Opher does the same thing, he simply dismisses my comments, defensively, adding humor, sarcasm and fallacy.</p>
<p>I am sorry Opher is so defensive of his narrow society; however I will not yield, because I do not need to resort to sarcasm, fallacy and <em>ad hominums</em>; the facts obviously support my view.  For proof that Opher has a narrow view of event processing, go no further than look at the companies he hand-picked for his EPTS Steering Committee; most startups (or with startup products) in the event processing space, working on common messages to distinguish themselves in a market with much more mature players excluded - classic &#8220;not invented here,&#8221; isn&#8217;t it?</p>
<p>Opher&#8217;s claims the EPTS view on event processing is quite general, but the  majority of vendors on the EPTS Steering Committee members are selling similar platforms, a very narrow segment of the CEP/EP space.    Opher claims that he agrees that other domains (like sensor fusion) are significant to CEP/EP, but he simply dismisses my advice to create a true, general EPTS, inclusive of the prior-art and science of CEP/EP (before the marketing folks took over).  He insists on having the EPTS &#8220;reinvent the wheel&#8221; and develop their own vocabulary, as if event processing did not exist prior to one book on CEP.</p>
<p>Opher&#8217;s fun-to-read blog counterpoints to my concerns are evolving to a mixture of <a href="http://http://en.wikipedia.org/wiki/Ad_hominum" target="_blank"><em>ad hominums</em></a> and sarcasm, sometime wrapped in a defensive tone.   I think we can do better and we must be more inclusive of the other prior-art.  I say we, because I am also a founding member of the EPTS, althought I suspect Opher will banish my name from the membership for trying to diminish the &#8220;not invented here&#8221; attitude that seems to dominate the EPTS since inception.</p>
<p>The truth of the matter is that the EPTS has a relatively narrow view of event processing, evident by the makeup of the steering committee and the focus of their discussions.    It is not a technical society about event processing, <em>per se</em>; it is a marketing society with a narrowly focused membership that discounts most of the prior-art in the event processing space, it is really, an<em> Event Processing Marketing Society (EPMS) </em>for a narrow group of niche players.</p>
<p>The event processing domain is much, much larger.   The art-and-science of event processing is deep and mature, much more mature (and inclusive) than what we see in the EPTS. </p>
<p>I think Opher (and the EPTS committee) should take these comments seriously and not discount them with sarcasm and subtle <em>ad hominum </em>replies.</p>
<p> </p>
]]></content:encoded>
      <pubDate>Wed, 13 Aug 2008 04:02:57 +0000</pubDate>
      <category domain="http://securityratty.com/tag/epts">epts</category>
      <category domain="http://securityratty.com/tag/event">event</category>
      <category domain="http://securityratty.com/tag/vendors onthe epts">vendors onthe epts</category>
      <category domain="http://securityratty.com/tag/epts committee">epts committee</category>
      <category domain="http://securityratty.com/tag/technical societyabout event">technical societyabout event</category>
      <category domain="http://securityratty.com/tag/forhis epts">forhis epts</category>
      <category domain="http://securityratty.com/tag/epts reinvent">epts reinvent</category>
      <category domain="http://securityratty.com/tag/narrow">narrow</category>
      <category domain="http://securityratty.com/tag/community">community</category>
      <source url="http://www.thecepblog.com/2008/08/13/epts-an-event-processing-marketing-society-epms/">EPTS: An Event Processing Marketing Society (EPMS)</source>
    </item>
    <item>
      <title><![CDATA[The Secret Life of CEP]]></title>
      <link>http://securityratty.com/article/e452d659bce6955164d7e64080c735b6</link>
      <guid>http://securityratty.com/article/e452d659bce6955164d7e64080c735b6</guid>
      <description><![CDATA[Catching up on the blogs, I couldnt help but comment on, Is CEP Mature? Or a Curious Case of Information Asymmetry by Mark Tsimelzon, President &amp; CTO, Coral8. Mark says
I know for a fact that every...]]></description>
      <content:encoded><![CDATA[<p>Catching up on the blogs, I couldn&#8217;t help but comment on, <a title="Is CEP Mature? Or a Curious Case of Information Asymmetry" href="http://www.coral8.com/blogs/blog-entry/cep-mature-or-curious-case-information-asymmetry">Is CEP Mature? Or a Curious Case of Information Asymmetry</a> by Mark Tsimelzon, President &amp; CTO, Coral8.  Mark says,</p>
<blockquote><p>&#8220;I know for a fact that every <em>major</em> CEP vendor has several dozen paying customers.&#8221;</p></blockquote>
<p>Somehow Mark, I don&#8217;t find a dozen paying customers by the top CEP vendors very impressive.</p>
<p>Then, as to somehow justify the lack of public reference clients, Mark takes the position of a Coral8 customer and says,</p>
<blockquote><p>&#8220;We believe that the use of Coral8 gives us a strategic advantage over our competitors. Why would we want to clue them in?&#8221;</p></blockquote>
<p>Naturally, the same thing could have been said about the first desktop computer, or the first back-office banking system, or the first calculator, or the first telephone, frankly speaking.</p>
<p>Of course, when the technology is mature, then it is &#8220;Hey we have lots of computers!&#8221; &#8220;Hey, look at my fully functional sexy iPhone!&#8221; &#8220;We have the best back office banking systems on the planet by &lt;insert your favorite big vendor here&gt;!&#8221;</p>
<p>Well, all this CEP Solution Secrecy (CEPSS) might just be similar to why the government keeps many IT projects a secret;  the main reason is so we don&#8217;t know how much taxpayer money they are spending!</p>
<p>So, folks, the debate counterpoint that there is some &#8220;Secret Life of CEP&#8221; and that the CEP solutions today are somehow changing the way C-Level executives, and corporate America, thinks is just wishful thinking.</p>
<p>Companies don&#8217;t need to keep their strong technical solutions a secret. Like, Wow! I am using Coral8 and it is so impressive that I have to keep it TOP SECRET.  (Sorry Mark, nothing personal, you simply gave me a big red target and painted &#8220;fire when ready&#8221; on it)</p>
<p>Note:  I happen to like Coral8, and Coral8 Studio, as an event stream processing platform.</p>
<p>Back on point, I consider my laptop and cellphone more indispensable than most of the first generation rule-based stream processing engines out there today, and I am sure most CEOs agree.</p>
<p>The Secret Life of CEP&#8230;.   you just have to just love it <img src='http://www.thecepblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
      <pubDate>Tue, 05 Aug 2008 14:32:44 +0000</pubDate>
      <category domain="http://securityratty.com/tag/cep">cep</category>
      <category domain="http://securityratty.com/tag/secret">secret</category>
      <category domain="http://securityratty.com/tag/cep solutions">cep solutions</category>
      <category domain="http://securityratty.com/tag/major cep vendor">major cep vendor</category>
      <category domain="http://securityratty.com/tag/secret life">secret life</category>
      <category domain="http://securityratty.com/tag/cep solution secrecy">cep solution secrecy</category>
      <category domain="http://securityratty.com/tag/cep mature">cep mature</category>
      <category domain="http://securityratty.com/tag/top secret">top secret</category>
      <category domain="http://securityratty.com/tag/coral8">coral8</category>
      <source url="http://www.thecepblog.com/2008/08/05/the-secret-life-of-cep/">The Secret Life of CEP</source>
    </item>
    <item>
      <title><![CDATA[On CEP as a Discipline]]></title>
      <link>http://securityratty.com/article/a9d1f2721b6335854aee35ef66fda256</link>
      <guid>http://securityratty.com/article/a9d1f2721b6335854aee35ef66fda256</guid>
      <description><![CDATA[In CEP as a Discipline , David Luckham wrote
Actually, it is fair to say that some of CEP can be found in other disciplines. Event processing has been going on in one form or another, for the past 50...]]></description>
      <content:encoded><![CDATA[<p>In  <a href="http://http://forum.complexevents.com/viewtopic.php?f=13&amp;t=121" target="_blank">CEP as a Discipline</a>,  David Luckham wrote: </p>
<blockquote><p><em>&#8220;Actually, it is fair to say that some of CEP can be found in other disciplines. Event processing has been going on in one form or another, for the past 50 years. Simulation, Networking, Active DBs, Middleware.</p>
<p>{ &#8230;. }</p>
<p>CEP has only just begun. The foundations are unexplored. Its an open field of research issues.&#8221;</em></p></blockquote>
<p>Actually, on slide 12 of this presentation from 2006 <a class="postlink" href="http://www.complexevents.com/slides/TIBCO_MARCH_2006.ppt">Processing Patterns for PredictiveBusiness</a>, we show that the foundations for complex event processing have been in place for many years and in many disciplines such as multisensor data fusion, control theory, sensor management, planning, correlation, estimation, tracking, information fusion, data fusion, data mining and more.</p>
<p>One obvious problem (or at least obvious to many of us) with the current group think marketing CEP is that many have ignored the established foundations for event processing and complex event processing that have been mature for many decades. It is not very efficient (nor good for customers) to pick a phrase, or concept, like &#8220;CEP&#8221; and ignore the relevant mulitiple disciplines that have been used to solve complex classes of distributed event processing problems for decades.</p>
<p>Therefore, &#8220;CEP has only begun&#8221; is only true for those who have &#8216;drank the CEP koolaid&#8221; and do not understand (yet) that they are &#8220;reinventing the event processing wheel&#8221; and ignoring (by accident or purposely, I have no idea of the motives) the prior-art and/or selectively picking the prior art or research associated with their company, byline, favorite researcher, CEO, etc. This is a fundamental issue (and constraint) with CEP, in my opinion. Complex event processing does not stand alone as an art or a science, nor should it, nor should it be based on single dimensional, or small groups of single dimensional, technologies.</p>
<p>If you want to see many of the foundations of CEP, you don&#8217;t need to go much further than slide 12 of this  presentation from 2006, <a class="postlink" href="http://www.complexevents.com/slides/TIBCO_MARCH_2006.ppt">Processing Patterns for PredictiveBusiness</a>.</p>
<p>Based on my observation, it reminds me of a small group of folks on a discovery mission where their ship lands on the shore of a distant land and they call this &#8220;new land&#8221; &#8212; &#8220;CEP&#8221; because they feel they have discovered a new land.  Nevermind the big cities that already exist or the many people already &#8220;in the fields&#8221; of their new land.  These &#8221;CEP explorers&#8221; are seemingly in some kind of modern day epic struggle to define themselves as &#8220;discoverers&#8221; or &#8220;founders&#8221; and they are coming up with new names of the lakes, rivers, streams and mountains that defined the landscape long before their ship arrived.</p>
<p>Note: It is encouraging to see folks slowly &#8220;catching up&#8221;&#8230;. maybe in a few years we will move CEP beyond the &#8220;not invented here&#8221; mind share that we see today.</p>
<p>Also note that, recently we saw a flurry of posts where many people rightly stated that &#8220;CEP was overhyped&#8221; - but then in rebuttal the EPTS community leaders came back with &#8220;Is CEP a mere hype?&#8221; or &#8220;Is CEP a hype?&#8221;. spinning the discussion to an extreme position that is wildly different than &#8220;CEP is Overhyped&#8221;.   </p>
]]></content:encoded>
      <pubDate>Tue, 05 Aug 2008 04:46:27 +0000</pubDate>
      <category domain="http://securityratty.com/tag/cep">cep</category>
      <category domain="http://securityratty.com/tag/move cep">move cep</category>
      <category domain="http://securityratty.com/tag/land cep">land cep</category>
      <category domain="http://securityratty.com/tag/multisensor data fusion">multisensor data fusion</category>
      <category domain="http://securityratty.com/tag/data">data</category>
      <category domain="http://securityratty.com/tag/complex event">complex event</category>
      <category domain="http://securityratty.com/tag/event">event</category>
      <category domain="http://securityratty.com/tag/prior art">prior art</category>
      <category domain="http://securityratty.com/tag/art">art</category>
      <source url="http://www.thecepblog.com/2008/08/05/on-cep-as-a-discipline/">On CEP as a Discipline</source>
    </item>
  </channel>
</rss>
