Securosis

Research

Understanding and Selecting an Enterprise Firewall

What? A research report on enterprise firewalls. Really? Most folks figure firewalls have evolved about as much over the last 5 years as ant traps. They’re wrong, of course, but people think of firewalls as old, static, and generally uninteresting. But this is unfounded. Firewalls continue to evolve, and their new capabilities can and should impact your perimeter architecture and firewall selection process. That doesn’t mean we will be advocating yet another rip and replace job at the perimeter (sorry, vendors), but there are definitely new capabilities that warrant consideration – especially as the maintenance renewals on your existing gear come due. We have written a fairly comprehensive paper that delves into how the enterprise firewall is evolving, the technology itself, how to deploy it, and ultimately how to select it. We assembled this paper from the Understand and Selecting an Enterprise Firewall blog series from August and September 2010. Special thanks to Palo Alto Networks for sponsoring the research. Download: Understanding and Selecting an Enterprise Firewall Attachments Securosis_Understanding_Selecting_EFW_FINAL.pdf [340KB] Share:

Share:
Read Post

Understanding and Selecting a Tokenization Solution

Tokenization is currently one of the hottest topics in database and application security. In this report we explain what tokenization is, when it works best, and how it works – and give recommendations to help choose the best solution. Tokenization is just such a technology: it replaces the original sensitive data with non-sensitive placeholders. Tokenization is closely related to encryption – they both mask sensitive information – but its approach to data protection is different. With encryption we protect the data by scrambling it using a process that’s reversible if you have the right key. Anyone with access to the key and the encrypted data can recreate the original values. With tokenization we completely replace the real value with a random, representative token. Understanding and Selecting a Tokenization Solution Attachments Securosis_Understanding_Tokenization_V.1_.0_.pdf [1.4MB] Share:

Share:
Read Post

Data Encryption 101: A Pragmatic Approach to PCI

The Payment Card Industry (PCI) Data Security Standard (DSS) was developed to encourage and enhance cardholder data security and facilitate the broad adoption of consistent data security measures. The problem is that the guidance provided is not always clear. This is especially true when it comes to secure storage of credit card information. The gap between recommended technologies and how to employ them leaves a lot of room for failure. This white paper examines the technologies and deployment models appropriate for both security and compliance, and provides actionable advice on how to comply with the PCI-DSS specification. This page provides a place to participate with comments, recommendations or critiques in the comment fields below. As always, we research and write the content, and sponsors decide to participate (or not) only after the content was made publicly available on the blog. We would like to thank Prime Factors, Inc. for their sponsorship of this paper. Data Encryption 101: A Pragmatic Approach to PCI Compliance. (PDF) (Version 1.0, September 2010) Attachments Data_Encryption_101_FINAL.pdf [289KB] Share:

Share:
Read Post

Understanding and Selecting SIEM/Log Management

Anyone worried about security and/or compliance has probably heard about Security Information and Event Management (SIEM) and Log Management. But do you really understand what the technology can do for your organization, how the products are architected, and what is important when trying to pick a solution for your organization? Unfortunately far too many end user organizations have learned what’s important in SIEM/LM the hard way – by screwing it up. But you can learn from the pain of others, because we have written a fairly comprehensive paper that delves into the use cases for the technology, the technology itself, how to deploy it, and ultimately how to select it. We assembled this paper from the Understand and Selecting a SIEM/Log Management blog series from June and July 2010. Special thanks to Nitro Security for sponsoring the research. Download: Understanding and Selecting SIEM/Log Management (PDF) Attachments Securosis_Understanding_Selecting_SIEM_LM_FINAL.pdf [439KB] Share:

Share:
Read Post

White Paper: Endpoint Security Fundamentals

Endpoint Security is a pretty broad topic. Most folks associate it with traditional anti-virus or even the newfangled endpoint security suites. In our opinion, looking at the issue just from the perspective of the endpoint agent is myopic. To us, endpoint security is as much a program as anything else. In this paper we discuss endpoint security from a fundamental blocking and tackling perspective. We start with identifying the exposures and prioritizing remediation, then discuss specific security controls (both process and product), and also cover the compliance and incident response aspects. If you are trying to understand how to comprehensively protect your endpoint devices, this paper will provide a great perspective and allow you to put all your defenses into context. We assembled this document from the Endpoint Security Fundamentals series posted to the blog in early April, all compiled together, professionally edited, and prettified. Special thanks to Lumension Security for licensing the report. Download: Endpoint Security Fundamentals (PDF) Attachments Securosis_EndpointSecurityFundamentals_v2.1.pdf [190KB] Share:

Share:
Read Post

Understanding and Selecting a Database Encryption or Tokenization Solution

This paper includes descriptions of major database encryption and tokenization technologies, a decision tree to help determine which type of encryption is best for you, and example use cases drawn from real world deployments. If you are considering any database encryption or tokenization project, this paper should save you hours of research and architecture development time. Understanding and Selecting a Database Encryption or Tokenization Solution Version 1.0 (PDF, 516KB) You can see the history in the original blog posts, starting with Introduction To Database Encryption – The Reboot! and ending with Database Encryption, Part 7: Wrapping Up. Attachments Securosis_Understanding_DBEncryption.V_.1_.pdf [502KB] Share:

