Electronic device and security setting method for electronic device
By integrating a security management system within portable electronic devices to set and adjust security levels based on environmental information, the challenges of inefficient security settings and rapid security threat changes are addressed, resulting in enhanced security and resource efficiency.
Patent Information
- Application Number
- PCT/KR2024/011921
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-30
- Filing Date
- 2024-08-09
- Publication Date
- 2025-04-10
AI Technical Summary
Existing security settings for portable electronic devices often rely on external servers, which can lead to inefficiencies and increased risks of personal information leakage, especially in dynamic mobile environments where security threats can change rapidly.
Implementing a security management system within the electronic device itself, allowing for the setting and adjustment of security levels for each service or application based on environmental information without the need for additional servers. This system identifies the lowest security level among applications and transmits it to them, enabling real-time adaptation of security policies.
This approach reduces the need for external servers, minimizes the risk of personal information leakage, and allows for flexible and real-time application of security policies in response to changing security threats, all while optimizing resource usage.
Smart Images

Figure KR2024011921_10042025_PF_FP_ABST
Abstract
Description
Electronic devices and how to set up security for them
[0001] Embodiments of this document relate to electronic devices and methods for setting security of electronic devices.
[0002] As portable electronic devices become more popular, their security is becoming increasingly important. In a mobile environment, application (app) installation and deletion are frequent, and the external environment can change frequently. Therefore, the environment for internal and external security threats to electronic devices can change in real time. To ensure the security of portable electronic devices, a service manager can directly configure security features for each service (or app). Alternatively, the service manager can receive security policies from a server (e.g., an admin server) and apply them to each service (or app).
[0003] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.
[0004] Various embodiments of this document are intended to dynamically set security functions based on security information of each service (or app) in an on-device environment without an additional server.
[0005] A method for setting security of an electronic device according to various embodiments of the present document may include allowing at least one application included in the electronic device to set a security level of a domain based on environment information. A security manager included in the electronic device may receive a security level of the domain from the at least one application. The security manager may identify a lowest security level among the received security levels of the domain. The security manager may transmit the identified lowest security level to the at least one application associated with the domain. The at least one application may change the security level of the domain based on the received lowest security level.
[0006] An electronic device according to various embodiments of the present document may include a memory for storing commands and at least one processor for executing the commands. The commands stored in the memory may be configured to cause the electronic device (101) to set a security level of a domain of at least one application included in the electronic device based on environment information. The commands stored in the memory may be configured to cause the electronic device (101) to transmit the security level of the domain from the at least one application to a security manager included in the electronic device. The commands stored in the memory may be configured to cause the electronic device (101) to identify a lowest security level among the security levels of the domain received from the security manager. The commands stored in the memory may be configured to cause the electronic device (101) to transmit the identified lowest security level to the at least one application associated with the domain. The commands stored in the memory may be configured to cause the electronic device (101) to change the security level of the domain in the at least one application based on the received lowest security level.
[0007] A non-transitory computer-readable storage medium having recorded thereon a program for performing a method for setting security of an electronic device according to various embodiments of the present document may include an operation in which at least one application included in the electronic device sets a security level of a domain based on environment information. A security manager included in the electronic device may include an operation in which the security level of the domain is received from the at least one application. The security manager may include an operation in which the lowest security level among the received security levels of the domain is identified. The security manager may include an operation in which the identified lowest security level is transmitted to the at least one application associated with the domain. The at least one application may include an operation in which the security level of the domain is changed based on the received lowest security level.
[0008] The various embodiments described in this document reduce redundant data collection from external environments, enabling efficient resource utilization. The various embodiments described in this document enable serverless security features, minimizing the risk of personal information leakage. Furthermore, the various embodiments described in this document can flexibly apply security policies in response to changing security threats in real time.
[0009] The effects of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.
[0010] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.
[0011] FIG. 2 is a block diagram illustrating the configuration of an electronic device according to various embodiments.
[0012] FIG. 3 is a block diagram illustrating the configuration of an electronic device according to functions according to various embodiments.
[0013] FIG. 4 is a diagram illustrating the structure of transmission and reception data according to various embodiments.
[0014] Figure 5 is a diagram illustrating examples of domain-specific classification according to various embodiments.
[0015] Figure 6a is a diagram illustrating security levels according to various embodiments.
[0016] Figure 6b is a diagram illustrating a security level by domain according to the surrounding environment according to various embodiments.
[0017] FIG. 7a is a flowchart illustrating the operation of a security manager according to various embodiments.
[0018] Figure 7b is a flowchart illustrating the operation of the app according to various embodiments.
[0019] FIG. 8 is a diagram illustrating a process of setting a security function in an electronic device connected to an external site according to various embodiments.
[0020] FIG. 9 is a diagram illustrating a process for setting security functions for multiple apps according to various embodiments.
[0021] FIG. 10 is a diagram illustrating a process of setting a security function in an electronic device connected to a public communication network according to various embodiments.
[0022] Figure 11 is a flowchart illustrating a security setting method according to various embodiments.
[0023] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In connection with the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and conciseness.
[0024] FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) according to various embodiments. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with an electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).
[0025] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or a secondary processor (123) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor)) that can operate independently or together therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a specified function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.
[0026] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.
[0027] The memory (130) can store various data used by at least one component (e.g., the processor (120) or the sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., the program (140)) and input data or output data for commands related thereto. The memory (130) can include a volatile memory (132) or a non-volatile memory (134). The non-volatile memory (134) can include at least one internal memory (136) and an external memory (138).
[0028] The program (140) may be stored as software in the memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).
[0029] The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).
[0030] The audio output module (155) can output audio signals to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.
[0031] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.
[0032] The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).
[0033] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.
[0034] The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). In one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.
[0035] The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).
[0036] A haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. In one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.
[0037] The camera module (180) can capture still images and videos. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.
[0038] The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least a part of a power management integrated circuit (PMIC).
[0039] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
[0040] The communication module (190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).
[0041] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (192) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC realization.
[0042] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), may be selected from the plurality of antennas by, for example, the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).
[0043] According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band.
[0044] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).
[0045] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In one embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.
[0046] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.
[0047] FIG. 2 is a block diagram illustrating the configuration of an electronic device according to various embodiments.
[0048] Referring to FIG. 2, the electronic device (101) may include a processor (120) and a memory (130).
[0049] The memory (130) (e.g., the memory (130) of FIG. 1) may store data and algorithms that perform functions of the electronic device (101) (e.g., the electronic device (101) of FIG. 1), and may store programs (e.g., applications) and commands that are run on the electronic device (101). The data, algorithms, programs, and / or commands stored in the memory (130) may be loaded into and executed by the processor (120) (e.g., the processor (120) of FIG. 1).
[0050] The processor (120) can control each component of the electronic device (101). The electronic device (101) can include one or more processors (120). The processor (120) can obtain environmental information. The environmental information can include information related to the surrounding environment of the electronic device (101) and / or information related to functions set in the electronic device (101). As an example, the environmental information can include authentication-related information, communication connection information, and / or location information of the electronic device (101).
[0051] The processor (120) can execute an application (app). The application executed in the processor (120) can set the security level of the domain based on environmental information under the control of the processor (120). The domain may be a security category that sets a security level classified according to the application function. For example, a Wi-Fi domain may be a security category that sets a security level for the Wi-Fi function. If the type of the Wi-Fi domain is WEB (wired equivalent privacy), it is a type that is vulnerable to security, so the security level of the Wi-Fi domain may be set to 1. Alternatively, if the type of Wi-Fi is WPA (Wi-Fi protected access)2, it is a more secure type, so the security level of the Wi-Fi domain may be set to 4. A higher security level value may indicate a more secure security state. The domain may be set to various levels according to the security strength, and the value indicating the security strength may be referred to as a security level.
[0052] The processor (120) can transmit the security level of a domain set in an application to a security manager. An application transmitting a security level to the security manager may include a transmission attribute. The processor (120) can execute one or more applications, and each application may include transmission (sender) and / or reception (receiver) attributes. For example, a first application may include a transmission attribute, a second application may include a reception attribute, and a third application may include transmission and reception attributes. Under the control of the processor (120), the first application and the third application including the transmission attribute can transmit the set security level to the security manager. Each application may include one or more domains, and may transmit a security level for each domain. As an example, a smart lock application may include a communication domain, a device domain, and a lock screen domain, and may transmit the security level of the communication domain, the security level of the device domain, and the security level of the lock screen domain to the security manager.
[0053] The security manager of the processor (120) can compare the security levels received for each domain. The security manager can identify one security level among the security level comparison results. The one security level identified by the security manager can be referred to as a decision level. For example, the security manager can identify the lowest security level among the security levels for each domain. In the above example, if the first to third applications include a communication domain, the security manager can receive a communication domain security level of 1 from the first application including a transmission attribute, and receive a communication domain security level of 3 from the third application including a transmission attribute. The security manager can compare the security levels of the received communication domains. The security manager can identify the communication domain security level of 1 received from the first application as the lowest security level, and determine the decision level of the communication domain as 1. Alternatively, the security manager can identify the highest security level among the security levels for each domain. In this case, the security manager can determine the decision level of the communication domain as 3.
[0054] Alternatively, the security manager may determine the security level with the largest number of security levels in the domain as the decision level, and may determine the security level of the most important domain as the decision level based on the importance of the domain.
[0055] The security manager can transmit the lowest identified security level (decision level) to the application. The security manager can identify an application that includes a domain associated with the identified security level and transmit the lowest security level to the identified application. In the example described above, the application to which the security manager transmits the security level may include a communication domain and an application whose attribute is set to the recipient. In other words, the security manager can transmit the security level of the communication domain of the first application to the second application and the third application.
[0056] An application that receives a security level from the security manager can change the security level of a domain based on the received security level. Furthermore, the application can execute a function corresponding to the changed security level. For example, a third application can change the security level of a communication domain set to 3 to 1. Furthermore, the third application can execute a function of the communication domain corresponding to the security level of 1. For example, if the security level of the third application is set to 3, the third application can allow connections to faster Wi-Fi networks in the vicinity regardless of security. However, if the security level is changed to 1, the third application can only allow connections to Wi-Fi networks with secured security.
[0057] Alternatively, the processor (120) may determine the security level of a domain based on the installation of a malicious application, an update of a malicious application, a change in application settings, and / or a change in environment information. For example, malicious applications may include malicious applications, applications not installed through an authorized store, applications included in a deny list, and / or applications not included in an allow list. Applications that operate in real time, such as anti-malware applications, may generate a trigger for determining a security level when a malicious application is installed and / or updated. Alternatively, the application may generate a trigger for determining a security level based on a change in settings and / or a change in environment information. The application may determine the security level based on the occurrence of a trigger. If the determined security level of the domain is different from the configured security level of the domain, the application may transmit the determined security level of the domain to the security manager. The security manager may identify the lowest security level based on the security levels of the domains determined and transmitted by the application.
[0058] FIG. 3 is a block diagram illustrating the configuration of an electronic device according to functions according to various embodiments. FIG. 4 is a diagram illustrating the structure of transmitted and received data according to various embodiments. FIG. 5 is a diagram illustrating an example of domain-specific classification according to various embodiments. FIG. 6a is a diagram illustrating security levels according to various embodiments. And, FIG. 6b is a diagram illustrating domain-specific security levels according to surrounding environments according to various embodiments. The following description will be made with reference to FIGS. 3 to 6b together.
[0059] Referring to FIG. 3, a security manager (121) loaded onto a processor (120) and a plurality of applications (122-1, 122-2, 122-3) are illustrated. The security manager (121) can control the security setting function of the domain. For example, the security manager (121) can be implemented as software and stored in the memory (130). The security manager (121) can be loaded onto the processor (120) under the control of the processor (120) and perform the security setting control function of the domain. The applications (122-1, 122-2, 122-3) can be received from an external device via a communication interface (e.g., the communication module (190) of FIG. 1) or an interface (e.g., the interface (177) of FIG. 1). The received applications (122-1, 122-2, 122-3) are stored in the memory (130) and can be loaded into the processor (120) and executed under the control of the processor (120).
[0060] For example, the security manager (121) may include a communication module (1211), an app verification module (1212), a domain management module (1213), and a security stage setting module (1214). Each module included in the security manager (121) may be a module implemented in software.
[0061] The communication module (1211) can receive the security level of the domain from the applications (122-1, 122-2, 122-3) or transmit the determined level (e.g., the lowest identified security level) to the applications (122-1, 122-2, 122-3). The communication module (1211) can receive the determined security level from the applications (122-1, 122-2, 122-3) including the transmission attribute for each domain. In addition, the communication module (1211) can transmit the determined level of the domain to an application that includes the same domain and is set as the receiver attribute. For example, if the first application and the third application are defined as the sender of the Wi-Fi domain, the communication module (1211) can receive the security level of the Wi-Fi domain from the first application and the third application. And, if the second application is defined as a receiver of the Wi-Fi domain, the communication module (1211) can transmit the decision level of the Wi-Fi domain to the second application.
[0062] Figure 4 illustrates an example of a data structure to be transmitted and received. For example, data transmitted by applications (122-1, 122-2, 122-3) to the communication module (1211) of the security manager (121) may include information on a domain, security level, and timestamp. Data transmitted by the communication module (1211) to applications (122-1, 122-2, 122-3) may include information on a package name, domain, decision level, and timestamp.
[0063] The app verification module (1212) can verify whether the information received from the applications (122-1, 122-2, 122-3) is information received from the registered applications. In this document, the applications (122-1, 122-2, 122-3) whose security levels are controlled by the security manager (121) may be registered applications. The security manager (121) may register the package name and signature value of the application in advance through an external device. The app verification module (1212) can compare the registered package name and signature value with the package name and signature value of the application that transmits and receives the security level to determine the validity of the application. That is, the app verification module (1212) can verify the validity of the application based on the pre-registered package name and signature value.
[0064] The domain management module (1213) can manage applications that transmit and receive security levels for each domain. For example, an application can register whether to transmit or receive information for a domain as metadata in the Android manifest. The security manager (121) can collect the Android manifests of applications and manage them for each domain. In addition, the security manager (121) can transmit and receive information to and from applications that require security levels for each domain.
[0065] Figure 5 illustrates an example of grouping by domain. For example, the attribute for the Wi-Fi domain of the second application may be set to "sender," and the attributes for the Wi-Fi domains of the first and fourth applications may be set to "transmitter / receiver." The domain management module (1213) may group the second application into a transmission group for the Wi-Fi domain, and the first and fourth applications into transmission / reception groups. The domain management module (1213) may group and manage all applications registered for all domains into transmission groups, reception groups, or transmission / reception groups.
[0066] The security level setting module (1214) can store and manage the domain-specific security level received from the application.
[0067] Figure 6a illustrates an example of security level criteria. For example, security level 1 may be set to indicate a security threat that could have a critical impact on a terminal (electronic device). Security level 2 may be set to indicate a threat that could have a critical impact on the terminal but is not critical or relatively minor. Security level 3 may be set to indicate a situation where international security standards are not met but there are no known security threats. Security level 4 may be set to indicate a situation where international security standards are met. Therefore, a lower security level may indicate a more vulnerable domain.
[0068] Figure 6b illustrates an example of applying security levels by domain. For example, a first application may determine the security levels for the domains of Wi-Fi, Internet Protocol, and the lock screen and transmit them to the security manager (121). A second application may determine the security levels for the domains of Wi-Fi, the device, and the lock screen and transmit them to the security manager (121). A third application may not transmit the security levels to the security manager (121) because it is set as a recipient. A fourth application may determine the security levels for the domains of the device and the lock screen and transmit them to the security manager (121).
[0069] The security manager (121) can classify the security levels sent by each application by domain and determine the decision level. The security manager (121) can determine the lowest security level for each domain as the decision level. In the case of a Wi-Fi domain, the security level of the first application is 4, but the security level of the second application is 2, which is a lower level, so the security manager (121) can set the decision level of the Wi-Fi domain to 2. Similarly, the security manager (121) can set the decision level of the device domain to 1, the decision level of the Internet Protocol domain to 3, and the security level of the lock screen domain to 1. The security manager (121) can receive security levels from each application in real time and set the decision level for each domain. In addition, if the decision level changes according to a change in the security level of the domain, the security manager (121) can transmit the changed decision level to the application.
[0070] Each application (122-1, 122-2, 122-3) may include a communication module (1221), a calculation module (1222), an application module (1223), and a registration module (1224). Each module included in the application (122-1, 122-2, 122-3) may be a module implemented in software.
[0071] The communication module (1221) can transmit the domain-specific security level to the communication module (1211) of the security manager (121) or receive the decision level from the communication module (1211) of the security manager (121). The calculation module (1222) can determine the domain-specific security level based on environmental information and security level criteria (e.g., FIG. 6a). When the application module (1223) receives the decision level from the security manager (121), it can change the security level and set an operation to be performed in the application (or domain) based on the changed security level. The application module (1223) sets an operation corresponding to the received decision level depending on the application, and thus, the operation may vary depending on the application. The registration module (1224) can manage the registration process of the application for the operation of this document. As an example, the registration module (1224) can register the application as a target of the operation of this document on an external device (e.g., an admin site) before being installed on the electronic device (101). The registration module (1224) can declare whether registration is required in the Android user feature. In addition, the registration module (1224) can register whether a domain can be sent or received as metadata in the Android manifest.
[0072] FIG. 7a is a flowchart illustrating the operation of a security manager according to various embodiments.
[0073] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.
[0074] According to one embodiment, steps 710 to 770 may be understood to be performed in a processor (e.g., processor (120) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 2).
[0075] Referring to FIG. 7A, when the electronic device (101) is in operation, the security manager of the processor (120) may be executed (710). The security manager may operate in real time. Alternatively, the security manager may operate based on information transmitted by a registered application or preset conditions (e.g., time, user-defined conditions, etc.).
[0076] When an application is executed and the security level determined by the application is transmitted to the security manager (720-a), the security manager can determine whether the application transmitting the security level is an authorized application (720). For example, the app verification module of the security manager can verify the validity of the application transmitting the security level based on registered application information. For example, the app verification module can verify the validity by comparing the package name and signature value (hash value) received from the application with the registered information. As an example, the app verification module can determine whether the application is valid based on whether the package name and signature value match through the Android package manager.
[0077] If the application is validated (e.g., registered) (720-YES), the security manager may receive the security level of the domain received from the application (730). Alternatively, if the application is not validated (720-NO), the security manager may ignore the security level of the received domain.
[0078] The security manager can compare and update the security level of the received domain with the decision level of the current domain (740). For example, the security manager can compare the security level of the received domain with the decision level of the corresponding domain. Furthermore, the security manager can determine whether to update the decision level based on the comparison result. For example, if the security level of the received domain is lower than the decision level of the corresponding domain, the security manager can determine whether to update the decision level and update the decision level to the security level of the received domain.
[0079] When the decision level is updated, the security manager can determine whether to transmit the updated decision level of the domain to the application (750). The security manager can transmit the decision level to the application set as the recipient. If the security level of the domain of the application set as the recipient is equal to the updated decision level (750-NO), the security manager can determine that there is no need to transmit the updated decision level. If the security level of the domain of the application set as the recipient is higher than the updated decision level (750-YES), the security manager can determine that there is a need to transmit the updated decision level.
[0080] The security manager can determine the application to which the updated decision level will be transmitted (760). For example, the security manager can parse the recipient information in the list's metadata and determine the recipient application for the corresponding domain. The security manager can transmit the updated decision level to the determined application (770).
[0081] Figure 7b is a flowchart illustrating the operation of the app according to various embodiments.
[0082] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.
[0083] According to one embodiment, steps 810 to 840-2 may be understood to be performed in a processor (e.g., processor (120) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 2).
[0084] The first application (app1) of FIG. 7B is an application set as a sender in the list, and the first application set as a sender can determine the security level for a domain based on environmental information (810). The operating cycle or determination cycle of the application may vary depending on the application. For example, an anti-malware application may operate in real time and generate a trigger for determining the security level in real time when a malicious application is installed or updated. Alternatively, a lock screen application may generate a trigger for determining the security level when its settings are changed. The application can determine the security level based on the occurrence of the trigger. The first application may determine whether to transmit the determined security level to the security manager (820).
[0085] If the determined security level is the same as the existing security level, the first application may determine that there is no need to transmit the changed security level to the security manager (820-NO). Alternatively, if the determined security level is changed from the existing security level, the first application may determine that there is a need to transmit the changed security level to the security manager (820-YES). The first application may transmit the changed security level to the security manager (820-a).
[0086] Thereafter, as described in Figure 7a, the security manager can operate and transmit the updated decision level to the applications set as recipients. The second application (app2) and the third application (app3) of Figure 7b may be applications set as recipients in the list. The security manager can transmit the updated decision level to the second application and the third application.
[0087] A second application can receive an updated decision level from the security manager (830-1). Then, the second application can apply a security policy for the application based on the received updated decision level (840-1). Similarly, a third application can receive an updated decision level from the security manager (830-2). Then, the third application can apply a security policy for the application based on the received updated decision level (840-2).
[0088] FIG. 8 is a diagram illustrating a process of setting a security function in an electronic device connected to an external site according to various embodiments.
[0089] Referring to FIG. 8, an example is illustrated in which a device protection application (122-4) and an Internet application (122-5) are dynamically protected through a security manager. That is, the device protection application (122-4) and the Internet application (122-5) may be registered applications managed by the security manager (121).
[0090] For example, the electronic device (101) may be used as a distributed denial of service (DDoS) bot by an attacker. The device protection application (122-4) and the Internet application (122-5) may include abnormal operation domains. The device protection application (122-4) may be set as a receiver, and the Internet application (122-5) may be set as a sender. A malicious application may be installed in the electronic device (101), and the malicious application may attack the chat site (11). The Internet application (122-5) may include a function for identifying the malicious application based on environmental information. For example, the environmental information may include device information (125). The Internet application (122-5) may determine that the electronic device (101) is being used as a bot based on the device information (125) and / or usage trends.
[0091] The application can determine the security level for each domain and transmit the determined security level to the security manager (121). For example, the Internet application (122-5) can determine the security level of an abnormally operating domain as 1. In addition, the Internet application (122-5) can transmit the security level of the abnormally operating domain determined to be 1 to the security manager (121).
[0092] Since the application set as the sender is only the Internet application (122-5), the security manager (121) can determine the security level received from the Internet application (122-5) as the decision level. For example, since the security level of the abnormal domain received from the Internet application (122-5) is 1, the security manager (121) can determine the decision level for the abnormal domain as 1. The security manager (122-5) can transmit the decision level of the abnormal domain determined to be 1 to the device protection application (122-4) set as the receiver.
[0093] The device protection application (122-4) can perform corresponding actions based on the decision level of the abnormal domain received from the security manager (121). For example, the decision level of the abnormal operation domain received by the device protection application (122-4) is 1, and decision level 1 may indicate the most vulnerable security state. Accordingly, the device protection application (122-4) can activate the application and delete the malicious application.
[0094] FIG. 9 is a drawing illustrating a process for setting security functions for multiple apps according to various embodiments, and FIG. 10 is a drawing illustrating a process for setting security functions in an electronic device connected to a public communication network according to various embodiments.
[0095] Referring to FIG. 9, an example is illustrated in which a smart lock application (123-1), a secure Wi-Fi application (123-2), a quick share application (123-3), a Bluetooth application (123-4), and a Wi-Fi application (123-5) are dynamically protected through a security manager. That is, the smart lock application (123-1), the secure Wi-Fi application (123-2), the quick share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5) may be registered applications managed by the security manager (121).
[0096] For example, the smart lock application (123-1) may be set as a sender and include a user authentication domain. The secure Wi-Fi application (123-2) may be set as a sender and include a POI (point of interest) domain. The POI function may utilize the user's location information to determine whether a location is public. The quick share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5) may be set as receivers and include a user authentication domain and a POI domain. The smart lock application (123-1) included in the electronic device (101) may be set to automatically unlock when the wearable device is placed near the electronic device (101) by the user.
[0097] The smart lock application (123-1) can determine user authentication information based on environmental information. For example, the environmental information may include communication connection information and biometric authentication information. The smart lock application (123-1) can determine the security level of the user authentication domain as 5 and transmit the determined security level of the user authentication domain to the security manager (121).
[0098] The security manager (121) can receive the security level of the user authentication domain only from the smart lock application (123-1). Accordingly, the security manager (121) can determine the decision level for the user authentication domain as 5. The security manager (121) can transmit the decision level of the user authentication domain determined to be 5 to the quick share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5).
[0099] The Quick Share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5) can determine that the electronic device (101) is secure based on the decision level of the received user authentication domain. Accordingly, each application can set (or change) a security function based on the received decision level. For example, the Quick Share application (123-3) can change the sharing permission target to allow people (or devices) nearby. The Bluetooth application (123-4) can change the connection target to allow all. In addition, the Wi-Fi application (123-5) can change the connection target to connect to the fastest and most stable Wi-Fi.
[0100] At this time, the user can visit the cafe with the smart lock activated and use the Internet via Wi-Fi (12).
[0101] Referring to Figure 10, an example of changing the security level when connecting to a cafe's Wi-Fi is shown.
[0102] The secure Wi-Fi application (123-2) may include a POI function. The secure Wi-Fi application (123-2) may obtain environmental information. The environmental information may include device information (125). Based on the obtained environmental information, the secure Wi-Fi application (123-2) may use the POI to identify whether a location is public and determine the security level of the POI domain. For example, the Wi-Fi (12) of a cafe may be public Wi-Fi, and the secure Wi-Fi application (123-2) may determine the security level of the POI domain as 1 and transmit it to the security manager (121).
[0103] The security manager (121) can receive the security level of the POI domain only from the secure Wi-Fi application (123-2). Therefore, the security manager (121) can determine the decision level for the POI domain as 1. The security manager (121) can transmit the decision level of the POI domain determined to be 1 to the quick share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5). Alternatively, the security manager (121) can transmit the decision level of the user authentication domain and the decision level of the POI domain together.
[0104] The Quick Share application (123-3), the Bluetooth application (123-4), and the Wi-Fi application (123-5) can determine that the electronic device (101) is unsafe based on the decision level of the received POI domain and / or user authentication domain. Accordingly, each application can set (or change) a security function based on the received decision level. For example, the Quick Share application (123-3) can change the sharing permission target from allowing people (or devices) nearby to allowing only specified contacts. The Bluetooth application (123-4) can change the connection target from allowing everyone to connecting only specified devices. In addition, the Wi-Fi application (123-5) can change the connection target from connecting to the fastest and most stable Wi-Fi to a saved network connection.
[0105] Figure 11 is a flowchart illustrating a security setting method according to various embodiments.
[0106] In the following examples, the operations may be performed sequentially, but are not necessarily sequential. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.
[0107] According to one embodiment, steps 1110 to 1150 may be understood to be performed in a processor (e.g., processor (120) of FIG. 2) of an electronic device (e.g., electronic device (101) of FIG. 2).
[0108] Referring to FIG. 11, an application of an electronic device (101) can set (or determine) a security level of a domain based on environmental information (1110). For example, the environmental information may include information related to the surrounding environment of the electronic device (101) and / or information related to functions set in the electronic device (101). As an example, the environmental information may include authentication-related information, communication connection information, and / or location information of the electronic device (101).
[0109] An application can include one or more domains and set security levels for each domain. For example, an application can determine a domain's security level upon initial installation. A real-time monitoring application can trigger a security level determination when a malicious application is installed and / or updated, and can then determine the domain's security level. Alternatively, the application can trigger a security level determination based on user-defined settings and / or environmental information changes, and can then determine the domain's security level.
[0110] An application can set an initial security level and transmit the set security level to the security manager. Alternatively, if the security level of the determined domain is different from the security level of the set domain, the application can transmit the determined security level to the security manager. The application transmitting the security level to the security manager can be an application whose attribute is set to "sender."
[0111] The security manager of the electronic device (101) can receive the security level of the domain from the application (1120). For example, the application may be a registered application. The security manager of the electronic device (101) can verify the validity of the application based on the pre-registered package name and signature value. Once the validity of the application is verified, the security manager can receive the security level transmitted by the application.
[0112] The security manager can identify the lowest security level among the security levels of the received domain (1130). The lower the security level, the higher the security risk of the electronic device (101). Therefore, the application can perform more powerful security functions. The security manager can identify the lowest security level for each domain. The security manager can determine the identified lowest security level as the decision level for the corresponding domain. For example, the security manager can determine the lowest security level among the received security levels of the first domain as the decision level for the first domain.
[0113] The security manager can transmit the lowest security level identified as being associated with a domain (1140). The application to which the security manager transmits the decision level may be an application whose attribute is set as a recipient. For example, the security manager can transmit the decision level of a first domain to an application that includes the first domain and is set as a recipient.
[0114] The application can change the security level of the domain based on the lowest security level (decision level) received (1150). At least one application can execute a function corresponding to the changed security level. For example, if the received decision level is lower than the security level set by the application, the security risk of the electronic device (101) has increased, and the application can perform (or set) a more robust security function.
[0115] As an example, a method for setting security of an electronic device (101) may include at least one application included in the electronic device (101) setting a security level of a domain based on environment information. A security manager included in the electronic device (101) may receive a security level of the domain from the at least one application. The security manager may identify a lowest security level among the received security levels of the domain. The security manager may transmit the identified lowest security level to the at least one application associated with the domain. The at least one application may change the security level of the domain based on the received lowest security level.
[0116] As an example, the method may enable the at least one application to execute a function corresponding to the changed security level.
[0117] As an example, the method may enable the security manager to verify the validity of the at least one application based on a pre-registered package name and signature value.
[0118] As an example, the method may allow the at least one application to determine the security level of the domain based on at least one of installation of a harmful application, an update of the harmful application, a change in settings of the at least one application, and a change in environment information.
[0119] As an example, the method may transmit the security level of the determined domain to the security manager if the security level of the determined domain is different from the security level of the set domain.
[0120] As an example, the operation of identifying the lowest security level may identify the lowest security level based on the security level of the determined domain.
[0121] As an example, at least one application of the method may include multiple domains. The operation of determining the security level of the domain may determine the security level of each of the multiple domains.
[0122] As an example, the operation of identifying the lowest security level may identify the lowest security level of the first domain based on the security level of the first domain among the security levels of the received domains.
[0123] As an example, the operation of transmitting the identified lowest security level may identify at least one application associated with a second domain and transmit the lowest security level of the second domain to the identified at least one application.
[0124] As an example, the at least one application may be set as at least one of a sender transmitting the security level of the domain and a receiver receiving the security level.
[0125] As an example, an electronic device (101) may include a memory (130) that stores a command and at least one processor (120) that executes the command. The command stored in the memory (130) may be configured to cause the electronic device (101) to set a security level of a domain of at least one application included in the electronic device (101) based on environment information. The command stored in the memory (130) may be configured to cause the electronic device (101) to transmit the security level of the domain from the at least one application to a security manager included in the electronic device (101). The command stored in the memory (130) may be configured to cause the electronic device (101) to identify a lowest security level among the security levels of the domain received from the security manager. The command stored in the memory (130) may be configured to cause the electronic device (101) to transmit the identified lowest security level to the at least one application associated with the domain. The command stored in the memory (130) may be configured to cause the electronic device (101) to change the security level of the domain in the at least one application based on the lowest security level received.
[0126] As an example, the command stored in the memory (130) may be set to cause the electronic device (101) to execute a function corresponding to the changed security level in the at least one application.
[0127] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to verify the validity of at least one application based on a pre-registered package name and signature value.
[0128] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to determine the security level of the domain based on at least one of installation of a harmful application, update of the harmful application, change of settings of the at least one application, and change of the environment information.
[0129] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to transmit the security level of the determined domain from the at least one application to the security manager if the security level of the determined domain is different from the security level of the set domain.
[0130] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to identify the lowest security level based on the security level of the determined domain.
[0131] As an example, the at least one application may include multiple domains. The instructions stored in the memory (130) may be configured to cause the electronic device (101) to determine the security level of each of the multiple domains.
[0132] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to identify the lowest security level of the first domain based on the security level of the first domain among the security levels of the received domains.
[0133] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to identify at least one application associated with a second domain and to transmit the lowest security level of the second domain to the identified at least one application.
[0134] As an example, the command stored in the memory (130) may be configured to cause the electronic device (101) to be set as at least one of a sender transmitting the security level of the domain and a receiver receiving the security level.
[0135] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.
[0136] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).
[0137] Various embodiments of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.
[0138] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.
[0139] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and arranged in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
[0140] The effects of this document are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the above description.
Claims
1. In a method for setting security of an electronic device (101), An operation of at least one application included in the electronic device (101) to set a security level of a domain based on environmental information; An operation in which a security manager included in the electronic device (101) receives a security level of the domain from at least one application; An action by the security manager to identify the lowest security level among the security levels of the received domain; The action of the security manager transmitting the lowest security level identified to at least one application associated with the domain; and A method for setting security in an electronic device, comprising: changing the security level of the domain based on a lowest security level received by at least one application; 2. In paragraph 1, A method for setting security of an electronic device, further comprising: an operation of executing a function corresponding to the changed security level by at least one application; 3. In paragraph 1, A method for setting security of an electronic device, further comprising: an operation of verifying the validity of at least one application based on a pre-registered package name and signature value by the security manager; 4. In paragraph 1, A method for setting security in an electronic device, further comprising: an operation of determining a security level of the domain by the at least one application based on at least one of installation of a harmful application, updating of the harmful application, changing settings of the at least one application, and changing environment information; 5. In paragraph 4, A method for setting security in an electronic device, further comprising: an operation of transmitting the security level of the determined domain to the security manager if the security level of the determined domain is different from the security level of the set domain; 6. In paragraph 5, The action to identify the lowest security level is: A method for setting security of an electronic device, wherein the lowest security level is identified based on the security level of the determined domain.
7. In paragraph 1, wherein at least one of the above applications comprises multiple domains, The action to determine the security level of the above domain is: A method for setting security of an electronic device for determining the security level of each of the plurality of domains.
8. In paragraph 7, The action to identify the lowest security level is: A method for setting security of an electronic device, wherein the lowest security level of the first domain is identified based on the security level of the first domain among the security levels of the received domains.
9. In paragraph 1, The action that transmits the lowest security level identified above is: A method for setting security in an electronic device, the method comprising: identifying at least one application associated with a second domain; and transmitting the lowest security level of the second domain to the identified at least one application.
10. In paragraph 1, At least one of the above applications, A method for setting security of an electronic device, wherein at least one of a sender transmitting a security level of the above domain and a receiver receiving the same is set.
11. In an electronic device (101), Memory (130) for storing commands; and At least one processor (120) for executing the above command; The command stored in the above memory (130) causes the electronic device (101) to: Setting the security level of the domain of at least one application included in the electronic device (101) based on the environmental information, Transmitting the security level of the domain from at least one application to the security manager included in the electronic device (101), Identify the lowest security level among the security levels of the domain received from the above security manager, Transmitting the lowest security level identified above to at least one application associated with said domain, An electronic device configured to change the security level of said domain in said at least one application based on a lowest security level received.
12. In paragraph 11, The command stored in the above memory (130) causes the electronic device (101) to: An electronic device configured to execute a function corresponding to said changed security level in at least one application.
13. In paragraph 11, The command stored in the above memory (130) causes the electronic device (101) to: An electronic device configured to verify the validity of at least one application based on a previously registered package name and signature value.
14. In paragraph 11, The command stored in the above memory (130) causes the electronic device (101) to: An electronic device configured to determine the security level of the domain based on at least one of: installation of a malicious application, update of the malicious application, change in settings of the at least one application, and change in environment information.
15. In paragraph 14, The command stored in the above memory (130) causes the electronic device (101) to: An electronic device configured to transmit the security level of the determined domain to the security manager from at least one application if the security level of the determined domain is different from the security level of the set domain.
Citation Information
Patent Citations
Information processor, information processing method, program and recording medium
JP2005149394A
Method of controlling a mobile terminal based on location information and applying security policues based on priority rules, and system thereof
KR101503597B1
System and method for strengthening security of mobile terminal
KR1020130005950A
Method and apparatus for providing network communication association information to applications and services
KR1020130091353A
Synchronizing parallel applications in an asymmetric multi-processing system
US9304945B2