Skip navigation
  • RSA Conference Twitter
  • RSA Conference Facebook
  • RSA Conference RSS
  • RSA Conference Youtube
  • RSA Conference Flickr
  • RSA Conference LinkedIn
  • RSA Conference iTunes
1 2 3 ... 9 Previous Next

Tim Mather: Experienced Security

126 Posts

Lessons from Egypt

Posted by Tim Mather Feb 1, 2011
0

The astounding and thrilling events in Egypt during the last couple of days, and Tunisia previously, should serve as a reminder to information security professionals about a couple of points.  The glaringly obvious point about Egypt is not to forget about the “A” in CIA – that is, confidentiality, integrity, and availability.  Amazingly, Egyptian government officials apparently (no confirmation from the government itself) ordered that the country be effectively taken off the Internet, as is graphically (literally) shown in a very interesting blog posting by Renesys.  This should be a stark reminder about not dismissing now unfashionable satellite communications (compared to fiber optic cables) entirely.  While satellite communications has its negatives (e.g., latency, relatively high bandwidth costs), it can and does still provide a critical link (literally) in parts of the world where the communications infrastructure suffers from a lack of build out, political uncertainty, or both.

 

Both Tunisia and Egypt are also a reminder of the challenges in trying to prevent data leakage – especially at the network-level alone.  To paraphrase the old saying that 'one man's terrorist is another man's freedom fighter,' one man's data extrusion is another man's social media postings in favor of revolution.  Even the government apparatus of two highly authoritarian states were unable to stop the flow of information about protest activities out of their countries.  And, even Egypt's withdrawal from the Internet has failed to stem the flow of information.  While Facebook and Twitter are unavailable via the Internet within the country, information still flows out by satellite communications (e.g., from Al Jazeera), and from such immediate innovations as speak2tweet.  (For example, see “New Service Allows Egyptian Voices to Be Heard” in today's The New York Times.)  It is also ironic that some of the tools commonly used for circumvention (i.e., evading government censorship) around the world, were actually funded, at least in part, by the United States Government.  SafeWeb, Tor, and Martus have all received U.S. Government funding at some time.

 

So as you watch and listen to these events, keep in the mind the implications that they have for information security practitioners.

ENISA – Again

Posted by Tim Mather Jan 19, 2011
0

In case you missed it, ENISA (European Network Information Security Agency) this week issued another very good report on cloud computing security.  The report, Security and Resilience in Governmental Clouds, obviously focuses on cloud computing used by governments, but the issues discussed are relevant to all users of cloud computing.  The report is 146 pages long, and while I have not finished yet myself, I will tell you that it is worth your time if you are involved (or going to be) with ensuring the security of your organization's cloud computing activities.

 

A lot of good people contributed to the report, and Daniele Catteddu of ENISA edited it and did a great job putting out another excellent ENISA report on cloud computing security.  (ENISA's first report on cloud computing security, Cloud Computing Risk Assessment, from November 2009, is also a must read for those information security practitioners involved with cloud computing – and was also edited by Daniele Catteddu.)  Well done ENISA – again.

“Revolution”

Posted by Tim Mather Jan 11, 2011
0

If you're a geek who lives in the San Francisco Bay Area (or a geek who will be visiting the Bay Area – for example, for next month's RSA Conference), then you owe it to yourself to visit the Computer History Museum on the peninsula in Mountain View.  Specifically, I recommend that you feed your inner geek and see the museum's new “Revolution” exhibit.

 

Revolution: The First 2000 Years of Computing opens to the public on January 13, 2011. This major exhibition, more than six years in the making, will transform the way you think about computers, the software that runs them, and the people who set the ongoing computing revolution in motion.”

 

I had a chance to tour the exhibit as part of a preview access, and it is a great exhibit.  Not only does the exhibit obviously deal with technology involved in computing, but it traces the history of various aspects of computing providing insight into how and why these technologies developed the way they have.  The exhibit takes up most of the museum's first floor, and is densely packed.  I would recommend that you allow yourself at least 90 minutes to two hours to take in all that the exhibit offers.  Make sure that you pick-up a map of the exhibit so that you know where in the exhibit you are, and don't miss anything.  For seasoned geeks, this is a great walk down memory lane, and for younger geeks this is a great way to understand how all of your cool devices of today came into being.

 

