SAM Log Audit Facility
The Business Challenge
What rights have been allocated to particular users, and when? At a given period X, which
user has certain access rights? When a user changes to a different activity, are all changes to
their access rights fully implemented? Are all access rights promptly removed when an employee
leaves the company? You must be able to respond to these and other questions to comply with legal
standards such as Sarbanes-Oxley, Basel II or ISO 17799.
Our Solution
The solution to this problem, the SAM Jupiter log audit facility, is in fact a functional
expansion of the tried-and-tested
Beta 92 Enterprise
log management system. It allows SAM Jupiter transaction logs to be transferred into Beta 92
Enterprise. The SAM Jupiter logs are then archived in Beta 92 Enterprise, where searches and checks
can be run on them according to a range of criteria. Various archive pools can also be defined as
part of this process, e.g. pools with five-year and ten-year run times.
Beta 92 Enterprise provides a user-friendly ISPF interface for evaluating the SAM Jupiter transaction logs. The interface makes it easy for you to determine report criteria.
Reports can be configured according to need, and show data from the SAM Jupiter transaction logs in accordance with the following criteria:
- Time frame for the executed administration
- Administrator name
- Business object name: master data, authorisations, roles
- Actions undertaken: Insert, change, delete
- Affected user
Two additional criteria can be defined for a full-text search.









