Permission-greedy apps not always rogue or lazy

Negotiate security, manage risk for better business outcomes
  • Stilgherrian (CSO Online (Australia))
  • — 22 December, 2011 12:30

The principle of least privilege is an information security fundamental. But applications that fail by asking for more than they need aren't necessarily poorly written. Maybe they're just being realistic.

Yesterday I started to create an account at Twistory, a web applications that creates an archive and calendar of your Twitter activity. I needed to give Twistory permission to access my Twitter account via OAuth.

But the authentication dialog told me that Twistory wasn't just requesting permission to read my tweets. It wanted permission to see who I follow, follow new people on my behalf, post tweets and even update my profile.

No way!

Read-only access was needed, Twistory, nothing more. Why are you asking for all this write access?

"We did so because some future Twistory functionality might require those [functions]," wrote Twistory representative Tijs Vrolix in response to last month's question in the application's support forum at Get Satisfaction.

"Don't worry though, we're kind people and won't abuse your confidence," he wrote.

My friend Eric TF Bat calls that "security through sincerity". Trust us, we sound trustworthy. Obviously that's not how security works.

Even if Twistory kept their promise to play nice today, will they still play nice tomorrow? What if  they're compromised? Hackers could issue fake tweets. That would be impossible if Twistory simply didn't have those unneeded write permissions.

Last night Australian time I pressed Vrolix further, and more reasons emerged.

"We choose for full-permissions as it is very hard to get users to re-authorise when we need them to do so (at some point in the future)," Vrolix wrote.

Twistory doesn't have users' email addresses, only their Twitter IDs. Sending tweets or direct (private) messages to all 50,000 users is a no-go, because Twitter would immediately flag them as spammers.

"We had a lot of trouble getting users to 'upgrade' (authorize) from V1 to V2, so while I do agree we shouldn't take security lightly, we're somewhere in between user and 'business' interests here," Vrolix wrote.

In a delightful twist, when I tried to post my comments on Get Satisfaction by authenticating with my Twitter account, they too wanted write access.

"We definitely don't use the 'write' access for anything," wrote Get Satisfaction co-founder Amy Muller.

"There was talk about doing that in the past, but given that we don't currently do so there's no real need for us to ask for that permission. We just haven't updated that login code in a while."

Tags: authentication, Get Satisfaction, hackers, OAuth, security, Twistory, twitter, Vrolix

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
Users posting comments agree to the CSO comments policy.
Login or register to link comments to your user profile, or you may also post a comment without being logged in.
CSO Corporate Partners
  • FirEye
  • Clear Swift
  • Trend Micro
  • Sophos
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

ZENworks® Endpoint Security Management

Get Powerful Protection for All of Your Mobile Devices

Security Awareness Tip
Clearswift tips: Guidelines for introducing and policing an effective IT Policy

1. Make it clear that the policy is not about playing ‘Big Brother’ but to ensure the security of employees, company information and data and to safeguard the company’s reputation.
2. Invest time to get buy-in from managers and their teams.
3. Convey the message of flexibility – with regard to social media, it is not about blocking staff usage but working in everyone’s interests to ensure that threats are contained.
4. Introduce a regular company-wide training programme that everyone attends at regular intervals throughout the year, not merely as part of an induction programme.
5. Within the training programme make sure that there are specific examples to demonstrate each rule or regulation, and that there is a clear explanation of the dangers of casual or careless talk on social networking sites. Again use examples, employees need to understand the consequences of raising a throwaway comment that has negative connotations for the business, as much as they need to be aware of dangers of making a more direct but ill-considered attack on a competitor, regulator or even a fellow colleague. They need to be clearly advised on any impact on the company and/or legal action or inquires that may be raised as a result.
6. Alert employees to any changes in policy through regular clear communication.
7. Reinforce the operational policy guidelines regularly, cover everything from blogging to Facebook, LinkedIn and Twitter.
8. Ensure that the rules are fair and that they apply throughout the business.
9. Enforce the rules – if there is a deliberate or malicious contravening, disciplinary action needs to be taken. A policy isn’t worth having if it is seen to be lax and unenforced.
10. Review the policy regularly to ensure you keep up to date with new systems and technology.

Phil Vasic is Regional Director, APAC, at Clearswift, the software security company www.clearswift.com
Security ABC Guides

7 Ways to Protect Your Business Printers

Can a hacker burn down your business by remotely setting one of your printers on fire? Researchers at Columbia University have recently proposed such a scenario, although HP quickly denied that it's possible. However, even if your printers can't be used as remote firestarters, there are many risks involved in networking a printer.