Threat Intelligence

6/22/2017
03:15 PM
50%
50%

Most General Counsels Fret over Data Security

An overwhelming percentage of in-house attorneys say cyberattacks and the impact on their business keeps them up at night, a recent survey shows.

Fears over hacking, phishing, malware, and ransomware cause great concern among a vast majority of general counsels, according to a survey released today by ALM Intelligence and Morrison & Foerster.

The survey of more than 200 in-house top attorneys at US companies reveals that 87% toss and turn at night over these particular cyber threats. Some 62% are concerned that employee mistakes will lead to data security and privacy loss, while 50% fear potential security breaches by non-law firm vendors.

The survey also found that a majority of attorneys worry about cybersecurity threats (57%); the potential cost or impact to the firm's budget by these attacks (55%); and the potential for a government or regulatory investigation to be launched as a result of a breach (55%).

Hacking, phishing, malware, and ransomware are a bigger deal to attorneys than labor and employment litigation (59%) and than intellectual property infringement (60%), according to the survey.

Read more about the survey here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/25/2017 | 1:44:36 PM
Understandable
It's not hard to see why in-house counsel is so concerned with cybersecurity, considering (1) the increasing awareness that CISOs should not report to CIOs (because of the inherent conflict of interest) that has led some organizations to trend to having CISOs work closely with and/or report to General Cousel, and (2) developments like this one -- leading to greater InfoSec-related compliance costs: darkreading.com/partner-perspectives/f5/talking-cyber-risk-with-executives/a/d-id/1329161?
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.