Share:
Read Post

Low Hanging Fruit: Quick Wins with Data Loss Prevention (V2.0)

Two of the most common criticisms of Data Loss Prevention (DLP) that comes up in user discussions are a) its complexity and b) the fear of false positives. Security professionals worry that DLP is an expensive widget that will fail to deliver the expected value – turning into yet another black hole of productivity. But when used properly DLP provides rapid assessment and identification of data security issues not available with any other technology. We don’t mean to play down the real complexities you might encounter as you roll out a complete data protection program. Business use of information is itself complicated, and no tool designed to protect that data can simplify or mask the underlying business processes. But there are steps you can take to obtain significant immediate value and security gains without blowing your productivity or wasting important resources. In this paper we highlight the lowest hanging fruit for DLP, refined in conversations with hundreds of DLP users. These aren’t meant to incorporate the entire DLP process, but to show you how to get real and immediate wins before you move on to more complex policies and use cases. Download: Low Hanging Fruit: Quick Wins with Data Loss Prevention Previous Versions: Download: Low Hanging Fruit: Quick Wins with Data Loss Prevention Attachments QuickWins_with_DLP.v.2.pdf [300KB] QuickWins_with_DLP.v_.1_.pdf [285KB] Share:

Share:
Read Post

Report: Database Assessment

Our goal with this paper is to help customers cut through the marketing fluff, and spotlight the differentiators between current database assessment platforms and the previous generation of DBA tools. While we discuss the individual functional components that constitute assessment platforms, don’t get scared off by the technical discussions. We also cover business justification and compliance for those who are not responsible for managing databases, but need information from the database to do their jobs. We did our best to address questions that will be posed by the different groups who are interested in database assessment technologies. Database Assessment is distinctly different than other forms of platform and network assessment you may already be familiar with. This is partially due to the complexity of the database itself, and also because assessment provides information to multiple audiences besides the database administrators (DBAs). Databases require specialized skills to manage and secure. As database threats evolve – and as we see a continuing growth of compliance requirements relevant to data and database infrastructure – most admins are reliant on assessment support for specialized security and compliance policies. These topics are outside the core job skills of the average DBA. Assessment tools have evolved into full-fledged enterprise class products that not only address underlying vulnerability and patch management issues; but a complete range of security, compliance, and operational tasks. We are also including a comment area for you to participate with comments, recommendations, and critiques. As we anticipate periodic updates to the content, we recommend that you periodically revisit this section for updates. As always, we research and write the content, and sponsors choose to participate only after the content was made publicly available on the blog. We would like to thank Application Security Inc. (AppSec), Imperva, and Qualys for their sponsorship of this paper. (Version 1.0, February 2010) Understanding and Selecting a Database Assessment Solution (PDF) Attachments Understanding_DB_Assessment_v1.pdf [317KB] Share:

Share:
Read Post

Database Assessment

Our goal with this paper is to help customers cut through the marketing fluff, and spotlight the differentiators between current database assessment platforms and the previous generation of DBA tools. While we discuss the individual functional components that constitute assessment platforms, don’t get scared off by the technical discussions. We also cover business justification and compliance for those who are not responsible for managing databases, but need information from the database to do their jobs. We did our best to address questions that will be posed by the different groups who are interested in database assessment technologies. Database Assessment is distinctly different than other forms of platform and network assessment you may already be familiar with. This is partially due to the complexity of the database itself, and also because assessment provides information to multiple audiences besides the database administrators (DBAs). Databases require specialized skills to manage and secure. As database threats evolve – and as we see a continuing growth of compliance requirements relevant to data and database infrastructure – most admins are reliant on assessment support for specialized security and compliance policies. These topics are outside the core job skills of the average DBA. Assessment tools have evolved into full-fledged enterprise class products that not only address underlying vulnerability and patch management issues; but a complete range of security, compliance, and operational tasks. We are also including a comment area for you to participate with comments, recommendations, and critiques. As we anticipate periodic updates to the content, we recommend that you periodically revisit this section for updates. As always, we research and write the content, and sponsors choose to participate only after the content was made publicly available on the blog. We would like to thank Application Security Inc. (AppSec), Imperva, and Qualys for their sponsorship of this paper. (Version 1.0, February 2010) Understanding and Selecting a Database Assessment Solution (PDF) Attachments Understanding_DB_Assessment_v1.pdf [317KB] Share:

Share:
Read Post

Project Quant Metrics Model Report

This report represents the current findings of the Project Quant open patch management project. The report will be updated as the research continues and we refine the model. Please see the project site for more information. Click here for Version 1.0 of the report, released July 27, 2009 Attachments ProjectQuant.v1_.pdf [1.1MB] 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.