From: "Boyce, Kevin P. (AS)" <kevin.boyce@ngc.com>
To: linux-audit@redhat.com
Subject: CD Burner Auditing
Date: Tue, 22 Apr 2014 15:14:28 -0400 [thread overview]
Message-ID: <5356BF94.6050901@ngc.com> (raw)
Does anyone know if it is possible to audit what filenames users are
burning to optical media?
I suppose I can put a watch on the /dev/sr0 device for write events, but
this does not give me any idea what was written to the disc. I suppose
I could also set an execve watch all burner programs, eg. /usr/bin/k3b
/usr/bin/brasero /usr/bin/cdrecord /usr/bin/cdrdao /usr/bin/dvdrecord,
to know if someone opened the burning interface; but how could I tell
what it was they were writing?
Any suggestions are welcome.
Kevin
next reply other threads:[~2014-04-22 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:14 Boyce, Kevin P. (AS) [this message]
2014-04-22 19:32 ` CD Burner Auditing Satish Chandra Kilaru
2014-04-22 19:35 ` EXT :Re: " Boyce, Kevin P. (AS)
2014-04-22 19:39 ` Satish Chandra Kilaru
2014-04-22 19:44 ` Boyce, Kevin P. (AS)
2014-04-22 19:55 ` Satish Chandra Kilaru
2014-04-22 20:06 ` Steve Grubb
2014-04-22 20:39 ` Steve Grubb
2014-04-22 22:00 ` Burn Alting
2014-04-22 22:11 ` Steve Grubb
2014-04-23 0:13 ` Josh
2014-04-22 20:02 ` Steve Grubb
2014-04-22 20:43 ` Steve Grubb
2014-04-22 21:52 ` Burn Alting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5356BF94.6050901@ngc.com \
--to=kevin.boyce@ngc.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox