Take a look at a great reference document with examples on policy definition for the S-TAP on DB2 z/OS:
KRZ 060000CA4Y 682 Visitas
9.1 for the appliance is Patch 100 on top of 9.0 product image. If you download from Passport Advantage, you will get Patch 100 as well as the base image. But do not forget to go through appropriate health checks before upgrading. The patches for 32-bit, 64-bit, and the health checks are on FixCentral.
The Windows S-TAP is available now on FixCentral as well. The UNIX one will be available a little later.
Documentation and planning
Program Directories for the z S-TAPS
What's new presentations (tech talks)
tiv_ashok 060001TPAX 1.669 Visitas
tiv_ashok 060001TPAX 918 Visitas
Unit Utilization Report
Unit utilization report is not showing up in Guardium version 9.
Statistics for these reports are not enabled by default on any of the appliances.
To get this report working on collectors/aggregators following command has to be executed
“store monitor gdm_statistics 1”
Guardium Monitor -> Units Utilization
Enterprise Buffer Usage Report
This report will give the overall buffer usage report from all the appliances on the central manager view.
This report by default does not get populated by default on the central manager, please find the screen shot below about the error message seen by default.
Once the collection is enabled on the CM, the report on the central manager will be like shown below which will have Buffer report from all the appliances.
I will be the first to admit that when I first heard of 'data level security' I had no idea what it meant. It's one of those terms that could mean almost anything, depending on what context you first heard it. So, let's get over the term and focus on what the capability is. Simply put, it enables you to create automatic filtering of audit data based on who the viewer is and their association with the particular audited database (hence the term data-level...). The beauty of this is that you can create one report definition, such as a report that shows database activity, and when the Oracle DBA sees it he or she would only see Oracle information, and when the DB2 DBA he or she would only see activity for the DB2 database. Furthermore, you can overlay your organizational structure so that the DBA manager could see the audit data for all the databases. This is quite a simplification, but I think trying to explain it in words is hard. You really need a visual and an example.
For this reason, I urge you to go read this developerWorks article that one of my colleagues and I coauthored. It has nice pictures and walks you through a scenario that includes not just DBA roles, but auditor roles as well. Check it out.
I wanted to let everyone know that F5 has published two step by step deployment guides- you can find them on their dw wiki page: One to support what we call Guardium "grid" and another for the real-time application end user identification from their firewall. If you didn't listen in or download the notes and slides from the What is new in V9 Tech Talk, you may not have a clue what I'm talking about so I'll briefly summarize: