Why Someone Will Eventually Hack This Site (and Maybe Your Computer in the Process)

I hate to admit it, but someone will probably hack this site at some point. And they may even use it to hack your computer. And there’s not a darn thing I can do about it. Security, and hacking, are kind of trendy. Both the good guys and the bad guys have a habit of focusing on certain attacks and defenses based on what’s “hot”. We’re kind of the fashion whores of the IT world. I mean I just can’t believe Johnny calls himself a 1337 hax0r for finding a buffer overflow in RPC. I mean that’s just so 2002. Everyone knows that all the cool hackers are working on XSS and browser attacks. The trend of the month seems to be cross-site scripting and embedding attacks into trusted websites. Cross site scripting (XSS) is a form of attack where the attacker takes advantage of poorly-programmed or poorly-configured web pages, and can embed his or her own code in the page to go after your browser (a seriously simple explanation, check out Wiki for more). MITRE (they speak CVE!) called cross-site scripting the number 1 vulnerability of all time (in terms of volume). Dark Reading reports a number of major sites hacked recently this way. Possibly hundreds of sites hosted on HostGator were hacked (not with cross site scripting) and code inserted (using an iframe for you geeks) to infect anyone with the temerity to visit the sites using Internet Explorer (we DID warn you). None of this is new. We’ve had attackers embedding attacks into trusted sites for years. It may be trendy, but it isn’t new by any means. Some are pretty devious- like hacking advertising servers that then distribute their ads on sites all over the net. It’s a great form of social engineering- compromising a trusted authority and using that to distribute your attack. Not that I’m assuming my paranoid readers actually trust this site, but I won’t be surprised if it’s hacked, and hopefully most of you are following security precautions and won’t be compromised yourself. Why? Because this site is hosted. I manage my little part of the server, but I don’t control it myself. I use all sorts of tools like WordPress and cPanel, all of which have their own security flaws. Sure, I’ve managed secure servers and coded secure pages in the past, but I kind of have a day job now. I rely on my hosting provider, and while I tried to choose one with a good reputation, my ego can’t write checks their bodies can’t cash. We, as users, need to take some responsibility ourselves. Just staying away from “those” sites isn’t enough, we also need to understand trusted sites may be compromised at some point, too. So far I’m safe on a Mac, and you Windows users can stay off IE (maybe until 7 comes out) and use anti-spyware and antivirus tools with maybe a little host intrusion prevention. Not that I don’t want you to trust me, but heck, I don’t even really trust myself. I’m just some dude with a blog waiting for the fall security colors… Share:

Read Post

How to Smell Security Snake Oil in One Sentence or Less

If someone ever tells you something like the following: “We defend against all zero day attacks using a holistic solution that integrates the end-to-end synergies in security infrastructure with no false positives.” Run away. Share:

Read Post

It Ain’t Over- Apple Responds to Ou/Toorcon Showdown?

I swear, every time I think this thing is dead, its pale desiccated hand reaches from the grave, grabbing at our innocent ankles. Lynn Fox at Apple responded to some very direct questions from George Ou at ZDNet. At this point I’m surprised Apple is letting this drag on; all it does is bring the black spotlight of security on them which, as Microsoft and Oracle will attest to, isn’t necessarily a good thing. Fox’s response seems risky unless she is absolutely certain Maynor and Ellch have nothing, and are basically, you know, suicidal. That doesn’t jive with what I know- even what I’m allowed to (and have) revealed. Toorcon is the end of this week. Ou will be there to watch Maynor and Ellch present. I suspect it will be somewhat interesting. I never suspected a chance meeting at Defcon would drop me into what’s become one of the most bizarre disclosure situations I’ve ever seen. This is even making Ciscogate look tame. Share:

Read Post

Amrit Loves Cowbell

Amrit Williams is a coworker over at Gartner and he’s obsessed with cowbell and security tools that go to 11. Let’s just say this post isn’t the first time he’s brought it up. Seriously, Amrit is a great analyst and welcome addition to the security blogging world. Unlike many of us he worked his way through the trenches of the vendor world, including stints at McAfee and NCircle. And, in this case, he’s right. A dirty secret of security is that if you do your job too well, people stop buying new product. Remember when AV was $30 with unlimited free updates (and didn’t bring your system to its knees)? Seriously, it was. Here’s a snippet, and check out his site: Bottom line: You should not have to pay more for increased functionality year over year – demand more from your vendors, tell them that you don’t need an anti-virus, anti-spyware, anti-rootkit, anti-phishing, anti-x, with a personal firewall, host-based intrusion detection, and wireless security and networking configuration capabilities each sold to you at a premium – get them all for a single price, the price you paid last year for AV. Let them know that turning it up to 11 is not going to win the gig when what you are really looking for is more cow-bell. Share:

Read Post

Totally Transparent Research is the embodiment of how we work at Securosis. It’s our core operating philosophy, our research policy, and a specific process. We initially developed it to help maintain objectivity while producing licensed research, but its benefits extend to all aspects of our business.

Going beyond Open Source Research, and a far cry from the traditional syndicated research model, we think it’s the best way to produce independent, objective, quality research.

Here’s how it works:

  • Content is developed ‘live’ on the blog. Primary research is generally released in pieces, as a series of posts, so we can digest and integrate feedback, making the end results much stronger than traditional “ivory tower” research.
  • Comments are enabled for posts. All comments are kept except for spam, personal insults of a clearly inflammatory nature, and completely off-topic content that distracts from the discussion. We welcome comments critical of the work, even if somewhat insulting to the authors. Really.
  • Anyone can comment, and no registration is required. Vendors or consultants with a relevant product or offering must properly identify themselves. While their comments won’t be deleted, the writer/moderator will “call out”, identify, and possibly ridicule vendors who fail to do so.
  • Vendors considering licensing the content are welcome to provide feedback, but it must be posted in the comments - just like everyone else. There is no back channel influence on the research findings or posts.
    Analysts must reply to comments and defend the research position, or agree to modify the content.
  • At the end of the post series, the analyst compiles the posts into a paper, presentation, or other delivery vehicle. Public comments/input factors into the research, where appropriate.
  • If the research is distributed as a paper, significant commenters/contributors are acknowledged in the opening of the report. If they did not post their real names, handles used for comments are listed. Commenters do not retain any rights to the report, but their contributions will be recognized.
  • All primary research will be released under a Creative Commons license. The current license is Non-Commercial, Attribution. The analyst, at their discretion, may add a Derivative Works or Share Alike condition.
  • Securosis primary research does not discuss specific vendors or specific products/offerings, unless used to provide context, contrast or to make a point (which is very very rare).
    Although quotes from published primary research (and published primary research only) may be used in press releases, said quotes may never mention a specific vendor, even if the vendor is mentioned in the source report. Securosis must approve any quote to appear in any vendor marketing collateral.
  • Final primary research will be posted on the blog with open comments.
  • Research will be updated periodically to reflect market realities, based on the discretion of the primary analyst. Updated research will be dated and given a version number.
    For research that cannot be developed using this model, such as complex principles or models that are unsuited for a series of blog posts, the content will be chunked up and posted at or before release of the paper to solicit public feedback, and provide an open venue for comments and criticisms.
  • In rare cases Securosis may write papers outside of the primary research agenda, but only if the end result can be non-biased and valuable to the user community to supplement industry-wide efforts or advances. A “Radically Transparent Research” process will be followed in developing these papers, where absolutely all materials are public at all stages of development, including communications (email, call notes).
    Only the free primary research released on our site can be licensed. We will not accept licensing fees on research we charge users to access.
  • All licensed research will be clearly labeled with the licensees. No licensed research will be released without indicating the sources of licensing fees. Again, there will be no back channel influence. We’re open and transparent about our revenue sources.

In essence, we develop all of our research out in the open, and not only seek public comments, but keep those comments indefinitely as a record of the research creation process. If you believe we are biased or not doing our homework, you can call us out on it and it will be there in the record. Our philosophy involves cracking open the research process, and using our readers to eliminate bias and enhance the quality of the work.

On the back end, here’s how we handle this approach with licensees:

  • Licensees may propose paper topics. The topic may be accepted if it is consistent with the Securosis research agenda and goals, but only if it can be covered without bias and will be valuable to the end user community.
  • Analysts produce research according to their own research agendas, and may offer licensing under the same objectivity requirements.
  • The potential licensee will be provided an outline of our research positions and the potential research product so they can determine if it is likely to meet their objectives.
  • Once the licensee agrees, development of the primary research content begins, following the Totally Transparent Research process as outlined above. At this point, there is no money exchanged.
  • Upon completion of the paper, the licensee will receive a release candidate to determine whether the final result still meets their needs.
  • If the content does not meet their needs, the licensee is not required to pay, and the research will be released without licensing or with alternate licensees.
  • Licensees may host and reuse the content for the length of the license (typically one year). This includes placing the content behind a registration process, posting on white paper networks, or translation into other languages. The research will always be hosted at Securosis for free without registration.

Here is the language we currently place in our research project agreements:

Content will be created independently of LICENSEE with no obligations for payment. Once content is complete, LICENSEE will have a 3 day review period to determine if the content meets corporate objectives. If the content is unsuitable, LICENSEE will not be obligated for any payment and Securosis is free to distribute the whitepaper without branding or with alternate licensees, and will not complete any associated webcasts for the declining LICENSEE. Content licensing, webcasts and payment are contingent on the content being acceptable to LICENSEE. This maintains objectivity while limiting the risk to LICENSEE. Securosis maintains all rights to the content and to include Securosis branding in addition to any licensee branding.

Even this process itself is open to criticism. If you have questions or comments, you can email us or comment on the blog.