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.

Operations

6/7/2016
11:30 AM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail

How To Prepare For A Data Breach

These five from-the-trenches strategies will help you win the fight against today's sophisticated, conniving attackers.
2 of 6

Have an Incident Response (IR) plan in place and test it regularly

'I can't stress this enough,' says Grillo. 'Organizations must have an incident response plan, exercise it against two to three likely attack vectors, and see how well the company reacts.' 

- All organizations, regardless of size, should have an IR plan where you clearly define how to respond when a potential breach is identified, or when an actual attack occurs -- including who needs to be involved from a notification and decision-making perspective.
- Be prepared to respond at your very best in a real breach scenario by conducting simulation exercises for different types of breaches that could affect your organization, possibly including these scenarios: 

- Advanced Threats
- Cybercrime
- Fraud
- Malicious Insider
- Careless Insider


- Extend your plan and simulation exercises beyond the IT staff. Ensure that every member of the IR team knows exactly what their roles are and has a good understanding of the time commitment involved when an incident does occur. The IR team should include key stakeholders from all applicable areas of the organization, such as: 

- Legal
- HR
- Executive Management
- PR / Communications
- Information Technology


- Have a plan that includes your third-party vendors, so you can manage their risk from the beginning of the relationship. For example, your vendors should have a service level agreement (SLA) in their contract that governs their responses to security incidents. Get a clear view into those requirements, and determine where liability rests if a third-party vendor exposes your data.



More Reading | Lack of Third-Party Risk Reporting: http://www.dfs.ny.gov/about/press/pr1504091.htm

Image Source: imsmartin

Have an Incident Response (IR) plan in place and test it regularly

I cant stress this enough, says Grillo. Organizations must have an incident response plan, exercise it against two to three likely attack vectors, and see how well the company reacts.

  • All organizations, regardless of size, should have an IR plan where you clearly define how to respond when a potential breach is identified, or when an actual attack occurs -- including who needs to be involved from a notification and decision-making perspective.
  • Be prepared to respond at your very best in a real breach scenario by conducting simulation exercises for different types of breaches that could affect your organization, possibly including these scenarios:
    • Advanced Threats
    • Cybercrime
    • Fraud
    • Malicious Insider
    • Careless Insider
  • Extend your plan and simulation exercises beyond the IT staff. Ensure that every member of the IR team knows exactly what their roles are and has a good understanding of the time commitment involved when an incident does occur. The IR team should include key stakeholders from all applicable areas of the organization, such as:
    • Legal
    • HR
    • Executive Management
    • PR / Communications
    • Information Technology
  • Have a plan that includes your third-party vendors, so you can manage their risk from the beginning of the relationship. For example, your vendors should have a service level agreement (SLA) in their contract that governs their responses to security incidents. Get a clear view into those requirements, and determine where liability rests if a third-party vendor exposes your data.

More Reading | Lack of Third-Party Risk Reporting: http://www.dfs.ny.gov/about/press/pr1504091.htm

Image Source: imsmartin

2 of 6
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
US Sets $5 Million Bounty For Russian Hacker Behind Zeus Banking Thefts
Jai Vijayan, Contributing Writer,  12/5/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19719
PUBLISHED: 2019-12-11
Tableau Server 10.3 through 2019.4 on Windows and Linux allows XSS via the embeddedAuthRedirect page.
CVE-2019-19720
PUBLISHED: 2019-12-11
Yabasic 2.86.1 has a heap-based buffer overflow in the yylex() function in flex.c via a crafted BASIC source file.
CVE-2019-19707
PUBLISHED: 2019-12-11
On Moxa EDS-G508E, EDS-G512E, and EDS-G516E devices (with firmware through 6.0), denial of service can occur via PROFINET DCE-RPC endpoint discovery packets.
CVE-2019-19708
PUBLISHED: 2019-12-11
The VisualEditor extension through 1.34 for MediaWiki allows XSS via pasted content containing an element with a data-ve-clipboard-key attribute.
CVE-2019-19709
PUBLISHED: 2019-12-11
MediaWiki through 1.33.1 allows attackers to bypass the Title_blacklist protection mechanism by starting with an arbitrary title, establishing a non-resolvable redirect for the associated page, and using redirect=1 in the action API when editing that page.