Articles & Content

Archives

DB2 Auditing and the Need for NO Secrecy (J10)

Topic: DB2 for z/OS

Subtopic: 2007



DATE: 2007-5-9 (01:40 PM - 02:40 PM)
SPEAKERS: Steen Rasmussen (CA)

Auditing has always been an issue - at least to some IT organizations. The past few years have really widened the scope and auditing is now a part of everybodyís daily tasks. In the past we only had to worry about what the SYSADMís were doing and which users should be allowed to use which secondary authorization-idís. Dozens of regulatory requirements are now present and it has become mandatory to define processes making sure none of "the rules" are violated. Also, besides from checking certain rules, it is becoming more and more important to document changes of many kinds. This presentation will illustrate how some of the CA DB2 solutions can be used to comply the regulatory requirements and automate the processes needed to satisfy these requirements. In many cases it is more productive to not implement a lot of restrictions, but instead have solid reporting processes in place.

EXP. LEVEL: Beginner,Intermediate,Advanced

OBJECTIVES:

Possible solutions to consider being in a position to describe the physical structure at any point-in-time in the past

The catalog only holds information for when an object was created and when the most recent change was implemented. Solutions to also describe what the change was as well as previous alterations and dropped objects will be illustrated

Despite DB2 V8 offers some relief in terms of Schema Management, the need to execute the drop with cascading effects still exist. Letís see how these "undesired drops and cascading effects" can be documented

Auditing usually has two different approaches. Which user-idís did what - or - who touched this table and what did they do. Both scenarios will be covered in terms of automatic reporting. This topic will also touch Multi-Level-security

A relative new issue has started to arise - the need to find out who executed which commands, in order to describe either performance changes or application impact



Click Here to Download

NOTE: These are only open to members of IDUG. If you are not a member, please CLICK HERE for more information.