BR102015028194A2 - secure georeferenced application development method and system using dynamic, non-intrusive metainformation-based access control - Google Patents

Abstract

Abstract Method and system for developing secure georeferenced applications using nonintrusive dynamic access control based on metadata. new method and system for developing secure georeferenced applications using dynamic, non-intrusive metadata-based access control that applies to the field of information technology, more specifically software engineering in the management of data communication networks. and regarding the development of secure georeferenced applications. The method and system proposed here aims to provide a reliable method for the development of secure network management software geoapplications, with all the necessary security control for this type of system, offering greater technological security and agility in the development of geoapplications focused for mission-critical environments by providing a new solution or module of an existing solution to facilitate future integration and expansion of geoapplications generated through a computational system that implements the metamodel-based access control self-configuration method without the need for component recoding, providing a set of implementation elements, hardware / software requirements and quality requirements that enable the construction of these components, standardizing the form of access control in geoapplications at its various levels such as menu, base of given away s, objects, operations, attributes, attribute value, and spatial value to provide a set of components that can be used, such as the administration interface, auto-configuration component, and application programming interface (API) for integration and auditing. geoapplications. ?? ?? ?? ?? 1/1

Description

METHOD AND SYSTEM FOR DEVELOPING SAFE GEORREFERRED APPLICATIONS USING DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL BASED ON METAINFORMATION.

[001] This report describes the detailed description accompanied by illustrative figures of a new secure georeferenced application development method and system using dynamic, non-intrusive metadata-based access control that applies to the field of Information Technology. Information, specifically Software Engineering in the management of data communication networks and in the development of secure georeferenced applications. The method and system proposed here aims to provide a reliable method for the development of secure network management software geoapplications, with all the necessary security control for this type of system, offering greater technological security and agility in the development of geoapplications focused for mission-critical environments by providing a new solution or module of an existing solution to facilitate future integration and expansion of geoapplications generated through a computational system that implements the metamodel-based access control self-configuration method without the need for component recoding, providing a set of implementation elements, hardware / software requirements and quality requirements that enable the construction of these components, standardizing the form of access control in geoapplications at its various levels such as menu, base of given away s, objects, operations, attributes, attribute value, and spatial value, to provide a set of components that can be used, such as the administration interface, self-configuration component, and application programming interface (API) for integration and auditing. geoapplications.

The method and system for developing secure georeferenced applications using dynamic and non-intrusive metainformation-based access control, object of the present patent, is a system and its method of operation essentially composed of components for the management of permissions via metamodel and integration API, is a method for creating a new solution and / or module that comprises the steps of defining a new module, defining the existing module metamodel, and defining the packaging of the solution. This system comprises a set of components for use in geospatial solutions that can be reused to play the role of access control and auditing, providing a visual administration interface with a self-configuring component, an API (Application Programming). Programming interface) and an access control layer at the application server input layer. State of the Art [003] With the great technological evolution that has occurred in the last decades, more and more solutions in the area of Information Technology need to adapt more quickly and easily to the changes and the new reality that presents itself. As a result, an increasing number of users have been installing and accessing communication networks.

[004] Access control for all these new users and systems is a constant challenge because security is very sensitive to change. This problem is potentiated in the spatial context, because in addition to traditional control, a user may have to be controlled by their area of operation and even their geographical position at the time of data update.

[005] This is a recurring problem because in today's world it is inconceivable to build an application without worrying about the security context. In addition, security modules and / or components take time to mature and should not have their code constantly changed so as not to introduce new faults.

[006] Therefore componentization and reuse are fundamental for this subject and with this come up with a flexible and well tested component so that it can be used in new applications.

[007] In this context some patent documents and published works describing aspects of access control can be found, however none of these documents take into account geographical aspects as described in this patent. These include: [008] Patent Document CN101257377 B, DYNAMIC ACCESS CONTROL METHOD BASED ON COMMUNITY AUTHORIZATION SERVICE, which describes a community-based dynamic access control method based on community enablement services where users register their information to virtual organizations and consequently gain a role based on user registration information. However, the spatial context is not addressed in these communities, as the focus is on the computational grid;

Patent Document CN 103605916 A, ROLE-BASED POLICIES ACCESS CONTROL (RBAC) ACCESSING CONTROL MODEL BASED ON ORGANIZATION, which describes a method that provides an access control function-based policies (RBAC) that access a control based on an organization. This document does not address the dynamism based on the geographic area where the work will be done and needs access control, nor how the developer can build an application without the direct involvement of the access control component;

