In any sane shop, the security auditors have far too much to do to worry
about EVERY violation. People fat-finger DSNs all the time, not only
on-line but in their program code as well. I've been responsible for
monitoring the violations reports at several companies; I glance over them
not for individual events but for (as Robert said) patterns that raise my
eyebrows. In fact, usually I write some REXX tools to filter out certain
routine patterns and pass on to me everything else.
There may be individual datasets that get my attention - certain payroll
files, for example, and data related to RACF itself - but mostly to make me
look twice requires multiple hits AND other characteristics. And even when
I'm moved to inquire into an event, it's almost always just a mistake of
some kind. In 19 years of mainframe security work I don't think I've run
across more than half a dozen users about whom I am still suspicious.
Individual violations are just too routine to bother your head about.
John, if your name merely appears on a violations report once in a while,
that wouldn't cause anyone even to notice you at any company I've ever
worked at. If once in a while someone asks you what you were doing, well,
someone's trying to be vigilant, I suppose; just tell 'em and forget it.
But if you're actually being contacted about every individual violation,
that sounds pretty dumb to me. And if they're batching up their violations
and handling them - trying to handle them - no more often than every two
months, that's just crazy.
---
Bob Bridges,
rhb...@attglobal.net, cell
336 382-7313
/* Maybe those of us who have never been Beatles shouldn't judge them too
severely. That degree of celebrity would test anyone's maturity, never mind
four boys in their twenties. Still, we might reflect on the fact that none
of Nat Cole's fans ever tried to shoot him. -Joseph Sobran, 2001-12-06 */
-----Original Message-----
From: Adrian Stern
Sent: Wednesday, May 23, 2012 09:36
Hurrah! A voice of reason!
Sorry, but I was really impressed by the line "timely identification and
investigation of unusual patterns and trends of access and violations" which
is what I believe security staff should be doing rather than demanding a
reason for every violation.
-----Original Message-----
From: Robert S. Hansel (RSH)
Sent: den 23 maj 2012 14:53
RACF does not log usage of the LISTDSD (LD), RLIST (RL), and SEARCH (SR)
commands. These commands can be used to probe the defenses of a system as
discussed in the article entitled " Should You Monitor or Restrict LISTDSD,
RLIST, or SEARCH?" in the October 2009 issue of our RACF Tips Newsletters
(available via URL
www.rshconsulting.com/racfres.htm). As a RACF security
professional, I share the concerns expressed by others about the proposed
use of the LD command.
On the other hand, I can appreciate John's dilemma and his desire to avoid
violations. Asking months after the fact why a violation occurred seems
counterproductive both for the user and the security staff. We believe a
better approach is the timely identification and investigation of unusual
patterns and trends of access and violations, such as repeated attempts to
access restricted APF libraries or production files.