Application Level

With the RYO SUITE Application’s role based security has been implemented to control who is allowed to browse, delete or update which information stored at the application. This is a significant improvement, making the RYO SUITE Applications more scalable, flexible, and easier to implement for larger corporations.

The RYO SUITE Applications operate based on a state of the art security management which utilizes the concepts of roles, similar to the implementation of security in many current computer operating systems.

Role based security (also called role based access control) is built on the premise that users are authenticated, which is the process of identifying the user. Once identified, roles and permissions are assigned. It specifies and enforces enterprise-specific security policies in a way that maps naturally to an organization's structure. It has become the predominant model for advanced access control because it reduces the complexity and cost of security administration.

While role-based security may be overkill in trivial settings (e.g. small enterprises with a couple of users who are all allowed to browse, delete or update all data) it is an extremely powerful tool to get a handle on complex environments. That includes typical company settings where various sales teams or customer service teams need to browse, delete or update customer related data while at the same time permissions on such data may vary depending on the function or task of an employee within the company. This concept is especially SUITEd for companies:

• Who would like to have a larger number of people to work with the RYO SUITE Applications simultaneously,
• Who would like to have restricted browse, delete or update capabilities for individual users, and
• Who would like to have an hierarchical privilege order implemented.

Although role based security does not promote any one protection policy, it has been shown to support several well-known security principles and policies that are important to commercial and government enterprises that process unclassified but sensitive information. These policies can be enforced at the time profiles are authorized for a role, at the time users are authorized as members of a role, at the time of role activation (e.g., when a role is established as part of a user's active session), or when a user attempts to perform an operation on data.