US20070157310A1 - Security ensuring by program analysis on information device and transmission path - Google Patents

Security ensuring by program analysis on information device and transmission path Download PDF

Info

Publication number
US20070157310A1
US20070157310A1 US10/587,609 US58760905A US2007157310A1 US 20070157310 A1 US20070157310 A1 US 20070157310A1 US 58760905 A US58760905 A US 58760905A US 2007157310 A1 US2007157310 A1 US 2007157310A1
Authority
US
United States
Prior art keywords
program
function
information
received
receiving
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US10/587,609
Other versions
US8490183B2 (en
Inventor
Satoshi Kondo
Shigeru Yatabe
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Trend Micro Inc
Original Assignee
Trend Micro Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Trend Micro Inc filed Critical Trend Micro Inc
Assigned to TREND MICRO INCORPORATED reassignment TREND MICRO INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KONDO, SATOSHI, YATABE, SHIGERU
Publication of US20070157310A1 publication Critical patent/US20070157310A1/en
Application granted granted Critical
Publication of US8490183B2 publication Critical patent/US8490183B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245Protecting personal data, e.g. for financial or medical purposes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2101Auditing as a secondary aspect
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2113Multi-level security, e.g. mandatory access control
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2115Third party
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149Restricted operating environment

Definitions

  • the present invention relates to a technique of ensuring security of an information device.
  • JP2001-117769 discloses a program executing device wherein identification information (for example, an IP address or a URL) indicating reliable sources of programs in a memory in the program executing device; and if identification information indicating a source of a program received via a network is registered in the memory, execution of the program is permitted.
  • identification information for example, an IP address or a URL
  • security is enhanced by, for example, analyzing at a mobile terminal a content of a program received at the mobile terminal via a network to determine whether the program is a security threat, it is necessary for the mobile terminal to have a high level of computing power. Moreover, determination of security threats at the mobile terminal places a heavy load on a processing unit of the mobile terminal and takes a substantial amount of time to complete. Similarly, if at a relay device such as a server on a network, a content of a program received via a network is analyzed to thereby determine whether execution of the program in a communication terminal will constitute a security threat, it is necessary to provide the relay device with a high level of computing power. If the relay device is not provided with sufficient computing power, delays in communications are likely to occur.
  • the present invention has been made in view of the problems discussed above, and provides a technique of determining, at a receiving device or a relay device, whether a program provided via a network is a security threat, by using a simple method which can be quickly carried out.
  • the present invention provides registering means for registering information on whether a function of a received program is permitted to be used; receiving means for receiving a program and function information indicating a function used in the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a program received by the receiving means includes a function not permitted to be used; and outputting means for outputting a result determined by the determining means.
  • the present invention also provides a program for causing a computer to function as a receiving device, and provides a computer-readable storage medium for recording the program.
  • the program may be pre-installed in a memory of a computer, or it may be installed in a computer by way of communications conducted via a network, or be installed from the storage medium.
  • a receiving device determines whether a prohibited function is present in a received program by comparing function information of the program and information registered by the registering means, and outputs the determination result.
  • the present invention also provides a receiving device comprising: registering means for registering information on whether a function of a received program is permitted to be used; receiving means for receiving a program and function information indicating a function used in the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to execute a program received by the receiving means; and executing means for executing a program if the determining means determines to execute the program.
  • the present invention also provides a program for causing a computer to function as a receiving device, and provides a computer-readable storage medium for recording the program.
  • a receiving device determines whether a received program should be executed by comparing function information of the program and information registered by the registering means.
  • the present invention also provides a receiving device comprising: registering means for registering means for registering information on whether a function of a received program is permitted to be used; first receiving means for receiving, before receiving a program, function information indicating a function used in the program; determining means for determining whether to receive a program, by comparing function information received by the first receiving means and information registered by the registering means; second receiving means for receiving a program if the determining means determines to receive the program; and executing means for executing a program received by the second receiving means.
  • the present invention also provides a program for causing a computer to function as a receiving device, and a computer-readable storage medium for recording the program.
  • a receiving device determines whether a program should be received by comparing function information of the program and information registered by the registering means.
  • the present invention provides a relay device comprising: registering means for registering information on whether a function of a program provided via a network is permitted to be used; receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to relay a program received by the receiving means; and sending means for sending a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program.
  • the present invention also provides a program for causing a computer to function as a relay device, and provides a computer-readable storage medium for recording the program.
  • the program may be pre-installed in a memory of a computer, or it may be installed in a computer by way of communications conducted via a network, or be installed from the storage medium.
  • a relay device determines whether to relay a received program by comparing function information of the program and information registered by the registering means.
  • the present invention also provides a relay device comprising: registering means for registering information on whether a function of a program provided via a network is permitted to be used; receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a function not permitted to be used is used in a program received by the receiving means; and sending means for sending a determination result by the determining means and a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program.
  • the present invention also provides a program for causing a computer to function as a relay device, and provides a computer-readable storage medium for recording the program.
  • a relay device determines whether a prohibited function is present in a received program by comparing function information of the program and information registered by a registering means, and sends the determination result with the program.
  • a receiving device or a relay device it can be readily determined at a receiving device or a relay device whether a program provided via a network is one that poses a security threat, by employing a simple method and within a short time.
  • FIG. 1 is a block diagram illustrating a configuration of a communication system according to the first embodiment.
  • FIG. 2 is a diagram illustrating a data structure of inspection result data 202 according to the first embodiment.
  • FIG. 3 is a block diagram illustrating a hardware configuration of mobile phone 50 according to the first embodiment.
  • FIG. 4 is a diagram illustrating a data structure of security management table 507 a according to the first embodiment.
  • FIG. 5 is a sequence chart illustrating operations of each component forming communication system 1 according to the first embodiment, which are performed until a program and inspection result data 202 thereof are downloaded to mobile phone 50 .
  • FIG. 6 is a diagram illustrating a screen displayed on a mobile phone 50 when a security level is set according to the first embodiment.
  • FIG. 7 is a flowchart illustrating operations for determining whether to execute a program received via a network, which operations are carried out in mobile phone 50 according to the first embodiment.
  • FIG. 8 is a diagram illustrating a screen displayed on mobile phone 50 when execution of a program is not permitted according to the first embodiment.
  • FIG. 9 is a block diagram illustrating a hardware configuration of relay device 60 according to the second embodiment.
  • FIG. 10 is a flowchart illustrating operations of determining whether to execute a program received via a network, which operations are carried out in relay device 60 according to the second embodiment.
  • FIG. 11 is a block diagram illustrating a configuration of communication system 2 according to the modification ( 1 ).
  • FIG. 12 is a flowchart illustrating operations carried out in mobile phone according to the modification ( 2 ).
  • FIG. 13 is a diagram illustrating a screen displayed on mobile phone 50 according to the modification ( 2 ).
  • FIG. 1 is a block diagram illustrating a configuration of communication system according to the first embodiment.
  • content provider 10 is a service provider that provides content to mobile phone 50 .
  • Content server 10 a conducts packet communication with mobile phone 50 via Internet 30 and mobile packet communication network 40 .
  • Content server 10 a stores programs for mobile phone 50 and inspection result data 202 which are obtained as a result of inspection of the program in inspection institution 20 .
  • the programs stored in content server 10 a may be software containing image or audio data used when a program is executed.
  • Inspection institution 20 is an institution which inspects a program provided to mobile phone 50 upon an inspection request from content provider 10 , and program inspection device 20 a stores security evaluation list 201 .
  • security evaluation list 201 there are listed functions such as a function call and a system call which may compromise security in mobile phone 50 if provided with a program via a network and the program is executed.
  • Security evaluation list 201 also lists resources accessible by mobile phone 50 which may compromise security in mobile phone 50 if accessed in accordance with a program provided via a network.
  • Program inspection device 20 a analyzes a program to be inspected with reference to security evaluation list 201 , and extracts from the program functions listed in security evaluation list 201 .
  • Program inspection device 20 a also identifies, among resources accessed when the program is executed, resources listed in security evaluation list 201 .
  • program inspection device 20 a generates inspection result data 202 containing the names of the extracted functions and information on the identified resources (for example, URLs or paths indicating where the resources have been stored or identifiers assigned to the resources). Inspection result data 202 is returned to content provider 10 and stored along with the program in content server 10 a.
  • Program inspection device 20 a may record as inspection result data 202 all functions contained in a program to be inspected, or may record all resources accessed when a program to be inspected is executed.
  • Mobile phone 50 is a communication terminal (receiving device) served by mobile packet communication network 40 , and can download a program from content server 10 a and execute it.
  • FIG. 2 is a diagram illustrating a data structure of inspection result data 202 .
  • inspection result data 202 contains the name of an inspected program, the name of a hash algorithm used for calculating a hash value of the program, and the calculated hash value.
  • Inspection result data 202 also contains a list of the name of functions contained in the program and a list of information on resources accessed when the program is executed, which are obtained as a result of an analysis of the program using security evaluation list 201 .
  • the hash value contained in inspection result data 202 is used for verifying that the program has not been changed or falsified after inspection by program inspection device 20 a.
  • FIG. 3 is a block diagram illustrating a hardware configuration of mobile phone 50 .
  • CPU 501 executes a variety of programs stored in ROM 502 and nonvolatile memory 507 , and thereby controls components of mobile phone 50 .
  • ROM 502 stores programs for controlling mobile phone 50 .
  • RAM 503 is used as a work area of CPU 501 .
  • Wireless communication unit 504 under the control of CPU 501 , controls wireless communication with a base station (not shown) of mobile packet communication network 40 .
  • Operation input unit 505 consists of a plurality of keys, and outputs an operation signal to CPU 501 in response to an operation of the keys.
  • Liquid crystal display unit 506 consists of a liquid crystal display panel and a driving circuit for controlling a display of the liquid crystal display panel.
  • Nonvolatile memory 507 stores software such as an operating system and a WWW (World Wide Web) browser for mobile phone 50 .
  • Nonvolatile memory 507 also stores programs downloaded from content server 10 a and stores inspection result data 202 thereof.
  • Nonvolatile memory further stores security management table 507 a.
  • Security management table 507 a registers, among functions contained in programs for mobile phone 50 , the names of functions permitted to be used when a program received via a network is executed, and the names of functions not permitted to be used when a program received via a network is executed.
  • Security management table 507 a also registers, among resources accessible by mobile phone 50 , information on resources permitted to be accessed when a program received via a network is executed, and information on resources not permitted to be accessed when a program received via a network is executed.
  • a term “user confirmation” is registered in the item “permission” column of security management table 507 a.
  • Nonvolatile memory 507 stores a plurality of security management tables 507 a for each security level available in mobile phone 50 such as security management table 507 a for “Level 1 ” or security management table 507 a for “Level 2 ”.
  • security management table 507 a corresponding to a security level presently set in mobile phone 50 is used among the plurality of security management tables 507 a .
  • the security level is set by a user of mobile phone 50 .
  • Functions registered in security management table 507 a and information on whether to permit uses of the functions may be changed by a user of mobile phone 50 . This is the same for resources registered in security management table 507 a and information on whether to permit access of the resources.
  • FIG. 5 is a sequence chart illustrating operations of each component forming communication system 1 , which are performed until a program and corresponding inspection result data 202 are downloaded to mobile phone 50 .
  • a program for mobile phone 50 written by content provider 10 is sent along with an inspection request from content server 10 a to program inspection device 20 a (Step S 101 ).
  • Program inspection device 20 a upon receipt of the program and the inspection request, analyzes the received program (Step S 102 ).
  • Program inspection device 20 a extracts from the program functions listed in security evaluation list 201 , and identifies resources which are accessed if the program is executed, and which are listed in security evaluation list 201 .
  • Program inspection device 20 a also calculates a hash value of the program using a hash algorithm.
  • Program inspection device 20 a then generates inspection result data 202 containing the names of the extracted functions, the information on the identified resources, the calculated hash value, the name of the algorithm used, and the file name of the program (Step S 103 ).
  • program inspection device 20 a attaches an electronic signature to the generated inspection result data 202 (Step S 104 ).
  • This electronic signature is used for verifying in mobile phone 50 that the program has not been changed or falsified.
  • program inspection device 20 a returns inspection result data 202 with the electronic signature to content server 10 a (Step S 105 ).
  • Content server 10 a upon receipt of inspection result data 202 , stores inspection result data 202 with the inspected program in a memory (Step S 106 ), and renders the program and inspection result data 202 downloadable by mobile phone 50 .
  • a security level is set (Step S 107 ).
  • a screen shown in FIG. 6 is displayed on liquid crystal display unit 506 , and a user can select a security level of mobile phone 50 from “Level 0 (Nothing)” to “Level 5 ” using operation input unit 505 .
  • the security level set by the user is stored in nonvolatile memory 507 .
  • Step S 108 If mobile phone 50 downloads a program from content server 10 a , a WWW browser is launched in mobile phone 50 (Step S 108 ), and packet communications are started between mobile phone 50 and content server 10 a .
  • a signal requesting download of the program is sent from mobile phone 50 to content server 10 a (Step S 109 ).
  • Content server 10 a reads the requested program and inspection result data 202 of the program from memory, and sends them to mobile phone 50 (Steps S 110 and S 111 ).
  • Mobile phone 50 upon receipt of the program and inspection result data 202 , stores them in nonvolatile memory 507 (Step S 112 ).
  • FIG. 7 is a flowchart illustrating operations of determining whether to execute a program received via a network, and which are carried out in mobile phone 50 .
  • the operations are carried out by CPU 501 if the execution of a program received via a network is instructed in mobile phone 50 .
  • CPU 501 reads from nonvolatile memory 207 inspection result data 202 of a program the execution of which has been instructed (Step S 201 ).
  • CPU 501 verifies an electronic signature of inspection result data 202 (Step S 202 ), and thereby confirms that inspection result data 202 has been generated by inspection institution 20 , and that inspection result data 202 is an authentic inspection result data which has not been falsified. If, as a result of the verification of the electronic signature, it is found that inspection result data 202 is not authentic (Step S 203 : NO), CPU 501 cancels the execution of the program (Step S 210 ), and causes liquid crystal display unit 506 to display a message stating that the execution of the program has been cancelled because falsification has been found in inspection result data 202 .
  • Step S 203 if inspection result data is verified to be authentic (Step S 203 : YES), CPU 501 calculates a hash value of the program using a hash algorithm described in inspection result data 202 .
  • CPU 501 compares the calculated hash value and a hash value described in inspection result data 202 (Step S 204 ). As a result of the comparison, if the hash values do not match (Step S 205 : NO), CPU 501 cancels the execution of the program (Step S 210 ), and causes liquid crystal display unit 506 to display a message stating that execution of the program has been cancelled because falsification has been found in the program.
  • Step S 205 if the hash values match (Step S 205 : YES), CPU 501 identifies a value of a security level currently set in mobile phone 50 , and reads from nonvolatile memory 507 security management table 507 a corresponding to the identified value of the security level (Step S 206 ).
  • CPU 501 compares the read security management table 507 a and inspection result data 202 read in Step S 201 (Step S 207 ), and thereby determines whether to execute the program (Step S 208 ).
  • CPU 501 for each function described in inspection result data 202 , namely for each function extracted from the program to be executed, determines whether the function is a function permitted to be used in security management table 507 a .
  • CPU 501 for each resource described in inspection result data 202 , determines whether the resource is a resource permitted to be accessed in security management table 507 a.
  • CPU 501 determines that the program violates the security policy (security management table 507 a ) set by a user, and does not permit the execution of the program (Step S 208 : NO). Consequently, CPU 501 cancels the execution of the program (Step S 210 ), and causes liquid crystal display unit 506 to display a message as shown in FIG. 8 .
  • security policy security management table 507 a
  • inspection result data 202 is as shown in FIG. 2 and security management table 507 a is as shown in FIG. 4
  • inspection result data 202 contains a function “Function 1 ( )” which is not permitted to be used according to security management table 507 a
  • a resource “Local/UserData/AddressBook” which is not permitted to be accessed according to security management table 507 a
  • a program corresponding to inspection result data 202 is not permitted to be executed in mobile phone 50 .
  • CPU 501 determines that the program meets the security policy set by the user, and permits the execution of the program (Step S 208 : YES). Consequently, CPU 501 reads the program permitted to be executed from nonvolatile memory 507 , launches the program (Step S 209 ), and proceeds with operations in accordance with the program.
  • inspection result data 202 contains a resource requiring a user confirmation as a resource “http://www.xxx.co.jp” in security management table 507 a of FIG. 4
  • CPU 501 generates a message asking a user whether to execute a program, causes liquid crystal display unit 506 to display it, and determines the execution of the program in accordance with an instruction from operation input unit 505 .
  • program inspection device 20 a pre-inspects the content of a program provided to mobile phone 50 via a network, and generates inspection result data 202 containing functions contained in the program and information on resources accessed when the program is executed.
  • Mobile phone 50 compares inspection result data 202 and security management table 507 a registering information on whether a function may be used for each function and information on whether a resource may be accessed for each resource, and thereby determines whether to execute the program received via the network. Accordingly, mobile phone 50 , without analyzing the received program, only by comparing inspection result data 202 and security management table 507 a , can determine whether the program meets the security policy (security management table 507 a ) set in mobile phone 50 . Consequently, the determination process can be completed in mobile phone 50 by using a simple method and within a short time.
  • Security management table 507 a for determining whether to execute a received program can be changed easily by changing a security level. Accordingly, even if a program violates a security policy and thereby is determined not permitted to be executed, if a user determines that the program is valid, the program can be executed in mobile phone by temporarily lowering the security level. As stated above, in the present embodiment, flexible setting of a security level of mobile phone 50 relative to a received program can be carried out in accordance with a user's wishes.
  • FIG. 9 is a block diagram illustrating a hardware configuration of relay device 60 relaying packet communications between content server 10 a and mobile phone 50 .
  • Relay device 60 may be provided on either of Internet 30 or mobile packet communication network 40 .
  • communication interface 604 under the control of CPU 601 , controls packet communication with content server 10 a or mobile phone 50 .
  • Operation input unit 605 has a mouse and a keyboard, and outputs an operation signal to CPU 601 in accordance with operations carried out via the mouse and the keyboard.
  • Display unit 606 is a LCD or CRT display.
  • HD (Hard Disk) 607 stores security management table 507 a explained in the first embodiment.
  • Relay device 60 of the present embodiment uses security management table 507 a , determines whether to relay a program sent from content server 10 a to mobile phone 50 .
  • Relay device 60 receives, along with the program, inspection result data 202 of the program and destination information indicating the destination of the program from content server 10 a .
  • Inspection result data 202 is generated by program inspection device 20 a explained in the first embodiment.
  • the address information is a communication address assigned to mobile phone 50 such as an IP address.
  • a security level in relay device 60 is set by a carrier of mobile packet communication network or an administrator of relay device 60 .
  • HD 607 stores different security management tables 507 a for each security level as described in the first embodiment, and in accordance with the security level set in relay device 60 , security management table 507 a for determining whether to relay a program is determined.
  • FIG. 10 is a flowchart illustrating operations performed for determining whether to relay a program which are carried out in relay device 60 .
  • the operations are performed by CPU 601 if relay device 60 receives a program and inspection result data 202 thereof transmitted from content server 10 a to mobile phone 50 .
  • CPU 601 verifies an electronic signature of inspection result data 202 (Step S 301 ). If upon verification of the electronic signature, it is confirmed that inspection result data 202 is not authentic (Step S 302 : NO), CPU 601 cancels transfer of the program to mobile phone 50 (Step S 309 ), and sends to mobile phone 50 a message stating that the download of the program has been cancelled because falsification has been found in inspection result data 202 .
  • Step S 302 if inspection result data is verified to be authentic (Step S 302 : YES), CPU 601 calculates a hash value of the program using a hash algorithm described in inspection result data 202 , and compares the calculated hash value and a hash value described in inspection result data 202 (Step S 303 ). If as a result of the comparison, it is determined that the hash values do not match (Step S 304 : NO), CPU 601 cancels transfer of the program to mobile phone 50 (Step S 309 ), and sends to mobile phone 50 a message stating that download of the program has been cancelled because falsification has been found in the program.
  • Step S 304 if the hash values match (Step S 304 : YES), CPU 601 identifies a value of a security level set in relay device 60 at the time, and reads from HD 607 security management table 507 a corresponding to the identified value of the security (Step S 305 ). CPU 601 compares the read security management table 507 a and the received inspection result data 202 (Step S 306 ), and thereby determines whether to relay the program to mobile phone 50 (Step S 307 ).
  • CPU 601 for each function described in inspection result data 202 , namely for each function extracted from the received program, determines whether the function is a function permitted to be used according to security management table 507 a .
  • CPU 601 for each resource described in inspection result data 202 , determines whether the resource is a resource permitted to be accessed according to security management table 507 a.
  • CPU 601 determines that the program violates the security policy (security management table 507 a ) set by, for example a carrier of mobile packet communication network 40 , and does not permit relay of the program to mobile phone 50 (Step S 307 : NO). Consequently, CPU 601 cancels the transfer of the program (Step S 309 ), and sends to mobile phone 50 a message stating that the download of the program has been cancelled.
  • security policy security management table 507 a
  • CPU 601 determines that the received program meets the security policy set by the carrier of mobile packet communication network 40 , and permits the relay of the program to mobile phone 50 (Step S 307 : YES). Consequently, CPU 601 transfers the program to mobile phone 50 designated by the address information (Step S 308 ).
  • program inspection device 20 a pre-inspects the content of a program provided to mobile phone 50 via a network, and generates inspection result data 202 containing functions contained in the program and information on resources accessed when the program is executed.
  • Relay device 60 compares inspection result data 202 and security management table 507 a registering information for each function on whether that function may be used and information on each resource on whether that resource may be accessed; and thereby determines whether to relay the program to mobile phone 50 . Accordingly, relay device 60 , without analyzing the program to be relayed, only by comparing inspection result data 202 and security management table 507 a , can determine whether the program meets the security policy (security management table 507 a ) set in relay device 60 .
  • the determination process can be completed in relay device 60 by using a simple method and within a short time, thereby avoiding any delay in communications. Also, since transfer of a program violating a security policy is cancelled, provision of such a program to mobile phone 50 is prevented.
  • Functions registered in security management table 507 a and information on which functions may be used can be changed by a carrier of mobile packet communication network 40 or by an administrator of relay device 60 . This is the same for resources registered in security management table 507 a and information on which resources may be accessed.
  • CPU 501 if a determination in Step S 208 of FIG. 7 is negative, causes liquid crystal display unit 506 to display, as shown in FIG. 13 , a message that a program to be executed violates a security policy, and a message confirming whether the program should be executed with available functions limited (Step S 401 ). Responsive to these messages, a user instructs mobile phone 50 using operation input unit 505 to execute the program with available functions limited or to cancel execution of the program. The messages may be outputted as voice messages from mobile phone 50 .
  • CPU 501 if canceling execution of the program is instructed via operation input unit 505 (Step S 402 : NO), cancels execution of the program (Step S 403 ). On the other hand, if execution of the program is instructed via operation input unit 505 (Step S 402 : YES), CPU 501 reads the program from nonvolatile memory 507 and launches it (Step S 404 ). After that, CPU 501 determines whether the running program has been terminated (Step S 405 ), and until termination of the running program, limits functions available in the program in accordance with security management table 507 a (Step S 406 ). Security management table 507 a for limiting available functions corresponds to a security level set in mobile phone 50 at that time.
  • Step S 406 if CPU 501 identifies a function such as a function call and a system call when sequentially interpreting and running the program, CPU 501 determines whether the function is a function permitted to be used according to security management table 507 a . If the function is a function permitted to be used, CPU 501 permits the use of the function and continues the running of the program. On the other hand, if the function is a function not permitted to be used, CPU 501 does not permit the use of the function and suspends the running of the program.
  • a function such as a function call and a system call
  • CPU 501 monitors an access request to a resource occurring when sequentially interpreting and running the program, and determines whether the resource for the access request is a resource permitted to be accessed according to security management table 507 a . If the resource is a resource permitted to be accessed, CPU 501 permits an access to the resource and continues the running of the program. On the other hand, if the resource is a resource not permitted to be accessed, CPU 501 does not permit an access to the resource and suspends the running of the program.
  • mobile phone 50 can execute even a program violating a security policy by limiting available functions of the program.
  • the user In the cases stated above where a determination is made not as to whether program should be executed but as to whether the program meets a security policy, and the determination result is reported to a user, the user, on the basis of the reported determination result, deletes (uninstalls) the program from nonvolatile memory 507 or avoids execution of the program, which consequently maintains the security of mobile phone 50 . In this case, if the program violates the security policy, the names of functions not permitted to be used and information on resources not permitted to be accessed, which are contained in the program, may be reported to the user along with the determination result.
  • mobile phone 50 may cause liquid crystal display unit 506 to display a message confirming whether to delete the program, and if instructed by use of operation input unit 505 to delete the program, will uninstall the program from nonvolatile memory 507 .
  • relay device 60 when transferring a program to mobile phone 50 , may determine whether the program meets a security policy (security management table 507 a ) by comparing inspection result data 202 of the program and security management table 507 a , and send the determination data to mobile phone 50 along with the program.
  • a security policy security management table 507 a

Abstract

The present invention provides a technique of determining, in a receiving device or a relay device, using a simple method and within a short time, whether a program provided via a network is a program causing security concerns. Program inspection device 20 a pre-inspects the content of a program provided to mobile phone 50 via a network, and generates inspection result data 202 containing functions contained in the program and information on resources accessed when the program is executed. Mobile phone 50 has security management table 507 a registering information for each function on whether the function may be used and information on whether a resource may be accessed for each resource. Mobile phone 50 compares inspection result data 202 of a program received via a network and security management table 507 a, and thereby confirms whether the program causes security concerns when it is executed.

Description

    TECHNICAL FIELD
  • The present invention relates to a technique of ensuring security of an information device.
  • BACKGROUND ART
  • In an open network such as the Internet, people can freely publicize information or provide programs. Accordingly, there exists a possibility of a malicious program being provided via an open network to, for example, a communication terminal, and which if executed will result in a security breach with information stored in the terminal being read and sent out from the terminal. There are known in the art means to protect communication terminals from such programs. For example, JP2001-117769 discloses a program executing device wherein identification information (for example, an IP address or a URL) indicating reliable sources of programs in a memory in the program executing device; and if identification information indicating a source of a program received via a network is registered in the memory, execution of the program is permitted.
  • However, in the art disclosed in JP2001-117769, it is necessary to register all reliable program sending sources. Accordingly, each time a reliable program sending source is added or deleted, identification information stored in a memory must be updated. Moreover, since in a large network such as the Internet, there exists a large number of reliable program sending sources, it is substantially difficult to register in a memory of a terminal all identification information thereof. Further, even if it is possible to register in a memory in a terminal all such identification information, in order to do so it is necessary to increase a size of a memory used, particularly of that in a small communication terminal such as mobile phone, which results in an increase in manufacturing costs of such a terminal.
  • On the other hand, if security is enhanced by, for example, analyzing at a mobile terminal a content of a program received at the mobile terminal via a network to determine whether the program is a security threat, it is necessary for the mobile terminal to have a high level of computing power. Moreover, determination of security threats at the mobile terminal places a heavy load on a processing unit of the mobile terminal and takes a substantial amount of time to complete. Similarly, if at a relay device such as a server on a network, a content of a program received via a network is analyzed to thereby determine whether execution of the program in a communication terminal will constitute a security threat, it is necessary to provide the relay device with a high level of computing power. If the relay device is not provided with sufficient computing power, delays in communications are likely to occur.
  • The present invention has been made in view of the problems discussed above, and provides a technique of determining, at a receiving device or a relay device, whether a program provided via a network is a security threat, by using a simple method which can be quickly carried out.
  • DISCLOSURE OF INVENTION
  • To solve the problems, the present invention provides registering means for registering information on whether a function of a received program is permitted to be used; receiving means for receiving a program and function information indicating a function used in the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a program received by the receiving means includes a function not permitted to be used; and outputting means for outputting a result determined by the determining means.
  • The present invention also provides a program for causing a computer to function as a receiving device, and provides a computer-readable storage medium for recording the program. The program may be pre-installed in a memory of a computer, or it may be installed in a computer by way of communications conducted via a network, or be installed from the storage medium.
  • According to the present invention, a receiving device determines whether a prohibited function is present in a received program by comparing function information of the program and information registered by the registering means, and outputs the determination result.
  • The present invention also provides a receiving device comprising: registering means for registering information on whether a function of a received program is permitted to be used; receiving means for receiving a program and function information indicating a function used in the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to execute a program received by the receiving means; and executing means for executing a program if the determining means determines to execute the program. The present invention also provides a program for causing a computer to function as a receiving device, and provides a computer-readable storage medium for recording the program.
  • According to the present invention, a receiving device determines whether a received program should be executed by comparing function information of the program and information registered by the registering means.
  • The present invention also provides a receiving device comprising: registering means for registering means for registering information on whether a function of a received program is permitted to be used; first receiving means for receiving, before receiving a program, function information indicating a function used in the program; determining means for determining whether to receive a program, by comparing function information received by the first receiving means and information registered by the registering means; second receiving means for receiving a program if the determining means determines to receive the program; and executing means for executing a program received by the second receiving means. The present invention also provides a program for causing a computer to function as a receiving device, and a computer-readable storage medium for recording the program.
  • According to the present invention, a receiving device determines whether a program should be received by comparing function information of the program and information registered by the registering means.
  • The present invention provides a relay device comprising: registering means for registering information on whether a function of a program provided via a network is permitted to be used; receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to relay a program received by the receiving means; and sending means for sending a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program.
  • The present invention also provides a program for causing a computer to function as a relay device, and provides a computer-readable storage medium for recording the program. The program may be pre-installed in a memory of a computer, or it may be installed in a computer by way of communications conducted via a network, or be installed from the storage medium.
  • According to the present invention, a relay device determines whether to relay a received program by comparing function information of the program and information registered by the registering means.
  • The present invention also provides a relay device comprising: registering means for registering information on whether a function of a program provided via a network is permitted to be used; receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program; determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a function not permitted to be used is used in a program received by the receiving means; and sending means for sending a determination result by the determining means and a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program. The present invention also provides a program for causing a computer to function as a relay device, and provides a computer-readable storage medium for recording the program.
  • According to the present invention, a relay device determines whether a prohibited function is present in a received program by comparing function information of the program and information registered by a registering means, and sends the determination result with the program.
  • According to the present invention, it can be readily determined at a receiving device or a relay device whether a program provided via a network is one that poses a security threat, by employing a simple method and within a short time.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram illustrating a configuration of a communication system according to the first embodiment.
  • FIG. 2 is a diagram illustrating a data structure of inspection result data 202 according to the first embodiment.
  • FIG. 3 is a block diagram illustrating a hardware configuration of mobile phone 50 according to the first embodiment.
  • FIG. 4 is a diagram illustrating a data structure of security management table 507 a according to the first embodiment.
  • FIG. 5 is a sequence chart illustrating operations of each component forming communication system 1 according to the first embodiment, which are performed until a program and inspection result data 202 thereof are downloaded to mobile phone 50.
  • FIG. 6 is a diagram illustrating a screen displayed on a mobile phone 50 when a security level is set according to the first embodiment.
  • FIG. 7 is a flowchart illustrating operations for determining whether to execute a program received via a network, which operations are carried out in mobile phone 50 according to the first embodiment.
  • FIG. 8 is a diagram illustrating a screen displayed on mobile phone 50 when execution of a program is not permitted according to the first embodiment.
  • FIG. 9 is a block diagram illustrating a hardware configuration of relay device 60 according to the second embodiment.
  • FIG. 10 is a flowchart illustrating operations of determining whether to execute a program received via a network, which operations are carried out in relay device 60 according to the second embodiment.
  • FIG. 11 is a block diagram illustrating a configuration of communication system 2 according to the modification (1).
  • FIG. 12 is a flowchart illustrating operations carried out in mobile phone according to the modification (2).
  • FIG. 13 is a diagram illustrating a screen displayed on mobile phone 50 according to the modification (2).
  • BEST MODE FOR CARRYING OUT THE INVENTION
  • Below, with reference to the drawings, embodiments of the present invention will be described.
  • A. FIRST EMBODIMENT
  • FIG. 1 is a block diagram illustrating a configuration of communication system according to the first embodiment. In FIG. 1, content provider 10 is a service provider that provides content to mobile phone 50. Content server 10 a conducts packet communication with mobile phone 50 via Internet 30 and mobile packet communication network 40. Content server 10 a stores programs for mobile phone 50 and inspection result data 202 which are obtained as a result of inspection of the program in inspection institution 20. The programs stored in content server 10 a may be software containing image or audio data used when a program is executed.
  • Inspection institution 20 is an institution which inspects a program provided to mobile phone 50 upon an inspection request from content provider 10, and program inspection device 20 a stores security evaluation list 201. In security evaluation list 201 there are listed functions such as a function call and a system call which may compromise security in mobile phone 50 if provided with a program via a network and the program is executed. Security evaluation list 201 also lists resources accessible by mobile phone 50 which may compromise security in mobile phone 50 if accessed in accordance with a program provided via a network.
  • Program inspection device 20 a analyzes a program to be inspected with reference to security evaluation list 201, and extracts from the program functions listed in security evaluation list 201. Program inspection device 20 a also identifies, among resources accessed when the program is executed, resources listed in security evaluation list 201. Subsequently, program inspection device 20 a generates inspection result data 202 containing the names of the extracted functions and information on the identified resources (for example, URLs or paths indicating where the resources have been stored or identifiers assigned to the resources). Inspection result data 202 is returned to content provider 10 and stored along with the program in content server 10 a.
  • Program inspection device 20 a may record as inspection result data 202 all functions contained in a program to be inspected, or may record all resources accessed when a program to be inspected is executed.
  • Mobile phone 50 is a communication terminal (receiving device) served by mobile packet communication network 40, and can download a program from content server 10 a and execute it.
  • FIG. 2 is a diagram illustrating a data structure of inspection result data 202. As shown in FIG. 2, inspection result data 202 contains the name of an inspected program, the name of a hash algorithm used for calculating a hash value of the program, and the calculated hash value. Inspection result data 202 also contains a list of the name of functions contained in the program and a list of information on resources accessed when the program is executed, which are obtained as a result of an analysis of the program using security evaluation list 201. The hash value contained in inspection result data 202 is used for verifying that the program has not been changed or falsified after inspection by program inspection device 20 a.
  • FIG. 3 is a block diagram illustrating a hardware configuration of mobile phone 50. CPU 501 executes a variety of programs stored in ROM 502 and nonvolatile memory 507, and thereby controls components of mobile phone 50. ROM 502 stores programs for controlling mobile phone 50. RAM 503 is used as a work area of CPU 501. Wireless communication unit 504, under the control of CPU 501, controls wireless communication with a base station (not shown) of mobile packet communication network 40. Operation input unit 505 consists of a plurality of keys, and outputs an operation signal to CPU 501 in response to an operation of the keys. Liquid crystal display unit 506 consists of a liquid crystal display panel and a driving circuit for controlling a display of the liquid crystal display panel.
  • Nonvolatile memory 507 stores software such as an operating system and a WWW (World Wide Web) browser for mobile phone 50. Nonvolatile memory 507 also stores programs downloaded from content server 10 a and stores inspection result data 202 thereof. Nonvolatile memory further stores security management table 507 a.
  • Security management table 507 a, as shown in FIG. 4, registers, among functions contained in programs for mobile phone 50, the names of functions permitted to be used when a program received via a network is executed, and the names of functions not permitted to be used when a program received via a network is executed. Security management table 507 a also registers, among resources accessible by mobile phone 50, information on resources permitted to be accessed when a program received via a network is executed, and information on resources not permitted to be accessed when a program received via a network is executed. As to a function and a resource which require asking a user whether to execute a program, a term “user confirmation” is registered in the item “permission” column of security management table 507 a.
  • Nonvolatile memory 507 stores a plurality of security management tables 507 a for each security level available in mobile phone 50 such as security management table 507 a for “Level 1” or security management table 507 a for “Level 2”. In mobile phone 50, when it is determined whether to execute a program received via a network, security management table 507 a corresponding to a security level presently set in mobile phone 50 is used among the plurality of security management tables 507 a. The security level is set by a user of mobile phone 50.
  • Functions registered in security management table 507 a and information on whether to permit uses of the functions may be changed by a user of mobile phone 50. This is the same for resources registered in security management table 507 a and information on whether to permit access of the resources.
  • Operations of the first embodiment will now be described below.
  • FIG. 5 is a sequence chart illustrating operations of each component forming communication system 1, which are performed until a program and corresponding inspection result data 202 are downloaded to mobile phone 50. As shown in FIG. 5, a program for mobile phone 50 written by content provider 10 is sent along with an inspection request from content server 10 a to program inspection device 20 a (Step S101).
  • Program inspection device 20 a, upon receipt of the program and the inspection request, analyzes the received program (Step S102). Program inspection device 20 a extracts from the program functions listed in security evaluation list 201, and identifies resources which are accessed if the program is executed, and which are listed in security evaluation list 201. Program inspection device 20 a also calculates a hash value of the program using a hash algorithm. Program inspection device 20 a then generates inspection result data 202 containing the names of the extracted functions, the information on the identified resources, the calculated hash value, the name of the algorithm used, and the file name of the program (Step S103).
  • Subsequently, program inspection device 20 a attaches an electronic signature to the generated inspection result data 202 (Step S104). This electronic signature is used for verifying in mobile phone 50 that the program has not been changed or falsified. After that, program inspection device 20 a returns inspection result data 202 with the electronic signature to content server 10 a (Step S105). Content server 10 a, upon receipt of inspection result data 202, stores inspection result data 202 with the inspected program in a memory (Step S106), and renders the program and inspection result data 202 downloadable by mobile phone 50.
  • In mobile phone 50, a security level is set (Step S107). In the setting of a security level, a screen shown in FIG. 6 is displayed on liquid crystal display unit 506, and a user can select a security level of mobile phone 50 from “Level 0 (Nothing)” to “Level 5” using operation input unit 505. The security level set by the user is stored in nonvolatile memory 507.
  • If mobile phone 50 downloads a program from content server 10 a, a WWW browser is launched in mobile phone 50 (Step S108), and packet communications are started between mobile phone 50 and content server 10 a. When the user selects a program to be downloaded using operation input unit 505, a signal requesting download of the program is sent from mobile phone 50 to content server 10 a (Step S109). Content server 10 a reads the requested program and inspection result data 202 of the program from memory, and sends them to mobile phone 50 (Steps S110 and S111). Mobile phone 50, upon receipt of the program and inspection result data 202, stores them in nonvolatile memory 507 (Step S112).
  • FIG. 7 is a flowchart illustrating operations of determining whether to execute a program received via a network, and which are carried out in mobile phone 50. The operations are carried out by CPU 501 if the execution of a program received via a network is instructed in mobile phone 50. As shown in FIG. 7, CPU 501 reads from nonvolatile memory 207 inspection result data 202 of a program the execution of which has been instructed (Step S201).
  • CPU 501 verifies an electronic signature of inspection result data 202 (Step S202), and thereby confirms that inspection result data 202 has been generated by inspection institution 20, and that inspection result data 202 is an authentic inspection result data which has not been falsified. If, as a result of the verification of the electronic signature, it is found that inspection result data 202 is not authentic (Step S203: NO), CPU 501 cancels the execution of the program (Step S210), and causes liquid crystal display unit 506 to display a message stating that the execution of the program has been cancelled because falsification has been found in inspection result data 202.
  • On the other hand, if inspection result data is verified to be authentic (Step S203: YES), CPU 501 calculates a hash value of the program using a hash algorithm described in inspection result data 202. CPU 501 compares the calculated hash value and a hash value described in inspection result data 202 (Step S204). As a result of the comparison, if the hash values do not match (Step S205: NO), CPU 501 cancels the execution of the program (Step S210), and causes liquid crystal display unit 506 to display a message stating that execution of the program has been cancelled because falsification has been found in the program.
  • On the other hand, if the hash values match (Step S205: YES), CPU 501 identifies a value of a security level currently set in mobile phone 50, and reads from nonvolatile memory 507 security management table 507 a corresponding to the identified value of the security level (Step S206). CPU 501 compares the read security management table 507 a and inspection result data 202 read in Step S201 (Step S207), and thereby determines whether to execute the program (Step S208).
  • To explain the operations in Steps S207 and S208 specifically, CPU 501, for each function described in inspection result data 202, namely for each function extracted from the program to be executed, determines whether the function is a function permitted to be used in security management table 507 a. Similarly, CPU 501, for each resource described in inspection result data 202, determines whether the resource is a resource permitted to be accessed in security management table 507 a.
  • As a result, if any function that are not permitted to be used is contained in inspection result data 202, or if any resource not permitted to be accessed is contained in inspection result data 202, CPU 501 determines that the program violates the security policy (security management table 507 a) set by a user, and does not permit the execution of the program (Step S208: NO). Consequently, CPU 501 cancels the execution of the program (Step S210), and causes liquid crystal display unit 506 to display a message as shown in FIG. 8.
  • For example, assuming that inspection result data 202 is as shown in FIG. 2 and security management table 507 a is as shown in FIG. 4, since inspection result data 202 contains a function “Function 1 ( )” which is not permitted to be used according to security management table 507 a, and a resource “Local/UserData/AddressBook” which is not permitted to be accessed according to security management table 507 a, a program corresponding to inspection result data 202 is not permitted to be executed in mobile phone 50.
  • On the other hand, if all of the functions described in inspection result data 202 are functions that are permitted to be used according to security management table 507 a, and all resources described in inspection result data 202 are resources permitted to be accessed according to security management table 507 a, CPU 501 determines that the program meets the security policy set by the user, and permits the execution of the program (Step S208: YES). Consequently, CPU 501 reads the program permitted to be executed from nonvolatile memory 507, launches the program (Step S209), and proceeds with operations in accordance with the program.
  • If inspection result data 202 contains a resource requiring a user confirmation as a resource “http://www.xxx.co.jp” in security management table 507 a of FIG. 4, CPU 501 generates a message asking a user whether to execute a program, causes liquid crystal display unit 506 to display it, and determines the execution of the program in accordance with an instruction from operation input unit 505.
  • As stated above, in the present embodiment, program inspection device 20 a pre-inspects the content of a program provided to mobile phone 50 via a network, and generates inspection result data 202 containing functions contained in the program and information on resources accessed when the program is executed. Mobile phone 50 compares inspection result data 202 and security management table 507 a registering information on whether a function may be used for each function and information on whether a resource may be accessed for each resource, and thereby determines whether to execute the program received via the network. Accordingly, mobile phone 50, without analyzing the received program, only by comparing inspection result data 202 and security management table 507 a, can determine whether the program meets the security policy (security management table 507 a) set in mobile phone 50. Consequently, the determination process can be completed in mobile phone 50 by using a simple method and within a short time.
  • Security management table 507 a for determining whether to execute a received program can be changed easily by changing a security level. Accordingly, even if a program violates a security policy and thereby is determined not permitted to be executed, if a user determines that the program is valid, the program can be executed in mobile phone by temporarily lowering the security level. As stated above, in the present embodiment, flexible setting of a security level of mobile phone 50 relative to a received program can be carried out in accordance with a user's wishes.
  • B. SECOND EMBODIMENT
  • Below, the second embodiment of the present invention will be described.
  • In the present embodiment, elements common to the first embodiment are denoted by like symbols, and descriptions common to the first embodiment will be omitted.
  • FIG. 9 is a block diagram illustrating a hardware configuration of relay device 60 relaying packet communications between content server 10 a and mobile phone 50. Relay device 60 may be provided on either of Internet 30 or mobile packet communication network 40. In FIG. 9, communication interface 604, under the control of CPU 601, controls packet communication with content server 10 a or mobile phone 50. Operation input unit 605 has a mouse and a keyboard, and outputs an operation signal to CPU 601 in accordance with operations carried out via the mouse and the keyboard. Display unit 606 is a LCD or CRT display.
  • HD (Hard Disk) 607 stores security management table 507 a explained in the first embodiment. Relay device 60 of the present embodiment, using security management table 507 a, determines whether to relay a program sent from content server 10 a to mobile phone 50. Relay device 60 receives, along with the program, inspection result data 202 of the program and destination information indicating the destination of the program from content server 10 a. Inspection result data 202 is generated by program inspection device 20 a explained in the first embodiment. The address information is a communication address assigned to mobile phone 50 such as an IP address.
  • In the present embodiment, a security level in relay device 60 is set by a carrier of mobile packet communication network or an administrator of relay device 60. HD 607 stores different security management tables 507 a for each security level as described in the first embodiment, and in accordance with the security level set in relay device 60, security management table 507 a for determining whether to relay a program is determined.
  • FIG. 10 is a flowchart illustrating operations performed for determining whether to relay a program which are carried out in relay device 60. The operations are performed by CPU 601 if relay device 60 receives a program and inspection result data 202 thereof transmitted from content server 10 a to mobile phone 50. As shown in FIG. 10, CPU 601 verifies an electronic signature of inspection result data 202 (Step S301). If upon verification of the electronic signature, it is confirmed that inspection result data 202 is not authentic (Step S302: NO), CPU 601 cancels transfer of the program to mobile phone 50 (Step S309), and sends to mobile phone 50 a message stating that the download of the program has been cancelled because falsification has been found in inspection result data 202.
  • On the other hand, if inspection result data is verified to be authentic (Step S302: YES), CPU 601 calculates a hash value of the program using a hash algorithm described in inspection result data 202, and compares the calculated hash value and a hash value described in inspection result data 202 (Step S303). If as a result of the comparison, it is determined that the hash values do not match (Step S304: NO), CPU 601 cancels transfer of the program to mobile phone 50 (Step S309), and sends to mobile phone 50 a message stating that download of the program has been cancelled because falsification has been found in the program.
  • On the other hand, if the hash values match (Step S304: YES), CPU 601 identifies a value of a security level set in relay device 60 at the time, and reads from HD 607 security management table 507 a corresponding to the identified value of the security (Step S305). CPU 601 compares the read security management table 507 a and the received inspection result data 202 (Step S306), and thereby determines whether to relay the program to mobile phone 50 (Step S307).
  • To explain the operations in Steps S306 and S307 specifically, CPU 601, for each function described in inspection result data 202, namely for each function extracted from the received program, determines whether the function is a function permitted to be used according to security management table 507 a. Similarly, CPU 601, for each resource described in inspection result data 202, determines whether the resource is a resource permitted to be accessed according to security management table 507 a.
  • As a result, if any functions that are not permitted to be used exist in inspection result data 202, or if any resources that are not permitted to be accessed exist in inspection result data 202, CPU 601 determines that the program violates the security policy (security management table 507 a) set by, for example a carrier of mobile packet communication network 40, and does not permit relay of the program to mobile phone 50 (Step S307: NO). Consequently, CPU 601 cancels the transfer of the program (Step S309), and sends to mobile phone 50 a message stating that the download of the program has been cancelled.
  • On the other hand, if all functions described in inspection result data 202 are functions permitted to be used according to security management table 507 a, and all resources described in inspection result data 202 are resources permitted to be accessed according to security management table 507 a, CPU 601 determines that the received program meets the security policy set by the carrier of mobile packet communication network 40, and permits the relay of the program to mobile phone 50 (Step S307: YES). Consequently, CPU 601 transfers the program to mobile phone 50 designated by the address information (Step S308).
  • As stated above, in the present embodiment, program inspection device 20 a pre-inspects the content of a program provided to mobile phone 50 via a network, and generates inspection result data 202 containing functions contained in the program and information on resources accessed when the program is executed. Relay device 60 compares inspection result data 202 and security management table 507 a registering information for each function on whether that function may be used and information on each resource on whether that resource may be accessed; and thereby determines whether to relay the program to mobile phone 50. Accordingly, relay device 60, without analyzing the program to be relayed, only by comparing inspection result data 202 and security management table 507 a, can determine whether the program meets the security policy (security management table 507 a) set in relay device 60. Consequently, the determination process can be completed in relay device 60 by using a simple method and within a short time, thereby avoiding any delay in communications. Also, since transfer of a program violating a security policy is cancelled, provision of such a program to mobile phone 50 is prevented.
  • Functions registered in security management table 507 a and information on which functions may be used can be changed by a carrier of mobile packet communication network 40 or by an administrator of relay device 60. This is the same for resources registered in security management table 507 a and information on which resources may be accessed.
  • C. MODIFICATIONS
    • (1) In the first embodiment, inspection result data 202 is sent to mobile phone 50 along with a program. However, as shown in FIG. 11, there may be provided inspection result registering server 70 for registering inspection result data 202 of each program inspected in inspection institution 20. In this case, mobile phone 50, after downloading a program from content server 10 b, obtains inspection result data 202 of the program from inspection result registering server 70. This is the same as in the second embodiment, namely, inspection result registering server 70 registers inspection result data 202 of each program, and relay device 60, if receiving a program to be transferred to mobile phone 50 from content server 10 b, obtains inspection result data 202 of the program from inspection result registering server 70. Inspection result registering server 70 may be provided either on mobile packet communication network 40 or in inspection institution 20.
    • (2) In the first embodiment, when a determination in Step S208 of FIG. 7 is negative, operations may be changed as shown in FIG. 12.
  • Namely, CPU 501, if a determination in Step S208 of FIG. 7 is negative, causes liquid crystal display unit 506 to display, as shown in FIG. 13, a message that a program to be executed violates a security policy, and a message confirming whether the program should be executed with available functions limited (Step S401). Responsive to these messages, a user instructs mobile phone 50 using operation input unit 505 to execute the program with available functions limited or to cancel execution of the program. The messages may be outputted as voice messages from mobile phone 50.
  • CPU 501, if canceling execution of the program is instructed via operation input unit 505 (Step S402: NO), cancels execution of the program (Step S403). On the other hand, if execution of the program is instructed via operation input unit 505 (Step S402: YES), CPU 501 reads the program from nonvolatile memory 507 and launches it (Step S404). After that, CPU 501 determines whether the running program has been terminated (Step S405), and until termination of the running program, limits functions available in the program in accordance with security management table 507 a (Step S406). Security management table 507 a for limiting available functions corresponds to a security level set in mobile phone 50 at that time.
  • To explain the operations in Step S406 specifically, if CPU 501 identifies a function such as a function call and a system call when sequentially interpreting and running the program, CPU 501 determines whether the function is a function permitted to be used according to security management table 507 a. If the function is a function permitted to be used, CPU 501 permits the use of the function and continues the running of the program. On the other hand, if the function is a function not permitted to be used, CPU 501 does not permit the use of the function and suspends the running of the program.
  • Also, CPU 501 monitors an access request to a resource occurring when sequentially interpreting and running the program, and determines whether the resource for the access request is a resource permitted to be accessed according to security management table 507 a. If the resource is a resource permitted to be accessed, CPU 501 permits an access to the resource and continues the running of the program. On the other hand, if the resource is a resource not permitted to be accessed, CPU 501 does not permit an access to the resource and suspends the running of the program.
  • According to the configuration stated above, mobile phone 50 can execute even a program violating a security policy by limiting available functions of the program.
    • (3) Security management table 507 a may register only functions permitted to be used and those not permitted to be used; while security management table 507 a may register only information on resources permitted to be accessed and those not permitted to be accessed. Further, security management table 507 a may register only functions permitted to be used or only functions not permitted to be used; while security management table 507 a may register only resources permitted to be accessed or only resources not permitted to be accessed.
    • (4) In the second embodiment, HD 607 of relay device 60 may register for each mobile phone 50 a security level set by a user of mobile phone 50. In this case, relay device 60 may identify a security level of mobile phone 50 to which a program is to be transferred, and determine whether to relay the program using security management table 507 a corresponding to the security level.
    • (5) In the first embodiment, nonvolatile memory 507 of mobile phone 50 may store a security management table for a program to which inspection result data 202 has not been attached. Also, nonvolatile memory 507, if there are a plurality of inspection institutions similar to inspection institution 20, may store a security management table for a program to which inspection result data generated in an inspection institution other than inspection institution 20 has been attached. This is the as same in the second embodiment; namely, HD 607 may store a security management table for a program to which inspection result data 202 has not been attached, or a security management table for a program to which inspection result data generated in an inspection institution other than inspection institution 20 has been attached.
    • (6) In the first embodiment, inspection result data 202 may further contain provider identification information for identifying a provider of a program such as the name of a content provider or a URL of a program sending source; and nonvolatile memory 507 of mobile phone 50 may store different security management tables 507 a for each provider identification information. In this case, mobile phone 50 may determine whether to execute a received program using security management table 507 a corresponding to a provider identification information contained in received inspection result data 202. This is the same in the second embodiment, namely, inspection result data 202 may further contain a provider identification information, HD 607 of relay device 60 may store different security management tables 507 a for each provider identification information; and relay device 60 may determine whether to relay a received program using security management table 507 a corresponding to a provider identification information contained in received inspection result data 202.
    • (7) In the first embodiment, mobile phone 50, on completion of downloading a program, may determine whether the program meets a security policy (security management table 507 a) by comparing inspection result data 202 of the program and security management table 507 a, and cause liquid crystal display unit 506 to display the determination result. The determination result may be outputted as voice messages from mobile phone 50. Also, mobile phone 50, when instructed by a user using operation input unit 505 to check the safety of a received program, may determine whether the program meets a security policy by comparing inspection result data 202 of the program and security management table 507 a, and output the determination result.
  • In the cases stated above where a determination is made not as to whether program should be executed but as to whether the program meets a security policy, and the determination result is reported to a user, the user, on the basis of the reported determination result, deletes (uninstalls) the program from nonvolatile memory 507 or avoids execution of the program, which consequently maintains the security of mobile phone 50. In this case, if the program violates the security policy, the names of functions not permitted to be used and information on resources not permitted to be accessed, which are contained in the program, may be reported to the user along with the determination result. Alternatively, if the program violates the security policy, mobile phone 50 may cause liquid crystal display unit 506 to display a message confirming whether to delete the program, and if instructed by use of operation input unit 505 to delete the program, will uninstall the program from nonvolatile memory 507.
  • In the second embodiment, relay device 60, when transferring a program to mobile phone 50, may determine whether the program meets a security policy (security management table 507 a) by comparing inspection result data 202 of the program and security management table 507 a, and send the determination data to mobile phone 50 along with the program.
    • (8) In the first embodiment, mobile phone 50, before downloading a program from content server 10 a, may download only inspection result data 202 of the program from content server 10 a. In this case, mobile phone 50 compares received inspection result data 202 and security management table 507 a, and thereby determines whether the program to be downloaded meets a security policy (security management table 507 a). As a result of the determination, if the program meets the security policy, mobile phone 50 downloads the program from content server 10 a. On the other hand, if the program violates the security policy, mobile phone 50 cancels download of the program. According to this configuration, if a program to be downloaded violates a security policy, downloading the program is prevented, and consequently unnecessary packet communications can be avoided.
    • (9) In the first and second embodiment, a program may be distributed to mobile phone 50 instead of being downloaded. A receiving device according to the present invention may be applied to a wireless terminal communicating via a public wireless LAN or a personal computer communicating via the Internet. A relay device according to the present invention may be applied to a gateway server, a proxy server, or a switching center or a base station provided on mobile packet communication network 40. A program for causing a computer such as mobile phone 50 or relay device 60 to execute processes according to the present invention may be installed in a computer via a network, or may be stored in a variety of computer-readable storage media for distribution.

Claims (18)

1. A receiving device comprising:
registering means for registering information on whether a function of a received program is permitted to be used;
receiving means for receiving a program and function information indicating a function used in the program;
determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a program received by the receiving means includes a function not permitted to be used; and
outputting means for outputting a result determined by the determining means.
2. A receiving device comprising:
registering means for registering information on whether a function of a received program is permitted to be used;
receiving means for receiving a program and function information indicating a function used in the program;
determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to execute a program received by the receiving means; and
executing means for executing a program if the determining means determines to execute the program.
3. A receiving device comprising:
registering means for registering information on whether a function of a received program is permitted to be used;
receiving means for receiving a program and function information indicating a function used in the program;
determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to execute a program received by the receiving means; and
outputting means for outputting a message asking whether to execute a program while limiting available functions, if the determining means determines not to execute the program.
operating means;
executing means for executing a program if execution of the program is instructed via the operating means in response to a message outputted by the outputting means; and
limiting means for limiting functions available in a program executed by the executing means, in accordance with information registered by the registering means.
4. A receiving device according to claim 2, wherein
the determining means compares the function information received by the receiving means and the information registered by the registering means, and if a function not permitted to be used is not used by the program received by the receiving means, permits execution of the program.
5. A receiving device according to claim 1, wherein:
the registering means registers information on whether a function of a received program is permitted to be used; and
the function information is information on a function contained in the program received by the receiving means.
6. A receiving device according to claim 1, wherein:
the registering means registers information on whether a resource of a received program is permitted to be accessed; and
the function information is information on a resource accessed in accordance with the program received by the receiving means.
7. A receiving device comprising:
registering means for registering information on whether a function of a program provided via a network is permitted to be used;
first receiving means for receiving, before receiving a program, function information indicating a function used in the program;
determining means for determining whether to receive a program, by comparing function information received by the first receiving means and information registered by the registering means;
second receiving means for receiving a program if the determining means determines to receive the program; and
executing means for executing a program received by the second receiving means.
8. A relay device comprising:
registering means for registering information on whether a function of a program provided via a network is permitted to be used;
receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program;
determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether to relay a program received by the receiving means; and
sending means for sending a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program.
9. A relay device according to claim 8, wherein
the determining means compares the function information received by the receiving means and the information registered by the registering means, and if a function not permitted to be used is not used in the program received by the receiving means, permits relay of the program.
10. A relay device comprising:
registering means for registering information on whether a function of a program provided via a network is permitted to be used;
receiving means for receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program;
determining means for determining, by comparing function information received by the receiving means and information registered by the registering means, whether a function not permitted to be used is used in a program received by the receiving means; and
sending means for sending a determination result by the determining means and a program to a destination designated by destination information received by the receiving means, if the determining means determines to relay the program.
11. A relay device according to claim 8, wherein:
the registering means registers information on whether a function of the program provided via a network is permitted to be used; and
the function information is information on a function contained in the program received by the receiving means.
12. A relay device according to claim 8, wherein:
the registering means registers information on whether a resource in the program provided via a network is permitted to be accessed; and
the function information is information on a resource accessed in accordance with the program received by the receiving means.
13. A program for causing a computer to execute:
a first step of receiving a program and function information indicating a function used in the program;
a second step of determining, by comparing function information received in the first step and information on whether a function of a received is permitted to be used, which is pre-registered in memory, whether a function not permitted to be used is used in a program received in the first step; and
a third step of outputting a determination result in the second step.
14. A program for causing a computer to execute:
a first step of receiving a program and function information indicating a function used in the program;
a second step of determining, by comparing function information received in the first step and information on whether a function of a received program is permitted to be used, which is pre-registered in memory, whether to execute a program received in the first step; and
a third step of executing a program if it is determined in the second step to execute the program.
15. A program for causing a computer to execute:
a first step of receiving, before receiving a program, function information indicating a function used in the program;
a second step of determining, by comparing function information received in the first step and information on whether a function of a received program is permitted to be used, which is pre-registered in memory, whether to receive a program associated with the function information;
a third step of receiving a program if it is determined in the second step to receive the program; and
a fourth step of executing a program received in the third step.
16. A program for causing a computer to execute:
a first step of receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program;
a second step of determining, by comparing function information received in the first step and information on whether a function of a program provided via a network is permitted to be used, which is pre-registered in memory, whether to relay a program received in the first step; and
a third step of sending a program to a destination designated by destination information received in the first step, if it is determined in the second step to relay of program.
17. A program for causing a computer to execute:
a first step of receiving a program, function information indicating a function used in the program, and destination information indicating a destination of the program;
a second step of determining, by comparing function information received in the first step and information on whether a function of a program provided via a network is permitted to be used, which is pre-registered in memory, whether a function not permitted to be used is used in a program received in the first step; and
a third step of sending a determination result in the second step and a program to a destination designated by destination information received in the first step, if it is determined in the second step to relay the program.
18. A computer-readable storage medium recording a program according to claim 13.
US10/587,609 2004-02-05 2005-02-04 Security ensuring by program analysis on information device and transmission path Active 2028-07-20 US8490183B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2004-029928 2004-02-05
JP2004029928A JP4164036B2 (en) 2004-02-05 2004-02-05 Ensuring security on the receiving device for programs provided via the network
PCT/JP2005/002104 WO2005076105A1 (en) 2004-02-05 2005-02-04 Security ensuring by program analysis on information device and transmission path

Publications (2)

Publication Number Publication Date
US20070157310A1 true US20070157310A1 (en) 2007-07-05
US8490183B2 US8490183B2 (en) 2013-07-16

Family

ID=34835973

Family Applications (1)

Application Number Title Priority Date Filing Date
US10/587,609 Active 2028-07-20 US8490183B2 (en) 2004-02-05 2005-02-04 Security ensuring by program analysis on information device and transmission path

Country Status (4)

Country Link
US (1) US8490183B2 (en)
JP (1) JP4164036B2 (en)
CN (1) CN100495286C (en)
WO (1) WO2005076105A1 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070220137A1 (en) * 2006-03-17 2007-09-20 Chess David M Computer system evaluation
US20080083031A1 (en) * 2006-12-20 2008-04-03 Microsoft Corporation Secure service computation
US20090135451A1 (en) * 2005-09-13 2009-05-28 Canon Kabushiki Kaisha Image forming apparatus, control method therefor, and program
US20100083006A1 (en) * 2007-05-24 2010-04-01 Panasonic Corporation Memory controller, nonvolatile memory device, nonvolatile memory system, and access device
US20100146116A1 (en) * 2008-12-10 2010-06-10 Jeong Young Ho Method of controlling download load of secure micro client in downloadable conditional access system
US20120054864A1 (en) * 2005-04-22 2012-03-01 Christopher Scott Linn Security methods and systems
US20120240238A1 (en) * 2011-03-18 2012-09-20 International Business Machines Corporation System and Method to Govern Data Exchange with Mobile Devices
US8955152B1 (en) * 2010-09-07 2015-02-10 Symantec Corporation Systems and methods to manage an application
US9043863B1 (en) 2010-09-07 2015-05-26 Symantec Corporation Policy enforcing browser
US20160072825A1 (en) * 2013-04-15 2016-03-10 Giesecke & Devrient Gmbh Mobile Station Comprising Security Resources with Different Security Levels
US9350761B1 (en) 2010-09-07 2016-05-24 Symantec Corporation System for the distribution and deployment of applications, with provisions for security and policy conformance
US9501646B2 (en) 2012-09-26 2016-11-22 Mitsubishi Electric Corporation Program verification apparatus, program verification method, and computer readable medium
EP2486509A4 (en) * 2009-10-09 2016-11-30 Nokia Technologies Oy Platform security

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2336169A1 (en) 2000-04-21 2011-06-22 New England Medical Center Hospital G protein coupled receptor (GPCR) agonists and antagonists and methods of activating and inhibiting GPCR using the same
US7696168B2 (en) 2000-04-21 2010-04-13 Tufts Medical Center, Inc. G protein coupled receptor agonists and antagonists and methods of activating and inhibiting G protein coupled receptors using the same
US8990929B2 (en) * 2006-08-21 2015-03-24 Blackberry Limited Auditing application activities
EP1892620B1 (en) * 2006-08-21 2017-04-19 BlackBerry Limited Auditing application activities
EP1956509A1 (en) 2007-02-06 2008-08-13 Research In Motion Limited System and method for setting application permissions
US8856859B2 (en) 2007-02-06 2014-10-07 Blackberry Limited System and method for setting application permissions
JP5142551B2 (en) * 2007-02-22 2013-02-13 キヤノン株式会社 Electronic document processing apparatus, electronic document processing method, and computer program
US20100138896A1 (en) * 2007-04-05 2010-06-03 Atsushi Honda Information processing system and information processing method
KR100951046B1 (en) * 2007-12-11 2010-04-05 한국전자통신연구원 Download server apparatus for transmitting secure micro client software using data carousel protocol and method for transmitting and receiving secure micro client software
JP5449905B2 (en) * 2009-07-29 2014-03-19 フェリカネットワークス株式会社 Information processing apparatus, program, and information processing system
JP2011096050A (en) * 2009-10-30 2011-05-12 Kyocera Mita Corp Method, program and apparatus for preparing installer, and installer system
KR101051641B1 (en) * 2010-03-30 2011-07-26 주식회사 안철수연구소 Mobile communication terminal and behavior based checking virus program method using the same
JP2012008732A (en) * 2010-06-23 2012-01-12 Kddi Corp Installation control device and program
RU2477520C1 (en) 2012-03-14 2013-03-10 Закрытое акционерное общество "Лаборатория Касперского" System and method for device configuration-based dynamic adaptation of antivirus application functional
US20130339334A1 (en) * 2012-06-15 2013-12-19 Microsoft Corporation Personalized search engine results
EP2909775B1 (en) * 2012-10-19 2022-01-26 McAfee, LLC Mobile application management
JP6236816B2 (en) * 2013-03-15 2017-11-29 株式会社リコー Image processing system, information processing apparatus, and program
US9202057B2 (en) * 2013-08-30 2015-12-01 Symantec Corporation Systems and methods for identifying private keys that have been compromised
JP5702458B2 (en) * 2013-12-27 2015-04-15 フェリカネットワークス株式会社 Information processing apparatus, program, and information processing system
KR102412436B1 (en) * 2014-11-26 2022-06-24 삼성전자주식회사 Electronic device for managing use of data from other electronic devcie and method for controlling thereof
JP6300896B2 (en) * 2016-12-22 2018-03-28 キヤノン株式会社 Image processing apparatus, control method therefor, and program
US20200356662A1 (en) * 2018-01-31 2020-11-12 Sony Corporation Information processing apparatus and information processing method, and computer program
CN113678128A (en) * 2019-04-16 2021-11-19 三菱电机株式会社 Data processing system, data processing apparatus, and method for verifying application program
JP7448005B2 (en) 2020-06-03 2024-03-12 日本電気株式会社 Backdoor inspection device, backdoor inspection method, and program
JP7448003B2 (en) 2020-06-05 2024-03-12 日本電気株式会社 System and method
WO2023084561A1 (en) * 2021-11-09 2023-05-19 日本電気株式会社 Installation control device, installation control method, sharing system, sharing method, and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5951698A (en) * 1996-10-02 1999-09-14 Trend Micro, Incorporated System, apparatus and method for the detection and removal of viruses in macros
US6088801A (en) * 1997-01-10 2000-07-11 Grecsek; Matthew T. Managing the risk of executing a software process using a capabilities assessment and a policy
US20030056117A1 (en) * 1997-03-10 2003-03-20 Doron Elgressy Method and system for preventing the downloading and execution of executable objects
US20050120295A1 (en) * 2003-11-28 2005-06-02 Hitachi, Ltd. Application system with function for preventing modification
US20050160045A1 (en) * 2002-04-03 2005-07-21 Nobuyuki Watanabe Distrubution method, distribution system, and terminal device
US20060101511A1 (en) * 2003-01-23 2006-05-11 Laurent Faillenot Dynamic system and method for securing a communication network using portable agents
US7123914B2 (en) * 1999-03-31 2006-10-17 Kabushiki Kaisha Toshiba Communication network system

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IL123512A0 (en) 1998-03-02 1999-03-12 Security 7 Software Ltd Method and agent for the protection against hostile resource use access
JP3873624B2 (en) * 1999-01-13 2007-01-24 株式会社日立製作所 Mobile code execution method and system
JP2001138611A (en) * 1999-08-31 2001-05-22 Canon Inc Image processor, image processing method
JP2001117769A (en) 1999-10-20 2001-04-27 Matsushita Electric Ind Co Ltd Program executing device
JP2002041170A (en) * 2000-07-27 2002-02-08 Matsushita Electric Ind Co Ltd Program performance controller
JP4566460B2 (en) 2001-06-07 2010-10-20 パイオニア株式会社 Email virus check system
JP2003067210A (en) * 2001-08-22 2003-03-07 Just Syst Corp Program execution prevention device, program execution prevention method, program for computer to execute the method, and computer readable recording medium stored with the program
JP2003337630A (en) * 2002-05-17 2003-11-28 Ntt Docomo Inc Communication terminal, program, recording medium, access control method of the communication terminal, and method of providing content
JP4102639B2 (en) * 2002-10-09 2008-06-18 株式会社エヌ・ティ・ティ・ドコモ Communication terminal, program and recording medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5951698A (en) * 1996-10-02 1999-09-14 Trend Micro, Incorporated System, apparatus and method for the detection and removal of viruses in macros
US6088801A (en) * 1997-01-10 2000-07-11 Grecsek; Matthew T. Managing the risk of executing a software process using a capabilities assessment and a policy
US20030056117A1 (en) * 1997-03-10 2003-03-20 Doron Elgressy Method and system for preventing the downloading and execution of executable objects
US7123914B2 (en) * 1999-03-31 2006-10-17 Kabushiki Kaisha Toshiba Communication network system
US20050160045A1 (en) * 2002-04-03 2005-07-21 Nobuyuki Watanabe Distrubution method, distribution system, and terminal device
US20060101511A1 (en) * 2003-01-23 2006-05-11 Laurent Faillenot Dynamic system and method for securing a communication network using portable agents
US20050120295A1 (en) * 2003-11-28 2005-06-02 Hitachi, Ltd. Application system with function for preventing modification

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120054864A1 (en) * 2005-04-22 2012-03-01 Christopher Scott Linn Security methods and systems
US20090135451A1 (en) * 2005-09-13 2009-05-28 Canon Kabushiki Kaisha Image forming apparatus, control method therefor, and program
US20070220137A1 (en) * 2006-03-17 2007-09-20 Chess David M Computer system evaluation
US20080083031A1 (en) * 2006-12-20 2008-04-03 Microsoft Corporation Secure service computation
US20100083006A1 (en) * 2007-05-24 2010-04-01 Panasonic Corporation Memory controller, nonvolatile memory device, nonvolatile memory system, and access device
US20100146116A1 (en) * 2008-12-10 2010-06-10 Jeong Young Ho Method of controlling download load of secure micro client in downloadable conditional access system
US8260919B2 (en) * 2008-12-10 2012-09-04 Electronics And Telecommunications Research Institute Method of controlling download load of secure micro client in downloadable conditional access system
EP2486509A4 (en) * 2009-10-09 2016-11-30 Nokia Technologies Oy Platform security
US9350761B1 (en) 2010-09-07 2016-05-24 Symantec Corporation System for the distribution and deployment of applications, with provisions for security and policy conformance
US8955152B1 (en) * 2010-09-07 2015-02-10 Symantec Corporation Systems and methods to manage an application
US9043863B1 (en) 2010-09-07 2015-05-26 Symantec Corporation Policy enforcing browser
US9443067B1 (en) 2010-09-07 2016-09-13 Symantec Corporation System for the distribution and deployment of applications, with provisions for security and policy conformance
US8560722B2 (en) * 2011-03-18 2013-10-15 International Business Machines Corporation System and method to govern sensitive data exchange with mobile devices based on threshold sensitivity values
US20120240238A1 (en) * 2011-03-18 2012-09-20 International Business Machines Corporation System and Method to Govern Data Exchange with Mobile Devices
US9501646B2 (en) 2012-09-26 2016-11-22 Mitsubishi Electric Corporation Program verification apparatus, program verification method, and computer readable medium
US20160072825A1 (en) * 2013-04-15 2016-03-10 Giesecke & Devrient Gmbh Mobile Station Comprising Security Resources with Different Security Levels
US9900320B2 (en) * 2013-04-15 2018-02-20 Giesecke + Devrient Mobile Security Gmbh Mobile station comprising security resources with different security levels

Also Published As

Publication number Publication date
JP4164036B2 (en) 2008-10-08
CN1918528A (en) 2007-02-21
CN100495286C (en) 2009-06-03
WO2005076105A1 (en) 2005-08-18
JP2005222341A (en) 2005-08-18
US8490183B2 (en) 2013-07-16

Similar Documents

Publication Publication Date Title
US8490183B2 (en) Security ensuring by program analysis on information device and transmission path
EP2129148B1 (en) Content distribution system
US7532882B2 (en) Method and system for automatically configuring access control
US9124578B2 (en) Service opening method and system, and service opening server
US7801964B2 (en) System and method for providing conditional access to server-based applications from remote access devices
US20180048476A1 (en) System and method for interapplication communications
WO2020181914A1 (en) Mobile phone number rebinding verification method and apparatus, and device and storage medium
JP2008521134A (en) Method and apparatus for enforcing application level restrictions on local and remote content
US20100211861A1 (en) Content distribution management device, communication terminal, program, and content distribution system
JP4664565B2 (en) Communication system architecture and method for controlling the downloading of data to a subscriber unit
US7558963B2 (en) Communication device and program
RU2354054C2 (en) Method and device for device integrity detection
CN113994330A (en) System and method for single sign-on of application program
US7818815B2 (en) Communication device
JP4512083B2 (en) Ensuring security on the transmission path for programs provided to communication terminals via the network
KR20020027702A (en) Method for intercepting the harmfulness site connection on the Internet
EP1462909B1 (en) A computer for managing data sharing among application programs
KR20100022281A (en) Wireless internet service system for blocking access to harmful site and method thereof
CN114765554A (en) Method for determining trust terminal and related device
CN111475139B (en) Configuration method, terminal and storage medium based on BS architecture privatization function
JP2003333133A (en) Access control method for communication terminal, providing method for contents, communication system, repeater, communication terminal, program and recording medium
JP4629024B2 (en) Authentication server and authentication method
KR101397431B1 (en) System for providing isolated- executing-environment and method thereof
JP2002157367A (en) Authenticated result notification method and its system and its device

Legal Events

Date Code Title Description
AS Assignment

Owner name: TREND MICRO INCORPORATED, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KONDO, SATOSHI;YATABE, SHIGERU;REEL/FRAME:018134/0474

Effective date: 20060714

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8