This page (revision-9) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 26-Nov-2021 10:22 9 KB JMyers to previous
8 26-Nov-2021 10:22 9 KB JMyers to previous | to last
7 26-Nov-2021 10:22 9 KB RForbes to previous | to last
6 26-Nov-2021 10:22 9 KB JAiken to previous | to last
5 26-Nov-2021 10:22 9 KB RForbes to previous | to last
4 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - DETAILED CHANGE AUDITING ==> WP-DETAILED CHANGE AUDITING
3 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - DDETAILED CHANGE AUDITING ==> WP - DETAILED CHANGE AUDITING
2 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - Detailed Change Auditing ==> WP - DDETAILED CHANGE AUDITING
1 26-Nov-2021 10:22 8 KB Administrator to last

Page References

Incoming links Outgoing links
WP-DETAILED CHANGE AUDITING...nobody
WP-DETAILED CHANGE AUDITING

Version management

Difference between version and

At line 2 changed one line
Detailed change auditing in ePersonality was created to fulfill the need to identify “who” has changed “what” data, “when” and “how”. The rules of what data to log are configurable by table and column. The scope of detailed change auditing embraces all changes made by P2K users, eP users, SS users, candidates and external users (e.g. SQL*Plus).
Detailed change auditing was created to fulfill the need to identify “who” has changed “what” data, “when” and “how”. The rules of what data to log are configurable by table and column. The scope of detailed change auditing embraces all changes made by P2K users, eP users, SS users, candidates and external users (e.g. SQL*Plus).
At line 10 changed one line
*To enforce tight audit controls, sessions that are initiated outside ePersonality and P2K that must update the database, will be forced to do the following:
*To enforce tight audit controls, sessions that are initiated outside teh application interfaces that must update the database, will be forced to do the following:
At line 18 changed one line
*All database changes made inside and outside the ePersonality and P2K applications must be monitored
*All database changes made inside and outside the application must be monitored
At line 21 changed one line
*In ePersonality, all of the change logging is done via Java code in the middle tier
*In [{$applicationname}], all of the change logging is done via Java code in the middle tier
At line 24 changed 2 lines
*ePersonality sessions are fully tracked and more extensively audited than in the past
*P2K sessions will be tracked and audited the same as in the past with enhancements to say that they are from reports or forms, etc.
*[{$applicationname}] sessions are fully tracked and more extensively audited than in the past
*In previous versions of the application sessions will be tracked and audited the same as in the past with enhancements to say that they are from reports or forms, etc.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by JMyersTop