Kudos to the Computer History Museum for putting together such a great exhibit!  You really should not miss this.

New Year – New Issues

Posted by Tim Mather Jan 6, 2011
0

Now that the new year is here, and everyone is back to work after the holidays, it is time to recheck your proficiency list.  Unfortunately, that list never seems to get any shorter.  Every year it seems that information security practitioners are expected to, and often required, to be proficient about an ever increasing number of subjects and technologies.  I have a suggestion to add to your list.

 

While cloud computing got much of the media hype last year (along with social networking), an alternative view of both is what O'Reilly and The Economist have termed “Big Data”.  While that term is not precise or technical, it does express a concept that is now upon us: the never ending and exploding accumulation of data that is too large, too raw, or too unstructured for storage or analysis in traditional relational databases (RDBMSs).

 

We're not talking about terabytes of data any longer.  We're now talking routinely about petabytes of data – and in some cases, even larger amounts.  Tools such as Hadoop / MapReduce for the processing of these large amounts of data are becoming common.  RDBMSs are giving way to NoSQL data stores instead.  And analysis with traditional business intelligence (BI) tools comes only after initial analysis with new tools, such as Clojure, Hive, and Thrift.

 

If these are new terms for you, then I suggest that you set aside some of your 'copious' free time early in this new year to begin getting familiar with “Big Data” – and how to secure such.  It is one more subject to be proficient on (or at least somewhat knowledgeable about) in this new year.

Predictions for 2011

Posted by Tim Mather Dec 29, 2010
0

Well, it's that time of year when 'everyone' either does a 'Top 10' list for the year ending, or makes predictions about the coming year.  So, I'll offer two predictions for the coming year.  Neither one of those predictions are 'rocket science' by any means, but both should be on your radar for the implications that both will have on information security and privacy.

 

First, there will be a major clash in the United States (in particular, but also with ramifications for the same debate in Europe) over network neutrality.  Congressional Republicans and mobile network operators versus the Federal Communications Commission (FCC), various rights groups (e.g., the Electronic Frontier Foundation – EFF, the Electronic Privacy Information Center – EPIC), and some technology companies.  This will be a major 'food fight,' which will definitely have an impact on network, and host device, security – as well as other, broader technology implications.

 

