Social engineering key to preach infosec

Powered by SC Magazine
 

Security challenges good for the workplace.

The tenets of good information security practice should take a leaf from social engineering.

Social engineering was commonly used to trick users into opening malicious links or attachments but it could also be used to change conventional thought on security, said John Proctor, director of cyber resilience at IT outsourcing and consulting firm CGI.

"Social engineering is only bad if we let it bad," Proctor said at the SC Congress Canada. "[Humans] are only the greatest weakness if you let them be."

Citing the success of Canadian anti-smoking campaigns that impelled young people not to pick up the habit, Proctor said the same can be done for security.

The goal was to "get inside" the heads of workers and adolescents, and to make security interesting.

He recommended instituting measures ranging from quizzes and tests all the way to challenges with prizes. This could include a competition to be the first employee to walk over to a co-worker's unlocked computer to send an email from their account without them knowing.

The key, Proctor said, is to create value, connect security with social norms, and, most importantly, offer employees feedback of their progress.

He added that it is important to make employees aware of all the personal information about them that may be publicly available on the web.

This article originally appeared at scmagazineus.com

Copyright © SC Magazine, US edition


Social engineering key to preach infosec
 
 
 
Top Stories
Westpac committed to core banking plan
[Blog post] Now with leadership.
 
The True Cost of BYOD - 2014 survey
Twelve months on from our first study, is BYOD a better proposition?
 
Photos: Unboxing the Magnus supercomputer
Pawsey's biggest beast slots into place.
 
 
Sign up to receive iTnews email bulletins
   FOLLOW US...
Latest Comments
Polls
What is delaying adoption of public cloud in your organisation?







   |   View results
Lock-in concerns
  29%
 
Application integration concerns
  3%
 
Security and compliance concerns
  27%
 
Unreliable network infrastructure
  9%
 
Data sovereignty concerns
  22%
 
Lack of stakeholder support
  3%
 
Protecting on-premise IT jobs
  4%
 
Difficulty transitioning CapEx budget into OpEx
  3%
TOTAL VOTES: 1147

Vote