Risk
12/17/2012
07:04 AM
Dark Reading
Dark Reading
Quick Hits
Connect Directly
RSS
E-Mail
50%
50%

Application Monitoring For Security Professionals

Keeping an eye on applications can help your organization avoid data breaches. Here are some tips on how to do it right

[The following is excerpted from "Application Monitoring For Security Professionals," a new, free report posted this week on Dark Reading's Security Monitoring Tech Center.]

Every IT professional worth his or her salt knows that, when it comes to information security, monitoring is tremendously important.

IT pros in regulated environments know the importance placed on monitoring controls from a compliance standpoint, but even when compliance isn't a factor, monitoring controls are often a key mechanism for determining when a security event is in progress in an environment -- and a key mechanism for analyzing root cause after the fact.

However, despite the importance of monitoring, most organizations have a significant blind spot in their monitoring capabilities. And this blind spot appears at the highest level of the stack: the application layer.

But this doesn’t have to be the case. For the practical-minded security professional, there can be tremendous value in expanding monitoring capabilities to include the application space. In fact, in many cases, you can leverage monitoring tool investments you’ve already made to help expand visibility and derive additional value for application-level security events.

Oftentimes, technology professionals associate monitoring only with logging. But it’s important to recognize that logging is only one of a few different vehicles available for gaining information about applications in the environment.

Monitoring can include any number of other controls over and above logs. Any control, process, metadata, or other information that informs security personnel about the security health of an application is a potential data point to target as part of your monitoring strategy.

There are as many methodologies for security logging as there are applications themselves. This matters because it has a direct impact on your ability to use stock tools to collect log information. Many organizations with log management tools in place will want to leverage existing investments for their applications.

To read more about the tools that can be used to do application security monitoring -- and some steps for implementing them -- download the free report on application monitoring and security.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0972
Published: 2014-08-01
The kgsl graphics driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly prevent write access to IOMMU context registers, which allows local users to select a custom page table, and consequently write ...

CVE-2014-2627
Published: 2014-08-01
Unspecified vulnerability in HP NonStop NetBatch G06.14 through G06.32.01, H06 through H06.28, and J06 through J06.17.01 allows remote authenticated users to gain privileges for NetBatch job execution via unknown vectors.

CVE-2014-3009
Published: 2014-08-01
The GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 through 11.0 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 does not properly handle FRAME elements, which makes it easier for remote authenticated users to conduct ph...

CVE-2014-3302
Published: 2014-08-01
user.php in Cisco WebEx Meetings Server 1.5(.1.131) and earlier does not properly implement the token timer for authenticated encryption, which allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCuj81708.

CVE-2014-3534
Published: 2014-08-01
arch/s390/kernel/ptrace.c in the Linux kernel before 3.15.8 on the s390 platform does not properly restrict address-space control operations in PTRACE_POKEUSR_AREA requests, which allows local users to obtain read and write access to kernel memory locations, and consequently gain privileges, via a c...

Best of the Web
Dark Reading Radio