Second, there will probably be an even bigger 'food fight' over a likely Obama Administration request to Congress for expanded authority under the Communications Assistance for Law Enforcement Act (CALEA) for monitoring of communications over the Internet.  What the Administration and law enforcement view as only a 'modernization' of CALEA authorities (so-called CALEA II), is viewed by many others as nothing less than 'Clipper II' (i.e., a re-run of the 1990s fight over the National Security Agency's proposal for the Clipper chip).

 

Look for both of these issues to make headlines in the coming year, and both will have implications for information security practitioners – regardless of which side of the debate you are on for either issue.

0

When it comes to federated identity management (FIM) in the (public) cloud, FIM is 'broken'.  It is not the technology that is broken.  SAML (Security Assertion Mark-up Language) and XACML (eXtensible Access Control Mark-up Language) work as intended in the cloud for their specific actions.  It is the business process (i.e., credential acceptance) for FIM that breaks.

 

In fact, FIM never really worked pre-cloud either.  With 'traditional' enterprise IT, what FIM exists is primarily intra-enterprise or intra-domain.  Effectively, this FIM model is a master / slave relationship.  For example, corporate sets the policy for its business units and compels their adherence to the FIM.  Or, a company contractually binds certain of its suppliers to adherence to the company's FIM, usually based on business needs of having 3rd party suppliers service a  company's customers with the user experience based on a company seemingly providing all of its own customer service.  (In today's world of outsourcing, this is now common practice; that is, vendor x to ABC Company poses as ABC Company to ABC Company's customers.)

 

But, the original notion of FIM, built on peer-to-peer trust (identity provider-to-identity provider) has never been realized.  It has been tried however.  Such was the original business model for IdenTrust, which was established in 1999 ('The Year of PKI') to facilitate the inter-enterprise acceptance of PKI certificates.  IdenTrust never gained traction though.  Covisint has also tried to facilitate FIM, with only limited success.

 

The problem has not been technology, but business considerations, and specifically legal issues around accepting an authentication credential issued by another organization.  (OpenID effectively skirts this issue by not being trustworthy enough for business transactions.  OpenID is fine for social networking sites, but insufficiently secure for any 'meaningful' transaction – apologies OpenID.)

 

But even a master / slave relationship for FIM breaks down in the (public) cloud – it simply does not scale.  It doesn't even scale in today's single cloud environments, let alone for coming inter-cloud operations.  What is needed is a FIM that can meet business considerations (i.e., acceptance of authentication credentials issued by other organizations), and so far the current FIM vendors seem to have been happy to ignore this reality.  There is hope however.  For the first time, I just read a very good article proposing a solution to this problem.  If you are an IEEE member (e.g., a reader of Security & Privacy), then read “Toward a Multi-Tenancy Authorization System for Cloud Services” by HP Labs personnel in the latest (November / December) issue of Security & Privacy.  The authors explicitly address FIM in the cloud, and offer an intriguing solution.  Its nice to see an on-point discussion of this issue, rather than the usual vendor 'hand waving'.

0

In the United States, the debate around the WikiLeaks disclosure of classified U.S. Government information has quickly morphed into a much broader fight – and I do mean fight.  What started as as debate over the release of classified information and what those disclosures meant to secrecy versus transparency obscured the rather ridiculous situation of how it was that an Army Specialist (a junior enlisted person) could allegedly get access to so much information – and not just Department of Defense information (obviously Department of State too).  Just what sort of data protection measures had actually been implemented – or not?

 

With the electronic attacks against WikiLeaks, and the retaliatory electronic attacks back against corporate infrastructures of companies that denied services to WikiLeaks (e.g., Amazon Web Services, PayPal, MasterCard, Visa) by groups such as Anonymous, the debate has now shifted to freedom on the Internet versus attribution.  Rather suddenly, the WikiLeaks debate, on a technology perspective, has become a 'warm-up' fight over the reported Obama Administration's intention to submit proposals to Congress next year for revisions to CALEA (Communications Assistance for Law Enforcement Act).

 

The fight comes about because the Administration, so far, has not clearly articulated why changes to CALEA are necessary (from its perspective) – for example, that circuit-switched voice communications are going the way of the dinosaurs.  As more and more traffic is VoIP, the ability of law enforcement to quickly listen in on such communications is diminished.  However, what appears to the Administration to be 'CALEA II' appears to civil libertarians and privacy rights advocates to be nothing less than 'CLIPPER II' (as in the enormously contentious debate over the Clipper chip in the 1990s).  The changes to CALEA that the Administration is reportedly considering will impact not only voice communications, but all communications on the Internet.  Therefore, the original Clipper debate may in fact look tame compared to the coming debate.  And, that coming debate has effectively started with WikiLeaks as a proxy.

0

Earlier this week Microsoft announced a tracking protection privacy feature in its upcoming Internet Explorer 9 (IE9).  That announcement was in response to increased interest in on-line privacy by the Federal Trade Commission and the Commission's testimony to Congress on do not track legislation the week before.  That attention was raised in part by an investigation conducted by The Wall Street Journal earlier this year, and detailed in a series of articles, “The Web's New Gold Mine: Your Secrets”.  While none of this (i.e., the lack of on-line privacy) is new to information security professionals, it is new and/or disturbing to millions of people who are not information security professionals and happen to use the Internet regularly.

 

And, while Microsoft's announcement about IE9 is a step in the right direction for helping to preserve privacy, it is by no means novel.  In fact, IE is simply imitating what NoScript has provided to Firefox users for several years.  And Firefox has long provided far more granular control over the use of cookies, especially 3rd party cookies than IE has.  So, hopefully Microsoft's new tracking protection privacy feature will help to raise the bar in on-line privacy – and hopefully the FTC will keep up its efforts to ensure that such actually happens.  Go FTC!

Stuxnet's Own Hype Cycle

Posted by Tim Mather Nov 30, 2010
0

And, I'm back...  Free now from the vortex of graduate school (having just completed a Master's Degree in Information Assurance).

