Visual Guard for .NET Key Features
Visual Guard for .NET
   
 
     
 
 
Key Features

Flash Demos

Try Visual Guard
 
 
 
 
How does it work?
 
 
What's in Visual Guard?
Integrating Visual Guard for .NET
What happens at runtime?
 

What's in Visual Guard?

Visual Guard Repository

The repository stores user accounts, passwords, roles and permissions. It can centralize the permissions of all .NET applications (Winform, Webform, Web services), as well as all user accounts, in a single and secured place.

Note: You can let Visual Guard .Net create and manage its own user accounts or you can re-use existing accounts created in Active Directory or in your Database.

Visual Guard .NET supports the following types of storage:

VG supports SQL Server and Oracle for users, permissions and roles storage
VG provides proprietary encrypted files for users, permissions and roles storage

If you choose to re-use Windows Accounts for Single Sign-On & authentication purposes, credentials are stored in Active Directory

You do not need to change your application database when integrating Visual Guard .NET. Visual Guard provides a wizard to create its own repository. You can choose between creating the corresponding Visual Guard .Net tables in your application database or in an independent database.


Visual Guard runtime

Visual Guard runtime:

Is composed of .NET assemblies
Is integrated and deployed with your application
Communicates with the repository to verify user identity and retrieve its permissions
Dynamically adjusts your application to the user permissions


Integrating Visual Guard for .NET

Integration is fast and easy:

  1. Add Visual Guard runtime to your project and activate Visual Guard security services (just a few lines of code required).
  2. Implement Visual Guard login form (or use your own login form).
  3. Create a security repository and declare your project in this repository.
  4. Compile and deploy the application.
  5. Define, for each application, the related permissions with Visual Guard Console. The initial permission list is usually defined by the development team before the application goes to production. But permissions can be created and modified any time, even after deployment. They are immediately effective for the application.
  6. Manage user accounts, granting them roles and permissions (usually done by administrators though of course can also be done by the development team).
For more information about the integration process, click here...
Would you like to try Visual Guard with your own application? click here...


What happens at runtime?

The end-user provides its credentials (unless a Single Sign-On process is activated)
Visual Guard verifies the user identity
Visual Guard connects to the security repository and retrieves the user permissions.
Visual Guard runtime adjusts the project according to these permissions.

Example: When a form opens, Visual Guard may hide controls and filter a list (same features supported for ASP.NET, winform and webservices).

For more information, see the Visual Guard Getting Started Guide



Previous: Visual Guard Security Tools Next: Technical Specifications

Take the tour...
Try Visual Guard now!

 
 
 
Key Features
 

What is Visual Guard?

Authentication
Verifying the identity of the user

Permissions
What a user can do in an application?

Auditing and Reporting
Visual Guard ready-to-use auditing and reporting features

Visual Guard Security Tools
Developer, Administrator and Auditor Tools

How does it work?

Technical Specifications

Visual Guard detailed features in pdf

 
 
 
Request a trial version
  Request a trial version of Visual Guard!  
more info
 
Ressources
  See a demo for .NET
Getting started
Visual Guard Architecture
How to... (Flash movies):
  Integrate VG into Winform apps
  Integrate VG into ASP.NET 2.0 apps
  Manage user roles and memberships
Visual Guard Support Website
Visual Guard Technical Documentation
Visual Guard Update List