Securosis

Research

The Internet is for Pr0n

Apparently the folks at Twitter forgot the first rule of the Internet. As Avenue Q so elegantly stated, The Internet is for Porn. NetworkWorld points out a minor unintended consequence of Twitter’s new Vine video sharing application, Sex and NSFW clips flood new Vine app from Twitter. Will Apple respond? The Vine app, much like Twitter, lets users explore and discover content via hashtags. However, it didn’t take long at all for hashtags for words like #sex and #porn to take center stage. Indeed, any NSFW term one can think of likely already has a listing via Vine. While the Vine app has functionality that enables users to flag videos as inappropriate, this only serves to provide a warning to users before a video begins playing. So you’re telling me no one in a product management meeting at Twitter suggested that some enterprising user would upload pictures of their, uh, equipment? I find that hard to believe. Chatroulette, anyone? Of course, Apple is pretty sensitive to their apps being used to serve up NSFW content. I’d assume they’ll put up the 17+ gate when downloading the app, but besides that I don’t think there is much they can do. They could kick it out of the App Store, but that seems a bit heavy handed. And it’s not like kids can’t get around the protections and view the app on the web if they want to. When there’s a will there’s a way. And for 14-year-old boys there is a will. Not that I’d know anything about that. Share:

Share:
Read Post

Gartner on Software Defined Security

Neil MacDonald on Software Defined Security: Here’s what I propose: “Software defined” is about the capabilities enabled as we decouple and abstract infrastructure elements that were previously tightly coupled in our data centers: servers, storage, networking, security and so on. I believe to truly be “software-defined”, these foundational characteristics must be in place Abstraction – the decoupling of a resource from the consumer of the resource (also commonly referred to as virtualization when talking about compute resources). This is a powerful foundation as the virtualization of these resources should enable us to define ‘models’ of infrastructure elements that can be managed without requiring management of every element individually. Instrumentation – opening up of the decoupled infrastructure elements with programmatic interfaces (typically XML-based RESTful APIs). Automation – using these APIs, wiring up the exposed elements using scripts and other automation tools to remove “human middleware” from the equation. This is an area where traditional information security tools are woefully inadequate. Orchestration – beyond script-based automation, automating the provisioning of data center infrastructure through linkages to policy-driven orchestration systems where the provisioning of compute, networking, storage, security and so on is driven by business policies such as SLAs, compliance, cost and availability. This is where infrastructure meets the business. I will surely quibble on the details when I publish my own research on the topic, but Neil’s take is excellent. The key piece we need ASAP is security product APIs. You don’t want to know the ugliness which security abstraction and automation startups need to go through for even the most mundane tasks. Share:

Share:
Read Post

The Graduate: 2013 Style

When in doubt, throw money at the problem. From the Washington Post, Pentagon to boost cybersecurity force: The Pentagon has approved a major expansion of its cybersecurity force over the next several years, increasing its size more than fivefold to bolster the nation’s ability to defend critical computer systems and conduct offensive computer operations against foreign adversaries, according to U.S. officials. Of course US adversaries have allegedly tasked 100,000 folks to cybersecurity activities, but this clearly indicates the reality of nation-state behavior in 2013. Evidently a couple different kinds of kung fu will be valued by the military-industrial complex. And when they inevitably remake The Graduate, plastics won’t be the can’t-miss occupation. And Mrs. Robinson will be going after the pen tester – tattoos, earrings, and all. Share:

Share:
Read Post

Threatpost on Active Defense

Mike Mimoso has a very good article on active defense at Threatpost. (Yes, we are linking to them a lot today). While every corporate general counsel, CIO and anyone with a CISSP will tell you that hacking back against adversaries is illegal and generally a bad thing to do, there are alternatives that companies can use to gain insight into who is behind attacks, collect forensic evidence and generally confound hackers, perhaps to the point where they veer away from your network. The one thing the article doesn’t spend enough time on is how useful these approaches can be for triggering alerts in your security monitoring. Especially if you correlate two or more events, which are highly unlikely to be a false positive. I wrote about this last June with some definitions. Finally, the CrowdStrike guys need to get their messaging lined up. Mixed messages aren’t great when you are in pretend-stealth mode. Share:

Share:
Read Post

The Inside Story of SQL Slammer