_______________________________________________________________________________________________

 

In late September I noted that the Stuxnet worm, which was receiving a lot of media attention at that time for targeting Siemens SCADA systems, may actually be an Israeli cyberattack directed against Iran's Bushehr nuclear reactor with the intention of disrupting Iran's nuclear program.  I based that statement in part on the informed speculation of Ralph Langner, who is a well respected expert on industrial systems security, and had just published an analysis of the worm.   Additionally, having been in information security for a number of years and having worked with the intelligence community previously, it did not seem to take a proverbial rocket scientist to believe that scenario to be plausible.

 

In October, I talked with a couple of people with Federal Government information security efforts and privy to classified information.  Without providing any classified information, they downplayed Stuxnet, saying that the worm was not that sophisticated, and saying it was highly doubtful that the worm was targeting Iran's nuclear efforts.

 

In November, came word publicly from no less than Sean McGurk, head of the Department of Homeland Security's Cybersecurity Center, that Stuxnet is a “game changer,” as he testified before the Senate Homeland Security Committee.  Then Iranian President Mahmoud Ahmadinejad said that Iran's uranium-enrichment program has been the target of sabotage –  but he refused to say whether the Stuxnet computer virus had been responsible for the problems.

 

As more information about Stuxnet becomes available, it seems increasingly likely that the worm is indeed not only particularly sophisticated, but is also an actual example of a cyberattack.  As I noted previously, there is a great deal of hype around “cyberwar” in this country.  Stuxnet, however, appears to be the real thing.

 

By the way, if you have not read Symantec's excellent analysis of Stuxnet, then you owe to yourself to do so.  Kudos to Eric Chien and the team at Symantec for this analysis.

Replacement SAS-70

Posted by Tim Mather Oct 11, 2010
0

Over the course of a year, how many times do you get asked by customers, or by your own sales personnel on behalf of customers, for a SAS-70 audit report on your information security operations?  Conversely, over the course of a year, how many times do you ask for a SAS-70 audit report on a vendor providing services to your organization – or you ask a prospective vendor for due diligence reasons?  You probably hear or deal with a “SAS-70” several times a year.

 

If you have been doing information security for awhile, then you are probably only too painfully aware of the limitations of a SAS-70 audit.  Essentially, a SAS-70 is being used today in ways that it was never intended to be used; it has been stretched way beyond its original use.  And, with cloud computing comes the breaking point for SAS-70 audits.

 

Earlier this year, the AICPA (American Institute of Certified Public Accountants) released a new standard that will be replacing the SAS-70.  The new standard, Statement on Standards for Attestation Engagements 16 (SSAE 16), goes into effect for periods dated on or after June 15, 2011.   While these two standards are similar, you should also be aware of the differences between the two.  As an information security practitioner, you should be preparing for the SSAE 16 and getting familiar with it now – before it comes into effect.

0

Several weeks ago, I wrote about U.S. Deputy Secretary of Defense William Lynn's article in the September / October issue of Foreign Affairs, “Defending a New Domain”.  One of the important points that Lynn makes in his article is that “Although the threat to intellectual property is less dramatic than the threat to critical national infrastructure, it may be the most significant cyberthreat that the United States will face over the long term.”

 

