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

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
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web