How to define a security incident
Do we need to do a better job of understanding exactly what a security incident actually is? Davey Winder takes a look...
Asking 'what is a security incident?' may seem like something of a silly question, however when Lancope recently conducted a survey of IT and security professionals the results pointed towards the answer being far from straightforward.
Indeed, with some 65 per cent of those asked apparently being in security incident denial, there is an argument to suggest that there is a systemic problem in understanding security within the enterprise.
I started by asking Kurt Hagerman, FireHost's director of information security, the question and he admitted that it's a lot harder to answer than it seems. "It's a funny thing really. Everyone thinks that they know what a security incident is, but in truth there are a number of different definitions and they don't all sit well together," he says.
You cannot have a partial incident; you are either pregnant or not pregnant!
Although the most basic of definitions would appear to classify an incident as 'an intrusion or attempted intrusion' Hagerman argues that the enterprise needs to define the term within the context of their operations.
Lisa Myers, virus hunter at Intego, agrees that organisations will define the term depending on the importance of security to their specific industry. "Organisations that are under more frequent attack will likely define it differently than those that are attacked more seldom," Myers points out. She adds: "Those with more sensitive or potentially life-threatening data will define it differently from those with limited data." This is true, but perhaps not very helpful in getting us closer to that elusive definition.
Most of the security industry professionals that I spoke to agreed on one important thing: the need for any definition to be 'high level.'
"[By] being too specific you run the risk of missing certain incidents," warns Alan Carter, head of consulting at SecureData. "For example, defining SQL attacks as a security incident could result in a new type of attack not being defined in future."
So can we come up with a high-level, broad church, definition? Andrew Wild, CSO at Qualys believes he can. "At a very high level, an information security incident should be considered an event that impacts the confidentiality, integrity, or availability of an information resource or asset," he says.
The organisation's information security management team, in coordination with its executive management and the incident response team, should then determine responsibilities for managing specific types of likely events, according to Wild.
In This Article
The IT Pro guide to Windows 10 migration
Everything you need to know for a successful transitionDownload now
Managing security risk and compliance in a challenging landscape
How key technology partners grow with your organisationDownload now
Software-defined storage for dummies
Control storage costs, eliminate storage bottlenecks and solve storage management challengesDownload now
6 best practices for escaping ransomware
A complete guide to tackling ransomware attacksDownload now