Tuesday, June 28, 2016

Are You Updating Your Breach Response Plan Often Enough?

 
 
 
 
 
While “set it and forget it” may be a great philosophy for a convection oven or programmable thermostat, it should never be your approach to a data breach response plan. Yet a stunning number of companies are acting as if their plans are on autopilot.

In our Second Annual Study on Data Breach Preparedness, the Ponemon Institute found that 37 percent of surveyed organizations said they had not reviewed or updated their data breach response plan since creating it. Another 41 percent said they have no set time for reviewing or updating their plan. Fourteen percent review it once a year and just 3 percent review quarterly.

On a positive note, the study showed that more companies than ever are creating plans, and awareness is high regarding the importance of being prepared to deal with a data breach. The number of companies with a data breach response plan increased 12 percent between 2013 and 2014, with 73 percent of this year’s respondents reporting they have a plan in place. More companies also now have a data breach response team – 72 percent in 2014.

That’s very good news considering that data breaches are occurring more frequently. The number of companies reporting a data breach increased 10 percent, with 43 percent reporting breaches, and 60 percent saying their company had experienced more than one breach in the past two years.

With more breaches occurring and cyber-attacks in constant flux, cyber criminals seem to develop new tactics on an almost-daily basis. To be effective, a data breach response plan must be as flexible and dynamic as the situations it’s supposed to address. Reviewing, updating and practicing your data breach response plan should happen regularly – far more often than quarterly – and certainly not never!

Improving data breach response requires continual review of your response plan, fire drills to test how well it works, adequate budget to administer and maintain the plan, and more oversight from senior executives. One more piece of good news – it seems companies are aware of what needs to be done to improve their data breach response. In our survey, 77 percent said conducting more fire drills and practicing breach response was the single-most important step they could take toward owning a more effective data breach response.

The full survey report is available for free download here.

Legal Notice: The information you obtain herein is not, nor intended to be, legal advice. We try to provide quality information but make no claims, promises or guarantees about the accuracy, completeness or adequacy of the information contained. As legal advice must be tailored to the specific circumstances of each case and laws are constantly changing, nothing provided herein should be used as a substitute for the advice of competent legal counsel.

The post Are You Updating Your Breach Response Plan Often Enough? appeared first on Data Breach Resolution.



from Data Breach Resolution http://ift.tt/291nUZt

US Businesses Quite Likely to Pay a Cyber-Ransom

IBM Check out the new support experience beta

There are multiple vulnerabilities in IBM® Runtime Environment Java™ Version 6.0.16.21 and earlier that is shipped with Tivoli Storage Productivity Center for download and use with its Java WebStart GUI. These issues were disclosed as part of the IBM Java SDK updates in April 2016.

CVE(s): CVE-2016-0363

Affected product(s) and affected version(s):

IBM® Runtime Environment Java™ Technology Edition, Version 6.0.16.21 and earlier that is provided for download and use with the Java WebStart GUI from the following versions:

  • Tivoli Storage Productivity Center 5.2.0 through 5.2.7.1
  • Tivoli Storage Productivity Center 5.1.0 through 5.1.1.10
  • Tivoli Storage Productivity Center 4.2.0 through 4.2.2.195

The versions listed above apply to all licensed offerings of Tivoli Storage Productivity Center, including IBM SmartCloud Virtual Storage Center Storage Analytics Engine.

System Storage Productivity Center is affected if it has one of the versions listed above installed.

Note:
The Tivoli Storage Productivity Center server component is not directly affected. However, the affected versions listed above provide an interface to download the affected IBM® Runtime Environment Java™ Technology Edition. It you did not download and install this IBM® Runtime Environment Java™ Technology Edition on any systems, such as is required for the Tivoli Storage Productivity Center GUI that launches using Java WebStart, you are not affected and do not need to apply a fix.

Starting with IBM Spectrum Control 5.2.8, the IBM Runtime Environment Java Technology Edition is not included and IBM Spectrum Control is not affected.

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/292VL1b
X-Force Database: http://ift.tt/1Tg5v67



from IBM Product Security Incident Response Team http://ift.tt/292GWvU

IBM Vulnerabilities in BIND affect AIX (CVE-2016-1285 and CVE-2016-1286)

There are vulnerabilities in BIND that impact AIX.

CVE(s): CVE-2016-1285, CVE-2016-1286

