| View500 - FAQ - XML Applications | |||
|
In View500 Identity Hub today we have the ability to store both business roles and XACML Security policies and privileges and using our webDUA based Security Policy & Certificate Administration tool we can search, create, delete, update & edit XACML security policies as well as searching for specific X.509 Digital certificates based on criteria such as date of expiry. This allows View500 to be used to provide the basis for a well-designed infrastructure for privileges management for administering large user populations and controlling access to resources. The need to effectively and securely manage access rights in large organizations, together with a growing number of regulations that demand consistency and enforcement of clear policies, have driven IT administrators to increasingly migrate to role-based security management models. Role-based Access Control (RBAC) is considered the most effective and secure privileges management philosophy. A good RBAC implementation groups privileges around "business roles", e.g., corresponding to organizational structure, job functions, business processes, etc. As such, most modern enterprise software support and encourage RBAC. Also unlike most other vendors solutions which require separate Policy Administration Point (POP) and Policy Information Point (PIP) stores, View500 with its ability to store XML files natively and through Component matching to retrieve them can act as both a combined PIP, PAP and LDAP Directory on a single highly efficient authorization server basis. View500 can support multiple XACML policies all within a single attribute or by using separate attributes within a single entry, or by placing them in many entries. How does View500 support XML? The operational attributes defined for View500 (v6.0-XED) allow XML Schema to be imported into the directory. Once the directory is aware of an XML Schema, the schema definition can be used as the syntax of new user attributes. This allows XML to be stored within the directory, whereby the directory has complete knowledge of the syntax of the XML, which allows it to complete proper XML validation. This provides the directory with the unique capability of being able to accept new syntax definitions from users. This is something that is not possible with current LDAP and X.500 directories. Since the directory has knowledge of the XML Schema, it can complete component matching queries on the XML values. This allows users to construct search operations that interrogate the inner contents of the XML values. This ability transforms a directory from uselessly storing XML BLOBs to intelligently storing and processing XML documents. | ||
|
|||