[010] US Patent Document 2008/0016546 A1, DYNAMIC PROFILE ACCESS CONTROL, which describes a dynamic method based on hierarchy organization. Here dynamically formed user groups are treated as the subject in a common access control component and are used to grant permission to or revoke permission for individual or groups of elements. As in the previous document this document does not deal with the dynamism based on the geographical area where the work will be done and needs access control, nor with the way the developer can build an application without the direct involvement with the component. access control;

[011] The Academic Article (2011) (Felipe Leão, Sergio Puntar, Leonardo Guerreiro Azevedo, Fernanda Baião, Claudia Cappelli) Data Access Control in Information Systems through Identity Propagation Mechanisms and Authorization Rules Execution in http : //www.researchgate.net/publication/266876142_Data_Access_Control_in_System_Information_Tracks_ID_Propagation_Mechanisms_and_Execution_of_AuthorizationRules, which introduces the importance of a task's development control to the scheduling mechanism, and the importance of scheduling a mechanism;

[012] Academic paper (2004) (Eduardo Martins Guerra, Rodrigo Cunha de Paiva, Clovis Torres Fernandes) Role-Based Access Control (RBAC) contexts with role-based access control model for web systems used by multiple divisions of an organization at ftp://linorg.cirp.usp.br/pub1/SSI/SSI2004/Poster/P04_ssi04.pdf, which presents the importance of corporate access control, where we extend the concept to the development allowing the creation of new modules (context) in the same enterprise solution.

[013] In general, publications in the areas of access control do not specify how to handle spatial concepts in the context of access control and do not have a systematic way that anyone who builds an application does not have to be programming access control. access.

[014] The advantages of an approach such as the one proposed in this patent is that it can have semi-ready, code-tested designs to be widely reused in new geographic applications with standard programming and without having to report new objects.

[015] To achieve this goal, various techniques can be used as introspective programs using metadata / metaprograms, dynamic behavior change (code) through behavioral reflection, and data structure through structural reflection associated with spatial data standards.

Description of the Figures [016] The following is a reference to the Figures accompanying this descriptive report for a better understanding and illustration thereof: Figure 1 is a flow chart illustrating the standard flow of a Method application and development system. of secure georeferenced applications using nonintrusive dynamic access control based on metainformation, object of the present patent.

Figure 2 illustrates the access control component modeling of the secure georeferenced method and application development system using dynamic, non-intrusive metainformation-based access control, object of the present patent, highlighting the Involved Standards: Composite, CallBack; State, Observe; Abstract Factory, and the Menus Figure 3 illustrates the logical model of the necessary infrastructure of the Method and system of development of secure georeferenced applications using dynamic and non-intrusive metainformation-based access control, object of the present patent, highlighting the Conceptual Model. , which acts on non-Java programs: C / C ++, VB, etc .; and Java that enables a JAAS-compliant Administration Profile

Figure 4 illustrates the interaction model between a new application and the access control components of the Method and secure georeferenced application development system using dynamic and non-intrusive metainformation-based access control, object of the present invention.

Figure 5 illustrates the layers of an example application of the secure georeferenced application development method and system using dynamic, non-intrusive metainformation-based access control object of the present invention. Highlighting the application access control mechanism, which acts in the pre-presentation layers, Identifies and authenticates users, authorizes user actions within applications, and filters unauthorized interface items. Figure 6 illustrates the Method and system execution model. of secure georeferenced application development using dynamic and non - intrusive metainformation - based access control, object of the present patent.

Description of the Invention The following describes a non-restrictive preferred embodiment of the present method and system, object of this patent, where the configuration, manner of implementation and application may vary in the form appropriate for each desired model and application situation. ; describing one of the constructive and functional possibilities that lead to the realization of the object described and the way in which it is used.

[018] METHOD AND SYSTEM FOR DEVELOPING SAFE GEOREFERRED APPLICATIONS WITH THE USE OF DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL, PURPOSE OF THE PRESENT PATENT, provides for the creation of secure solutions by creating or adding new modules.

[019] The proposed method meets the wide range of requirements for safe geoapplications and implements the concept of incremental evolution. The combination of these two factors provides new technical effects, ie a number of benefits over existing solutions.

[020] To meet these characteristics, the solution must be flexible and follow international standards. In addition to having a visual administration interface, it must have a set of Application Programming Interface (APIs) for development.

[021] Java SDK language, as of version 1.4 - Provides a standard authentication and authorization service called Java Authentication and Authorization Service (JAAS). From this standard, an authorization, that is, permission checking API was developed, which works basically on the same principles as JAAS, but offers a simpler interface for the programmer while allowing for greater flexibility.