Affected product(s) and affected version(s):
AIX 5.3, 6.1, 7.1, 7.2 VIOS 2.2.x The following fileset levels are vulnerable: key_fileset aix Fileset Lower Level Upper Level KEY ——————————————————— bos.net.tcp.client 5.3.12.0 5.3.12.10 key_w_fs bos.net.tcp.server 5.3.12.0 5.3.12.6 key_w_fs bos.net.tcp.client 6.1.9.0 6.1.9.102 key_w_fs bos.net.tcp.server 6.1.9.0 6.1.9.101 key_w_fs bos.net.tcp.client 7.1.3.0 7.1.3.47 key_w_fs bos.net.tcp.server 7.1.3.0 7.1.3.47 key_w_fs bos.net.tcp.client 7.1.4.0 7.1.4.1 key_w_fs bos.net.tcp.server 7.1.4.0 7.1.4.1 key_w_fs bos.net.tcp.bind 7.2.0.0 7.2.0.0 key_w_fs bos.net.tcp.bind_utils 7.2.0.0 7.2.0.1 key_w_fs Note: to find out whether the affected filesets are installed on your systems, refer to the lslpp command found in AIX user’s guide. Example: lslpp -L | grep -i bos.net.tcp.client

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/28YBTvv
X-Force Database: http://ift.tt/1WhPh1c
X-Force Database: http://ift.tt/1TnICjP



from IBM Product Security Incident Response Team http://ift.tt/29778s3

IBM Check out the new support experience beta

A vulnerability in Open Source BeanShell has been addressed by LCMS Premier

CVE(s): CVE-2016-2510

Affected product(s) and affected version(s):

All versions prior to 10.1.0

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/292VlI6
X-Force Database: http://ift.tt/1W1VwYd



from IBM Product Security Incident Response Team http://ift.tt/292H3aW

IBM Check out the new support experience beta

Installation programs for the Microsoft Windows components of IBM Tealeaf Customer Experience are vulnerable to attack under certain conditions.

CVE(s): CVE-2016-2542

Affected product(s) and affected version(s):

IBM Tealeaf Customer Experience: v8.0-v9.0.2

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/2977kYp
X-Force Database: http://ift.tt/1rhWtyP



from IBM Product Security Incident Response Team http://ift.tt/2977hM9

IBM Vulnerabilities in NTP affect AIX CVE-2015-7973 CVE-2015-7977 CVE-2015-7979 CVE-2015-8158 CVE-2015-8139 CVE-2015-8140

There are multiple vulnerabilities in NTP that impact AIX.

CVE(s): CVE-2015-7973, CVE-2015-7977, CVE-2015-7979, CVE-2015-8139, CVE-2015-8140, CVE-2015-8158

Affected product(s) and affected version(s):
AIX 5.3, 6.1, 7.1, 7.2 VIOS 2.2.x The following fileset levels are vulnerable: key_fileset aix For NTPv3: Fileset Lower Level Upper Level KEY —————————————————– bos.net.tcp.client 5.3.12.0 5.3.12.10 key_w_fs bos.net.tcp.client 6.1.9.0 6.1.9.102 key_w_fs bos.net.tcp.client 7.1.3.0 7.1.3.47 key_w_fs bos.net.tcp.client 7.1.4.0 7.1.4.1 key_w_fs bos.net.tcp.ntp 7.2.0.0 7.2.0.2 key_w_fs bos.net.tcp.ntpd 7.2.0.0 7.2.0.2 key_w_fs For NTPv4: Fileset Lower Level Upper Level KEY —————————————————– ntp.rte 6.1.6.0 6.1.6.5 key_w_fs ntp.rte 7.1.0.0 7.1.0.5 key_w_fs Note: to find out whether the affected filesets are installed on your systems, refer to the lslpp command found in AIX user’s guide. Example: lslpp -L | grep -i ntp.rte

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/1Q1mBt3
X-Force Database: http://ift.tt/1Q1mu0F
X-Force Database: http://ift.tt/1Q1mFcj
X-Force Database: http://ift.tt/1Q1ol5w
X-Force Database: http://ift.tt/1Q1nEcF
X-Force Database: http://ift.tt/1Q1n3rm
X-Force Database: http://ift.tt/1Q1n3HJ



from IBM Product Security Incident Response Team http://ift.tt/2977rTT