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/13/2016
12:50 PM
Sean Martin
Sean Martin
Slideshows
Connect Directly
LinkedIn
RSS
E-Mail
50%
50%

12 Tips for Securing Cyber Insurance Coverage

As cyber insurance grows more available and popular it is also becoming increasingly complex and confusing. Our slideshow offers guidelines on how to get insurance, get decent coverage, and avoid limitations in coverage.
Previous
1 of 13
Next

Image Source: imsmartin/Mimecast

Image Source: imsmartin/Mimecast

Cyber Liability Insurance, or cyber insurance, can help protect your organization from the financial ramifications of a successful attack on your data systems, which might include the theft of customer data from your servers. There’s still a lot of confusion around what’s required to get coverage, what it takes to get good rates, and what it takes to ensure a claim will be paid. Some might question whether or not a claim will even be paid given some policies may not be up to snuff when it comes to covering some events such as email attacks.

It’s possible that all of this confusion is introducing some risk to both sides of the bargaining table – insurer and insured. The good news is that the focus on risk is good for all, as it is forcing organizations to look at their risk in light of their use of technology and tech-connected partnerships, thereby raising the cybersecurity posture across the board.

Note: imsmartin would like to thank Thomas Conway, Principal, Ernst & Young LLP, William Dixon vice president, Stroz Friedberg, Howard Miller of LBW Insurance’s Tech Secure division, and Mimecast for their research.

 

Sean Martin is an information security veteran of nearly 25 years and a four-term CISSP with articles published globally covering security management, cloud computing, enterprise mobility, governance, risk, and compliance—with a focus on specialized industries such as ... View Full Bio

Previous
1 of 13
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
roxychan
50%
50%
roxychan,
User Rank: Apprentice
4/10/2017 | 10:31:28 AM
192.168.1.1
Thanks for the help.
Shantaram
50%
50%
Shantaram,
User Rank: Ninja
3/16/2017 | 6:49:06 AM
Re: 192.168.0.1
nice tips, thanks
Pascal_Millaire
50%
50%
Pascal_Millaire,
User Rank: Author
3/15/2017 | 9:18:55 AM
Cyber insurance tips
All pertinent points. On the regulatory fines issue, it is also important to note that policy language may state that regulatory fines are payable "where permissible by law" however in some cases your jurisdiction may not allow for the payment, which renders the coverage moot.
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. 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-2019-5613
PUBLISHED: 2020-02-18
In FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13, a missing check in the ipsec packet processor allows reinjection of an old packet to be accepted by the ipsec endpoint. Depending on the higher-level protocol in use over ipsec, this could allow an action to be repeated.
CVE-2020-7450
PUBLISHED: 2020-02-18
In FreeBSD 12.1-STABLE before r357213, 12.1-RELEASE before 12.1-RELEASE-p2, 12.0-RELEASE before 12.0-RELEASE-p13, 11.3-STABLE before r357214, and 11.3-RELEASE before 11.3-RELEASE-p6, URL handling in libfetch with URLs containing username and/or password components is vulnerable to a heap buffer over...
CVE-2019-10792
PUBLISHED: 2020-02-18
bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10793
PUBLISHED: 2020-02-18
dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10794
PUBLISHED: 2020-02-18
All versions of component-flatten are vulnerable to Prototype Pollution. The a function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.