[022] This API is also intended to provide a simple implementation of the role-based access control (RBAC) model. This API provides a more generic implementation because it also allows discrete access control Discretionary Access Control (DAC).

[023] The default JAAS authorization mechanism works basically in two steps: [024] In the first step the user is authenticated using configurable modules that follow a standard interface (LoginModules). If authentication is successful, an object representing the authenticated user is returned to the class that requested authentication. This object is a subject, containing a set of principals associated with it at the end of the authentication process.

[025] In the second step during the verification of a permission, via the doAsPrivileged method of the subject class, the current user's principals are associated with the current thread of execution. The SecurityManager asks the Policy class what permissions are associated with those principals and checks the permission using the implies method of the PermissionCollection ”(collection / whitelist) returned by the“ Policy ”class.

[026] To perform these steps, some parameters or actions must be defined, such as: user identity, profiles, user association with profiles, groups, user association with groups, authorizations, associations, association of authorizations, and changing and customizing profiles. Described below: [027] User Identities [028] The “principals” used during the authorization process are identities that distinguish the authenticated user from other system users. Their meaning depends on the authentication mechanism used and the context in which the user was authenticated. These can be session numbers, access codes, tickets, etc. In the case of the API specified above, the "principals" associated with users are four: UserRegistrationPrincipal, UserGroupPrincipal, UserRolePrincipal, and RealmPrincipal, as follows: [029] The UserRegistrationPrincipal contains the user login. Only one such principal is associated.

[030] The UserGroupPrincipal is a group where each principal of this type contains the code of a group that is associated with the user.

[031] The UserRolePrincipal, and the relationship where each principal of this type contains the code of a role (or profile) that is associated with the user. Each user can have only one role per module.

[032] RealmPrincipal contains information regarding the context in which the user was authenticated (for example, host and bank). This principal is used by access control to determine where permissions should be loaded from.

[033] The association of principals that identify the groups and roles the user is associated with is intended to allow access control to determine which permissions the user has. These permissions may have been directly assigned to him or may be set by the profile he has or the groups he is associated with.

[034] Profiles [035] Profiles represent feature sets belonging to a single system module. Users who are associated with a profile have access to all the features that their profile allows to use.

[036] Each profile is equivalent to a different type of role, or role, that can be performed by users of a module. Thus, there may be one or more profiles available for the same module. For example, there may be multiple administrator profiles, each representing a different set of administration module functionality.

[037] On the other hand, each user can only be associated with a single profile per module, as each user is supposed to perform only one role when using each module. Thus, users who use more than one module should be associated with the profiles corresponding to the roles they perform in each of their modules. To facilitate management and prevent the same user from accumulating different roles in the same module, profiles are divided into categories. Each category corresponds to a particular system module and no user can be associated with more than one profile belonging to the same category.

[038] Associating users with profiles [039] Associating profiles with users can be done in two ways: by adding the desired profile to the user profile list or by adding the desired user to the profile user list.

[040] As explained earlier, it is not possible to associate more than one profile of the same category with a single user. Also, for security reasons, an administrator is not allowed to associate with a profile or unlink from a profile that has been associated with another administrator or the system root.

[041] Groups [042] A group represents a set of system users. These users may have different roles, but are allowed to perform the same functionality within one or more system modules.

[043] The most general character group is "All Users." When a new user is registered, they are automatically associated with that group. This allows authorizing certain system functionality to all users without having to authorize it. individually, which would be very costly.

[044] By creating user groups, it is also possible for certain features to be authorized for a particular set of users. Likewise, group members are quickly assigned permissions, as there is no need to individually authorize each user.

[045] Associating users with groups [046] Associating groups with users, or users with groups, is similar to profile association, and can also be done in two ways. The first way is by adding the desired group to the user's group list, and the second way by adding the desired group to the group's member list: [047] Unlike profiles, there are no restrictions on the number or type of groups a Ordinary user may belong as groups do not correspond to specific roles within a system. However, for security reasons, it is also not possible for an administrator to join a group or to disassociate from a profile that has been joined by another administrator or the system root.

[048] Authorizations [049] You can configure the features to which users, profiles, or groups have access by assigning permissions or prohibitions to them. Permissions can be understood as authorizations granted to perform operations on system objects or resources. Similarly, bans are denied authorizations to carry out operations.

[050] There may be different types of authorizations in a system, such as authorizations to use modules, authorizations to open databases, authorizations to network objects, or authorizations to open application menus. Thus, each authorization type controls access to a specific type of system resource.

[051] Likewise, operations such as opening, inserting, removing, and changing depend on the type of resource being considered. For example, you can open a bank, enter and remove a user, or change data from a register.