A first person account at Threatpost by David Litchfield, who discovered the vulnerability which was later exploited. Looking at my phone, I excused myself from the table and took the call; it was my brother. “David, it’s happened! Someone’s released a worm.” “Worm? Worm for what?” “Your SQL bug” My stomach dropped. Telling Mark I’d call him back later I rejoined the table. Someone, I can’t remember who, asked if everything was alright. “Not really,” I replied, “I think there’s going to be trouble.” Microsoft was going down the security path before this, but it clearly helped reinforce their direction and paid massive dividends on SQL Server itself. The first major flaw to be found in SQL Server 2005 came over 3 years after its release – a heap overflow found by Brett Moore, triggered by opening a corrupted backup file with the RESTORE TSQL command. So far SQL Server 2008 has had zero issues. Not bad at all for a company long considered the whipping boy of the security world. Oracle would prefer you not read that paragraph. Share:

Share:
Read Post

Java Moving from Ridiculous to Surreal

Adam Gowdiak in [SE-2012-01] An issue with new Java SE 7 security features: That said, recently made security “improvements” to Java SE 7 software don’t prevent silent exploits at all. Users that require Java content in the web browser need to rely on a Click to Play technology implemented by several web browser vendors in order to mitigate the risk of a silent Java Plugin exploit. This was via Ed Bott who has also been covering the deceptive installs included with nearly all Java updates: When you use Java’s automatic updater to install crucial security updates for Windows , third-party software is always included. The two additional packages delivered to users are the Ask Toolbar and McAfee Security Scanner. With every Java update, you must specifically opt out of the additional software installations. If you are busy or distracted or naive enough to trust Java’s “recommendation,” you end up with unwanted software on your PC. I have checked, and (so far) I cannot correlate kitten deaths with Java installs, so we’ve got that going for us. Which is nice. Share:

Share:
Read Post

Marketers take the path of least resistance

Rich constantly reminds us that “correlation does not imply causation,” relevant when looking at a recent NetworkWorld article talking about the decrease in spam, which concludes that botnet takedowns and improved filtering have favorably impacted the amount of spam being sent out. Arguably, the disruption of botnets – the platform used to send most spam – has probably had a larger effect, with the downing of several large distribution networks coinciding with the start of spam’s decline in 2010. Meh. Of course, that makes better headlines than all the various botnet chasing efforts paying off. But if you dig into Kaspersky’s research you get a different take. Ads in legal advertising venues are not as irritating for users on the receiving end, they aren’t blocked by spam filters, and emails are sent to target audiences who have acknowledged a potential interest in the goods or services being promoted. Furthermore, when advertisers are after at least one user click, legal advertising can be considerably less costly than advertising through spam. Based on the results from several third-party studies, we have calculated that at an average price of $150 per 1 million spam emails sent, the final CPC (cost per click, the cost of one user using the link in the message) is a minimum of $.4.45[sic]. Yet the same indicator for Facebook is just $0.10. That means that, according to our estimates, legal advertising is more effective than spam. Our conclusion has been indirectly confirmed by the fact that the classic spam categories (such as fake luxury goods, for example) are now switching over to social networks. We have even found some IP addresses for online stores advertising on Facebook that were previously using spam. Duh. Spam was great for marketers of ill repute because it was cheaper than any other way of reaching customers. If that changes marketers will move to the cheapest avenue. They always do – that’s just good business. So we can all pat ourselves on the back because our efforts to reduce spam have been effective, or we can thank places like Facebook that are changing the economics of mass online marketing. For now anyway. Share:

Share:
Read Post

Mobile Commerce Numbers Don’t Lie

We all want security to be front and center in terms of decisions on new applications. We all follow the researchers who show time and again how mobile apps, or web apps, or pretty much anything, can and will be gamed. Yet all that doesn’t matter, as security cannot get in the way of business. Branden Williams did a great job digging into the economics of Starbucks’ stored value cards to make a pretty compelling case that this stuff will happen, whether security likes it or not. Now, let’s say that I install the app on my phone, and set it to recharge $50 every time my balance gets low. I have now reduced their transaction volume with me to 10% of the original (26 times to recharge vs 260 transactions). This changes the fees to $23.27, or a 60% reduction in my cost burden to the company with the added benefit that they get to use my cash for anything they want while I work it off over a period of time. You should read the post because it hits on a number of the economic drivers that make stored value cards a huge win for small-ticket shops like Starbucks. Of course providing access to micropayments from a mobile app introduces risk. But given the numbers Branden outlines, that won’t stop Starbucks from doing everything they can to get everyone using their stored value cards & accounts. The numbers don’t lie – this stuff is going to happen. And these environments will be attacked because they represent a path of least resistance to get financial data. Which underscores the importance of working with the business people and app development team as early as possible to get ahead of the risks of these mobile-driven business processes. Photo credit: “Starbucks Mobile Card iPhone App” originally uploaded by Joe McCarthy Share:

Share:
Read Post

In through the Barracuda Back Door

