Securosis

Research

Data Security Lifecycle- Technologies, Part 2

In our last post on this topic we covered the technologies that encompass the Create and Store stages of the Data Security Lifecycle. Today we’ll detail out the tools for Use and Share. As a reminder, since we’ll be delving into each technology in more detail down the road, these posts will just give a high-level overview. There are also technologies used for data security, such as data-in-motion encryption and enterprise kay management, that fall outside the lifecycle and will be covered separately. Use Activity Monitoring and Enforcement: Probably one of the most underutilized tools in the security arsenal. Application Activity Monitoring and Enforcement is more than simply collecting audit logs, although it can include that, but uses more advanced techniques to capture all user activity within the application or database context. Database Activity Monitoring: Monitoring all database activity, including all SQL activity. Can be performed through network sniffing of database traffic, agents installed on the server, or via external monitoring, typically of transaction logs. Many tools combine monitoring techniques, and network-only monitoring is not recommended. DAM tools are managed externally to the database to provide separation of duties from database administrators (DBAs). All DBA activity can be monitored without interfering with their ability to perform job functions. Tools can alert on policy violations, and some tools can block certain activity. Application Activity Monitoring: Similar to Database Activity Monitoring, but at the application level. Third-party tools that can integrate with a number of application environments, such as standard web application platforms, SAP, and Oracle, and monitor user activity at the application level. As with DAM, tools can use network monitoring or local agents, and can alert and sometimes block on policy violations. Many Application Activity Monitoring tools are additional products or features from Database Activity Monitoring vendors. Endpoint Activity Monitoring: Watching all user activity on a workstation or server. Includes monitoring of network activity, storage/file system activity, and system interactions like cut and paste, mouse clicks, application launches, etc. Provides deeper monitoring than endpoint DLP/CMF tools that focus only on content that matches policies. Capable of blocking activity- such as launching a P2P application or pasting content from a protected directory into an instant message. Extremely useful for auditing administrator activity on servers. Will eventually integrate with endpoint DLP/CMF. File Activity Monitoring: Monitoring access and use of files in enterprise storage, such as file servers, SAN, and NAS. Gives an enterprise the ability to audit all file access and generate reports (which can sometimes aid compliance reporting). Capable of independently monitoring even administrator access and can alert on policy violations. Portable Device Control: Tools to restrict access to portable storage such as USB drives and DVD burners. Also capable of allowing access but auditing file transfers and sending that information to a central management server. Some tools integrate with encryption to provide dynamic encryption of content passed to portable storage. Will eventually be integrated into endpoint DLP/CMF tools that can make more granular decisions based on the content, rather than blanket policies that apply to all data. Some DLP/CMF tools already include this capability. Endpoint DLP: Endpoint data loss prevention/content monitoring and filtering tools that monitor and restrict usage of data through content analysis and centrally administered policies. While current capabilities vary highly among products, tools should be able to monitor what content is being accessed by an endpoint, any file storage or network transmission of that content, and any transfer of that content between applications (cut/paste). For performance reasons endpoint DLP is currently limited to a subset of enforcement policies (compared to gateway products) and endpoint-only products should be used in conjunction with network protection in most cases. Rights Management: Rights are assigned and implemented in the Create and Store phases, while policies are enforced in the Use phase. Rights are managed by labels, metadata, and tagging- as opposed to more complex logic enforced by logical controls. Label Security: Access to database objects (table, column, row) is enforced based on the user/group and the label. For example, in a healthcare environment employees without manager access can be restricted from seeing the records of famous patients that are labeled as sensitive. Enterprise DRM: Discussed more extensively in Part 1, Enterprise DRM enforces complex use rights based on policies assigned during creation. During the Use phase, EDRM limits the actions a user can perform with a given piece of content (typically a file). For example, the user may be able to add, edit, and delete parts of the document but not cut and paste to another document. A user might be allowed to view the document, but not print it, email it, or store it on a portable device. Logical Controls: Logical controls expand the brute-force restrictions of access controls or EDRM that are based completely on who you are and what you are accessing. Logical controls are implemented in applications and databases and add business logic and context to data usage and protection. While we expect to see logical controls for unstructured content there are currently no technology implementations. Object (Row) Level Security: Creating a rule-set restricting use of a database object based on multiple criteria. For example, limiting a sales executive to only updating account information for accounts assigned to his territory. While you can always do this through queries, triggers, and stored procedures, some database management systems offer it as an enforcement feature applied to the database object, outside of having to manually add it to every query. Today most DBMSs offer this only for rows, but the feature is expected to expand to other database objects. Structural Controls: Taking advantage of database design features to enforce security logic. For example, using the database schema to limit integrity attacks or restricting connection pooling to improve auditability. Application Logic: Enforcing security logic in the application through design, programming, or external enforcement. Today needs to be implemented by the application itself, but over time certain types of logic may be enforced through external services or tools. Application Security: Effective data

Share:
Read Post

Latest TidBITS Article Posted- Leopard Security

I just posted an explanation of Leopard Security (that’s Mac OS X 10.5 for you non-Apple geeks) up on TidBITS. It’s based on my original blog post here, but expanded and simplified to appeal to a more general audience. I realize I took some liberties with the explanations of buffer overflows, ASLR, vulnerabilities, and exploits, but I had to tailor the content for a less-security-geek audience. Check it out, and feel free to flame me here. I do believe that if everything works as advertised this is a very significant release. There are still some big holes (Quicktime anyone?), but Apple seems to be taking security more seriously than in the past few versions. 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.