KR20190109619A - Permission management process and permission management apparatus - Google Patents

Abstract

The present invention relates to a method for managing authority of an IoT device in an IoT platform connecting IoT devices, to an apparatus thereof, and to a system thereof. Specifically, in order to manage the authority currently used by the IoT device in an Android-based IoT platform, information on the IoT device is collected. The authority used by the IoT device is analyzed from the collected information, and authority data including the analyzed authority is generated. By providing a technology to provide the generated authority data to a user device through a server, indiscriminate use of the authority can be handled.

Description

PERMISSION MANAGEMENT PROCESS AND PERMISSION MANAGEMENT APPARATUS}

The present invention relates to a method, apparatus, and system for managing rights of an IoT device in an IoT platform connecting Internet of Things devices. Specifically, the present invention relates to managing rights currently used by IoT devices in an Android-based IoT platform. The present invention relates to a technology that can cope with indiscriminate use of authority.

Android Things is an Android-based IoT platform, developed on top of the existing Android platform, and first unveiled as a developer preview on December 13, 2016. Unlike the IoT platform previously announced by Google, Android Thing has made users more accessible by using various technologies such as existing Android services and APIs, and can be easily used by users such as Doorbell and Bluetooth. We have provided sample code to make development easier.

AndroidThings has the same form as the existing Android platform, so Android Thing is likely to face the same security threats that traditional Android devices can.

For example, an Android smartphone asks the user for permissions the application uses when the application is installed. In the case of Android smartphones, if an installed application requires excessive permissions, the application can perform malicious behavior with a different function than its original purpose. If permissions are used excessively, permissions may be used differently than the Android platform aims to protect a device's resources through permissions. For example, an application that performs a Bluetooth function may perform other functions such as GPS and text transmission on an Android smartphone.

Android Sings devices may use the same permissions as the existing Android platform to require excessive permissions on the device, which may pose the same security threat as Android smartphones. In general, an IoT device may not have a display indicating the device's status, so an AndroidThings device may not be able to request a dialog box from the user, such as asking for permission. Since the user cannot request permission, the developer can automatically approve the permission. After being approved automatically, the IoT device can reboot and the declared permissions can be applied after the reboot.

In other words, unlike an Android smartphone, an AndroidThings device can automatically grant permissions from the system without asking the user for the permissions required by the application. In this case, security threats caused by permissions on Android smartphones can also occur on Android phones, and may be a bigger threat because they automatically allow permissions.

AndroidThings is used on the same platform as Android platform-based devices such as existing Android smartphones, so the same security threats that can occur on existing Androids may occur.

Android applications are easy to distribute due to re-packaging techniques. Repackaging is a technique that modifies and repackages some source code of an existing application. In general, an attacker inserts malicious code into a famous application and distributes it after repackaging. Due to the repackaging technique, many malicious applications are spread in the Android environment, and malicious applications installed on the user's device leak user's personal information or disable the user's device.

AndroidThings is similarly based on the Android platform, so repackaging poses the same security threats as Android smartphones. When a repackaged malicious application is installed on an Android Sings device, the device is declared with an authority that is not related to its original function, and may cause damages such as leakage of user's personal information and device malfunction.

The present invention is derived to solve the above problems, and proposes an invention that can manage the authority used by the IoT device to perform a specific function in the Android environment platform-based IoT environment.

In one aspect of the present invention for solving the above problems, a method for managing the authority of the IoT device, comprising: collecting information about the IoT device; Analyzing the authority used by the IoT device from the collected information; Generating authority data including the analyzed authority; And providing the generated authorization data to a user device through a server.

In the rights management method of one embodiment of the present invention, analyzing the rights includes: searching for a manifest file for the IoT device; And collecting a permission list declared in the manifest file.

In the rights management method of one embodiment of the present invention, the generating of the authority data may include identifying the authority and a function to be performed for each authority.

In the rights management method of one embodiment of the present invention, the method may further include generating the right data for a plurality of IoT devices and classifying the rights used for each IoT device.

In the rights management method of one embodiment of the present invention, the collecting of information on the IoT device may be performed when the IoT device is first installed or updated in an IoT platform, and the authorization data may be generated by the IoT device. It may further include at least one of a name and an updated date.

