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.

Risk

10/29/2013
04:20 PM
James Bindseil
James Bindseil
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Think Hackers Are IT's Biggest Threat? Guess Again

More than one third of all data security breaches at government agencies are caused accidentally by internal employees.

Making matters more difficult is that many federal organizations can now be held liable for breaches occurring with partners. Healthcare, for instance, is currently adapting to the new HIPAA amendment that can hold business associates responsible for data breaches. The new regulations can cost violators up to $1.5 million per record.

Anticipating an employee-caused data breach can be incredibly difficult. However, there are several areas in which agencies can improve:

Assess the risk. Discovering and prioritizing possible vulnerabilities in the storage and transferring of sensitive data is a critical first step. To start, ask four questions about your agency:

-- How do your employees typically send and receive confidential files?

-- What's your agency's common practice for accessing mobile information?

-- If the agency has experienced previous incidents, what were the causes?

-- Do you have well-documented policies in place that teach staff which file transfer methods are okay, and which are risky?

Regularly review regulatory compliance requirements. The Federal Information Security Management Act (FISMA) requires agency officials to audit data security initiatives and report results annually. However, at the rate that technology evolves, IT should regularly determine the status of agency compliance, particularly if employees' routine actions meet regulatory requirements.

Secure and manage data in motion. Data that is being transferred from one source to another has a particularly high risk of being lost, stolen, or otherwise compromised -- especially in the case of internal breaches and the potential for human error. IT must implement systems that can effectively secure and manage data in motion. Transparency is also important. You need visibility into what was sent, how it was sent, to whom it was sent, and who accessed it.

Educate agency employees. Inside jobs with malicious intent do occur, but in reality many incidents are the result of accidents. Mitigate the risk at the source by educating agency employees on compliance issues and poor data-handling practices, such as third-party storage, insecure email and unapproved devices.

Tightening the security perimeter will always be a top priority for federal IT professionals. But as agencies invest to keep the bad guys out, it's equally important to consider the people who are already in.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Chuck Brooks
50%
50%
Chuck Brooks,
User Rank: Apprentice
11/8/2013 | 9:31:03 PM
re: Think Hackers Are IT's Biggest Threat? Guess Again
James is on point, cybersecurity risks are often teh result of internal breaches. The best way to address this is to have Informed risk management for employees on security protocols and processes to provide basic security awareness/identify threats.

-+
-+
pcalento011
50%
50%
pcalento011,
User Rank: Apprentice
10/31/2013 | 3:28:51 AM
re: Think Hackers Are IT's Biggest Threat? Guess Again
While certainly a "culture of security" can help address the threat, poorly architected systems also pose a risk. I'm not saying cloud computing or Big Data or any other technology is to blame, but a lack of planning leads to a lack of security. Blaming employees is too easy.
Ulf Mattsson
50%
50%
Ulf Mattsson,
User Rank: Moderator
10/30/2013 | 9:31:33 PM
re: Think Hackers Are IT's Biggest Threat? Guess Again
I agree that "Secure and manage data in motion" and "Tightening the security perimeter will always be a top priority for federal IT professionals", but I think that the perimeter is gone and that the most attractive target is data in large databases.

I think that the flow of sensitive data across different systems and databases should be protected. I recently read an interesting study from Aberdeen Group about security-related incidents. The study revealed that GǣOver the last 12 months, tokenization users had 50% fewer security-related incidents(e.g., unauthorized access, data loss or data exposure than tokenization non-usersGǥ. The name of the study is GǣTokenization Gets TractionGǥ.

I also think that security teams need to look at if data access patterns are normal for users that are accessing sensitive data. Tools can help to determine if the pattern is normal, is this what the typical employee does as part of their work, or is this behavior out of the ordinary.

Ulf Mattsson, CTO Protegrity
D. Henschen
50%
50%
D. Henschen,
User Rank: Apprentice
10/30/2013 | 6:38:01 PM
re: Think Hackers Are IT's Biggest Threat? Guess Again
This article has a government spin, but it's also very applicable to the private sector. Pay close heed to the practical advice on page two on curbing unintended data breaches unwittingly instigated by internal employees.
Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Major Brazilian Bank Tests Homomorphic Encryption on Financial Data
Kelly Sheridan, Staff Editor, Dark Reading,  1/10/2020
Will This Be the Year of the Branded Cybercriminal?
Raveed Laeb, Product Manager at KELA,  1/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3682
PUBLISHED: 2020-01-17
The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.
CVE-2019-17361
PUBLISHED: 2020-01-17
In SaltStack Salt through 2019.2.0, the salt-api NEST API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.
CVE-2019-19142
PUBLISHED: 2020-01-17
Intelbras WRN240 devices do not require authentication to replace the firmware via a POST request to the incoming/Firmware.cfg URI.
CVE-2019-19801
PUBLISHED: 2020-01-17
In Gallagher Command Centre Server versions of v8.10 prior to v8.10.1134(MR4), v8.00 prior to v8.00.1161(MR5), v7.90 prior to v7.90.991(MR5), v7.80 prior to v7.80.960(MR2) and v7.70 or earlier, an unprivileged but authenticated user is able to perform a backup of the Command Centre databases.
CVE-2019-19802
PUBLISHED: 2020-01-17
In Gallagher Command Centre Server v8.10 prior to v8.10.1134(MR4), v8.00 prior to v8.00.1161(MR5), v7.90 prior to v7.90.991(MR5), v7.80 prior to v7.80.960(MR2) and v7.70 or earlier, an authenticated user connecting to OPCUA can view all data that would be replicated in a multi-server setup without p...