[052] Assigning authorizations to profiles, user groups, or individuals has different purposes in a system. Profile authorizations act as templates for access control for different types of users. When you assign an authorization to a profile, all users associated with that profile automatically receive this authorization. However, there are situations where you want a specific set of people, regardless of their profiles, to have certain authorizations. In such cases, you must create a group that represents this specific set of people to assign authorizations to this group. Group permissions are also useful for giving a restricted group of users with the same profile access to a system resource. For example, you can specify that only a small group of administrators or operators have access to a bank containing sensitive information. You can also divide users with the same profile into groups that manage data obtained from specific regions (in this case, from a Geographic Information System (GIS)). Finally, you may need to specify individual authorizations when you want to control access to highly restricted resources or when you want to customize the profile for a specific user.

[053] Since authorizations for profiles, groups, and users exist, a priority order has been set for these authorizations to avoid inconsistencies or conflicts. Specific authorizations have higher priority than non-specific authorizations. This means that authorizations granted or denied to a specific user have priority over those assigned to the groups to which they belong, which in turn have priority over the authorizations assigned to the profiles with which they are associated. This priority queue allows you to customize profiles for a particular user group or, as mentioned earlier, to customize profiles for a specific user.

[054] In addition to the definition of priority over the specificity of authorizations, there is also the priority relationship regarding the type of authorization (whether it is a ban or a permit). Prohibitions are defined as having priority over permissions, which means that if for some reason authorization to access a system resource is granted and at the same time denied to a user, it is considered to be denied.

[055] Generally, in a large system, such as a Geographic Information System (GIS), the number of object types that must be controlled is very large. It is therefore impracticable to authorize each one individually. In such cases, it is more appropriate to allow unrestricted access to all resources and then to prohibit access to resources and / or operations that should be restricted to certain users. In this case, the higher priority of permissions bans is very useful because it allows you to grant permission to perform all operations on a given resource and then prohibit operations that are restricted to the profile, group, or user in question.

[056] A simple example of using bans is building or enabling application menus. Application users often have unrestricted access to most menus, but some menus should be disabled because they offer access to sensitive or very system-specific functionality. In these situations, the most appropriate solution is to allow access to all menus and then prohibit those not allowed for each of the user profiles using the application.

[057] Authorization Association [058] There is a chain of trust between system administrators, starting with root, as administrator users can only authorize / disallow features or resources that they themselves have been authorized by root. This prevents administrator users from intentionally "gaining" more privileges than those previously determined by their profiles, while allowing root to delegate certain administration tasks to other administrators in a more controlled manner.

[059] Assignment or association of authorizations to profiles can be done through the related Profile Permissions object. Similarly, this is done for groups through the related Group Permissions and for users through the related User Permissions. The operation of these three objects, explained below, is the same. As an example, to assign permissions to a profile, proceed as follows: [060] - Under User / Profile Management, select the desired profile and open the related Profile Permissions.

[061] - In the Permission field, choose the type of permission you want to grant or deny. Each permission type corresponds to a different type of resource, such as modules, banks, menus, etc.

[062] - Select the desired operation in the Operation field. In the help of this field only the operations that can be applied on the type of resource in question will be presented.

[063] - Then, in the Object field, choose the resource that should be controlled through this authorization. For example, if the permission type previously chosen was Menu Permission, in the help of this field you should be presented with a list of application menus that may be allowed or prohibited.

[064] - Finally, choose the action to perform: authorize or prohibit.

[065] In relevant cases, a special operation called "All Operations" may be chosen in the Operation field. It is equivalent to all other operations. This allows all others to be automatically authorized. do not allow this feature because they have only one operation, and for some resource types a special object called "All Objects" may be chosen. By authorizing it, the administrator automatically authorizes all objects of the same type that currently exist or may exist in the future.

[066] To assign permissions or prohibitions to groups and users, the same procedure is done, but it is important to note that the related User Permissions only has the permissions and prohibitions directly assigned to the user. Thus, the specific permissions of a user presented in this related object do not depend on groups or profiles to which that user may be associated.

[067] Changing and Customizing Profiles [068] Changing profiles can be done simply by associating or disassociating permissions or prohibitions with the profile, through the related Profile Permissions, as explained above. Changing a profile affects all users associated with it.

[069] Customizing a profile, by contrast, only affects a user group or a specific user. It can be done by authorizing features that were previously unauthorized by the profile or, similarly, by disabling features that were previously unauthorized by the profile.

