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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15505
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1, and Sentry before 9.7.3 and 9.8.x before 9.8.1, allow remote attackers to execute arbitrary code via unspecified vectors.
CVE-2020-15506
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to bypass authentication mechanisms via unspecified vectors.
CVE-2020-15507
PUBLISHED: 2020-07-07
MobileIron Core and Connector before 10.3.0.4, 10.4.x before 10.4.0.4, 10.5.x before 10.5.1.1, 10.5.2.x before 10.5.2.1, and 10.6.x before 10.6.0.1 allow remote attackers to read files on the system via unspecified vectors.
CVE-2020-15096
PUBLISHED: 2020-07-07
In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in the renderer can reach into the isolated Electron context and perform privileged actions. Apps using "contextIsolation" are affecte...
CVE-2020-4075
PUBLISHED: 2020-07-07
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened via window.open. As a workaround, ensure you are calling `event.preventDefault()` on all new-window events where the `url` or `options` is not ...