Attacks/Breaches
3/14/2014
03:00 PM
Becca Lipman
Becca Lipman
News
Connect Directly
RSS
E-Mail
100%
0%

7 Behaviors That Could Indicate A Security Breach

Breaches create outliers. Identifying anomalous activity can help keep firms in compliance and out of the headlines.

Here's a rather uncontested statement: In the world of cybersecurity, there are many things that can go wrong.

Some breaches are intentional, others accidental. A case in which an employee unwittingly discloses confidential information or is working from an infected machine may look similar to the actions of employee who has gone rogue by uploading or downloading inappropriate data.

Regardless of its cause, determining whether a behavior is normal or not is important when it comes to detecting a variety of security breaches.

Skyhigh Networks compiled the following real-world examples of behaviors that security teams identified as several standard deviations outside of normal activity.

Read the rest of this article on Wall Street & Technology.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
pfretty
100%
0%
pfretty,
User Rank: Apprentice
3/17/2014 | 3:32:50 PM
Not just staying out of headlines, but avoiding the costs
It's crucial to pay close attention to the warning signs. According to the Ponemon 2013 Cost of Cyber Crime Report (http://www.hpenterprisesecurity.com/ponemon-study-2013), the average company experiences 100+ attacks per year at a cost of $11.6 million. These make breaches not just cause embrassment, but in many instances can be crippling to even the most otherwise stable organizations. Fighting off attacks starts with strategy and technology and continues to improve through education. 

 

Peter Fretty, IDG blogger working on behalf of HP
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.