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.

Comments
CISOs' Cyber War: How Did We Get Here?
Newest First  |  Oldest First  |  Threaded View
Dimitri Chichlo
50%
50%
Dimitri Chichlo,
User Rank: Apprentice
1/14/2018 | 4:23:33 AM
Re: Software == Bugs
Thnak you for your article, Jack. Indeed, software==bugs but, yes, we know means of programming that avoids most of code mistakes. Plus by stretching the time to market, you are putting your business at risk (ex.: Diginotar).

What puzzles me in this industry, is that we take for granted something which is completely unacceptable in other industries. Take automotive for instance. Do you imagine that every month the car dealer calls you to fix something in your newly acquired car (ABS, airbag, brakes, etc.)? By the way, this can very much be the case in the future, as cars are no more than driving appliances but so far, we have seen limited cases, but they do exist. 

However, do you have to be a CISO to understand the need for security? I do not completely agree with that. I think that this is rather a question of common sense. One of the challenges we face as infosec professionals is to pass the message higher. Do we really succedd in that? I doubt. It is just that security is still not embedded in IT (yet) and not considered as a (potential) competitive advantage. 

Not sure also about the concept of cyber war. I would leave that term to a state level concern, not at business level, although some businesses are strategic for countries, but this is another story. I would rather use "IT security" (not really sexy though :). 

 

 
jackmillerciso@gmail.com
50%
50%
[email protected],
User Rank: Author
1/9/2018 | 11:39:06 PM
Re: Software == Bugs
Thank you for your comment. I do agree with you, these points you clearly articulate are valid and must be taken into consideration for developing any meaningful and workable policies or regulations.

While some discovered vulnerabilities might have been virtually impossible to find with even the best QA program, unfortunately, there have been many that should have easily been identified and remediated but were not and that problem must be resolved. 

Likewise, with concern to innovation, I don't think it is an either/or conversation.  Even in the most regulated industries there is always innovation, the most important thing is that we have a level playing field. 
Brook S.E.S308
50%
50%
Brook S.E.S308,
User Rank: Apprentice
1/9/2018 | 1:53:30 PM
Software == Bugs
The Turing Proof has not yet fallen. Short summary: an automated process cannot prove that an automated process is correct.

IOW, software can be proven to have errors, but not proven to be absolutely correct. That means that we will be living with software errors for sometime - imagining that viulnerability is entirely a business problem missed a key technical fact of life. 

Plus, not all vulnerabilities are equal. Many are not really of value to real-world adversaries. Risk assessment will continue to be important.

As I have noted both in my books and elsewhere, error is also an artifact of innovation. When attempting something new, it's not going to be "right" for a while; mistakes will be made. 

Finally, designs for yesteryear will likely not survive tomorrow's research.

Meltdown/Spectre is precisely this situation. Speculative execution has provided enormous CPU gains. We now know that those gains came with a security cost, because dedicated researchers probed and prodded to find holes in the design. future designs are thus improved. 

This last point is key: it's very hard to anticipate every possible use case and mis-use case for a design. While analytic tools like Threat Modeling can anticipate known techniques, it's very hard to see far into research and attack future.

While your points are certainly valid, the argument, I believe is incomplete without my additions

cheers

/brook s.e. schoenfield


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27491
PUBLISHED: 2021-07-30
Ypsomed mylife Cloud, mylife Mobile Application:Ypsomed mylife Cloud,All versions prior to 1.7.2,Ypsomed mylife App,All versions prior to 1.7.5,The Ypsomed mylife Cloud discloses password hashes during the registration process.
CVE-2021-27495
PUBLISHED: 2021-07-30
Ypsomed mylife Cloud, mylife Mobile Application:Ypsomed mylife Cloud,All versions prior to 1.7.2,Ypsomed mylife App,All versions prior to 1.7.5,he Ypsomed mylife Cloud reflects the user password during the login process after redirecting the user from a HTTPS endpoint to a HTTP endpoint.
CVE-2021-32807
PUBLISHED: 2021-07-30
The module `AccessControl` defines security policies for Python code used in restricted code within Zope applications. Restricted code is any code that resides in Zope's object database, such as the contents of `Script (Python)` objects. The policies defined in `AccessControl` severely restrict acce...
CVE-2021-22521
PUBLISHED: 2021-07-30
A privileged escalation vulnerability has been identified in Micro Focus ZENworks Configuration Management, affecting version 2020 Update 1 and all prior versions. The vulnerability could be exploited to gain unauthorized system privileges.
CVE-2021-34629
PUBLISHED: 2021-07-30
The SendGrid WordPress plugin is vulnerable to authorization bypass via the get_ajax_statistics function found in the ~/lib/class-sendgrid-statistics.php file which allows authenticated users to export statistic for a WordPress multi-site main site, in versions up to and including 1.11.8.