Access member only content, take part in discussions with comments on blogs, news and reviews and receive all the latest security industry news directly to your inbox. Join now for free.
Processing registration... Please wait.
This process can take up to a minute to complete.
A confirmation email has been sent to your email address - SUPPLIED EMAIL HERE. Please click on the link in the email to verify your email address. You need to verify your email before you can start posting.
If you do not receive your confirmation email within the next few minutes, it may be because the email has been captured by a junk mail filter. Please ensure you add the domain @scmagazine.com.au to your white-listed senders.
Getting employees to follow security policy requires having consequences that hurt them personally if they don't comply, said Jason Creasey, senior product manager at the nonprofit research organization Information Security Forum.
"If they don't follow policy, take their bonus away. Make them look stupid in front of their friends," he said.
A lot of people ignore policies because they don't see how they're relevant to them, said Andy Thompson, head of security services at systems integrator Cap Gemini Ernst & Young.
"They have to be relevant," he said. "If you can give them a free drink, meal, let them go home early - something that means something to them."
On the patching front, panelists had various views. Companies need to be selective with patches, Creasey advised. "You need to do a risk analysis on patches... It's quite dangerous to apply all patches automatically," he said.
Richard Hackworth, head of IT security at HSBC Holdings, agreed that a risk assessment is needed before implementing a patch but said a level of automation in patch management is "fundamental."
With some 250,000 devices connected to the network, 100,000 employees and many mobile workers and contractors at BT, the patching process "has to be a slick process," said Martin Roberts, group security director at the company.
Panelists said risk analysis is a key component to an infosec program.
"If an organization can't identify risk associated with a critical business application, it must be difficult to define the appropriate level of control," Creasey said.
Thompson said anything done in security should be based on a risk analysis that correlates security to the business goals: "It's important for us as security professionals to understand how the business works."
Hackworth said, "Essentially we're managing commercial risk...Security controls will be proportional to the commercial risk."
To begin commenting right away, you can log in below or register an account if you don't yet have one. Please read our guidelines on commenting. Offending posts will be removed and your access may be suspended. Abusive or obscene language will not be tolerated. The comments below do not necessarily reflect the views or opinions of SC Magazine, Haymarket Media or its employees.