Attacks/Breaches
8/31/2011
11:07 AM
50%
50%

14 Enterprise Security Tips From Anonymous Hacker

Former Anonymous member "SparkyBlaze" advises companies on how to avoid massive data breaches.

Want to avoid large-scale data breaches of the type served up by hacking group Anonymous, and its LulzSec and AntiSec offshoots? Start by paying attention to the security basics, including hiring good people and training employees to be security-savvy.

"Information security is a mess. ... Companies don't want to spend the time/money on computer security because they don't think it matters," said ex-Anonymous hacker "SparkyBlaze," in an exclusive interview with Cisco's Jason Lackey, published on Cisco's website Tuesday.

Accordingly, what's the best way for businesses to improve the effectiveness of their information security efforts? SparkyBlaze offered 14 tips, ranging from using "defense-in-depth" and "a strict information security policy"; regularly contracting with an outside firm to audit corporate security; and hiring system administrators "who understand security." Also encrypt data--"something like AE-256," he said--and "keep an eye on what information you are letting out into the public domain."

Other best practices: use an intrusion prevention system or intrustion detection system to detect unusual network activity. Employ "good physical security" too, he said, to ensure no one routes around your information security measures by simply walking through the front door. Finally, pay attention to employees' security habits and keep them briefed on the threat of social engineering attacks, since all it takes is one person opening a malicious attachment to trigger a data breach of RSA-scale proportions.

While SparkyBlaze's back-to-basics guidance isn't new, it bears repeating given the number of data breaches and releases executed by hacktivist groups in recent months. According to security experts, these attacks aren't necessarily highly sophisticated, and most don't make use of so-called advanced persistent threats. Rather, attackers often exploit common vulnerabilities or misconfigurations in Web applications, just as they've done for years.

SparkyBlaze defected from Anonymous earlier this month, saying via a Pastebin post that he was "fed up with Anon putting people's data online and then claiming to be the big heroes." As that suggests, there's no clear and easy definition of what constitutes "hacktivism." Even so, the "scope creep" in the type of data collected and released by Anonymous and its offshoots is evidently turning some people away from the collective.

"I love hacking and I believe in free speech and anti-censorship, so putting both together was easy for me. I feel that it is ok if you are attacking the governments. Getting files and giving them to WikiLeaks, that sort of thing, that does hurt governments," said SparkyBlaze to Cisco's Lackey.

But in his Pastebin post, SparkyBlaze said that AntiSec and LulzSec had increasingly been operating against the supposed mission statement of Anonymous, which was ostensibly formed to keep governments accountable. "AntiSec has released gig after gig of innocent people's information. For what? What did they do? Does Anon have the right to remove the anonymity of innocent people? They are always talking about people's right to remain anonymous so why are they removing that right?"

On a related note, the raison d'etre of Anonymous--WikiLeaks--appears to have lately suffered its own data breach, or at least loss of data control. On Monday, German weekly news magazine Der Spiegel reported that a file posted by WikiLeaks supporters to the Internet included concealed, password-protected, and unexpurgated versions of the 251,000 U.S. State Department cables that WikiLeaks released--with many sources omitted--in November 2010.

Through a somewhat circuitous sequence of events, possibly involving personnel disagreements inside WikiLeaks, the existence of a 1.73-GB "cables.csv" file, which contains the uncensored cables and which is protected by a password, became publicly known. Furthermore, thanks to an "external contact" of WikiLeaks, according to Der Spiegel, the password was also publicly disclosed, enabling the file to be unlocked.

But in a statement on Twitter, WikiLeaks disputed responsibility for the leak: "There has been no 'leak at WikiLeaks'. The issue relates to a mainstream media partner and a malicious individual." WikiLeaks, however, didn't name either.

The vendors, contractors, and other outside parties with which you do business can create a serious security risk. Here's how to keep this threat in check. Also in the new, all-digital issue of Dark Reading: Why focusing solely on your own company's security ignores the bigger picture. Download it now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-7830
Published: 2014-11-24
Cross-site scripting (XSS) vulnerability in mod/feedback/mapcourse.php in the Feedback module in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 allows remote authenticated users to inject arbitrary web script or HTML by leveraging the mod/feedback:mapcourse cap...

CVE-2014-7831
Published: 2014-11-24
lib/classes/grades_external.php in Moodle 2.7.x before 2.7.3 does not consider the moodle/grade:viewhidden capability before displaying hidden grades, which allows remote authenticated users to obtain sensitive information by leveraging the student role to access the get_grades web service.

CVE-2014-7832
Published: 2014-11-24
mod/lti/launch.php in the LTI module in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 performs access control at the course level rather than at the activity level, which allows remote authenticated users to bypass the mod/lti:view capability requirement by vi...

CVE-2014-7833
Published: 2014-11-24
mod/data/edit.php in Moodle through 2.4.11, 2.5.x before 2.5.9, 2.6.x before 2.6.6, and 2.7.x before 2.7.3 sets a certain group ID to zero upon a database-entry change, which allows remote authenticated users to obtain sensitive information by accessing the database after an edit by a teacher.

CVE-2014-7834
Published: 2014-11-24
mod/forum/externallib.php in Moodle 2.6.x before 2.6.6 and 2.7.x before 2.7.3 does not verify group permissions, which allows remote authenticated users to access a forum via the forum_get_discussions web service.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?