With all of the hype about “cyberwar” that has been bandied about since February of this year (kicked-off with an op-ed piece in The Washington Post, “Mike McConnell on how to win the cyber-war we're losing”), I appreciated seeing some rational remarks about such being made by no less than the Deputy Secretary of Defense.  There has been way too much FUD (fear, uncertainly, and doubt) being thrown around about “cyberwar”.

 

On the other hand, the MPAA (Motion Picture Association of America) and the RIAA (Recording Industry Association of America) have certainly done their best to stoke fears of wholesale losses of intellectual property through piracy and counterfeiting of physical goods.  However, the GAO (Government Accountability Office) acknowledged in an April 2010 report that “Efforts to estimate losses involve assumptions such as the rate at which consumers would substitute counterfeit for legitimate products, which can have enormous impacts on the resulting estimates.” [1]  While the losses that MPAA and RIAA members have suffered have not been insignificant, they are almost certainly lower than the FUD bandied about on this issue by those who like people believe such.  (For a slightly different U.S. Government perspective on this issue, see the 2010 Special 301 Report, dated April 30, 2010, from the Office of the United States Trade Representative.)

 

Frankly, both the “cyberwar” mongering and the entertainment providers need to lower their rhetoric and remember that significant amounts of other intellectual property (e.g., patents and trade secrets) are probably at greater risk, and are worth far more to the country's economy than either of these two groups limited interests (government contracts, and increased penalties for individuals involved in illegal copying and/or sharing).  So, it didn't come as a surprise that neither the “cyberwar” mongering or the entertainment providers had any formal comment on the Deputy Secretary of Defense's comments.

 

Let's lower the rhetoric and keep some perspective here please about the threat “ranking” of cyberwar versus intellectual property protection, and remember that intellectual property protection consists of more than piracy and counterfeiting of physical goods.

 

 

[1] “Intellectual Property: Observations on Efforts to Quantify the Economic Effects of Counterfeit and Pirated Goods,” GAO-10-423, page #2.

0

I'm a bit off the mainstream this week.  In fact, not only is this very much an inside the Beltway issue, it is really an inside the Pentagon issue.  However, it's interesting to me since I am a former Army SIGINT officer (35G).  And the issue is: is electronic warfare part of cybersecurity or not?  A bit of confusion reigns on this question, but first let's start with a definition of what electronic warfare is.  According to Joint Publication 3-13.1, Electronic Warfare (dated 25 January 2007), electronic warfare is defined as:


Military action involving the use of electromagnetic and directed energy to control the electromagnetic spectrum or to attack the enemy. Electronic warfare consists of three divisions: electronic attack, electronic protection, and electronic warfare support. Also called EW.

 

OK, but is that part of cybersecurity?  The Army in particular has shown confusion about such.  According to the Journal of Electronic Warfare, “In 2007, the Army authorized the merging of the CAC's Computer Network Operations (CNO) function with the EW function and formed what is now the USACEWP. The joining of the two disciplines grew from the Army's increasing need to understand, operate in and manipulate cyberspace.” [1]  However, after receiving a flood of negative feedback, the Army almost immediately reversed itself and again separated the two.  In June of this year (2010), when the Army announced the formation of Army Forces Cyber Command, it stated that “the Intelligence and Security Command [responsible for electronic warfare in the Army] will be under the operational control of ARFORCYBER for cyber-related actions.” [2]  Anyone with a military background should pick-up immediately on operational control – not operational command.  In other words, Intelligence and Security Command is under the control of, but not actually part of, ARFORCYBER.  Not an unambiguous organizational arrangement by the Army.

 

Additionally, the Army has further confused itself by TRADOC (Training and Doctrine Command) issuing a revised conops (concept of operations) which clearly states that cyber operations (military term for cybersecurity) includes cyberwar – which includes cyber exploitation (CyE) – and CyE includes electronic warfare. [3]

 

The Navy more clearly states that it's new 10th Fleet (its component command to U.S. Cyber Command – the sub-unified command under Strategic Command) includes operational control over “the full spectrum of computer network operations, cyber warfare, electronic warfare [emphasis added], information operations and signal intelligence capabilities and missions across the cyber, electromagnetic and space domains”. [4]

 

However, the U.S. Department of Defense Cyber Command Fact Sheet, issued on May 25, 2010, makes no mention of electronic warfare.  However, in his recent article in Foreign Affairs [5], Deputy Secretary of Defense William Lynn stated that, “Some of the United States' computer defenses are already linked with those of U.S. allies, especially through existing signals intelligence partnerships, but greater levels of cooperation are needed to stay ahead of the

cyberthreat”.  Signals intelligence is a component of electronic warfare.

 

Confused yet by all this inside the Pentagon bantering?  I'll bet that those inside the Pentagon and inside U.S. Cyber Command are too.  And, it is hard to be effective which such confusion.  I  hope that this subtle, but important definitional issue of whether electronic warfare is part of cybersecurity, is sorted out quickly – before something major (negatively) happens.

 

 

[1] March 2009 issue, page #26.

 

[2] “Cyber command to unite network defense efforts,” Army Public Affairs Office, June 2, 2010.

 

[3] TRADOC Pamphlet 525-7-8, “The United States Army’s Cyberspace Operations Concept Capability Plan 2016-2028,” dated 22 February 2010.

 

[4] “Navy Stands Up Fleet Cyber Command, Reestablishes U.S. 10th Fleet,” Navy Public Affairs Office, January 29, 2010.

 

[5] “Defending a New Domain,” in the September / October issue of Foreign Affairs, by U.S. Deputy Secretary of Defense William Lynn.

Cyberwar in the Shadows?

Posted by Tim Mather Sep 21, 2010
0

Earlier this month, at the annual Air & Space Conference, sponsored by the U.S. Air Force Association, conservative commentator Charles Krauthammer predicted that “Israel will probably attack Iran to keep it from developing a nuclear bomb”. [1]  He went on to speculate that, “The most direct route to Iran would be over Iraq, and the U.S; controls Iraqi airspace, meaning that an Israeli attack would require U.S. knowledge and acquiescence. But...the Saudis will consent to the over flight, albeit unofficially, and then pretend they didn’t know it was happening”.

 

The problem with such an air attack scenario is that the entire world would know that it was Israel that conducted such an attack – and it's very likely to be unsuccessful.  But it turns out that Krauthammer could be wrong for another reason.  Because of the two factors above, maybe the Israelis are not planning on conducting an old-fashioned kinetic attack, but are instead already conducting cyberwarfare?

 

Word this week is that the Stuxent worm, which has received a lot of media attention for targeting Siemens SCADA systems, may actually be an Israeli cyberattack directed against Iran's Bushehr nuclear reactor with the intention of disrupting Iran's nuclear program.  That is the informed speculation at least of Ralph Langner, who is a well respected expert on industrial systems security, and has just published an analysis of the worm. [2]

 

“It is hard to ignore the fact that the highest number of infections seems to be in Iran. Can we think of any reasonable target that would match the scenario? Yes, we can. Look at the Iranian nuclear program. Strange – they are presently having some technical difficulties down there in Bushehr. There also seem to be indications that the people in Bushehr don't seem to be overly concerned about cyber security. When I saw this screenshot last year (http://www.upi.com/News_Photos/Features/The-Nuclear-Issue-in-Iran/1581/2/) I thought, these guys seem to be begging to be attacked. If the picture is authentic, which I have no means of verifying, it suggests that approximately one and a half year before scheduled going operational of a nuke plant they're playing around with software that is not properly licensed and configured. I have never seen anything like that even in the smallest cookie plant. The pure fact that the relevant authorities did not seem to make efforts to get this off the web suggests to me that they don't understand (and therefore don't worry about) the deeper message that this tells."

 

