Friday Summary: January 13, 2012

You’ve probably noticed we have not been doing a lot of blogging lately. Sorry about that – we’ll start back up with a bang very soon. This will be a very exciting year for Securosis – we have a bunch of projects in the pipe. I’ll be launching a re-start of the Database Activity Monitoring 2.0 series now that we have finally settled on the terminology and done sufficient research on the trends to actually convey what’s going on. Mike and I want to cover some Log Management topics, and I have a data masking research project underway as well. All that is over and above new developments with the Securosis Nexus, the Cloud Security Alliance Training, and our RSA Guide – so Q1 will be very busy and we will be writing a lot. I’ll publish my Q2 research agenda in the coming weeks, so if you have anything you want to talk about at RSA we can go into detail then. And I wanted to comment on a ton of great posts I have seen, but alas… On a personal note, during the Christmas break I was wandering the local mall, when I saw this guy with a mountain bike. It’s cool! It’s got carbon fiber, big-azz shocks, and hydraulic disk brakes. He let me pick it up and it’s like 20 lbs. 20 lbs is less than a tire from my old bike! So I was fascinated. I had to have one. I did some looking on the Internet and decided to visit the last couple bike shops still in business in my area. I found a bike I like, they threw some pedals on it, and I headed out. I got on the bike and the first thing that ran through my mind was “FREEDOM! I can go anywhere. And I should!” Weird. Freedom. I felt like a kid with my first new bike – which would prove prophetic as I crashed it 4 times a few days later, just as I did with my first bike at age four. That was a weird sensation. It’s not like I don’t have freedom, and I have owned cars since I was sixteen, so I can pretty much go anywhere I want. But this was different. I went back into the shop, and the guy asked me how I liked it. “Beautiful” I said, and bought it. I got home, saddleed up, and headed straight out into the desert. I just pointed the bike in a direction I had never gone, over a hill I had never seen the other side of, and started pedaling. Open desert. Cactus, coyotes, and boulders be dammed! And it was awesome. Of course there are practical downsides to this freedom – other than plucking thorns out of my skin with tweezers and bathing road rash in betadine. I have over 10k hours on a BMX bike as a kid, and 5k hours on road bikes, so I considered myself an expert rider. Wrong! This is a totally difference experience. I am a novice, as proven emphatically by the four crahes on my second ride. Well, ‘crashed’ is not quite correct – technically the bike and I just swapped places, with the bike taking me for a short ride. And as with a new pair of shoes, you should make sure everything is broken in and comfortable before you go pushing the envelope. I found out – about 2 milliseconds after I needed to bail out – that my new snap-in pedals were much too tight. Jumping simply meant the bike followed me, turning the tables, so it was – ahem – in the driver’s seat. And I learned that mountain bikes have a variable stall speed: when pedaling furiously uphill in low gear you don’t actually have sufficient momentum to go over boulders like a badass – instead you can quickly find yourself going backwards. It’s a thought-provoking experience. Regardless, I am hooked. And now Christmas break is over and I am back at work. But like a little kid I keep looking out the window, wishing I could play with my new Christmas toy instead of talking to this vendor about a product of questionable quality, with its suspect value proposition. “Please tell me more about how you stop APT in a totally new way nobody has ever thought of before.” sigh On to the Summary: Webcasts, Podcasts, Outside Writing, and Conferences Adrian quoted in Sandhill Channels. Rich’s guest post on Trustworthy Computing. Mike and Jack Daniel on Continuous Monitoring. Securosis Posts Checking out a bootable Windows TPM thumb drive. Incite 1/11/2012: Spoilsport. Social Security Blogger Awards: Voting Open! Network-based Malware Detection: Where to Detect the Bad Stuff? Favorite Outside Posts Mike Rothman: Costco’s Value Chain. Of course it’s Gunnar who points out a great perspective on understanding your company’s value and sticking to that, using an example from Costco. Even if it’s hard. Even if it costs money in the short term. Rich: Nick Selby on how we need to stop blaming the victims. I’m not going to defend Stratfor’s massive mistakes, but we need to stop acting like a room full of a-holes, blaming the victims of crimes for being stupid… especially because we will all be eventual victims. And for the record, good luck using my 20-character random Stratfor password. Adrian Lane: Apple iWallet Security? Leverage “what you have” security – provided you don’t leave it in your hotel room! Dave Mortman: AES on the iPhone isn’t broken by Default. Project Quant Posts Malware Analysis Quant: Find Infected Devices. Malware Analysis Quant: Defining Rules. Malware Analysis Quant: The Malware Profile. Malware Analysis Quant: Dynamic Analysis. Malware Analysis Quant: Static Analysis. Malware Analysis Quant: Build Testbed. Malware Analysis Quant: Confirm Infection. Malware Analysis Quant: Process Map (Draft 1). Research Reports and Presentations Applied Network Security Analysis: Moving from Data to Information. Tokenization Guidance. Security Management 2.0: Time to Replace Your SIEM?. Fact-Based Network Security: Metrics and the Pursuit of

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.