Jim Hietala, GSEC, GCFW and CISSP, is the principal of Compliance Research Group, providing research, analysis, and consulting services in the areas of compliance, risk management, and IT security. Jim has provided consulting services to organizations such as SANS, The Open Group Security Forum, Logical Security, and a number of IT security and compliance vendors. He is a frequent speaker at industry conferences, and he recently authored a comprehensive course on IT risk management. He participates in the SANS Analyst/Expert program, having written several whitepapers and participated in several webcasts for SANS. He has also published numerous articles on information security, risk management, and compliance topics in publications including The ISSA Journal, Bank Accounting & Finance, Risk Factor, and others. He holds a B.S. in Marketing from Southern Illinois University. Editorial focus: Compliance, Risk Management, IT Security, IT-GRC software, HIPAA, GLBA, Privacy
Jim can be reached at: jim@compliancefocus.com
|
said this on 17 Sep 2008 12:37:52 PM EST
While bad software design and QA certainly contribute and enable breaches, I'm not sure that the ability to sue software manufacturers would do much to address either the quality of software or the losses incurred from breaches.
Verizon Business RISK Team “2008 Data Breach Investigations Report” reports these numbers:
Attacks -
from outside the organization: 73%
implicating business partners: 39%
from internal sources: 18%
Median number of records compromised -
from external attacks: 30000
from partner attacks: 187500
from internal threats: 375000
Internal attacks by IT admin: 50%
My takeaway from these numbers is that while software flaws and incorrect configuration may enable attacks, the most direct damage is a result of mismanaged trust, in partners and people inside the company - half of which are IT admins.
Perhaps the lesson that companies should learn is that their relationship with employees and partners directly effects their security posture and managing those trust relationships should be a priority.
Or just figure out how to get software manufacturers to share the pain.
|