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
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
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2003-1598
Published: 2014-10-01
SQL injection vulnerability in log.header.php in WordPress 0.7 and earlier allows remote attackers to execute arbitrary SQL commands via the posts variable.

CVE-2011-4624
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in facebook.php in the GRAND FlAGallery plugin (flash-album-gallery) before 1.57 for WordPress allows remote attackers to inject arbitrary web script or HTML via the i parameter.

CVE-2012-0811
Published: 2014-10-01
Multiple SQL injection vulnerabilities in Postfix Admin (aka postfixadmin) before 2.3.5 allow remote authenticated users to execute arbitrary SQL commands via (1) the pw parameter to the pacrypt function, when mysql_encrypt is configured, or (2) unspecified vectors that are used in backup files gene...

CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Chris Hadnagy, who hosts the annual Social Engineering Capture the Flag Contest at DEF CON, will discuss the latest trends attackers are using.