Logging: monitor actions of end
users and administrators
Why monitor actions of end users?
Keeping track of actions performed in an application allows :
- Improving the quality of service delivered by your company
- Ensuring the resources of the company are used properly
- 3. Giving evidence in case a fact needs to be proved
The kind of information which is worth logging depends on your
auditing and security requirements, in-house or legal (Sarbanes-Oxley
Act, CMMI, ISO, HIPAA…).
How to log events?
In a secured application: keep track of end users actions
Visual Guard .Net lets you free to choose the type of events to be
- Failed/successful connection attempt
- Modification of a field, etc…
Log entries contain some basic information by default (username
and role, date, action)
Visual Guard .Net lets you document the events logged to adapt it
to your security requirements:
Whether a field has been modified, and what modification has been
done (before/after value of a field).
In the VG console: Keep track of User Administrator actions
A set of sensitive events related to security daily management are
Which permission has been created, who has been granted a role,
modification of the password policy etc…