Jump to content



Last week, groups of congressional staffers gathered in conference rooms in the nation's capital. They were coming to hear from a representative from Symantec about the current threat landscape in cyberspace.

It's an annual event for the security software giant, one in which staffers are briefed on current and emerging threats. They, in turn, brief lawmakers who are looking for ways to "catch up" in the war in cyberspace.

As you might expect in a briefing on cybersecurity, lots of numbers were thrown out: an 81% increase in the number of malware attacks, 5.5 billion attacks blocked worldwide and some 403 million unique pieces of malware (many of them have variations of the same attack that are auto-generated) aimed at computer users around the world.

A lot of these threats are familiar to Symantec, and a big reason why they have become a powerhouse in the security industry. Protecting against old viruses and detecting new are how they make their money. Business is apparently good, with some 200,000 new pieces of malware being sent to them every week for further diagnosis.

That's one of the reasons the company staffs its security desk 24/7. It was that lucky weekend staffer who got first wind of a new threat this past Memorial Day. It was a new piece of malware sent to the company by a Hungarian researcher, a trusted partner, so it got moved a little closer to the top of the heap for scrutiny and what the researcher saw shocked him a little.

"The first thing was its size," said Kevin Haley, Symantec's director of security response, who was alerted over the holiday weekend that this virus was different

Share this post

Link to post
Share on other sites

1 answer to this question

  • 0


[quote][url="http://newstechnica.com/"]David Gerard[/url] writes:[quote]It seems the authors of Stuxnet/Duqu/Flame used the [url="http://www.oberhumer.com/opensource/lzo/"]LZO library[/url], which is straight-up GPL. And so, someone has asked the U.S. government to [url="http://blog.crysys.hu/2012/06/stuxnet-duqu-flame-open-source-license-questions-v0/"]release the code under the GPL[/url]. (Other code uses various permissive licenses. As works of the U.S. federal government, the rest is of course public domain.) Perhaps the author could enlist the SFLC to send a copyright notice to the U.S. government...[/quote][/quote]Source: [url="http://yro.slashdot.org/story/12/06/06/1256217/"]Slashdot[/url]


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.