In another aspect of the invention, there is provided an apparatus for managing rights of an IoT device, comprising a memory and a processor, the processor collecting information about the IoT device; Analyze the authority used by the IoT device from the collected information; Generate authority data that includes the analyzed authority; An apparatus for managing rights, configured to provide the generated right data to a user device via a server.

In the rights management device according to another aspect of the present invention, the processor retrieves a manifest file for the IoT device in order to analyze the authority used by the IoT device from the collected information, and the manifest file It may be configured to collect a list of rights declared within.

In the rights management apparatus according to another aspect of the present invention, the processor may be configured to identify the authority and the function to be performed for each authority to generate the authority data.

In the rights management apparatus according to another aspect of the present invention, the processor may be further configured to classify the rights generated by the IoT data for each IoT device by generating the authorization data for a plurality of IoT devices.

In the rights management apparatus according to another aspect of the present invention, the processor collects information about the IoT device, may be performed when the IoT device is first installed or updated in the IoT platform, the authorization data is It may further include at least one of a name and an updated date of the IoT device.

By using the present invention, by managing and monitoring the permissions used by the AndroidThings platform-based IoT device, the user can check the current permissions of the current IoT device in real time, thereby preventing future security problems.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and, together with the general description given above and the detailed description given below, serve to explain the features of the invention.
1 is a schematic of a system for managing rights of an IoT device.
FIG. 2 is a block diagram of a method illustrating the steps performed by the rights management system of FIG. 1 for rights management.
3 is a result of authority analysis of an IoT device.
4 is a diagram illustrating a window for a user to access authorization data of each IoT device.
5 is a result of stored data representing a list of permissions of each IoT device.

Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts. References made to particular examples and implementations are for illustrative purposes and are not intended to limit the scope of the invention or the claims.

AndroidThings is an Android-based IoT-only operating system announced by Google. Unlike the IoT platform previously announced by Google, AndroidThings makes various developments such as existing Android services and APIs more accessible to users, and makes development easier by providing sample code that users can easily use. To support them. AndroidThings is a developer kit that supports NXP Pico, Intel Edision, and Raspberry Pi 3. AndroidThings has the same form as the existing Android platform. The AndroidManifest.xml file in the AndroidThings-based application can be configured in the same form as the AndroidManifest.xml file used in existing Android smartphones. For example, Android smartphones and AndroidThings may have information such as permissions, start activities, etc. to be used in the form of Table 1 below in the AndroidManifest.xml file.

<manifest package
<uses-permission android: name = "per_name"/>
<uses-permission android: name = "per_name"/>
<application android: label = "@ string / app_name
<action android: name = "Activity"/>
<category android: name = "Main"/>
<category android: name = "LAUNCHER"/>
<activity android: name = ". StartActivity">
</ application>
</ manifest>

As mentioned above, since AndroidThings is based on the Android platform, security threats due to repackaging may occur in the same way as Android smartphones. Particularly, in the present invention, in the Android platform IoT environment, which is based on the Android platform, when the user automatically accepts the permission without obtaining consent for the user's use of the permission due to the uniqueness of the IoT device, a malicious function such as data leakage due to a function not related to the original function In order to prevent a problem that an action may be performed, it may be characterized in that it manages the authority used by the currently connected AndroidThings-based IoT device. Therefore, the system proposed in the present invention can analyze the authority used by all devices currently connected to the server when the application based on the AndroidThings platform is installed or the application used by the device is modified. In addition, the analyzed permissions can be managed for each device to manage what permissions are being used for each Android Sing device so that the user's mobile can be checked. Analysis of the Android Sings device and management of information about the device can be done through a Linux server, and information about the device can be provided to the user in real time through the Apache Web server.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

1 is a diagram related to a rights management system 1 for managing rights of an IoT device in accordance with one embodiment of the present invention. IoT devices 2a-2n, in particular AndroidThings devices 2a-2n, are connected to the rights management system 1. Analysis and management of the AndroidThings devices 2a-2n can be performed by the rights management system 1, and the rights management system 1 is connected to the mobile device 3 to provide the managed data to the user. have.

