Only a third of British businesses have a financial plan in place in case of a cyber attack, according to a survey at Lloyds Bank. Meanwhile, only half of companies discuss the risk of cyber attacks at board level.
The survey found that, if attacked, over a third of firms would pay a ransom to get their data back, but only a quarter had dedicated cyber insurance. IT security experts commented below.
Bill Evans, Senior Director at One Identity:
This is a real miss. Security must be a board level discussion. One need only look across any variety of news reporting agencies to understand why. Reasons to make this a board level discussion include GPDR violations with their hefty fines, damage to brand in the court of public opinion, and loss of revenue as customer confidence wanes in the wake of a breach.
As we talk with customers, one of the reasons they oftentimes give for not making security a board level discussion is that it doesn’t drive revenue or margin. It’s viewed as a “cost of doing business” and not worthy of being discussed in the rarified air of “mahogany row.” As a response, we like to remind them that there are two types of businesses; those that have been breached and those that are about to be. Then we follow on with, “if you think security is expensive, try being unsecure.”
Javvad Malik, Security Advocate at AlienVault:
The second aspect is the response that should be taken once an incident occurs. Again, the response steps should be planned in advance and based on the criticality of assets and data. For example, if an asset that contained personal information is compromised, the response plan would include notifying the relevant regulatory body. But if a test environment was attacked, the response could be as simple as re-imaging the servers.
By having a plan in advance based on business and information criticality, the cost of security controls can be managed, as well as response plans.”
Dr Anton Grashion, Managing Director, Security Practice at Cylance:
The opinions expressed in this post belongs to the individual contributors and do not necessarily reflect the views of Information Security Buzz.