Fifth Cable Down, Iran Offline, Coincidence Meter Drops

Update: Thanks to Windexh8er (who provides good information despite being far more inflammatory than he needs to, what’s up with that?) Iran is up and the traffic report is wrong. Another cable is down in the Middle East, and Iran is now offline. News stories indicate the cables are relatively new, and odds of simultaneous component failure are low. This can’t be seismic activity or we’d see other reports from scientists (kind of hard to hide earthquakes and volcanos these days). The odds are inching towards deliberate tampering, but I’m not going to go all crazy with conspiracy theories yet. There could still be other explanations. And no, I don’t think this is the CIA with black submarines. If we have that capability, which I’m sure we do, we wouldn’t blow it by screwing with cables during Super Bowl weekend just to annoy people. It’s too strategically important a capability to tip our hand without a compelling, immediate cause. < p style=”text-align:right;font-size:10px;”>Technorati Tags: Cyberattack Share:

Read Post

The DLP Guys Will Have A Field Day With This One

It seems that an attorney at Eli Lilly’s outside legal firm accidentally sent an email with confidential information over government settlement talks to a reporter at the New York Times. The Times reporter then started poking around, eventually breaking the story far before anyone was prepared. Oops. Did I mention it was a $1B settlement? Now before we get too excited, let’s keep in mind that even if Eli Lilly deployed DLP, it’s unlikely that their little outside law firm would. We also need to ask ourselves if any of their DLP policies would have prevented this type of leak, which will depend greatly on what was actually sent to the Times. Perhaps we should start by disabling autocomplete in our email applications first. I wonder what percentage of email leaks are merely the result of that little feature? Share:

Read Post

Most Amusing Security Breach Of The Week

Oops, over in England an HSBC branch forgot to lock the doors and turn on the alarm. A 5-year-old accidentally wandered in while his dad was using the ATM. Reading the article, the bank is trying to cover their asses with outright lies. My favorite line from the article? The Pettigrews stood guard at the bank until police officers arrived. I suspect someone might be in some remedial door-closing training right now. < p style=”text-align:right;font-size:10px;”>Technorati Tags: Physical security Share:

Read Post

Reminder- SunSec Is *TONIGHT*

6pm, at Furio in Scottsdale. Website/directions here. Happy hour runs to 7, and you don’t want to miss it (the food is better, tasty pasta dishes). Like last time, anyone with even a passing interest in security is welcome. We hang out, drink beer/wine/whatever, network, BS, and lie about our BBS hacking from the 80’s. At least, those of us old enough to remember what a BBS is do. Email me with questions. < p style=”text-align:right;font-size:10px;”>Technorati Tags: SunSec Share:

Read Post

Network Security Podcast- The Conspiracy Episode

This week on the Network Security Podcast, we discuss cut cables, government monitoring, and sea monsters. Okay, maybe not sea monsters, but there seem to be strange happenings out in the world. Our guest this week is Mike Murray, of the blog. Mike’s a friend of both Martin and myself, and one of the founders of the Source conference in Boston, which I’ll be speaking at in March. As always, the podcast and show notes are available here. < p style=”text-align:right;font-size:10px;”>Technorati Tags: Network Security Podcast, Physical security, Conspiracy Share:

Read Post

Three Applications That Will Cause Us Security Headaches For At Least Three Years

Internet Explorer/ActiveX QuickTime Adobe Acrobat Reader Each of these applications has plugin architectures and inadequate security models. Actually, IE 7 + Vista is a good model, but it will take 3 years for it to hit wide enough deployment. < p style=”text-align:right;font-size:10px;”>Technorati Tags: Adobe Acrobat, Apple, Internet Explorer, Microsoft, Adobe, QuickTIme 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.