Is your software vendor doing everything it can to secure its products? As Sun Microsystems learned this week, there is always room for improvement.
Sun changed the way it releases security updates to its destkop Java SE (Standard Edition) platform this week following pressure from customers and security experts like Marc Maiffret, chief technology officer with eEye Digital Security.
Maiffret had blasted Sun a few months ago for releasing Java fixes to developers ahead of regular users -- a practice that he said could give the bad guys a golden opportunity to reverse-engineer the developer code and uncover new ways of attacking Sun's 800 million Java SE users.
With Sun now pledging to release all of its Java SE updates at the same time, we asked Maiffret what suggestions he'd offer the software industry on improving security. Following are his top five tips:
1) Make it easy for the hackers to tell you what they know. According to Maiffret this is the number one way to improve your relationship with the security community and it's easily done: "Have the secure@ and security@ e-mail addresses listed under your contacts page or some sort of security landing page," he said.
2) Do what Sun did. Make sure that you fix the bugs in all of your products at the same time so you don't accidentally hand over security details in code that could be reverse engineered and then used to attack customers who haven't yet been given the fix.
3) Make sure there is a very straightforward way that the customer is notified of security fixes -- either via e-mail or through the product itself.
4) Separate security updates from feature updates. This is especially important for consumer products. "A lot of times you'll have a vendor trying to tell you, 'You want this new photobook album functionality?' and you'll say, 'no' without realizing that it actually contains critical security updates," Maiffret said.
5) List your upcoming security fixes as soon as you've identified a new issue. Yes it may make for some bad PR at first, but by notifying users as soon as a vulnerability has been verified, you document your ability to patch the problem "When you have that public timeline, it actually allows customers to see if someone's taking too long so they can put pressure to have it fixed more quickly," he said.