As I have previously written about, there is a great deal of hype around “cyberwar” in this country.  Maybe this is an actual example of such?

 

[1] “Israel Likely to Strike Iran,” by Bryant Jordan, DoD Buzz, September 13, 2010.

 

[2] “Stuxnet virus may be aimed at Iran nuclear reactor,” by Robert McMillan, ComputerWorld UK, September 21, 2010.

0

Earlier this summer (July), a report on cybersecurity was released that really didn't get much attention – certainly not as much attention as it deserved.  Maybe that is because we (the information security community) didn't really like what the report had to say – because the report says that we are not doing a very good job of educating ourselves (the information security community) with the skills that we actually need to be successful.

 

Specifically, I am referring to “A Human Capital Crisis in Cybersecurity,” which was released by CSIS (Center for Strategic and International Studies).  CSIS does very good work, and Jim Lewis has an extensive background in information security matters, so we actually should take a hard look at ourselves – as the report points out.

 

For practitioners already in the field, there are two take-aways from the report.  First, “technical proficiency matters”.  For example, as the report states, “That the nation and the world are now critically dependent on the cyber infrastructure is no longer a matter of debate...The problem is both the quantity and quality [of personnel] especially when it comes to highly skilled 'red teaming' of professionals.”  Put another way, “In many ways, cybersecurity is a lot like 19th century medicine – a growing field dealing with real threats with lots of often self-taught practitioners only some of whom know what they are doing.”

 

