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
SEC: Companies Must Disclose More Info on Cybersecurity Attacks & Risks
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
2/25/2018 | 9:42:05 PM
Re: Trading stocks
@Dr.T: To be fair, and to say nothing of self-dealing (which is a different, albeit related, matter entirely), there are some economists that have touted the theory that insider trading is good for markets and should be legalized as such -- because the immediate effect it has on market value allows information to reach investors more quickly. There is some good debate on this issue.

Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
2/25/2018 | 9:40:26 PM
Re: And this needs to be a RULE?????
This is part of the problem of being a company on the public stock exchange. Short-term-gain investors have motives and goals that are completely contrary to long-term organizational goals. And yet trying to please short-term investors is usually a failing strategy.
247locksmith
247locksmith,
User Rank: Apprentice
2/25/2018 | 1:16:45 PM
What the heck??
Why does this need to be a rule?? It should be obvious that they need to disclose risks such as this! Cybersecurity is something that has to be taken seriously. I think that's just as serious as hiring an emergency locksmith service when you need it.
Dr.T
Dr.T,
User Rank: Ninja
2/25/2018 | 11:33:26 AM
Trading stocks
“execs can't trade stocks if they have unannounced information on a security breach ” This is good I think. It should involve not only security breaches but all other things that can give advantages to execs.
Dr.T
Dr.T,
User Rank: Ninja
2/25/2018 | 11:31:55 AM
Re: And this needs to be a RULE?????
“Equifax” C-suite may be overlooking things, lower layer roles still have major roles to play, it the could not secure the network they should resign to avoid responsibility.
Dr.T
Dr.T,
User Rank: Ninja
2/25/2018 | 11:29:43 AM
Re: And this needs to be a RULE?????
“the C-Suite has zero understanding of what a threat can do” I would say they actually know what is happening, they may just hold it to themsleve to use it as a leverage.
Dr.T
Dr.T,
User Rank: Ninja
2/25/2018 | 11:27:53 AM
Re: And this needs to be a RULE?????
“Businesses should be open and forthcoming about events “ I would agree with this too. There are other laws and regulations that forces them to to the ethical thing.
Dr.T
Dr.T,
User Rank: Ninja
2/25/2018 | 11:26:21 AM
Re: And this needs to be a RULE?????
“COMMON SENSE really. ” I would agree with this, it needs to be based on common sense.
REISEN1955
REISEN1955,
User Rank: Ninja
2/23/2018 | 8:40:21 AM
And this needs to be a RULE?????
COMMON SENSE really.  Businesses should be open and forthcoming about events like this but because it is BAD news (depress shareholder value) and because the C-Suite has zero understanding of what a threat can do (save depress shareholder value) ... IT is encouraged to hide, sweep issues under the rug, deny and let the C-Suite blame it (as Equifax did) one ONE, JUST ONE, IT worker who has ( of course ) been discharged (thereby saving shareholder value).  THEN in a few months the truth comes out and all hell breaks loose, depressing (dramatically) shareholder value even more than had they been honest about it in the first place.


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 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.