Perimeter
5/21/2012
10:08 AM
Amy DeCarlo
Amy DeCarlo
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Overlook The Obvious And Risk Everything

Failure to follow fundamental common-sense security policies can produce disastrous results, as the state of Utah discovered

Ideally, security should be a multilayered process replete with the appropriate checks and balances to close any gaps that could expose information to a potential breach. However, in practice, far too often organizations fail to execute on what are typically thorough and well-designed policies they lay out exactly what controls should be in place to protect precious organizational and client information.

A classic example of this kind of misfire is the recent breach of hundreds of thousands of patient records from the Medicaid server at the Utah Department of Health. A number of very preventable mistakes made it relatively easy for cyberthieves to access approximate 280,000 medical files, complete with Social Security numbers and other personally identifiable information (PII), as well as many as 500,000 additional records.

The Utah data breach made headlines again last week when Utah Governor Gary R. Herbert announced he had accepted the resignation of state chief information officer Stephen Fletcher and ordered an independent audit of the security covering all of the state's IT systems. The resignation was tendered at the governor's request after an investigation of the incident found that under Fletcher's direction, the state's IT department failed to follow a number of procedures and policies that potentially foiled the attack.

For one thing, the compromised server was installed by an outside contractor who may not have had full knowledge of policies -- an exception to normal procedure. The contractor reportedly did not change the default factory passwords on the system. No audit took place that caught that mistake -- or the fact that Health Insurance Portability and Accountability Act (HIPAA)-protected data was stored unencrypted on the server and apparently without adequate firewall protection -- essentially leaving cyberattackers thought to be from Eastern Europe with a wide open door to a wealth of information.

While the attack serves as an unfortunate cautionary tale to other organizations that carelessness can bring about some terrible results, at least anecdotally, it appears that enterprises are taking more care with respect to protecting their most confidential, sensitive, and high-value information. However, the reality is that far too many vulnerabilities are still going unaddressed.

All businesses and government organizations should look at the Utah breach as more than just a water-cooler conversation starter. Instead, use the incident as an opportunity to assess whether there is a gulf between their best-laid security policy and production mentality. And if there is an issue, the organization should prioritize where it needs to make corrections based on the value and sensitivity of the impacted resources.

In Utah's case, beyond the personnel changes and the system audit, the state is also stepping up its data protection plans for regulated and sensitive information. The state will now reportedly encrypt high-risk data both at rest and in motion.

Amy DeCarlo is principal analyst for security and data center services at Current Analysis Amy brings 17 years of IT industry experience to her position as Principal Analyst, Security and Data Center Services. Amy assesses the managed IT services sector, with an emphasis on security and data center solutions delivered through the cloud including on demand ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.