Second, and related to the first take-away, the report states that,

 

A number of certification programs have evolved, some even ISO 17014 certified.  A few address specific equipment or technologies while others are more general.  While the existence of such programs has spurred investments in training, the consensus of the CSIS Commission was that, all too often, there was little if any connection to the specific technical cybersecurity skills that are needed in the workplace.

 

In the absence of an alternative, several organizations have built robust and highly profitable lines of [certification] business and are understandably anxious to evolve the work that they have done to meet the changing needs.

 

Ouch!  Sounds to me like we have too many latter day equivalents to “paper CNEs” running around – “paper CISXs”.  (Those of you who have been practitioners for long enough certainly remember the criticism that Novell faced earlier over its Certified Novell Engineer (CNE) program.)  The report even makes a recommendation for an independent Board of Information Security Examiners to correct this problem.

 

While some people may dismiss the report as being too negative, and some practitioners might be happy to just ignore the report, good for CSIS for pointing out these deficiencies.  Hopefully, it is a signing of the maturing of our profession that we face such issues and work to better ourselves and the profession itself.  If you have not yet read the report, then you should do so for your own professional development.  And, don't think that the issue raised are limited to the Federal Government, even though that is the focus of the report.

0

I was asked recently by a British publication, what can be done better in the cloud and can it really be safer than hosting on premise?  My response is that one obvious service is anti-malware protection.   There are several reasons for this.   First, let's recognize that the traditional method of providing anti-malware protection has been to do it on the endpoint itself.   However, this approach  has been growing increasingly ineffective.   An August 2010 study from Cyveillance  found that “...even the most popular AV [anti-virus] signature-based solutions detect on average less than 19% of malware threats.  That detection rate increases only to 61.7% after 30 days.” [1]     Those are terrible detection rates and are due largely to two factors.   First, endpoint devices can only run a single anti-malware engine at a time because of the need to control the TCP/IP protocol stack.   Second is the problem of quickly updating anti-malware signatures on the endpoint device itself.   Both of these problems are explicitly addressed by moving  protection from the endpoint  to the cloud.

 

With cloud-based anti-malware, multiple engines can and are run in parallel, to provide far more effective protection.  With multiple engines, an earlier University of Michigan study found that  detection rates could be boosted to 98%. [2]  Additionally, it is far easier and  faster to update anti-malware signatures to a unified group of servers in the cloud, rather than trying to update numerous endpoint devices.   Besides, with anti-malware signatures on cloud servers, the size of that signature set effectively becomes a moot issue.   Such is not the case when signatures must be stored and utilized on  endpoint devices that are mobile phones with limited storage and processing capabilities.   For example, “In 2009, Symantec created 2,895,802 new malicious code signatures...a 71% increase over 2008” [3]   And with a total signature set of approximately six million signatures, that simply is not feasible for today's mobile phones to handle effectively.   A third reason why operating anti-malware in the cloud is better is the fact that there is far greater visibility of threats and infections.   This provides better situational awareness about anti-malware and therefore better protection unto itself.

 

For these reasons, cloud-based anti-malware protection is superior to traditional endpoint-based anti-malware capabilities.   However, can such capabilities be provided more securely than traditional enterprise, premise-based solutions?   Absolutely;  it is far easier to update a group of cloud-based servers and to secure them, than it is to try and effectively secure those same capabilities on numerous endpoint devices.

 

 

[1] “Malware Detection Rates for Leading AV Solutions: A Cyveillance Analysis,” August 2010.

 

[2] “CloudAV: N-Version Antivirus in the Network Cloud,” July 2008.

 

[3] "Symantec Global Internet Security Threat Report: Trends for 2009, Volume XV," published April 2010 [latest available], page #47.


1 2 3 ... 9 Previous Next