• Visual Guard Professional for .NET
• Visual Guard Professional for PowerBuilder
• Visual Guard Enterprise Edition
• _________________________
• Visual Expert for PowerBuilder
• Visual Expert for Oracle
• Visual Expert for Sybase ASE
• Visual Expert for MS SQL Server
• _________________________
• Enable for PowerBuilder
• REX for PowerBuilder

• Try Visual Guard for .NET
• Try Visual Guard for PowerBuilder
• Try Visual Guard Enterprise Edition

• How to...
• Visual Guard Forum
• Visual Guard Update List
• Visual Guard Technical documentation
• Win Console Documentation
• Web Console Documentation
• VG Server Documentation

• Novalys News
• .Net Survey
• White Papers
• Articles

Visual Guard for PB  Key Features  Permissions

Visual Guard for PB   Key Benefits Key Features Authentication Permissions How Does it Work Permissions Examples See a Demo Try Visual Guard for PB Price Request		Permissions Managing permissions Why use dynamic permissions? Matching ever-changing security needs of an enterprise implies frequent modifications and recompilation of applications. Visual Guard enables you to: Define and store security rules out of the applications, and load security only at runtime Create high granularity permissions without changing the code of your application Unify the security of all PowerBuilder applications, whatever the version…           Managing permissions Why use dynamic permissions Advanced Managing permissions Keep security rules out of the code Why? Security rules are managed in a separate repository and are applied dynamically at runtime. No need to rebuild the application when permissions are modified. Permissions are defined without actually coding in the application Profiles, user account information, permissions are defined and managed in a dedicated repository. Visual Guard approach saves significant time and money In development phase In maintenance phase On a functional point of view, Visual Guard PowerBuilder respects the basic guidelines of role based access control: A user is added to a group A group is linked to a profile A profile contains functions (permissions) A function is composed of technical actions How to create permissions with Visual Guard Fine granularity Visual Guard permissions support a wide variety of components and object type: Non visual business objects are supported as well as objects which manage the access to the Database. Permissions without code: Modifying the properties of objects The VG Console lists all the objects of your application as well as their properties. A dedicated wizard enables changing the value of each property. This kind of permission can be defined for any .Net component, GUI or non GUI. Here is an example showing how to hide a control. You can add or modify this kind of permissions anytime. Applications are modified dynamically at run time.         Managing permissions Why use dynamic permissions Advanced Why use dynamic permissions By default, security rules are hard coded in the application. With this approach, managing the security means rebuild applications over and over, or delay the implementation of security rules, with potential security breaches. Maximize security level: Update security rules ANYTIME without waiting for the next build. Match any complex business requirements with fine grained permissions see permissions with conditions Cut maintenance cost Modify existing permissions in a few clicks demos Implement new permissions on demand, and keep applications aligned with business reality         Managing permissions Why use dynamic permissions Advanced Advanced Centralize Access control in a single tool By default, security rules are hard coded in the application. With this approach, managing the security means rebuild applications over and over, or delay the implementation of security rules, with potential security breaches. Unify access control and secure all your applications in one security system. Visual Guard integrates with any PowerBuilder application, from version 6 to 11.x. It also supports PB applications deployed in .Net, as well as native .Net and PB projects. Maximum or minimum Security? For security reasons, we strongly recommend to develop with maximum security: ”Close all doors” at development time and open them one by one with permissions. Rather than "Open all door" at development time and close them one by one with restrictions The reason is if you forget to close one door with a restriction, it may generate a security/confidentiality breach in the system: All users can go through that door. Whereas forgetting one permission is less critical: you just have to add the permission if/when a user request it. With Visual Guard dynamic permissions, you can add permissions anytime, even when the application is on production (dynamic permissions do not require any access or change in the code). Permissions with conditions VG permissions modify the properties of objects of your application. It allows hiding a button, disabling a menu, etc... This means the value of the property varies depending on the profile of a user. In some cases, the value of a property should vary depending on two different criteria: the profile AND an information from the application. Previous: Authentication Next: Auditing and Reporting Take the tour... Try Visual Guard now!       Index   What is Visual Guard? Authentication Permissions How does it work? Examples of Modifications Technical specifications       Active Directory   Re-use AD accounts for authentication   more information   Trial Version   Try Visual Guard! : - For PowerBuilder - For .NET