EP3889814A1 - Aktualisierungsvorrichtung und aktualisierungsverfahren - Google Patents
Aktualisierungsvorrichtung und aktualisierungsverfahren Download PDFInfo
- Publication number
- EP3889814A1 EP3889814A1 EP19909433.5A EP19909433A EP3889814A1 EP 3889814 A1 EP3889814 A1 EP 3889814A1 EP 19909433 A EP19909433 A EP 19909433A EP 3889814 A1 EP3889814 A1 EP 3889814A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- access
- file
- package
- package including
- files
- 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
Links
- 238000000034 method Methods 0.000 title claims description 51
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 11
- 230000010365 information processing Effects 0.000 description 5
- 230000007423 decrease Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000009434 installation Methods 0.000 description 4
- 238000007796 conventional method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 201000002266 mite infestation Diseases 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000010454 slate Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing 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/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Definitions
- the present invention relates to an update device and an update method.
- Non-Patent Literature 1 For control communication equipment such as a server, access control techniques to control permission/rejection of access to a file have been considered. For example, a technique to permit execution of only access to an execution file, for which integrity has been confirmed, based on an access control list (hereinafter also referred to as an ACL) set in advance is proposed (see Non-Patent Literature 1). An access control technique is also proposed in which a process permitted to access files is set in advance, and access to the files is monitored for every process so that processes other than the specified process cannot access the files.
- ACL access control list
- an ACL with access control policies for confirming integrity of a file based on correspondence of a hash value of the file is set.
- an access control technique of, by setting in advance a process permitted to access the file, limiting processes that can access the file is applied.
- an execution file of such a process of accessing the file is falsified, access from the falsified process may be permitted.
- an ACL with an inappropriate access control policy may be set.
- an access control policy that does not need to be set may be created and carelessly applied.
- the access control policy is utilized without being noticed to be a malicious access control policy.
- the security level of the ACL decreases, which may cause a security hole.
- the present invention has been made in view of the above, and an object is to restrict addition of an inappropriate access control policy to appropriately set an access control list.
- an update device includes: a storage unit configured to store package management information that includes associations between files and packages including the files and information indicating existence/non-existence of dependence relationships among the packages, and an access control list that includes associations between the files and access source files permitted to access the files; an identification unit configured to refer, when a combination of a file and an access source file is specified, to the package management information to identify a package including the file and a package including the access source file; and an addition unit configured to add, when the identified package including the file and the identified package including the access source file are the same or are mutually in a dependence relationship, the specified combination to the access control list.
- FIG. 1 is a diagram for describing an outline of a process of the access control device. As shown in Fig. 1 , when detecting a process of accessing an access destination file targeted by access control, the access control device performs access control to control permission/rejection to the access destination file by this process, based on an ACL indicating access control policies.
- the access control device permits the process to access the access destination file.
- the access control device confirms integrity of both of the access destination file and the access source file based on the ACL and permits access.
- the update device of the present embodiment performs the update process of updating the ACL of the access control device.
- permission of unnecessary access between files is carelessly added to the ACL, there is a possibility that the security level decreases, which may cause a security hole.
- package management information such as RPM (RPM Package Manager) of Linux (registered trademark) is known.
- the package management information is information to collect and manage execution files, setting files, library files and the like. Each package includes at least an execution file to be included at the time of installation. Files to be generated after installation may be included.
- the package management information includes information indicating dependence relationships among packages assumed by a software package developer, the information indicating which software of which package requires which software of which package, that is, which package depends on which package.
- the update device of the present embodiment executes the ACL update process of restricting at least unnecessary addition to the ACL in consideration of whether access is access between files assumed by the software package developer or not, using the package management information.
- an update device 10 is a device implemented in hardware different from the access control device in the description below, the update device 10 may be a device incorporated in the access control device.
- FIG. 2 is a schematic diagram illustrating a schematic configuration of the update device of the present embodiment.
- the update device 10 is realized by a general-purpose computer such as a personal computer and is provided with an input unit 11, an output unit 12, a communication control unit 13, a storage unit 14 and a control unit 15.
- the input unit 11 is realized by input devices such as a keyboard and a mouse, and inputs various kinds of instruction information for start of a process and the like, to the control unit 15, according to an input operation by an operator.
- the output unit 12 is realized by a display device such as a liquid crystal display, a printing device such as a printer, and the like.
- the communication control unit 13 is realized by an NIC (network interface card) or the like and controls communication between external devices and the control unit 15 via a telecommunication line such as a LAN (local area network) and the Internet.
- the communication control unit 13 controls communication between external devices, such as a management device managing the package management information used for the update process to be described later, the access control device managing the ACL targeted by the update process and a file management system managing a lot of files, and the control unit 15.
- the storage unit 14 is realized by a semiconductor memory element such as a RAM (random access memory) and a flash memory, or a storage device such as a hard disk and an optical disk.
- the storage unit 14 stores package management information 14a and an ACL 14b.
- the storage unit 14 may be configured to communicate with the control unit 15 via the communication control unit 13.
- Fig. 3 is a diagram illustrating the package management information 14a.
- the package management information 14a includes associations between files and packages including the files, and information indicating existence/non-existence of dependence relationships among the packages.
- Each package includes at least an execution file to be included at the time of installation and files to be generated after installation.
- the package management information 14a is information in which, for each package, a dependence destination package and files included in the dependence destination package are associated as shown in Fig. 3 .
- the dependence source package requires a dependence destination package in order to cause the dependence source package to function.
- a package “openssl” includes files “/.../openssl", “/.../openssl.conf” and the like.
- dependence destination packages the dependence source of which is a package "mod_ssl” are "openssl” and "httpd”.
- "/.../” is an expression indicating omission of a file path.
- the package "openssl” it is illustrated that there is not a dependence destination package assumed by the software package developer.
- the update device 10 acquires the package management information 14a via the input unit 11 or the communication control unit 13 and causes the package management information 14a to be stored into the storage unit 14 in advance prior to the update process to be described later.
- Fig. 4 is a diagram illustrating the ACL 14b.
- the ACL 14b includes associations between files and access source files permitted to access the files.
- the ACL 14b is a white list specifying access source files permitted to access destination files as described above.
- the update device 10 acquires the ACL 14b of the access control device via the input unit 11 or the communication control unit 13 and causes the ACL 14b to be stored into the storage unit 14 in advance prior to the update process to be described later.
- the control unit 15 is realized using a CPU (central processing unit) or the like, and executes a processing program stored in the memory. Thereby, the control unit 15 functions as an identification unit 15a and an addition unit 15b as illustrated in Fig. 4 .
- the identification unit 15a refers to the package management information 14a to identify a package including the access destination file and a package including the access source file.
- the identification unit 15a refers to the package management information 14a first. Then, the identification unit 15a identifies packages including the specified access destination file and access source file, respectively.
- the identification unit 15a identifies the package "openssl” of the access destination file. Further, the identification unit 15a identifies the package "mod_ssl” of the access source file.
- the addition unit 15b adds the specified combination to the ACL 14b.
- Figs. 5 and 6 are explanatory diagrams for describing a process of the addition unit 15b. If a package of an access source file and a package of an access destination file are the same as shown by an arrow a in Fig. 5 , the addition unit 15b adds the specified combination to the ACL 14b.
- the addition unit 15b adds the specified combination to the ACL 14b.
- a combination shown by an arrow b in Fig. 5 is regarded as an access control policy required for cooperation between a dependence source package and a dependence destination package and added to the ACL 14b.
- the addition unit 15b may further output a warning. Further, when a package including an access destination file and a package including an access source file are different from each other and are mutually in a dependence relationship, the addition unit 15b may reject addition or accept an instruction to permit/reject addition, instead of addition of the specified combination to the ACL 14b.
- the addition unit 15b may output a warning to refer to whether the combination shown by the arrow b in Fig. 5 violates the access control scheme or not or request the operator to approve permission/rejection of addition to the ACL 14b. Or alternatively, the addition unit 15b may indiscriminately reject addition to the ACL 14b in accordance with the operation scheme.
- the addition unit 15b adds the specified combination to the ACL 14b.
- a combination shown by an arrow c in Fig. 5 is an access control policy between independent packages that are not mutually in a dependence relationship, and there is a possibility that the combination may be access between files required by the operator though it is unexpected by the software package developer. Therefore, the addition unit 15b adds the combination to the ACL 14b.
- the addition unit 15b adds the combination to the ACL 14b.
- the addition unit 15b when a package including an access destination file and a package including an access source file are different from each other, are not mutually in a dependence relationship, and are not in the dependence relationship via another package, the addition unit 15b further outputs a warning.
- the addition unit 15b outputs the warning to leave the determination to the operator.
- the addition unit 15b outputs a warning to refer to whether the combination does not violate the access control scheme.
- the addition unit 15b may reject addition or accept an instruction to permit/reject addition, instead of addition of the specified combination to the ACL 14b.
- the addition unit 15b may request the operator to approve permission/rejection of addition to the ACL 14b.
- the addition unit 15b may indiscriminately reject addition to the ACL 14b.
- the addition unit 15b does not perform addition to the ACL 14b.
- the addition unit 15b does not perform addition to the ACL 14b.
- a definition of the dependence relationship may be omitted, or the definition may be missing in the package mange information.
- the addition unit 15b may request the operator to approve permission/rejection of addition to the ACL 14b. Or alternatively, the addition unit 15b may indiscriminately add the combination and output a warning to leave the determination to the operator. Thereby, it is possible to, without indiscriminately rejecting addition when there is an indirect dependence relationship between packages, perform addition to the ACL 14b in the case of omission of a definition or missing of the definition in the package management information.
- the addition unit 13b outputs the ACL 14b updated by the update process to the access control device. Thereby, it becomes possible for the access control device to apply the updated ACL 14b and control permission/rejection of access between files.
- Fig. 7 is a flowchart showing an update process procedure.
- the flowchart in Fig. 7 is started, for example, at a timing of the user performing an operation input to give a start instruction.
- the identification unit 15a accepts an input specifying a combination of an access destination file and an access source file. Further, the identification unit 15a refers to the package management information 14a to identify a package including the access destination file and a package including the access source file.
- the addition unit 15b confirms whether the identified package including the access destination file and the identified package including the access source file are the same or not (step S1). When the identified package including the access destination file and the identified package including the access source file are the same (step S1: Yes), the addition unit 15b adds the specified combination to the ACL 14b (step S6).
- the addition unit 15b confirms whether the identified package including the file and the identified package including the access source file are mutually in a dependence relationship or not. First, the addition unit 15b confirms whether the identified package including the access destination file is a dependence destination of the package including the access source file or not (step S2). When the package including the access destination file is the dependence destination of the package including the access source file (step S2: Yes), the addition unit 15b adds the specified combination to the ACL 14b (step S6).
- step S2 when the package including the access destination file is not the dependence destination of the package including the access source file (step S2: No), the addition unit 15b confirms whether the package including the access source file is a dependence destination of the package including the access destination file (step S3).
- step S3 When the package including the access source file is the dependence destination of the package including the access destination file (step S3; Yes), the addition unit 15b adds the specified combination to the ACL 14b (step S6).
- the addition unit 15b may accept an instruction to permit/reject addition, instead of addition of the specified combination to the ACL 14b. Specifically, the addition unit 15b may output a warning to refer to whether the specified combination violates the access control scheme or request the operator to approve permission/rejection of addition to the ACL 14b. Or alternatively, the addition unit 15b may indiscriminately reject addition to the ACL 14b in accordance with the operation scheme.
- step S3: No the addition unit 15b confirms whether the package including the access destination file and the package including the access source file are not in the dependence relationship via another package.
- the addition unit 15b confirms whether the package of the access destination file is reached through a dependence destination package of the access source file or not (step S4).
- the addition unit 15b does not perform addition of the specified combination to the ACL 14b, regarding the combination as access that is not assumed by the software package developer (step S7).
- step S4 when the package of the access destination file is not reached through the dependence destination package of the access source file (step S4: No), the addition unit 15b confirms whether the package of the access source file is reached through a dependence destination package of the access destination file (step S5).
- step S5 Yes
- the addition unit 15b does not perform addition of the specified combination to the ACL 14b regarding the combination as access that is not assumed by the software package developer (step S7).
- the addition unit 15b adds the specified combination to the ACL 14b as an access control policy between independent packages (step S8). Further, the addition unit 15b outputs a warning to leave the determination to the operator.
- the addition unit 15b outputs a warning to refer to whether the combination does not violate the access control scheme. Further, the addition unit 15b may request the operator to approve permission/rejection of addition to the ACL 14b. Or alternatively, as for the combination, the addition unit 15b may indiscriminately reject addition to the ACL 14b.
- the addition unit 15b may request an approval of permission/rejection of addition to the ACL 14b from the operator, instead of indiscriminately rejecting addition. Or alternatively, the addition unit 15b may indiscriminately add the combination and output a warning to leave the determination to the operator. Thereby, it becomes possible to, in the case of omission of a definition or missing of the definition in the package management information, perform addition to the ACL 14b.
- the update process procedure ends.
- the update device 10 can restrict addition of at least inappropriate access control policies to update the ACL 14b. Therefore, it becomes possible to minimize lessening of the security level of the ACL 14b.
- the storage unit 14 stores the package management information 14a that includes associations between files and packages including the files and information indicating existence/non-existence of dependence relationships among the packages, and the ACL 14b that includes associations between access destination files and access source files permitted to access the access destination files.
- the identification unit 15a refers to the package management information 14a to identify a package including the access destination file and a package including the access source file.
- the addition unit 15b adds the specified combination to the ACL 14b.
- the update device 10 can add the combination to the ACL 14b to update the ACL 14b while restricting addition of at least inappropriate access control policies. Therefore, it becomes possible to minimize lessening of the security level of the ACL 14b. Thus, it becomes possible for the update device 10 to appropriate set an ACL.
- the addition unit 15b may further output a warning. Or alternatively, the addition unit 15b may reject addition or accept an instruction to permit/reject addition, instead of addition of the specified combination to the ACL 14b. Thereby, it becomes possible to leave permission/rejection of addition to the ACL 14b to determination of the operator.
- the addition unit 15b adds the specified combination to the ACL 14b.
- the addition unit 15b further outputs a warning.
- the addition unit 15b may reject addition or accept an instruction to permit/reject addition, instead of addition of the specified combination to the ACL 14b. Thereby, it becomes possible to leave permission/rejection of addition to the ACL 14b to determination of the operator.
- the addition unit 15b can restrict addition of the combination to the ACL 14b. In other words, it is possible to restrict addition of such unnecessary access that there is not a mutual direct dependence relationship between packages and that is possibly access that the software package developer does not assume, to the ACL 14b.
- the update device 10 can be implemented by causing an update program to execute the above update process to be installed in a desired computer as package software or online software.
- the information processing device it is possible to cause the information processing device to function as the update device 10.
- a desktop type or notebook type personal computer is included.
- mobile communication terminals such as a smartphone, a mobile phone and a PHS (personal handy-phone system), and slate terminals such as a PDA (personal digital assistant) are included in the category of the information processing device.
- the functions of the update device 10 may be implemented in a cloud server.
- FIG. 8 is a diagram showing an example of the computer to execute the update program.
- a computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060 and a network interface 1070. These units are connected via a bus 1080.
- the memory 1010 includes a ROM (read-only memory) 1011 and a RAM 1012.
- the ROM 1011 stores, for example a boot program such as BIOS (basic input/output system).
- BIOS basic input/output system
- the hard disk drive interface 1030 is connected to a hard disk drive 1031.
- the disk drive interface 1040 is connected to a disk drive 1041.
- a removable storage medium such as a magnetic disk and an optical disk is inserted into the disk drive 1041.
- To the serial port interface 1050 for example, a mouse 1051 and a keyboard 1052 are connected.
- To the video adapter 1060 for example, a display 1061 is connected.
- the hard disk drive 1031 stores, for example, an OS 1091, an application program 1092, a program module 1093 and program data 1094. Each piece of information described in the above embodiment is stored, for example, in the hard disk drive 1031 or the memory 1010.
- the update program is stored in the hard disk drive 1031, for example, as a program module 1093 in which commands to be executed by the computer 1000 are written.
- the program module 1093 in which each process to be executed by the update device 10 described in the above embodiment is written is stored in the hard disk drive 1031.
- data to be used for information processing by the update program is stored, for example, in the hard disk drive 1031 as the program data 1094. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the hard disk drive 1031 as necessary and executes each procedure described above.
- program module 1093 and the program data 1094 related to the update program may not be stored in the hard disk drive 1031 but may be stored, for example, in a removable storage medium and read out by the CPU 1020 via the disk drive 1041 or the like.
- the program module 1093 and the program data 1094 related to the update program may be stored in another computer connected via a network such as a LAN and a WAN (wide area network) and read out by the CPU 1020 via the network interface 1070.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019003731A JP7040467B2 (ja) | 2019-01-11 | 2019-01-11 | 更新装置および更新方法 |
PCT/JP2019/050224 WO2020145100A1 (ja) | 2019-01-11 | 2019-12-20 | 更新装置および更新方法 |
Publications (3)
Publication Number | Publication Date |
---|---|
EP3889814A1 true EP3889814A1 (de) | 2021-10-06 |
EP3889814A4 EP3889814A4 (de) | 2022-08-17 |
EP3889814B1 EP3889814B1 (de) | 2023-04-19 |
Family
ID=71520335
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19909433.5A Active EP3889814B1 (de) | 2019-01-11 | 2019-12-20 | Aktualisierungsvorrichtung und aktualisierungsverfahren |
Country Status (6)
Country | Link |
---|---|
US (1) | US11809580B2 (de) |
EP (1) | EP3889814B1 (de) |
JP (1) | JP7040467B2 (de) |
CN (1) | CN113272808B (de) |
AU (1) | AU2019420941B2 (de) |
WO (1) | WO2020145100A1 (de) |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5761669A (en) * | 1995-06-06 | 1998-06-02 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
JP2002278839A (ja) * | 2001-03-15 | 2002-09-27 | Sony Corp | データアクセス管理システム、メモリ搭載デバイス、およびデータアクセス管理方法、並びにプログラム記憶媒体 |
CN100481013C (zh) * | 2004-08-03 | 2009-04-22 | 索芙特瑞斯提股份有限公司 | 用于经由上下文策略控制来控制应用程序间关联的系统和方法 |
JP2008021247A (ja) * | 2006-07-14 | 2008-01-31 | Nec Software Kyushu Ltd | 情報処理装置、ファイルアクセス制御方法、及びプログラム |
US8950007B1 (en) * | 2008-04-07 | 2015-02-03 | Lumension Security, Inc. | Policy-based whitelisting with system change management based on trust framework |
US8533844B2 (en) * | 2008-10-21 | 2013-09-10 | Lookout, Inc. | System and method for security data collection and analysis |
US8788655B2 (en) * | 2008-12-19 | 2014-07-22 | Openpeak Inc. | Systems for accepting and approving applications and methods of operation of same |
CN101615236B (zh) * | 2009-07-24 | 2011-07-20 | 北京工业大学 | 一种基于强制访问控制技术的可信应用环境构建方法 |
US8990561B2 (en) * | 2011-09-09 | 2015-03-24 | Microsoft Technology Licensing, Llc | Pervasive package identifiers |
US20140032733A1 (en) * | 2011-10-11 | 2014-01-30 | Citrix Systems, Inc. | Policy-Based Application Management |
JP5853817B2 (ja) * | 2012-03-28 | 2016-02-09 | 富士通株式会社 | 情報処理装置、制御方法及び制御プログラム |
US9454670B2 (en) * | 2012-12-03 | 2016-09-27 | International Business Machines Corporation | Hybrid file systems |
JP5750497B2 (ja) * | 2013-12-11 | 2015-07-22 | 株式会社アイキュエス | アクセス制御装置、プログラム及びアクセス制御システム |
US9875121B2 (en) * | 2014-09-17 | 2018-01-23 | International Business Machines Corporation | API server |
JP6088714B2 (ja) * | 2014-10-14 | 2017-03-01 | 日本電信電話株式会社 | 特定装置、特定方法および特定プログラム |
JP6529304B2 (ja) * | 2015-03-25 | 2019-06-12 | 株式会社日立ソリューションズ | アクセス制御システム及びアクセス制御方法 |
US10270778B2 (en) * | 2016-03-21 | 2019-04-23 | Google Llc | Methods and systems for dynamic creation of access control lists |
US10528749B2 (en) * | 2017-03-20 | 2020-01-07 | Huawei Technologies Co., Ltd. | Methods and apparatus for containerized secure computing resources |
CN108108633B (zh) * | 2017-12-20 | 2021-07-13 | 中国科学院深圳先进技术研究院 | 一种数据文件及其访问方法、装置及设备 |
-
2019
- 2019-01-11 JP JP2019003731A patent/JP7040467B2/ja active Active
- 2019-12-20 US US17/421,719 patent/US11809580B2/en active Active
- 2019-12-20 EP EP19909433.5A patent/EP3889814B1/de active Active
- 2019-12-20 WO PCT/JP2019/050224 patent/WO2020145100A1/ja unknown
- 2019-12-20 CN CN201980088321.2A patent/CN113272808B/zh active Active
- 2019-12-20 AU AU2019420941A patent/AU2019420941B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN113272808A (zh) | 2021-08-17 |
US20220092195A1 (en) | 2022-03-24 |
CN113272808B (zh) | 2024-01-30 |
EP3889814B1 (de) | 2023-04-19 |
WO2020145100A1 (ja) | 2020-07-16 |
AU2019420941B2 (en) | 2023-06-08 |
US11809580B2 (en) | 2023-11-07 |
JP7040467B2 (ja) | 2022-03-23 |
EP3889814A4 (de) | 2022-08-17 |
JP2020113072A (ja) | 2020-07-27 |
AU2019420941A1 (en) | 2021-07-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3552098B1 (de) | Verwaltung der betriebssystemaktualisierung für angemeldete vorrichtungen | |
US9767280B2 (en) | Information processing apparatus, method of controlling the same, information processing system, and information processing method | |
US7516477B2 (en) | Method and system for ensuring that computer programs are trustworthy | |
US10885200B2 (en) | Detecting security risks related to a software component | |
US11036862B2 (en) | Dynamic application deployment in trusted code environments | |
US9317396B2 (en) | Information processing apparatus including an execution control unit, information processing system having the same, and stop method using the same | |
JP6383445B2 (ja) | 保護されたアプリケーションへのアクセスを阻止するシステム及び方法 | |
CN109522683B (zh) | 软件溯源方法、系统、计算机设备及存储介质 | |
CN113779562A (zh) | 基于零信任的计算机病毒防护方法、装置、设备及介质 | |
US20160048685A1 (en) | Protected shell for risk validation | |
EP3889814B1 (de) | Aktualisierungsvorrichtung und aktualisierungsverfahren | |
CN115935328A (zh) | 资源访问控制方法、装置、设备及存储介质 | |
WO2021014595A1 (ja) | 検証情報作成システム、検証情報作成方法、および、検証情報作成プログラム | |
US20230214479A1 (en) | Method and system for detecting and preventing unauthorized access to a computer | |
US11620442B2 (en) | Interpretation risk detection | |
CN113765986B (zh) | 一种开放平台的流量控制方法和服务器 | |
US11983543B2 (en) | Information processing device, control method, and control program | |
JP7255681B2 (ja) | 実行制御システム、実行制御方法、及びプログラム | |
GB2561861A (en) | Computer device and method for isolating untrusted content | |
JP2009116391A (ja) | 安全度評価と連動するセキュリティの方針設定装置、そのプログラムおよびその方法 | |
EP3872640A1 (de) | Vorrichtung, verfahren und programm zur informationserzeugung | |
JP2022190970A (ja) | 情報処理装置、情報処理方法、およびプログラム | |
CN113238946A (zh) | 检测hook框架的方法、装置及电子设备 | |
CN115292096A (zh) | 一种备份数据保护系统、方法、设备及存储介质 | |
CN115766014A (zh) | 一种控制器安全管理方法、装置、车辆及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20210701 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20220720 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 9/40 20220101ALI20220714BHEP Ipc: G06F 21/60 20130101ALI20220714BHEP Ipc: G06F 8/65 20180101ALI20220714BHEP Ipc: G06F 8/61 20180101ALI20220714BHEP Ipc: G06F 8/60 20180101ALI20220714BHEP Ipc: G06F 21/57 20130101ALI20220714BHEP Ipc: G06F 21/51 20130101ALI20220714BHEP Ipc: G06F 21/62 20130101AFI20220714BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20221222 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602019027907 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1561748 Country of ref document: AT Kind code of ref document: T Effective date: 20230515 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20230419 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1561748 Country of ref document: AT Kind code of ref document: T Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230821 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230719 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230819 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230720 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231220 Year of fee payment: 5 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602019027907 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20231220 Year of fee payment: 5 Ref country code: FR Payment date: 20231222 Year of fee payment: 5 Ref country code: DE Payment date: 20231214 Year of fee payment: 5 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20240122 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20230419 |