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-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio