Securosis

Research

A Brief Privacy Breach History Lesson

The big ChoicePoint breach of 2004 was the result of criminals creating false business accounts and running credit reports on hundreds of thousands of customers (probably). Every major credit/background company has experienced this kind of breach of service going back decades – just look at the Dataloss DB. Doxxing isn’t necessarily hacking, even when technology is involved. All this has happened before, and all this will happen again. Even very smart humans are fooled every day. Share:

Share:
Read Post

Incite 3/13/13: Get Shorty

It’s hard to believe, but my family and I have been in Atlanta almost 9 years. The twins were babies; now they are people. Well, kind of. I grew up in the Northeast and spent many days shoveling our driveway during big snowstorms. Our 15 years in Northern Virginia provided a bit less shoveling time, but not much. But the ATL is a different animal. It snows maybe once a year, and the dusting is usually gone within a few hours. I can recall one time, over the past 8 winters, when we got enough snow to actually make a snowman. We are usually pummeled by one good ice storm a year, which wreaks havoc because no one in the South knows how to drive in bad weather, and I think there are a total of 3 snow plows in the entire state. Now that it’s starting to warm up a bit I look forward to breaking out my flipflops and summer work attire, which consists of shorts and T-shirts. Unless I have a meeting – then I wear a polo shirt. But that’s still probably 6 weeks away for me. Having grown up with the cold, I hate it now. I just don’t like to be cold. I get my Paul Bunyan on with a heavy lumberjacket (one of those flannel Thinsulate coats) to take the kids out to the bus in the AM. Even if it’s in the 40s. I have been known to wear my hat and gloves until May. Whatever it takes for me to feel toasty warm, regardless of how ridiculous I look. The Boy has a different opinion. It’s like he’s an Eskimo or something. Every morning (without fail) we have an argument about whether he can wear shorts. Around freezing? No problem, shorts work for him. Homey just doesn’t care. He’ll wear shorts at any time, literally. There was one morning earlier this year where I called his bluff. I said “fine, wear your shorts.” It was about 35 degrees. He did, and he didn’t complain at all about being cold. I even made him walk the two blocks to the bus and stand outside (while I sat in the warm car). He didn’t bat an eyelash. But the Boss did. I took a pounding when he came off the bus in shorts that afternoon. I tried to prove a point, but he took my point and fed it back to me, reverse alimentary style. No matter the temperature, a hoody sweatshirt and shorts are good for him. His behavior reminds me of returning to NYC after a college spring break in Acapulco many moons ago. Most of us were bundled up, but one of my buddies decided to leave his Jose Cuervo shorts on, while wearing his winter jacket. It was about 20 degrees, and after a week of chips and guacamole and Corona and 4am Devil Dogs (and the associated Montezuma’s revenge), we just absolutely positively needed White Castle. Don’t judge me, I was young. My friend proceeded to get abused by everyone in the restaurant. They asked if he was going to the beach or skiing. It was totally hilarious, even 25 years later. I can totally see the Boy being that guy wearing shorts in the dead of winter. But part of being a parent is saving the kids from making poor decisions. The Boss is exceptional at that. She proclaimed the Boy cannot wear shorts if it will be below 50 degrees at any time during the day. There were no negotiations. It was written on a stone tablet and the Boy had no choice but to accept the dictum. Now he dutifully checks the weather every night and morning, hoping to get the high sign so he can wear his beloved shorts. Who knows, maybe he’ll become a meteorologist or something. Unless they tell him he can’t wear shorts on air – then he’ll need to find something else to do. –Mike Photo credits: Taking a jog in shorts after Winter Storm Nemo originally uploaded by Andrew Dallos Upcoming Cloud Security Training Interested in Cloud Security? Are you in EMEA (or do you have a ton of frequent flyer miles)? Mike will be teaching the CCSK Training in Reading, UK April 8-10. Sign up now. Heavy Research We’re back at work on a variety of blog series, so here is a list of the research currently underway. Remember you can get our Heavy Feed via RSS, where you can get all our content in its unabridged glory. And you can get all our research papers too. Email-based Threat Intelligence Quick Wins Analyzing the Phishing Food Chain Industrial Phishing Tactics Understanding Identity Management for Cloud Services Buyers Guide Architecture and Design Integration Newly Published Papers Network-based Threat Intelligence: Searching for the Smoking Gun Understanding and Selecting a Key Management Solution Building an Early Warning System Implementing and Managing Patch and Configuration Management Defending Against Denial of Service Attacks Incite 4 U Everything increases risk if firewall management sucks: In this week’s mastery of the obvious piece, we hear that Segmentation Can Increase Risks If Firewalls Aren’t Managed Well. The article provides a bully pulpit the firewall management vendors to tell us how important their stuff is. Normally I’d lampoon this kind of piece, but operating a large number of firewalls really is hard. Optimizing their use is even harder. Do it wrong, and you create a hole big enough to drive a truck through. So after years of maturing, these tools are finally usable for large environments, which means we will be doing a series within the next month or so. Stay tuned… – MR Preparation: I loved the idea of Netflix’s Chaos Monkey when I heard of it. An application that looks for inefficient deployments and deliberately causes them to fail. Very much in the Big Data design philosophy, where you assume failure occurs regularly – which both makes Netflix service better and continually verifies system resiliency. So when I read Threatpost’s How Facebook Prepared to Be Hacked I thought it would be

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.