From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: EXT :Re: CD Burner Auditing Date: Tue, 22 Apr 2014 16:02:47 -0400 Message-ID: <1884427.kS0bph9V2f@x2> References: <5356BF94.6050901@ngc.com> <5356C473.2040601@ngc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tuesday, April 22, 2014 03:39:14 PM Satish Chandra Kilaru wrote: > Even if there is a file system it may not be mounted on a known a folder. > But monitoring access of sensitive content and execution of burning > programs can provide clues. You can use dd on devices that are not mounted. > You can use audit dispatcher to react to audit events.... When u get a > MOUNT event you can see where sr0 is mounted and start a new watch for that > path. If you are not writing an ISO I think it has to be mounted. I think hooking the udev rules might be better. This would let you check for hot plug events where something is not yet mounted. -Steve