Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

For Security Pros, Maintaining Credibility Means Walking A Fine Line

In security, crying wolf too often -- or too infrequently -- can both lead to big trouble

In the old fable, the Boy Who Cried Wolf was capricious and stupid. He cried "wolf" the first two times because he wanted to see who would come. The third time, when the wolf actually appeared, he cried out and no one came. He became wolf chow.

But what if the Boy Who Cried Wolf had actually seen a wolf the first two times? Would help still have come the third time? What would have happened, in that wolf-infested forest, if he had cried five, six, seven times?

This is a question that IT security professionals face every day. And there isn't always a clear answer.

For security pros, fear is often an ally. The fear of a new threat is what gets end users to pay attention. It's what pushes your project up the priority list, gains you time on your boss' calendar, and gets you extra budget. Fear of breaches often is why security tasks get done.

But for most security pros, fear is also a well that shouldn't be visited too often. Just like the Boy Who Cried Wolf, a security professional's livelihood rests on his/her credibility. Throw out too many warnings, and your bosses may eventually turn a deaf ear to them. Fail to provide enough warnings about a serious threat, and your organization may not have the tools and processes to stop it.

A security warning is only as good as the credibility of the professional who delivers it.

These days, it's difficult not to raise the alarm frequently. Nearly every day, a major vulnerability is exposed, a new exploit found, a new anomaly spotted in the logs. These threats are not capricious or made up -- they are real wolves. They threaten your systems and your data. Fail to report them -- fail to get the help you need -- and you are wolf chow. Ring the bells too often -- lose the trust of your top management -- and you are wolf chow.

In today's special Dark Reading digital supplement on data breaches, we look at the full impact of a data breach – not just the cost of finding a breach and fixing it, but the cost of service interruption to customers, to employees, and to the business itself. Depending on your business, a security breach might be a small blip in your operations -- or it can affect your entire business for years.

Maybe this sort of "impact assessment" is what the Boy Who Cried Wolf needed. Is just one sheep in danger? Or is it the whole herd? Is it 50 starving wolves, or just one fat wolf looking for a snack? The right reports might have built his credibility over time, so that when he cried wolf, the organization might have been prepared with the right response.

It isn't wrong to cry wolf when there is one. But when you're surrounded by wolves every day, you need to provide some perspective on you warnings. By measuring the risk and potential impact, as described in today's digital issue, you can build your credibility. And that credibility, in turn, might decrease your likelihood of becoming wolf chow -- one way or the other. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5783
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the login functionality does not contain any CSRF protection mechanisms.
CVE-2020-11031
PUBLISHED: 2020-09-23
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library c...
CVE-2020-5781
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the langSelection parameter is stored in the luci configuration file (/etc/config/luci) by the authenticator.htmlauth function. When modified with arbitrary javascript, this causes a denial-of-service condition for all other users.
CVE-2020-5782
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, if a user logs in and sets the ‘wan_type’ parameter, the wan interface for the device will become unreachable, which results in a denial of service condition for devices dependent on this connection.
CVE-2020-24213
PUBLISHED: 2020-09-23
An integer overflow was discovered in YGOPro ygocore v13.51. Attackers can use it to leak the game server thread's memory.