Specifically, the authority used by the IoT device may be confirmed through a manifest file, for example, an AndroidManifest.xml file, which is inside the IoT device application, similarly to the Android application. Because IoT devices do not change the functionality they provide to users due to their hardware characteristics, even if the application is updated, the required authority does not change significantly. However, in order to perform malicious actions, rights not related to the rights provided by the IoT device may be required, so the rights management system 1 may also manage the rights information for the previous version in addition to the current version. In this context, the rights management system 1 can collect information about the IoT device when the IoT device is first installed or when there is a change to the application from the IoT device update server.

The rights management system (1) can search the AndroidManifest.xml file based on the information about the input application, and if the AndroidManifest.xml file is found, can collect information including the list of permissions used by the device from the file. . That is, the rights management system 1 may analyze the file after searching the AndroidManifest.xml file to collect information on the permission used by the corresponding IoT device. When the authority list collection is completed, the authority management system 1 may store the authority information together with the device information. The rights management system 1 can then update the information so that the user can check with the mobile device 3.

The process performed in the rights management system 1 refers to a block diagram of a method 200 that represents the steps performed for rights management shown in FIG. 2. The rights management system 1 may include a processor configured to perform the process shown in FIG. 2 and may include a memory capable of storing data processed by the processor.

First, the rights management system can collect application information to analyze the application when a new IoT device is installed or a patch for the IoT is performed in an Android-based IoT environment. The rights management system may receive an application file (S210).

For example, the input of the IoT device may be performed in the form of an Android application package (APK) file in the rights management system. Afterwards, the analysis of the corresponding IoT device may be performed through the information on the IoT device input here.

The rights management system may search for a rights management information file including rights management information (S220).

In general, IoT created based on the AndroidThings platform may have an AndroidManifest.xml file in the app folder under the root folder, but it may not always exist in the same path, so the rights management system searches for all paths within the application. You can retrieve the AndroidManifest.xml file by running. The system can create a program with pseudo code in the form of searching for a list of permissions after searching AndroidManifest.xml file existing inside the IoT application as shown in Table 2 below.

No. authority Authorization information One BLUETOOTH Bluetooth
communication access 2 CAMERA Camera devices access 3 INTERNET Application network access 4 READ_EXTERNAL_STORAGE External stroage access 5 RECORD_AUDIO Audioreceiveand
record access 8 … …

When the search for the file is finished, all AndroidManifest.xml files existing in the IoT device are searched, and the path to the searched AndroidManifest.xml file can be collected in an absolute path form for analysis. 3 is a result of the data collected after the path search is finished. The rights management system may analyze the retrieved rights management information file (S230).

In one embodiment, the rights management system may analyze the retrieved AndroidManifest.xml file to perform an analysis on the authority used by the IoT device. AndroidThings can be declared as <uses-permissionandroid: name = "permission name" /> just like an existing Android application. Therefore, the authorization management system can collect the relevant information when there is a declaration in the form of permission declaration among the existing items in the AndroidManifest.xml file. On the other hand, the AndroidThings platform-based application provides developers with sample applications such as Doorbell and Bluetooth for easy development.The sample code includes two AndroidManifest.xml files in the form of CompanionApp. In some cases, at the time of permission analysis, the system analyzes the AndroidManifest.xml file in all paths.

The rights management system may store the analyzed rights information (S240).

In one embodiment, when the analysis of the authority used by the IoT device is completed, the rights management system may store the authority information (authority data) for providing the information to the user. However, in general, when collecting the permissions used by the Android platform through analysis of the AndroidManifest.xml file, if the collected data is provided to the user as it is, the user may not be able to know what permissions the collected permission list performs. have. Thus, once authority collection is complete, the authority management system may perform processing of the data before providing the information to the user. In this case, the system may store the authority and the meaning of each authority in a table form, and then match the authority list collected from the IoT device to identify what function each authority has. To analyze the functions performed by each authority, the system can create a program through the pseudo code shown in Table 3 below.

Algorithm Search_Permission
get Permission list
while (Size (Permission list)):
if Permission == table (Permission)
Find permission information
end if
end while
return result_permission

