IT solutions for global businesses
db2-zos-audit
SOFTWARE ENGINEERING GmbH is exited to play an important role in IBM‘s z/Security ecosystem.
Be Smart, be Secure and join our webinar. In cooperation with one of our customers we’ll show how WLX Audit is used to audit DBA activities to fulfill the BaFin guidelines, answering the Auditors questions… Who did What, When and from Where exploiting efficient OPX technology.
This Program started in Europe in 2016. We have „GIVEn“ various free-of-charge Use Cases from our SQL WorkloadExpert for Db2 z/OS like:
In return, we receive the results. We’d like to share this inspiring experiences with you and communicate with local User Groups worldwide.
January-March 2020 (1Q) – Flyer Audit More
April-June 2020 (2Q) – Presentation More
July – September 2020 (3Q) – Presentation – Flyer SAX More
and SQL Workload Performance for Db2 12Oct.-December 2020 (4Q)
and will communicate with the local User Groups for discussions
First option is the simplest, cheapest and quickest:
Whether or not this will help your company is a non-trivial question of course!
Next option is relatively simple and cheap, but requires a bit of work:
If you happen to have the skills for extracting the required audit data from existing data that is being collected anyway, then this might well be the best method if you are really strapped for resources.
Then we have not so simple, still cheap, but a ton of work:
This needs a serious amount of skills to get and keep up with the agile world of Db2. You will also need to take care of the amount of data that you will be collecting.
However, the auditor will be happy as you have everything they could ask for.
Last option is simple, not so cheap but very quick:
This is my preferred solution, especially as we just happen to sell one (WorkLoadExpert Audit).
This is actually the only real way to go. You probably don’t have the time to keep all these things up-to-date and running correctly.
So, you have chosen one of these ways to gather the data. Now you must evaluate what you got. Here again we have four separate ways to go forward:
There it is!
This is not really a solution and any auditor worth his, or her, salt would quite rightly be extremely upset!
A whole bunch of pre-written SQLs.
SPUFI is ok, but much better would be to see these in a GUI where graphical viewing is built in and saving and sharing results is much easier.
This is not bad, but still a manual “island” process. Just Db2 and nothing else plus it must be triggered by humans.
A whole bunch of pre-written and custom SQLs.
This time, all run in Batch and the results are emailed to the auditor directly. These emails can “just sit there” until the auditor checks the results. Naturally, if anything is found, then the underlying data must still be there for a detailed analysis.
Better, as it is getting automatic but still not really “round”, as it is still Db2 in isolation…
Use of LEEF or SYSLOGGER-style formats to export all audit data.
The data is then in a data-lake where SPLUNK, QRADAR et al can happily slice and dice their way through the data.
This is the best way!
You also get an extra bonus point for *removing* the data from the mainframe. As auditors *love* a single point of control, this is the only real way forward. It also pushes the Db2 data into the world of other data that auditors use and require.
If you would like to take part, then please just fire off an email to db2support@segus.com telling us who you are and which firm you work for and we will get in touch!
By the way, it is called “Give&Take” because :
TTFN,
Roy Boxwell
SEGUS & SOFTWARE ENGINEERING präsentieren
There are different ways and tools that promise they are able to do it, but what can they really do and what are the associated costs?
This presentation introduces Db2 technology exploitation that delivers DML, DDL, DCL activity in a Db2 environment along with identification details.
This presentation helps you understand the way Auditors look at Db2 and what they require in order to do their daily work. Learn how you can satisfy your Auditors needs, by interfacing with an SIEM system, like:
Roy Boxwell has more than 33 years of experience in MVS, OS/390, and z/OS environments – 31 of those in Db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG Db2 Listserv and sends out a monthly Db2 z/OS Newsletter.
DS, RDz, DSM, z/OSMF -to name just IBMs recent ones- always had a common downside, which I believe customers didn’t like at all: Users were unable to access all mainframe products from, and through, a common interface.
Bottom line:
We need a GUI that not only comes with a monitoring dashboard, job submission capabilities, includes a JES explorer, data set explorer and editor, scripting for automation and interaction with all major product, like CICS, Db2,
BUT it should be used by ALL vendors!
Of course, this GUI should also seamlessly integrate into all those robust security and resource management components we’re already familiar with. It needs to be the preferred interface for administrative tasks, development, test, and operation, no matter if using old applications, or brand-new ones.
Am I asking for too much?
ZOWE – THE z ecosystem to securely manage, control, script and develop – seems to be the way to go.
It comes with a RESTful API, an extensible command line interface and an HTML 5 web-based UI framework designed to fuse everything we already have with anything we want to do today and tomorrow. It is exactly what many of us have been asking for years. We see a clear commitment from some of the most important companies in the mainframe world and we also see the technical components required to do our daily work and to open up new opportunities for tomorrows modern apps.
Late 2018 our company strategically decided to build UIs based on the ZOWE ecosystem.
Learn how you can quickly define entire workflows and interact and control them using a Db2 z/OS cloning example along with workload capture and replay in a simulation environment – fully automated quality assurance as part of continuous delivery in an agile world.
Ulf Heinrich is the Director of Solutions Delivery at SOFTWARE ENGINEERING GmbH. He specializes in Db2 operations and performance tuning, focusing on the growing requirement for cost reduction and 24×7 operations. As a consultant at large customer sites, he has implemented database maintenance procedures and recovery strategies, and also experienced the pitfalls of recovery scenarios under realworld recovery pressure. His activities cover EMEA, as well as North America through SE’s U.S. subsidiary, SEGUS Inc. As a member of SE’s Request Board he’s working closely with customers and the development labs.
This year, as every year, the moment arrives for most of us when the clocks go forward and then in autumn back again. I really hate this, as I still have a bunch of clocks that do not automatically do it for me. My PC, phone, laptop, TV etc. all do it for me but the rest… anyway what has this got to do with Db2 I hear you all wonder? Well it really is quite a horrible little story coming up…
At precisely 02:00 on the 25th of March a SET CLOCK console command was issued to change the UTC Offset to +2 thus leaping from 02:00 to 03:00 in the blink of an eye.
Now “how long” is the blink of an eye? For Db2 these days – too long!
At 2018-03-25-02.00.00.006999 a transaction was logged in the Audit system, in fact *lots* of transactions were in-flight at this time. Normally it is not a problem and, in fact, nothing happened until nearly three months later when someone found that there was possibly some data missing.
Alarm bells are ringing as these inventory checks cannot have missing data. The code is nowadays all JAVA and the developer in charge of the problem found out that the data was indeed missing!
The DBA group were then involved, as it could be data corruption, and they looked and found the data – but it was not the same data as the developers had… then the penny dropped!
In fact, the data the developer had was *exactly* one hour later than the data found by the DBA group. I mentioned earlier that the 25th March was the switch to summer time and, perhaps, the JAVA Driver is “helping” us, a bit too much help if you ask me!
Here is a bit of SQL for you to recreate the problem and gaze in wonder at how cool/horrible (delete what is not applicable) JAVA really is.
CREATE TABLE BOXWELL.DAY_LIGHT (COL1 SMALLINT NOT NULL ,COL2 TIMESTAMP NOT NULL) ; INSERT INTO BOXWELL.DAY_LIGHT VALUES (1 , '2018-03-25-01.59.59.999999'); INSERT INTO BOXWELL.DAY_LIGHT VALUES (2 , '2018-03-25-02.00.00.006999'); INSERT INTO BOXWELL.DAY_LIGHT VALUES (3 , '2018-03-25-03.00.00.000099'); COMMIT ; SELECT * FROM BOXWELL.DAY_LIGHT ORDER BY 1 ; ---------+---------+---------+---------+---------+-------- COL1 COL2 ---------+---------+---------+---------+---------+-------- 1 2018-03-25-01.59.59.999999 2 2018-03-25-02.00.00.006999 3 2018-03-25-03.00.00.000099 DSNE610I NUMBER OF ROWS DISPLAYED IS 3
The output of SPUFI looks great! Timestamps are correct and all is fine.
Now do the select using a JAVA driver of your choice, here I am using DataStudio:
And then running it gives:
Isn’t that
great/terrifying (delete what is not applicable)
as the JAVA driver is “looking” at the timestamp data and seeing “oh oh! That timestamp is impossible! I know – I will add one hour to correct it!”
This scares me a little…actually quite a lot!
The only place I could find anything about this was in a chapter about not using 24 as midnight and the problem of using timestamps between October 5th 1582 and October 14th 1582:
https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/java/src/tpc/imjcc_r0053436.html
If a string representation of a date, time, or timestamp value does not correspond to a real date or time, Java adjusts the value to a real date or time value.
Which, of course, explains everything!
There is no quick fix!
1 – The customer must either change all SQL to use the CHAR function – Not good!
Or
2 – Check all of their important timestamp columns for the range 02.00.00.000000 -> 02.59.59.999999 data and then update them with plus one hour – Not good!
This problem will get worse the faster the machines get and so my idea to solve it next year is simply issue a
SET LOG SUSPEND
at one second before 02:00 which flushes the log, issues a system checkpoint (non data-sharing), updates the BSDS and basically pauses the system. Then do the SET CLOCK command and then do a
SET LOG RESUME
It all takes about three seconds and so should not cause any timeouts.
I really hope that, one day, we simply get rid of daylight saving time…
As always, any questions or comments would be most welcome!
TTFN,
Roy Boxwell
First up, this is not another Audit review and health check sell! We, and I mean especially in the European Union (EU), are about to get the biggest update to “my data”, “my right to know” and “my right to forget (delete)” that has ever happened, when the General Data Protection Regulation (GDPR) Kicks off on May 25th, 2018.
Well, we all should really! Very soon hordes of people could well start demanding to know if you have any data about them and if so where it is and who you give it to. Personal Data will be big business!
Just assuming all is ok is also no longer valid or lawful – any personal data that you keep must be kept with the *active* consent of the data owner… This is going to get awfully messy awfully quickly! Do not forget that the definition of personal data has also changed quite a bit e.g. IP Addresses. For the record here is the actual text in the GDPR regulations:
Art. 4 GDPR Definitions
For the purposes of this Regulation:
1. ‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
And
Art. 9 GDPR Processing of special categories of personal data
1. Processing of personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation shall be prohibited.
Very important are Articles 25 and 32:
Art. 25 GDPR Data protection by design and by default
1. Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures, such as pseudonymisation, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects.
2. The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual’s intervention to an indefinite number of natural persons.
Last part of Paragraph two is important here.
Art. 32 GDPR Security of processing
1. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
1. the pseudonymisation and encryption of personal data;
2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
3. the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
2. In assessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data transmitted, stored or otherwise processed.
Here paragraphs 1.2, 1.4 and 2 are the biggies!
The fines are also amazingly high. First, for the “minor” problem of being over 72 hours late when data leaks have occurred (a breach), is 2% of global turnover or €10,000,000 – whichever is *higher* and, if you are really naughty, like disregarding basic data laws, moving data abroad or ignoring an individual’s rights then you get hit for 4% of global turnover or €20,000,000 – again whichever is *higher*
I, for one, do not want to be the first company that makes the headlines… How about you?
Now I know that most of the talk about GDPR is “right to data” for the general public but we all know, as IT specialists, that the people to be really afraid of are ex-employees who did not leave on happy terms. They know *exactly* where the knife could best be put… They know exactly where, and on which platforms, all of the data really is.
What can you do? Well the first thing is to actually understand what GDPR means to you and your firm’s data. Then you must be able to prove to auditors that you tried your very best. We will all probably get hacked at some time, but if you tried your best it is enough. Using all of the data you gather in a post-mortem, or for forensics, is also a very good idea as can be seen in paragraphs 2.3 and 2.4 below:
Art. 83 GDPR General conditions for imposing administrative fines
1. Each supervisory authority shall ensure that the imposition of administrative fines pursuant to this Article in respect of infringements of this Regulation referred to in paragraphs 4, 5 and 6 shall in each individual case be effective, proportionate and dissuasive.
2. Administrative fines shall, depending on the circumstances of each individual case, be imposed in addition to, or instead of, measures referred to in points (a) to (h) and (j) of Article 58(2). When deciding whether to impose an administrative fine and deciding on the amount of the administrative fine in each individual case due regard shall be given to the following:
1. the nature, gravity and duration of the infringement taking into account the nature scope or purpose of the processing concerned as well as the number of data subjects affected and the level of damage suffered by them;
2. the intentional or negligent character of the infringement;
3. any action taken by the controller or processor to mitigate the damage suffered by data subjects;
4. the degree of responsibility of the controller or processor taking into account technical and organisational measures implemented by them pursuant to Articles 25 and 32;
The list goes on after these of course…
Most sites use SMF and do daily cuts to then offload to a repository system of some sort on some sort of hardware. The problem here is that the amount of SMF data you are generating can swamp you and this method is not nearly quick enough. Waiting a day is 24 hours of the 72 that are available to you…
If you can handle OPx and a bit of High Level Assembler then “Bob’s your uncle!” as long as Bob is your Auditor of course…There are more than enough examples in the web about how to write and do OPx reading (There are even vendors that are willing to sell you their software 🙂 )
Create a program that can issue the required IFI commands to start and stop traces and to issue the READA and READS IFI calls that you wish to have. If you don’t know which Audit Class is which IFCID – Here’s my handy list:
| Audit Class | IFCIDs | What | Why |
| 1 | 140 | Authorization failures | Possible brute force password attack |
| 2 | 141 | GRANTs and REVOKEs | Possible temporary raising of privilege |
| 3 | 142 | CREATE/ALTER/DROP of table with AUDIT attribute | Removing the AUDIT attribute is a big red flag |
| 4 | 143 | 1st Change of table with AUDIT attribute | Sensitive data updates |
| 5 | 144 | 1st Select of table with AUDIT attribute | Sensitive data usage |
| 6 | 145 | BIND/PREPARE using table with AUDIT attribute | Possible usage of sensitive data |
| 7 | 55, 83, 87, 169, 319 | SET CURRENT SQLID, end of identify, end of signon CICS/IMS | Elevation of privilege |
| 8 | 23, 24, 25, 219, 220 | Db2 Utilities | UNLOADing data to where? |
| 9 | 146, 392 | For customer use | n/a |
| 10 | 269, 270, 271*
271 is not started automatically with Class 10 | Establish reuse trusted context, trusted context CREATE/ALTER and Column Mask/Row Permission CREATE/DROP/ALTER | Anything with MASKs or ROW Permissions must be checked |
| 11 | 361 | Successful access | Only makes sense if working with AUDIT POLICY SYSADMIN or DBADMIN |
Well, what about the COMMANDs to actually see what people are issuing on the machine? So you must also add IFCIDs 90 and 91. Then you do not see any of the DDL so you must start IFCID 62 to get that as you do want to see what people are ALTERing, creating and dropping don’t you?
Once you have a system that gathers all these you must buffer them in memory and then do one of two things:
1) Write them out to a file for post-processing and enrichment later
2) Directly write them to your SIEM system of choice
I am not a fan of number 2 because if the SIEM system cannot accept the data then your data is lost…
With No. 1 you can keep processing even if the SIEM system cannot ingest, for whatever reason, and as long as you trigger yourself every 5 – 10 minutes or when the OPx buffer is full then that is “real time” enough for me!
Plus you can enrich the data with extra stuff that the naked IFCIDs do not have attached to them e.g. map dbid/psid to a real database and tablespace etc.
Store all of this data in a bunch of Db2 tables
then kick-off a Db2 to a LEEF re-formatter program that reads all the audit data that has been collected since last time
writes it all out.
Then you must do an ICONV for code page conversion, swiftly followed by a gzip to get it down to size and then copy it down to a USS file ready for your SIEM system to ingest its prey.
To prove that this system is always available you should also schedule a simple
GRANT SELECT ON SYSIBM.SYSDUMMY1 TO PUBLIC;
Every morning at 06:00 which you should see in the output every day. Remember – Due Diligence!
So now you are done and finished and can let the SIEM system do the completion!
As always, any questions or comments would be most welcome!
TTFN,
Roy Boxwell
PS: Please note that the bold of parts of the GDPR text is only from me!
Db2 Forum. Southwest Db2 Users Group – Februar 2018 – Grapevine (Dallas), TX, USA
SEGUS & SOFTWARE ENGINEERING sponsern diese Veranstaltung & präsentieren
There’s different ways and tools that promise to be able to do it, but what can they really do and what are the associated costs? This presentation introduces Db2 10/11 technology exploitation that delivers any DML, DDL, DCL being executed in a Db2 environment along with identification details. Learn how you can run Audit analytics against a long‐term repository, pinpointing who executed a query, when and from where. Analyze your entire workload to understand access patterns and abnormalities.
This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.
Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.
Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.
* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison
Audience Experience: Intermediate Advanced
Platform: Db2 z/OS
Presentation Length: 60 minutes
Presentation Category: Database Administration Performance Management Db2 Migration
– Benjamin Disraeli, Prime Minister of England (1868, 1874-1880)
The above line may, or may not, have been spoken well over 100 years ago, but the need for statistics and, above all else, accurate statistics is more important than ever in the Db2 world of today.
Roy Boxwell has more than 32 years of experience in MVS, OS/390, and z/OS environments – 30 of those in Db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG Db2 Listserv and sends out a monthly Db2 z/OS Newsletter.
HOTDUG – Heart of Texas Db2 User Group – Februar 2018 – Austin, TX, USA
SEGUS & SOFTWARE ENGINEERING sponsern diese Veranstaltung & präsentieren
There’s different ways and tools that promise to be able to do it, but what can they really do and what are the associated costs? This presentation introduces Db2 10/11 technology exploitation that delivers any DML, DDL, DCL being executed in a Db2 environment along with identification details. Learn how you can run Audit analytics against a long‐term repository, pinpointing who executed a query, when and from where. Analyze your entire workload to understand access patterns and abnormalities.
This will have a tremendous impact on migration strategies, because we have to find a reliable way to test these code deliveries in a fraction of time. If we make it, Business Divisions will become enthused at how quickly new technology becomes available for new applications. This presentation will describe the difference between Code, Catalog, Function and Application Levels, how you can control them and how you can fallback in case of anomalies. It also illustrates how we still can be pro-active in testing without burning weeks and months.
Learn how to choose from four different levels of testing and a new way of automation. CD-Screening allows you to pick and choose from KPI based test automation. The levels include simple anomaly alerting, access path verification, clone Pre-apply and even workload capture/replay to easily discover different behaviour resulting from a new code Level.
Joining this presentation, you’ll learn how to align Continuous Delivery to your Continuous Availability.
* Anomaly alerting based on Incompatibility Change Indicators (ICIs)
* Dyn./Stat.Access Path Change Detection e.g.via Plan Management
* Clone based code change pre-apply exploiting Backup System
* Workload-KPI verification using SQL replay and KPI comparison
Audience Experience: Intermediate Advanced
Platform: Db2 z/OS
Presentation Length: 60 minutes
Presentation Category: Database Administration Performance Management Db2 Migration
– Benjamin Disraeli, Prime Minister of England (1868, 1874-1880)
The above line may, or may not, have been spoken well over 100 years ago, but the need for statistics and, above all else, accurate statistics is more important than ever in the Db2 world of today.
Roy Boxwell has more than 32 years of experience in MVS, OS/390, and z/OS environments – 30 of those in Db2. He specializes in installation, migration, and performance monitoring and tuning. Roy leads the SEG development team responsible for the real time database maintenance solutions. He is also an active participant, speaker and contributor on the IDUG Db2 Listserv and sends out a monthly Db2 z/OS Newsletter.
SEGUS & SOFTWARE ENGINEERING präsentieren
TRIDEX – am Dienstag den 27. September 2016
Audit and Compliance is a need that many companies want and have to fulfill.
There’s different ways and tools that promise to be able to do it, but what can they really do and what are the associated costs? This presentation introduces DB2 10/11 technology exploitation that delivers any DML, DDL, DCL being executed in a DB2 environment along with identification details. Learn how you can run Audit analytics against a long‐term repository, pinpointing who executed a query, when and from where. Analyze your entire workload to understand access patterns and abnormalities.
| 1-Audit needs and musts Take a journey to GLB HIPAA PCI‐DSS Basel III Sarbanes‐Oxley CA SB1386 Federal Information Security Management Act “ed Flag”Rules (FRCA)5. | |
| 2-Solution overview and their Pros/Cons Get an overview about the existing solutions and understand how they work. | |
| 3-The viable way – let DB2 do the magic! Learn about DB2 enhancements in DB2 10/11 that deliver the DB2 workload being processed and understand why it’s so efficient. | |
| 4-Customer results from the banking industry Receive some experience from a large banking company and how they successfully replaced their DB2 Audit feature based reporting by a modern SQL tracking and analytics process. |
SEGUS & SOFTWARE ENGINEERING präsentieren
DVDUG – am Mittwoch den 28. September 2016
Audit and Compliance is a need that many companies want and have to fulfill.
There’s different ways and tools that promise to be able to do it, but what can they really do and what are the associated costs? This presentation introduces DB2 10/11 technology exploitation that delivers any DML, DDL, DCL being executed in a DB2 environment along with identification details. Learn how you can run Audit analytics against a long‐term repository, pinpointing who executed a query, when and from where. Analyze your entire workload to understand access patterns and abnormalities.
| 1-Audit needs and musts Take a journey to GLB HIPAA PCI‐DSS Basel III Sarbanes‐Oxley CA SB1386 Federal Information Security Management Act “ed Flag”Rules (FRCA)5. | |
| 2-Solution overview and their Pros/Cons Get an overview about the existing solutions and understand how they work. | |
| 3-The viable way – let DB2 do the magic! Learn about DB2 enhancements in DB2 10/11 that deliver the DB2 workload being processed and understand why it’s so efficient. | |
| 4-Customer results from the banking industry Receive some experience from a large banking company and how they successfully replaced their DB2 Audit feature based reporting by a modern SQL tracking and analytics process. |