Securosis

Research

Friday Summary – January 9, 2009

Here it is, our first Friday Summary of 2009. While it’s Adrian’s week to put the summary together, we thought it would be better if I handled the intro since I was at Macworld looking at cool stuff all week while he was manning the fort and cleaning my gutters (if he ever reads his employment contract, I’m totally screwed). Last year was my first Macworld, and I feel lucky I got to see the Great Jobsness give a keynote before he decided to take a break. Phil Shiller did a great job, there just wasn’t that much to announce; even without Jobs, these are still the best product announcement sessions I’ve ever seen. As for the products, I think Apple is hitting a home run with the iLife changes- the power in iPhoto and iMovie is just sturn ing. But if you want to read about this stuff, head over to our TidBITS coverage. On the security front I saw two really interesting things I’d like to award with the Securosis Best of Macworld Expo. First up is Agile Software for 1Password. They win for 2 reasons- first is that they decided to cancel My1password.com. The idea was to build a web application for password management you could access from anywhere. If you read this site, you know the difficulties in such as risky move. Instead they are leveraging DropBox and letting you move passwords via USB storage. Yes, there are still risks, but it’s a granular system and sometimes we really do need to move passwords around with us. The second reason is the upcoming 3.0 version of the product. It’s polished, secure, useful, and one of those tools I use daily. Our second winner is Checkpoint for a pre-alpha version of the iPhone VPN client. They added an option so that when you go to connect it sends a text message to your phone with a one time password. Sure, this has been done before, but on the iPhone the VPN client automatically picks the password out of the text message and logs you in… no manual cutting and pasting or anything. Which is good, because you sort of can’t cut and paste on the iPhone. I saw a lot of other really great stuff, and quite enjoyed the usual evening activities. Macworld is a lot less crazy than our security conferences, so Amrit Williams and Adam O’Do ell came out to spice things up, and Amrit ran into Raffi while parking his car. Who says Mac users hate security! (Then again, I was buying, which might explain a few things). On that note, it’s time to catch up on massive amounts of email and turn the Summary back over to Adrian for all the security news I missed… Here is the week’s security summary: Webcasts, Podcasts, Outside Writing, and Conferences: The Network Security Podcast this week was a little shorter with Rich being at Moscone Center and Martin needing to spend time with the family, but they covered some good stuff with a discussion on 0Auth, weak passwords, the Phishing attack on Twitter users and facial recognition in iPhoto. Rich has a nice writeup of the new MacBook Pro on Tidbits. Favorite Securosis Posts: Rich: Part 8 of Building a Web Application Security Program is a great ending to the series. Adrian: Contingency Plans: The tech collapse took its toll on me, but I learned a lot, and hopefully there might be some advice you find helpful during this go-round. Favorite Outside Posts: Adrian: Robert Graham’s post on Verisign’s Response to the MD5 cert problem is a good analysis of the situation and how Verisign responded. It’s a bad sign when a company fails to defend its core business and then reacts in this manner when issues are pointed out. Rich: Crazy Apple Rumors site: “The best Keynote Liveblog ever!” Top News and Posts: Twitter Phish reported this week. Social engineering gets better and it becomes increasingly difficult to tell a real from fake without close inspection. MacWorld with week, with a nice, shiny new MacBook Pro announced. Life parodies itself, with CheckFree having a breach of 5M records. Unemployment is officially listed at 7.2% nationally. Here in AZ, our state is telling us it is still around 6.8%, but I am willing to bet that it is closer to double that number. TJX Hacker gets 30 years. More and more fake shopping sites popping up. Blog Comment of the Week: windexh8er on Part 7, Secure Operations: Great series guys! I was just playing around with NSMnow! — so the content in the monitoring portion was fresh in my mind. Maybe look to include a tools list in your next post where you talk about balancing the program. http://www.securixlive.com/nsmnow/index.php   Which is one of our recommendations in part 8 … we’ll also do a ‘recommended free tools’ post in the coming weeks. Share:

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.