Given the angst, conspiracy theories, and tinfoil hats around any network/security products built in China, it’s curious to see Krebs’ story on the backdoors in Barracuda products found by Stefan Viehboeck of SEC Consult Vulnerability Lab. Viehboeck found that the username “product” could be used to login and gain access to the device’s MySQL database (root@localhost) with no password, which he said would allow an attacker to add new users with administrative privileges to the appliances. SEC Consult found a password file containing a number of other accounts and hashed passwords, some of which were uncomplicated and could be cracked with little effort. But having that back door creates exposures that most security conscious folks find unacceptable. As Viehboeck says: “In secure environments it is highly undesirable to use appliances with backdoors built into them. Even if only the manufacturer can access them.” Clearly you can draw the conclusion that this is bad, especially because Barracuda is playing the ostrich game a bit, calling these issues just ‘medium’ severity. But given that Barracuda caters to the small and mid-market, how many of these boxes are actually installed in secure environments? And how many of these unsophisticated customers will apply the fixes to eliminate the back doors? Right, not too many. We can’t let Barracuda off the hook here just because the back doors are there to facilitate support access in the event the box needs to be remotely fixed. Users lose their credentials and lock themselves out of their boxes all the time. They misconfigure stuff and a support rep would need deep (probably root) access to fix things. We get that. But we aren’t in the excuses business, and neither are Barracuda’s customers. Barracuda just can’t rely on a locked-down IP address range to provide security. That’s too easy to spoof and those addresses may change over time. Obscurity isn’t the answer. Moreover, customers need to have the option to shut down the back doors, especially if they install in one of these mythical secure environments. There must be a middle ground between installing an undocumented back door and not being able to support the device remotely. Maybe they ship the box without the default accounts and lock down the root account. Maybe they have a script that adds the support accounts to the box when a special “Activate Remote Support” setting is selected within the interface. They could use some kind of two-factor authentication to ensure Barracuda support is involved when activating the script. Then when the box is repaired, the user unchecks the box and another script cleans out the user accounts and locks down the box. Is that a perfect answer? Of course not – I’m just throwing crap against the wall. There must be a better way to ensure thousands of customers don’t have to ship their boxes back to Barracuda for simple fixes that can be done remotely by support. But having an undocumented back door isn’t it. Photo credit: “Vancouver, BC, Canada – Robson Street – Hippies Please Use Back Door (Antique Sign)” originally uploaded by Adam Jones Share:

Share:
Read Post

The Mid-market Security Squeeze

Most folks appreciate the challenges of securing a mid-sized company. They have important data and enough employees that someone is going to screw something up. They often don’t have the budget or infrastructure maturity to take security seriously. Many get by due more to obscurity (who is going to attack them?) than any active controls. And as automated tools make it easier to find chinks in any and every company’s armor, the seriousness of the problem is going to become much higher-profile. No less than Dan Geer has weighed in on the topic in a CSO contribution. He looks at it from the perspective of what the mid-sized company can do and what they can’t. By introducing the concept of a third party, which he calls a mentor, Dan is talking about helping an organization kickstart their security program and prioritize. Later, the mentor can move on to their next stop, when the organization is ready to do stand on its own. Information protection means a program, not a tool, not a silver bullet, not a small number of enlightened facts. It means learning what it is that you don’t know that you don’t know (without the expensive embarrassment of the serious errors our opponents will surely deliver). An information protection program is, at its best, something that a mentor jump starts for you and, over time, brings you to the point where whether you take it over entirely for yourself, or keep it as a partnership with your mentor, is a choice that you make for reasons that no longer include whether you know what you are doing. Everyone understands that, say, driving tractor trailers or doing surgery is not something you would teach yourself. Basically Dan is calling for the mentor to take a snapshot of an organization and use their experience, methods, and analysis to help the organization prioritize what they should fix first. This first-things-first approach demands a mentor with the tools to take a high definition photograph of your information in motion movement – the source, target, frequency, volume, etc., mentioned above. If experience is a guide, then you will have some surprises. Again, this is nothing to be ashamed of, but better you get those surprises quickly and from a trusted mentor rather than reading about your data breach in a newspaper. Note that the kind of mentor we suggest is not a penetration tester, not an auditor, not a per-diem consultant, and not a reformed criminal peddling a product. Dan is one of the big thinkers in the business, and he doesn’t talk much. But when he does, pay attention. As with any out of the box thinking, you can come up with a million reasons why something like this won’t work. But we should focus on how to make something like this happen; as technology advances (yes, Big Data) this kind of concept becomes more achievable. The reality is that far too many organization don’t know what they don’t know. And until they do things aren’t going to get better. Photo credit: “MSH0110-12 Squeeze Me” originally uploaded by f1uffster (Jeanie) 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.