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.

Attacks/Breaches

9/13/2019
01:30 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail

6 Questions to Ask Once Youve Learned of a Breach

With GDPR enacted and the California Consumer Privacy Act on the near horizon, companies have to sharpen up their responses. Start by asking these six questions.
3 of 7

2. How do we roll out our incident response plan?
Charles Carmakal, the strategic services CTO for FireEye Mandiant, says after the security team has initially triaged and confirmed malicious activity, it's time for the company to put its incident response plan into motion. Typically, there's a gradual process of escalating the communication of potential security incidents up to the CISO and then the company's general counsel.  The general counsel and CISO may notify other members of the executive leadership team as appropriate, depending on the scope and impact of the incident. Carmakal says these cases vary, but quite often the general counsel may only notify the CEO after the company has confirmed an intrusion took place.
Jon Oltsik, a senior principal analyst and fellow at the Enterprise Strategy Group, points out that companies should develop the ability to report breaches to authorities within 72 hours. The 72-hour response is stipulated by the EU's GDPR and the upcoming California Consumer Privacy Act, but Oltsik says it's a necessary goal even for companies not impacted by those laws. 
'This is how the world is moving,' he says. 'Plus, companies want to be ready with their story before the phones start ringing from the press.' 

Image Source: Adobe Stock: leowolfert

2. How do we roll out our incident response plan?

Charles Carmakal, the strategic services CTO for FireEye Mandiant, says after the security team has initially triaged and confirmed malicious activity, its time for the company to put its incident response plan into motion. Typically, there's a gradual process of escalating the communication of potential security incidents up to the CISO and then the company's general counsel. The general counsel and CISO may notify other members of the executive leadership team as appropriate, depending on the scope and impact of the incident. Carmakal says these cases vary, but quite often the general counsel may only notify the CEO after the company has confirmed an intrusion took place.

Jon Oltsik, a senior principal analyst and fellow at the Enterprise Strategy Group, points out that companies should develop the ability to report breaches to authorities within 72 hours. The 72-hour response is stipulated by the EU's GDPR and the upcoming California Consumer Privacy Act, but Oltsik says it's a necessary goal even for companies not impacted by those laws.

"This is how the world is moving, he says. "Plus, companies want to be ready with their story before the phones start ringing from the press."

Image Source: Adobe Stock: leowolfert

3 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
0%
100%
REISEN1955,
User Rank: Ninja
9/16/2019 | 3:22:27 PM
Nouns
Words are important and ages ago Cliff Stoll wrote an engaging book THE CUCKOO'S NEST which should be required reading for any cyber pro.  In this book, at one point, he was asked by the FBI to define the threat and theft.  Their language was proper and mild and I think this is so here...

Threat Actor?  No - how about Bald Faced Criminal

Ongoing?  No, how about barn door still unlocked?

Data theft?  No, how above did they empty Fort Knox.

Ongoing?  No, are the black trucks still at the docking back.

Restoration protocol?  No, are we still screwed in putting shit back-together?

Don't have a plan?  are we then up Schitt's creek with no paddle or boat? 

I noticed that responsibility for defense was not mentioned?
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11494
PUBLISHED: 2020-04-02
An issue was discovered in slc_bump in drivers/net/can/slcan.c in the Linux kernel through 5.6.2. It allows attackers to read uninitialized can_frame data, potentially containing sensitive information from kernel stack memory, if the configuration lacks CONFIG_INIT_STACK_ALL, aka CID-b9258a2cece4.
CVE-2020-7619
PUBLISHED: 2020-04-02
get-git-data through 1.3.1 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the arguments provided to get-git-data.
CVE-2020-7620
PUBLISHED: 2020-04-02
pomelo-monitor through 0.3.7 is vulnerable to Command Injection.It allows injection of arbitrary commands as part of 'pomelo-monitor' params.
CVE-2020-7621
PUBLISHED: 2020-04-02
strong-nginx-controller through 1.0.2 is vulnerable to Command Injection. It allows execution of arbitrary command as part of the '_nginxCmd()' function.
CVE-2020-7623
PUBLISHED: 2020-04-02
jscover through 1.0.0 is vulnerable to Command Injection. It allows execution of arbitrary command via the source argument.