[070] Customization example: Imagine a profile for a dummy module containing, among others, the following authorizations (permissions and prohibitions) used in the application menu load: Permission Operation Object Action Menu permission Open Deployment Prohibit Menu permission Open Installation Master File Authorize Menu Permission Open Pickup File Prohibit Menu Permission Open Updates Authorize [071] You want to customize this profile for a specific user so that only he or she can also make the checkout register. To do so, the following authorization must be granted to the user through the related User Permissions: Permission Operation Object Action Menu permission Open Withdrawal Registration Authorize [072] This permission will override the prohibition specified by the profile, but will only affect the user in question. question. The same idea of customization can be applied to user groups, remembering that the highest priority is that of the user, then that of groups, and finally that of profile.

[073] All of this infrastructure is designed to be automatically assembled from information retrieved from the metamodel.

[074] Preferred Embodiment of the Invention [075] The method and system for developing secure georeferenced applications using dynamic, non-intrusive metainformation-based access control object of the present invention is a computer system specifically developed for its application called "Secure Georeferenced Software Application Development System", which implements the system and method of this invention.

[076] This system provides a set of features and a secure environment for software applications for managing a Telecommunication Plant.

[077] Following are the key security features of the method proposed here, where the security environment used was created as described.

[078] The following feature examples have been provided according to the generic security aspects according to the method of this invention, namely: [079] Geoplication Security [080] -AccessManager: Access Control Implemented Using Standards such as: ISO 15408 Standard, National Institute of Standards and Technology (NIST) Role-Based Access Control (RBAC), and Java Authentication and Authorization Service (JAAS API). Layer made available on the application server.

[081] -MetaServer: Provides meta information for other features such as security.

[082] -MetaWizard: Provides modeling of meta information.

[083] -DeployWizard: Facilitates the installation and configuration of geoapplications.

[084] -WebAdm: Specific flexible security element that follows international security standards. In addition to administration tools, it has a set of APIs for development.

[085] - Generic Module: Specific element to create a module that will meet the safety specifications. It has the function of validating the opening of the module, validating the menus that will be presented as providing an attribute manager that assembles the screen dynamically respecting the configured access control.

[086] Accordingly, the secure GEORREFERENCED APPLICATION METHOD AND DEVELOPMENT SYSTEM WITH THE USE OF DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL, object of this patent, which describes a method of managing users and a security system as described above presents a unique new configuration that gives you great advantages over the known and currently used methods. These advantages include: providing greater security and agility in the development of secure network management software geoapplications; the fact that he had taken into account the space part; the fact that it is not intrusive; the fact that it has development in incremental evolution.

[087] Therefore, due to the configuration and operation characteristics described above, it can be clearly noted that the safe and non-intrusive geo-referenced GEORFERENTIAL APPLICATION DEVELOPMENT METHOD AND DEVELOPMENT METHOD is new device for the State of the Art which has the conditions of innovation, inventive activity and unprecedented industrialization, which earn it the Privilege of Invention Patent.

Claims (4)

1 - METHOD AND SYSTEM FOR DEVELOPING SAFE GEORREFERRED APPLICATIONS WITH THE USE OF DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL, BASED ON A SYSTEM AND ITS OPERATION METHOD THAT IS COMPLETELY composed of a set of components for the management of permits. metamodel and API integration interface, with geospatial solutions, which comprises the steps of: Definition of a new metamodel solution / module of the existing module; Definition of a new metadata; and Solution packaging with the inclusion of basic security components that can read metadata and dynamically mount the administration environment; providing a visual administration interface with a self-configuring component, a set of programming application programming interface (APIs), and an access control layer on the application server input layer. 2 - METHOD AND SYSTEM FOR DEVELOPING SAFE GEOREFERRED APPLICATIONS WITH USE OF DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL, according to claim 1, characterized in that the set of components have the adoption of technological concepts with dynamic screen for the control of attributes and execution of operations depending on access control including restrictions by geographic regions; and have the functionality of controlling module openness, validating menu visibility, and storing everything in and out of the application. 3. METHOD AND SYSTEM FOR DEVELOPING SAFE GEORREFERRED APPLICATIONS WITH THE USE OF DYNAMIC AND NON-INTRUSIVE ACCESS CONTROL, according to claim 1, characterized in that the authorization API operates basically on the same principles and uses the Java SDK language, Java Authentication and Authorization Service (JAAS). Method - System and system for developing secure geo-referenced applications using non-intrusive, non-intrusive access control according to claim 1, characterized in that systems constructed with the method comprise: automatic adaptation of the access management tool adding new functionality, permitting spatial management, auditing object operations, and creating a corporate security database.