Attacks/Breaches
5/2/2013
11:22 AM
Connect Directly
RSS
E-Mail
50%
50%

Twitter To News Outlets: More Takeovers Ahead

Twitter memo warns of ongoing account takeover attempts, urges media businesses to prepare. Should Twitter be doing more?

Twitter this week warned news and media outlets to expect ongoing attempts to take over their Twitter accounts and offered detailed guidance for how businesses could improve their security posture.

"There have been several recent incidents of high-profile news and media Twitter handles being compromised. We believe that these attacks will continue, and that news and media organizations will continue to be high value targets to hackers," read a memo distributed this week by Twitter and reprinted by Buzzfeed.

Twitter's security outreach campaign comes in the wake of the Syrian Electronic Army this week compromising more than a dozen Twitter accounts maintained by the Guardian to decry its "lies and slander about Syria." That followed the hacktivist group last week compromising multiple Associated Press accounts and issuing a hoax tweet claiming that explosions at the White House had injured President Obama. The tweet led to a brief downturn in the stock market. The group's previous Twitter account compromises have affected Al-Jazeera English, BBC, CBS, France24, National Public Radio, Reuters and Sky News.

How does Twitter recommend that businesses at high risk of having their Twitter accounts compromised -- by a hacktivist group that's strongly aligned to Syrian President Bashar al-Assad, or anyone else with a grudge -- protect themselves?

For starters, it recommended employee training, pointing out that recent account takeovers appear to be spear-phishing attacks that target corporate email. Thus it recommends that businesses promote individual awareness of these attacks within the organization. In other words, train your employees to recognize fake emails.

[ Two-factor authentication is a step in the right direction, but it's just a start. Read Twitter Two-Factor Authentication: Too Little, Too Late? ]

Twitter also recommends that businesses set a randomly generated password that's at least 20 characters in length, to never distribute passwords via email, use password managers, regularly change passwords and also ensure that all "authorized applications" that are allowed to access a Twitter account are recognized. It also recommends tying the Twitter account email to an email system that uses two-factor authentication -- be it Gmail, Hotmail or a corporate email system -- to make it harder for attackers to use password resets to gain control of accounts.

Finally, Twitter also suggested that high-risk businesses consider setting aside one computer for tweeting and little else. "Don't use this computer to read email or surf the Web, to reduce the chances of malware infection," Twitter recommended. "This helps keep your Twitter password from being spread around."

Twitter's guidance to businesses aside, is there more that the company could do to protect its users? Notably, Twitter is reportedly beta-testing two-factor authentication for its site. But two-factor authentication won't protect Twitter users from having their credentials intercepted via malware or phishing attacks. That's why many security experts have been calling on Twitter to put more robust defenses in place for blocking account takeovers -- for example, by taking a page from Facebook and allowing users to register machines as "trusted," or requiring additional login credentials when someone tries to access an account from a new geographic region for the first time.

Twitter may also need to begin encrypting the session tokens it issues. "Not all account hijacks are based on phishing and spear-phishing. Sometimes tweets are sent out because an unencrypted session is hijacked and while this may not be the case in this instance, it's sometimes convenient for service providers to assume that security breaches are the fault of the user," said David Harley, senior research fellow at security firm ESET, in a blog post.

"There are limits to what Twitter [or the user] can do about this issue," Harley added. "However, the risk can be reduced by browsing from VPN connections and/or accessing sites via SSL, but that's not always convenient. What might also help is not having a Twitter account running permanently in the background, but that may not be convenient for many Twitter users either."

People are your most vulnerable endpoint. Make sure your security strategy addresses that fact. Also in the new, all-digital How Hackers Fool Your Employees issue of Dark Reading: Effective security doesn't mean stopping all attackers. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
PJS880
50%
50%
PJS880,
User Rank: Ninja
5/27/2013 | 8:38:34 PM
re: Twitter To News Outlets: More Takeovers Ahead
If you are not taking
the security of your system seriously this day in age then you are not reading
the news and all the current breeches that are occurring. Most of the current
attacks are due to uninformed employees who answer these phishing emails. I agree
that with proper training an employee could spot a potentially dangerous email.
TwitterG«÷s recommendation of using a single node in the office is not at all
realistic.at the very least look at emails more cautiously because they are now
aware of the threats that exist. This also touches on the extent that Twitter is
liable for. If a user is careless with their credentials and lacks the knowledge
to protect their own systems, then I do not believe that is TwitterG«÷s responsibility.

Paul Sprague

InformationWeek Contributor
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3341
Published: 2014-08-19
The SNMP module in Cisco NX-OS 7.0(3)N1(1) and earlier on Nexus 5000 and 6000 devices provides different error messages for invalid requests depending on whether the VLAN ID exists, which allows remote attackers to enumerate VLANs via a series of requests, aka Bug ID CSCup85616.

CVE-2014-3464
Published: 2014-08-19
The EJB invocation handler implementation in Red Hat JBossWS, as used in JBoss Enterprise Application Platform (EAP) 6.2.0 and 6.3.0, does not properly enforce the method level restrictions for outbound messages, which allows remote authenticated users to access otherwise restricted JAX-WS handlers ...

CVE-2014-3472
Published: 2014-08-19
The isCallerInRole function in SimpleSecurityManager in JBoss Application Server (AS) 7, as used in Red Hat JBoss Enterprise Application Platform (JBEAP) 6.3.0, does not properly check caller roles, which allows remote authenticated users to bypass access restrictions via unspecified vectors.

CVE-2014-3490
Published: 2014-08-19
RESTEasy 2.3.1 before 2.3.8.SP2 and 3.x before 3.0.9, as used in Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0, does not disable external entities when the resteasy.document.expand.entity.references parameter is set to false, which allows remote attackers to read arbitrary files and have...

CVE-2014-3504
Published: 2014-08-19
The (1) serf_ssl_cert_issuer, (2) serf_ssl_cert_subject, and (3) serf_ssl_cert_certificate functions in Serf 0.2.0 through 1.3.x before 1.3.7 does not properly handle a NUL byte in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Dark Reading continuing coverage of the Black Hat 2014 conference brings interviews and commentary to Dark Reading listeners.