Visual Guard
is a flexible solution that complies with most architectures and technical
requirements.
Below are several examples of possible implementations:
VG Server Exposes Web Services to secure multiple technologies with the same system
Access Control Life Cycle
Development
Developers define permissions with the VG Win Console.
Permissions are stored in a development repository.
Developers deploy the permissions into production with a VG utility
Administration
Administrators manage Users and grant them permissions.
They update the production repository with the VG Web Console
Enforcement
VG Server exposes Web Services for User Authentication and Access Control.
Applications call VG Web Services to verify the user identity and check his access Privileges.
Each operation performed by the user is logged in the VG Repository.
Audit
Auditors use a specific application provided with VG.
They can control user attributes, roles and privileges across multiple systems. They can also review user operations.
Notes
Any windows or web application capable of SOAP calls or HTTP Requests is supported.
Applications do not need a direct access to the database.
Neither do the Administration Console or the Auditor Application.
Users, Administrators and Auditors can operate from any location with Internet Access
.NET applications with no direct access to the repository, communicating with the VG Server
Access Control Life Cycle
Development
Developers define permissions with the VG Win Console.
Permissions are stored in a development repository.
Developers deploy the permissions into production with a VG utility
Administration
Administrators manage Users and grant them permissions.
They update the production repository with the VG Web Console
Enforcement
End-users log in to the .NET application.
The VG runtime calls the VG Server to verify the user identity. The VG Server sends the user permissions back to the VG runtime The VG Runtime enforces user permissions by dynamically changing the application.
Audit
Auditors use a specific application provided with VG.
They can control user attributes, roles and privileges across multiple systems. They can also review user operations.
Notes
Applications do not need a direct access to the database.
Neither do the Administration Console or the Auditor Application.
Users, Administrators and Auditors can operate from any location with an Internet Access
.NET applications directly accessing the repository. The VG Server is not installed in this configuration.
Access Control Life Cycle
Developement
Developers define permissions with the VG Win Console.
Permissions are stored in a development repository.
Developers deploy the permissions into production with a VG utility
Administration
Administrators manage Users and grant them permissions.
They update the production repository with the VG Web Console
Enforcement
End-users log in to the .NET applications.
The VG Runtime queries the VG Repository to verify user identity.
The VG Runtime retrieves the user permissions and enforces security by dynamically changing the applications.
Audit
Auditors use a specific application provided with VG.
They can control user attributes, roles and privileges across multiple systems. They can also review user operations.
Notes
Applications need a direct access to the database.
Administration Console or the Auditor Application do NOT require such direct access.
Administrators and Auditors can operate from any location with Internet Access
A combination of Basic, Private and Public Mode in the same production environment
Access Control Life Cycle
Development
Developers define permissions with the VG Win Console.
Permissions are stored in a development repository.
Developers deploy the permissions into production with a VG utility
Administration
Administrators manage Users and grant them permissions.
They update the production repository with the VG Web Console.
Enforcement
Some .Net applications access directly the repository (for instance webforms and webservices)
Other .Net applications call the VG Server in private mode (for instance Winform applications running on remote sites)
Other technolgies call the VG Server in Public Mode (for instance Java, C++, PHP or PowerBuilder applications).
Audit
Auditors use a specific application provided with VG.
They can control user attributes, roles and privileges across multiple systems. They can also review user operations.
Notes
All the applications are secured by the same system, no matter the technology or the location of the user.
Administrators and Auditors can operate from any location with an Internet Access
Development 
Administration
Enforcement
Audit