The authorization management system may update the stored authorization information to the web server (S250). Specifically, when the processing of the collected data is completed, the authorization management system may use what authority to use to provide services to the user for each device. Can be organized and stored. For example, the rights management system may update the web server to provide information of the stored AndroidThings platform based IoT device to the user via the mobile device. Information about IoT devices may be provided through a web server of a Linux server, and information about IoT devices may be provided for a user to check for each device. A user can access a web server that manages and monitors IoT devices to check information about IoT devices connected to an IoT environment that is currently connected to the IoT. For example, as shown in FIG. 4, authority information may be accessed through a pre-registered ID and password. Saved data is stored in the result folder, which is the top-level folder, and a file including authority information can be created under each IoT device name under the result folder. When accessing the web server, only registered users can be accessed, so when the user connects to the server in real time, it is possible to check the information on each device such as authority and modification date existing in the IoT environment.

As an example, the form stored as the IoT device name under the result folder is as shown in FIG. 5, and the authority name and the function performed by the device are specified in each file. Users can access the server's result folder to access data stored on the server, and access the result folder to see a list of all Android Sing devices currently connected to the server. If you check the permission list that the device is using in the list of Android devices, it indicates the contents of "android.permission.permission_name" and the meaning of the permission.If the Android device connected to the server does not have the permission, it is being used. The phrase not authorized may be displayed.

In this way, the user can check the list of IoT devices provided by the server and the permission list used by each device, and can grasp the actions that can be performed through the corresponding permission. When the user grasps an action that can be performed through a permission, the user can check the permission that the IoT device uses unnecessarily as shown in Table 4 below. Based on this, the IoT device can be prevented from performing malicious actions such as personal information leakage and device control.

device authority Normal authority Indiscriminate authority D1 P1 √ P3 √ P7 √ D2 P2 √ P3 √ P4 √ D3 P2 √ P6 √ D4 P2 √ P5 √ P6 √ P7 √ D5 … … …

The descriptions and process flow diagrams of the method are provided merely as illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by those skilled in the art, the order of the steps in the foregoing embodiments may be performed in any order. Words such as "at this time", "thus", "next", etc., are not intended to limit the order of the steps, and these words are used to guide the reader through the description of the methods.

The various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality.

The hardware used to implement the various example logics, logic blocks, modules, and circuits described in connection with the aspects disclosed herein include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), It may be implemented or performed in a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In addition, in one or more illustrative aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope and principles and novel features disclosed herein consistent with the following claims.

1: rights management system
2a ~ 2n: IoT device
3: mobile device

Claims (10)

As a method for managing permissions of an IoT device,
Collecting information about the IoT device;
Analyzing the authority used by the IoT device from the collected information;
Generating authority data including the analyzed authority; And
Providing the generated authorization data to a user device via a server.
The method of claim 1,
Analyzing the authority,
Retrieving a manifest file for the IoT device; And
Collecting a list of rights declared in the manifest file.
The method according to claim 1 or 2,
Generating the authority data,
Identifying the authority and a function performed by the authority.
The method according to claim 1 or 2,
Generating the authorization data for a plurality of IoT devices, and further comprising the step of classifying the rights to use for each IoT device, rights management method.
The method according to claim 1 or 2,
Collecting information about the IoT device is performed when the IoT device is first installed or updated in the IoT platform,
The rights data further comprises at least one of a name and an updated date of the IoT device.
An apparatus for managing permissions of an IoT device,
Memory and processor,
The processor,
Collect information about the IoT device;
Analyze the authority used by the IoT device from the collected information;
Generate authority data that includes the analyzed authority;
And provide the generated authorization data to a user device via a server.
The method of claim 6,
For the processor to analyze the authority used by the IoT device from the collected information,
Retrieve a manifest file for the IoT device,
And collect a list of rights declared in the manifest file.
The method according to claim 6 or 7,
For the processor to generate the authorization data,
And identify the right and a function to be performed by each right.
The method according to claim 6 or 7,
The processor also,
And classifying the authority to generate the authority data for each of the IoT devices and to use each authority device.
The method according to claim 6 or 7,
Collecting information about the IoT device by the processor is performed when the IoT device is first installed or updated in an IoT platform,
The rights data further comprises at least one of a name and an updated date of the IoT device.

Images