From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: [PATCH] auvirt: a new tool for reporting events related to virtual machines Date: Tue, 24 Jan 2012 15:27:40 -0500 Message-ID: <201201241527.40706.sgrubb@redhat.com> References: <1323964611-30053-1-git-send-email-mhcerri@linux.vnet.ibm.com> <201201111620.06515.sgrubb@redhat.com> <4F1EF3B8.5080303@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F1EF3B8.5080303@linux.vnet.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Marcelo Cerri Cc: linux-audit@redhat.com, gcwilson@us.ibm.com, bryntcor@us.ibm.com List-Id: linux-audit@redhat.com On Tuesday, January 24, 2012 01:08:56 PM Marcelo Cerri wrote: > I took a look at some anomaly events and I'm thinking to correlate them > to guests based on the SELinux context or maybe based on the pid field. > > Do you think there is another ways to correlate them? I was thinking to correlate them based on the time and pid. If its within the time range between startup/shutdown and its the same pid, then you have the event correlated. If its outside the time range or a different pid, then you do not have correlation. I would not look at selinux label because not all systems/distros have it enabled or compiled in. So, pid and time are the most universal identifiers for correlation. -Steve