WO2013183150A1 - セキュリティアダプタプログラム及び装置 - Google Patents
セキュリティアダプタプログラム及び装置 Download PDFInfo
- Publication number
- WO2013183150A1 WO2013183150A1 PCT/JP2012/064715 JP2012064715W WO2013183150A1 WO 2013183150 A1 WO2013183150 A1 WO 2013183150A1 JP 2012064715 W JP2012064715 W JP 2012064715W WO 2013183150 A1 WO2013183150 A1 WO 2013183150A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- security adapter
- request message
- application unit
- message
- internal
- Prior art date
Links
- 238000012545 processing Methods 0.000 claims abstract description 60
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000012806 monitoring device Methods 0.000 claims abstract description 26
- 230000008569 process Effects 0.000 claims abstract description 21
- 238000004891 communication Methods 0.000 claims abstract description 7
- 230000005540 biological transmission Effects 0.000 claims description 55
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000013500 data storage Methods 0.000 claims description 8
- 230000000903 blocking effect Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 34
- 238000010586 diagram Methods 0.000 description 26
- 230000002093 peripheral effect Effects 0.000 description 10
- 230000004044 response Effects 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 238000003754 machining Methods 0.000 description 5
- 102100036848 C-C motif chemokine 20 Human genes 0.000 description 4
- 102100035353 Cyclin-dependent kinase 2-associated protein 1 Human genes 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 101000713099 Homo sapiens C-C motif chemokine 20 Proteins 0.000 description 3
- 101000737813 Homo sapiens Cyclin-dependent kinase 2-associated protein 1 Proteins 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 101000661816 Homo sapiens Suppression of tumorigenicity 18 protein Proteins 0.000 description 2
- 101000661807 Homo sapiens Suppressor of tumorigenicity 14 protein Proteins 0.000 description 2
- 101000585359 Homo sapiens Suppressor of tumorigenicity 20 protein Proteins 0.000 description 2
- 102100029860 Suppressor of tumorigenicity 20 protein Human genes 0.000 description 2
- 238000010248 power generation Methods 0.000 description 2
- 101000760620 Homo sapiens Cell adhesion molecule 1 Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000005728 strengthening Methods 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
-
- 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/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting 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
-
- 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/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/78—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/06—Energy or water supply
Definitions
- Embodiments described herein relate generally to a security adapter program and apparatus.
- FIG. 1 is a schematic diagram showing a monitoring device and its peripheral configuration in a conventional power system.
- a plurality of devices # 1 to #n transmit data to the monitoring device 10, and the monitoring device 10a stores the data in the power system DB 12 via the dedicated line 11.
- a processor (not shown) in the monitoring apparatus 10a functions as a plurality of internal application units 13A to 13C by executing a plurality of internal application programs A to C (hereinafter referred to as internal applications A to C) in a memory (not shown).
- the plurality of internal application units 13A to 13C appropriately read data from the power system DB 12, and transmit / receive messages including the data to / from each other.
- the internal application units 13A to 13C are directly linked to each other, so that the messages are transmitted and received by a unique method for each of the internal application units 13A to 13C.
- a mutual connection method is called a mutual connection method.
- Each of the bus connection adapters 15A to 15C includes a messaging layer L1, a connecting layer L2, and an adapter layer L3.
- the messaging layer L1 has a message transmission / reception function.
- the connecting layer L2 has a function of connecting to the common bus 14.
- the adapter layer L3 has a message processing function and a linkage function with an existing system.
- a service-oriented architecture (hereinafter referred to as SOA) is used, and an internal application is connected from an external application unit 20 via a common bus 14 in the monitoring device 10c.
- SOA service-oriented architecture
- the units 13A to 13C can be directly accessed.
- the external application unit 20 is a functional unit realized by a processor (not shown) in the external device executing an external application program (hereinafter referred to as an external application) in the memory of the external device.
- a problem to be solved by the present invention is to provide a security adapter program and apparatus capable of preventing leakage of processing contents and data of an internal application and identification of the internal application when accessing the internal application from an external application It is to be.
- the security adapter program of the embodiment is used in a monitoring device including a data storage unit, a plurality of internal application units, a first common bus, and a plurality of bus connection adapters.
- the data storage unit stores data received from a plurality of devices.
- the plurality of internal application units mutually transmit and receive messages including data in the data storage unit.
- the first common bus is a bus capable of transmitting a message between the internal applications.
- the plurality of bus connection adapters individually connect the internal application units and the first common bus.
- the monitoring device further includes first storage means.
- the first storage means stores a service name indicating the type of processing by each internal application unit and an application name for identifying each internal application unit in association with each other.
- the security adapter program is a program for causing the monitoring device to further function as security adapter means that intervenes in communication between each internal application unit and the external application unit.
- the security adapter means includes a receiving means, a first processing means, a sending means, and a sending means.
- the receiving means receives a request message designating the service name from the external application unit.
- the first processing means searches the first storage means based on the service name in the received request message, and processes the request message so that the application name obtained by the search is included in the destination.
- the sending means sends the processed request message to the first common bus so as to transmit the processed request message to the internal application unit identified by the destination application name.
- the transmission unit When the transmission unit receives a transmission message from any one of the internal application units via the bus connection adapter and the first common bus, the transmission unit transmits the transmission message to the external application unit. .
- FIG. 1 is a schematic diagram showing a monitoring device and its peripheral configuration in a conventional power system.
- FIG. 2 is a schematic diagram for explaining a conventional common bus system.
- FIG. 3 is a schematic diagram for explaining a conventional common bus system.
- FIG. 4 is a schematic diagram for explaining a message linkage method using a conventional SOA.
- FIG. 5 is a schematic diagram for explaining the outline of each embodiment.
- FIG. 6 is a schematic diagram showing a monitoring device to which the security adapter program according to the first embodiment is applied and its peripheral configuration.
- FIG. 7 is a schematic diagram for explaining the authentication DB in the embodiment.
- FIG. 8 is a schematic diagram for explaining a modification of the embodiment.
- FIG. 9 is a schematic diagram illustrating an example of a message before processing in the embodiment.
- FIG. 9 is a schematic diagram illustrating an example of a message before processing in the embodiment.
- FIG. 10 is a schematic diagram illustrating an example of a processed message in the embodiment.
- FIG. 11 is a schematic diagram for explaining the outline of the operation in the embodiment.
- FIG. 12 is a schematic diagram showing an operation in the embodiment.
- FIG. 13 is a flowchart for explaining the operation in the embodiment.
- FIG. 14 is a flowchart for explaining the operation in the embodiment.
- FIG. 15 is a schematic diagram illustrating an example of data in the embodiment.
- FIG. 16 is a schematic diagram showing an example of data in the embodiment.
- FIG. 17 is a schematic diagram illustrating an example of data in the embodiment.
- FIG. 18 is a schematic diagram illustrating an example of data in the embodiment.
- FIG. 19 is a schematic diagram illustrating an example of data in the embodiment.
- FIG. 15 is a schematic diagram illustrating an example of data in the embodiment.
- FIG. 16 is a schematic diagram showing an example of data in the embodiment.
- FIG. 17 is a schematic diagram illustrating an example of data in the embodiment
- FIG. 20 is a schematic diagram illustrating a monitoring device to which the security adapter program according to the second embodiment is applied and its peripheral configuration.
- FIG. 21 is a schematic diagram illustrating a monitoring device to which the security adapter program according to the third embodiment is applied and its peripheral configuration.
- FIG. 22 is a flowchart for explaining the operation in the embodiment.
- FIG. 23 is a schematic diagram illustrating a monitoring device to which the security adapter program according to the fourth embodiment is applied and its peripheral configuration.
- the conventional power system performs message linkage between applications using the common bus 12 as described above.
- the application of the first pattern is a traditional application and is used for managing know-how data.
- Application of the second pattern is an application developed in an open environment and has an external interface.
- the application of the third pattern is an application to be developed in the future and is a next generation application with added value.
- the three patterns of applications need to be organically linked and provide a service in response to a request from the external application unit 20.
- the bus connection adapters 15A to 15C deliver messages at the following three levels (Level 1) to (Level 3) according to each application pattern.
- Level 2 Message passing by calling an external application.
- Level 3 Message passing by API (application program interface) call.
- the power system system uses the SOA to link the external application unit 20 and the internal applications A to C.
- the configuration including the security adapter 17 prevents leakage of processing contents and data of the internal application and identification of the internal application. .
- the security adapter 17 may be read as an arbitrary name such as a power system security adapter, a power system security gateway, or a security gateway.
- FIG. 6 is a schematic diagram showing a monitoring device to which the security adapter program according to the first embodiment is applied and its peripheral configuration.
- the same part as the configuration shown in FIG. 4 and the like refers to the power system DB (data storage unit) 12, the plurality of internal application units 13A to 13C, the common bus (first common bus) 14, and the plurality of parts in the monitoring device 10.
- the bus connection adapters 15A to 15C are provided.
- the power system DB 12 stores data received from the plurality of devices # 1 to #n.
- the plurality of internal application units 13A to 13C transmit and receive messages including data in the power system DB 12 to each other.
- the common bus (first common bus) 14 is a bus capable of transmitting messages between the internal application units 13A to 13C.
- the plurality of bus connection adapters 15A to 15C individually connect the internal application units 13A to 13C and the common bus 14.
- the first embodiment further includes a security adapter 17 interposed in communication between each of the internal application units 13A to 13C and the external application unit 20 as compared with the configuration shown in FIG.
- the security adapter 17 refers to the authentication DB 16.
- the authentication DB (first to third storage means) 16 is a storage unit that can be read / written from the security adapter 17, and as shown in FIG. 7, an authentication table T1, an authority table T2, and a flow table T3. Is remembered. Note that the authentication table T1 and the authority table T2 are arbitrary additional items and may be omitted. The setting of each table T1 to T3 is executed by the security adapter 17 in advance by the operation of the administrator. Further, instead of the authentication DB 16, a memory storing an XML file F1 in which the contents of the tables T1 to T3 are described in the XML format as shown in FIG. 8 may be used.
- the authentication table T1 is information in which a user ID for identifying a user who operates the external application unit 20 is associated with a password for authenticating the user.
- the authority table T2 is information in which a user ID, a service name, and authority information indicating the authority of the user are described in association with each other.
- the flow table T3 is information in which a service name indicating the type of processing by each internal application unit 13A to 13C and an application name A to C for identifying each internal application unit 13A to 13C are described in association with each other.
- the application names in the flow table T3 are described in the execution order for each service name.
- a set of application names described in this execution order is called flow information.
- the security adapter (security adapter means) 17 is a functional unit realized by a processor (not shown) in the monitoring apparatus 10 executing a security adapter program in a memory (not shown).
- the security adapter 17 can be implemented with a combination of hardware resources and software.
- this software as shown in FIGS. 6, 20, 21, and 23, the monitoring device 10 is preliminarily stored on a network or a non-transitory computer-readable storage medium M.
- a security adapter program that is installed in the computer and causes the computer to realize the function of the security adapter 17 is used.
- the security adapter 17 is not limited to a combination configuration of hardware resources and software, but can be implemented as a security adapter device having a hardware configuration.
- the security adapter 17 has the following functions (f17-1) to (f17-4).
- (F17-1) A reception function that receives a request message specifying a service name from the external application part.
- (F17-2) A first processing function that searches the authentication DB 16 based on the service name in the received request message and processes the request message so that the application name obtained by the search is included in the destination.
- (F17-3) A sending function for sending the processed request message to the common bus 14 so that the processed request message is transmitted to an internal application part (eg, 13A) identified by the destination application name.
- an internal application part eg, 13A
- the security adapter 17 may further include, for example, the following functions (f17-5) to (f17-7).
- reception function (f17-1) When the reception function (f17-1) receives a request message including a user ID, password, and service name, the user ID and password in the received request message are replaced with the user ID and password in the authentication DB 16.
- An authentication function that authenticates the validity of the request message by checking with.
- a second processing function that searches the authentication DB 16 based on the service name in the request message that has been successfully authenticated, and processes the request message to include the authority information obtained by the search.
- a message m before machining by the first machining function (f17-3) and the second machining function (f17-6) is shown in FIG. 9, and the message m after machining is shown in FIG.
- the authority information and the flow information are set in the header part of the message m.
- the present invention is not limited to this, and may be set in the data part of the message m.
- F17-7 A blocking function that prevents the execution of the first machining function (f17-2) and the sending function (f17-3) when authentication fails.
- Such a security adapter 17 may include a messaging layer L1, a connecting layer L2, and an adapter layer L3, for example, as described above.
- the messaging layer L1 has a message transmission / reception function (f17-1) and (f17-4).
- the connecting layer L2 has a connection function (f17-3), (f17-5), and (f17-7) to the common bus 14.
- the adapter layer L3 has message processing and linkage functions (f17-2) and (f17-6) with the existing system.
- the external application unit 20 transmits a request message using the SOA to the security adapter 17.
- the security adapter 17 refers to the authentication DB 16 to authenticate the request message, and calls the internal applications A to C related to the request message.
- the request message from the external application unit 20 can be authenticated. Further, it is possible to confirm the user authority by the authentication and control access to the internal applications A to C.
- the monitoring device 10 activates the security adapter 17 when a processor (not shown) starts executing the security adapter program (ST1).
- the security adapter 17 performs a connection process to the common bus 14 and the authentication DB 16 as an initialization process (ST2).
- Example 1 When a message is periodically received from the external application unit 20 and stored in the internal application unit 13A or 13C.
- Example 2 A message including data such as energy usage and energy generation amount is acquired from monitored devices # 1 and # 2 at a certain period, and the data extracted from the message is stored in an internal database (eg, power system DB 12). When saving.
- an internal database eg, power system DB 12
- step ST2 it is assumed that the security adapter 17 receives a message from the external application unit 20 (ST3). Assume that the received message is a request message specifying a service name. This request message may further include a user ID and a password.
- the security adapter 17 decodes the received message, accesses the authentication DB 16, performs authentication, determines the type of application, and specifies the application to be called (ST4). Specifically, the security adapter 17 authenticates the validity of the request message by checking the user ID and password in the received request message against the user ID and password in the authentication table T1 in the authentication DB 16. Further, the security adapter 17 searches the flow table T3 in the authentication DB 16 based on the service name in the received request message, and obtains the application name by the search. The service name indicates the type of application. The application to be called is specified by the obtained application name.
- the security adapter 17 processes the message (ST5).
- the security adapter 17 processes the request message so that the application name obtained in step ST4 is included in the destination.
- the security adapter 17 searches the authority table T2 in the authentication DB 16 based on the service name in the request message that has been successfully authenticated, and requests to include the authority information obtained by the search. Process the message. If the authentication fails, the security adapter 17 does not execute steps ST5 to ST9.
- the security adapter 17 calls the internal application A in the order of the flow information (ST6) and receives the processing result from the internal application unit 13A. Subsequently, the security adapter 17 calls the internal application B in the order of the flow information (ST7), and receives the processing result from the internal application unit 13B.
- the security adapter 17 merges the processing results received in accordance with steps ST6 and ST7, and writes the merge result to the internal application unit 13C (ST8).
- the security adapter 17 sends the processed message to, for example, the internal application unit 13A. Specifically, the security adapter 17 sends the processed request message to the common bus 14 so as to transmit the processed request message to the internal application unit 13A identified by the destination application name.
- the internal application unit 13A writes the data in the sent message (ST9).
- the data written in step ST9 is data of each device at a specific date and time (eg, device ID, active power, power generation output, voltage, and frequency values) as shown in FIG. 15, for example.
- Example 3 When sending messages and commands to the external application unit 20.
- Example 4 When detecting an error in monitored devices # 1 to #n and sending an error message indicating the error and a countermeasure command.
- the security adapter 17 receives a message from any one of the internal application units 13A to 13C (eg, 13A) via the bus connection adapter 15A and the common bus 14. (ST10).
- This message is assumed to be a transmission message to the external application unit 20.
- this message includes a device ID indicating a device in which an abnormality is detected, an error code corresponding to an error message, and an instruction code corresponding to a handling instruction in the data portion.
- the security adapter 17 decodes the received message, accesses the authentication DB 16, searches for flow information based on the service name in the message, and is associated with the service name that matches the service name in the flow information.
- the external application unit 20 is specified by the application name indicating the external application unit 20 (ST11).
- the security adapter 17 executes message processing such as encryption processing based on the identified result (ST12).
- message processing such as encryption processing based on the identified result (ST12).
- encryption processing for example, the public key of the specified external application is used.
- the security adapter 17 transmits the message processed in step ST12 to the external application unit 20 (ST13). However, there is a case where processing is not performed in step ST12. In any case, the security adapter 17 transmits the transmission message received in step ST10 to the external application unit 20.
- Example 5 When necessary data is returned in response to a request from the external application unit 20.
- Example 6 When data such as a power supply / demand plan is requested from the external application unit 20, and the result data is returned to the request source.
- the request message When the request is received, the request message is authenticated, and when the authentication is successful, the result is transmitted to the external application unit 20.
- step ST2 it is assumed that the security adapter 17 receives a message from the external application unit 20 (ST14).
- the security adapter 17 decodes the received message, accesses the authentication DB 16, performs authentication, determines the type of application, and specifies the application to be called (ST15).
- the security adapter 17 processes the message (ST16).
- the security adapter 17 sends out the data in the message and calls, for example, the internal application C (ST17).
- the internal application unit 13C that operates in response to this call reads out the power system DB 12 based on the transmitted data, and transmits the read result data to the security adapter 17.
- the data in the message includes a device ID for specifying the requested data, a start date / time, and an end date / time in the data portion.
- the security adapter 17 calls the internal application A in the order of the flow information (ST18) and receives the processing result from the internal application unit 13A. Subsequently, the security adapter 17 calls the internal application B in the order of the flow information (ST19), and receives the processing result from the internal application unit 13B.
- the security adapter 17 merges the processing results received in steps ST18 and ST19 (ST20).
- the security adapter 17 creates a reply message including the data sent in accordance with step ST17 or the data merged in step ST20 (ST21).
- this data is hourly data (eg, device ID, date / time, supply power prediction, maximum power prediction value) between the designated device ID, start date / time, and end date / time.
- the supply capacity means the ability to generate electricity.
- the maximum power means the maximum value of power used by the device.
- Example 7 When making a request to the external application unit 20 and acquiring necessary data.
- Example 8 When acquiring information (active power, power generation output, voltage, current, frequency, etc.) for a certain period of time from the external application unit 20.
- step ST2 as shown in FIG. 14, it is assumed that the security adapter 17 receives a message from any of the internal application units 13A to 13C (ST22).
- this message includes in the data portion a device ID indicating a device from which data is to be acquired, a start date and time and an end date and time indicating a certain period.
- the security adapter 17 decodes the received message, accesses the authentication DB 16, searches for flow information based on the service name in the message, and is associated with the service name that matches the service name in the flow information.
- the external application unit 20 is specified by the application name indicating the external application unit 20 (ST23).
- the security adapter 17 executes message processing such as encryption processing based on the identified result (ST24).
- message processing such as encryption processing based on the identified result (ST24).
- the public key of the identified external application unit 20 is used.
- the security adapter 17 transmits the message processed in step ST24 to the external application unit 20 (ST25).
- the security adapter 17 receives a message from the external application unit 20 (ST26).
- the received message includes a device ID indicating a device from which data is to be acquired, hourly data between the start date and time and the end date and time (eg, device ID, date and time, supply power prediction, maximum power prediction Value).
- the security adapter 17 decodes the received message, accesses the authentication DB 16, performs authentication, determines the type of application, and specifies the application to be called (ST27).
- the security adapter 17 processes the message (ST28).
- the security adapter 17 returns a message to the application specified in step ST27 (ST29).
- the security adapter 17 is configured to intervene in communication between the internal application units 13A to 13C and the external application unit 20 to access the internal application from the external application. Furthermore, it is possible to prevent leakage of processing contents and data of the internal application and identification of the internal application.
- the security adapter 17 makes a call to the required internal application A,... By authenticating the connection from the external application unit 20. As a result, the following effects (1) to (4) can be obtained.
- the mechanism of the internal applications A to C is disclosed to the external application unit 20.
- the mechanism of the internal applications A to C can be concealed from the outside by making only the security adapter 17 visible from the external application unit 20.
- the locations of the internal applications A to C are specified.
- only the security adapter 17 can be seen from the external application unit 20, thereby concealing the locations of the internal applications A to C and preventing attacks from the outside.
- the security adapter 17 controls access to the internal applications A to C by confirming the authority of the user.
- the request message received from the external application unit 20 is received by the security adapter 17 to authenticate the request message and confirm the authority, thereby realizing appropriate access control for the internal application units 13A to 13C. it can.
- the common bus 14 and the security adapter 17 can be specified.
- the security adapter 17 may cause an unexpected situation such as a situation in which processing content is leaked or an attack is received.
- the common bus 14 is duplicated so that only the common bus dedicated to the external application can be seen from the external application unit 20.
- the security adapter 17 can also be concealed from the outside.
- Duplicated common buses can be connected by the routing function.
- FIG. 20 is a schematic diagram showing a monitoring device to which the security adapter program according to the second embodiment is applied and its peripheral configuration.
- This embodiment is a modification of the first embodiment, and the monitoring apparatus 10 can transmit a request message and a transmission message individually between the security adapter 17 and the external application unit 20, and an external dedicated common bus (first 2 common bus) 18.
- the reception function (f17-1) of the security adapter 17 receives the request message from the external application unit 20 via the external dedicated common bus 18.
- the transmission function (f17-4) of the security adapter 17 transmits a transmission message to the external application unit 20 via the external dedicated common bus 18.
- FIG. 21 is a schematic diagram showing a monitoring device to which the security adapter program according to the third embodiment is applied and its peripheral configuration.
- This embodiment is a modification of the first embodiment, and the security adapter 17 can transmit a transmission message to the external cloud DB 21.
- the transmission function (f17-4) of the security adapter 17 has the following functions (f17-4-1) to (f17-4-3).
- (F17-4-1) A determination function that, upon receiving a transmission message, determines whether the transmission message includes the result requested by the request message.
- this first transmission function can also transmit a transmission result notification indicating, for example, “Success” or “error” to the external application unit 20 after transmission to the cloud DB 21.
- the monitoring device 10 activates the security adapter 17 when a processor (not shown) starts executing the security adapter program (ST31).
- the security adapter 17 performs a connection process to the common bus 14 and the authentication DB 16 as an initialization process (ST32).
- step ST2 it is assumed that the security adapter 17 receives a message from the external application unit 20 (ST33).
- This message is assumed to be a request message.
- the data in the request message includes a device ID, a start date / time, and an end date / time for designating the requested data in the data part as shown in FIG. 17, for example.
- the security adapter 17 decodes the received message, accesses the authentication DB 16, performs authentication, determines the type of application, and specifies the application to be called (ST34).
- the security adapter 17 processes the message (ST35).
- the security adapter 17 sends the data in the message and calls, for example, the internal application C (ST36).
- the internal application unit 13C that operates in response to this call reads out the power system DB 12 based on the transmitted data, and transmits the read result data to the security adapter 17.
- the security adapter 17 calls the internal application A in the order of the flow information (ST37) and receives the processing result from the internal application unit 13A. Subsequently, the security adapter 17 calls the internal application B in the order of the flow information (ST38), and receives the processing result from the internal application unit 13B.
- the security adapter 17 merges the processing results received in steps ST37 and ST38 (ST39).
- the security adapter 17 determines whether or not the transmission message includes a result requested by the request message. If the result of this determination includes the requested result, the security adapter 17 transmits the transmission message to the external cloud DB 21 and writes the data in the transmission message to the cloud DB 21 (ST40).
- This data is, for example, hourly data between the designated device ID, start date and time and end date and time (eg, device ID, date and time, supply power prediction, maximum power prediction value) as shown in FIG. is there.
- the security adapter 17 transmits the transmission message to the external application unit 20 when the result of the determination is negative.
- the security adapter 17 transmits the result to the cloud DB 21 without returning the requested result to the external application unit 20, in addition to the effects of the first embodiment.
- the external application unit 20 can access the authentication system of the cloud DB 21 and check the result.
- the data stored in the cloud DB 21 is updated according to the processing result in response to the request from the external application unit 20 with the configuration in which the cloud DB 21 to which the processing result is written is set in the security adapter 17 in advance.
- This enables access from various external application units 20,... And reduces the load of message processing (encryption and others) when returning data.
- the external application unit 20,... Can confirm the result written in the cloud DB 21 by receiving authentication by the authentication system of the cloud DB 21.
- FIG. 23 is a schematic diagram showing a monitoring device to which the security adapter program according to the fourth embodiment is applied and its peripheral configuration.
- the present embodiment is a modified example in which the second and third embodiments are combined, and the monitoring apparatus 10 can externally transmit a request message and a transmission message between the security adapter 17 and the external application unit 20.
- a dedicated common bus (second common bus) 18 is provided, and the security adapter 17 is configured to transmit a transmission message to the external cloud DB 21.
- the security adapter 17 is configured to intervene in communication between each internal application unit and the external application unit 20, so that when accessing the internal application from the external application, It is possible to prevent leakage of processing contents and data of the internal application and identification of the internal application.
- the storage medium can store a program and can be read by a computer
- the storage format may be any form.
- an OS operating system
- MW middleware
- database management software network software
- the storage medium in each embodiment is not limited to a medium independent of a computer, but also includes a storage medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.
- the number of storage media is not limited to one, and the case where the processing in each of the above embodiments is executed from a plurality of media is also included in the storage media in the present invention, and the media configuration may be any configuration.
- the computer in each embodiment executes each process in each of the above embodiments based on a program stored in a storage medium, and a single device such as a personal computer or a plurality of devices are connected to a network. Any configuration of the system or the like may be used.
- the computer in each embodiment is not limited to a personal computer, and includes an arithmetic processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions of the present invention by a program. Yes.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- Tourism & Hospitality (AREA)
- Bioethics (AREA)
- Primary Health Care (AREA)
- Water Supply & Treatment (AREA)
- Databases & Information Systems (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Public Health (AREA)
- Game Theory and Decision Science (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
図6は第1の実施形態に係るセキュリティアダプタプログラムを適用した監視装置及びその周辺構成を示す模式図であり、図4及び図5に示した構成と同一部分には同一符号を付してその詳しい説明を省略し、ここでは異なる部分について主に述べる。なお、以下の各実施形態も同様にして重複した説明を省略する。また、図4等に示した構成と同一部分とは、監視装置10において、電力系統DB(データ記憶部)12、複数の内部アプリケーション部13A~13C、共通バス(第1共通バス)14及び複数のバス接続アダプタ15A~15Cを備えた構成である。また、電力系統DB12は、複数の機器#1~#nから受信したデータを記憶する。複数の内部アプリケーション部13A~13Cは、電力系統DB12内のデータを含むメッセージを互いに送受信する。共通バス(第1共通バス)14は、各内部アプリケーション部13A~13C間でメッセージを伝送可能なバスである。複数のバス接続アダプタ15A~15Cは、各内部アプリケーション部13A~13Cと共通バス14とを個別に接続する。
次に、第2の実施形態について概要を説明する。
図21は第3の実施形態に係るセキュリティアダプタプログラムを適用した監視装置及びその周辺構成を示す模式図である。
図23は第4の実施形態に係るセキュリティアダプタプログラムを適用した監視装置及びその周辺構成を示す模式図である。
Claims (5)
- 複数の機器から受信したデータを記憶するデータ記憶部と、前記データ記憶部内のデータを含むメッセージを互いに送受信する複数の内部アプリケーション部と、前記各内部アプリケーション間でメッセージを伝送可能な第1共通バスと、前記各内部アプリケーション部と前記第1共通バスとを個別に接続する複数のバス接続アダプタとを備えた監視装置に用いられるセキュリティアダプタプログラムであって、
前記監視装置は、前記各内部アプリケーション部による処理の種類を示すサービス名と、前記各内部アプリケーション部を識別するアプリケーション名とを関連付けて記憶した第1記憶手段を更に備えており、
前記監視装置を、
前記各内部アプリケーション部と前記外部アプリケーション部との間の通信に介在するセキュリティアダプタ手段、
として更に機能させ、
前記セキュリティアダプタ手段は、
前記サービス名を指定した要求メッセージを外部アプリケーション部から受信する受信手段と、
前記受信した要求メッセージ内のサービス名に基づいて前記第1記憶手段を検索し、当該検索により得られたアプリケーション名を宛先に含むように前記要求メッセージを加工する第1加工手段と、
前記加工された要求メッセージを前記宛先のアプリケーション名が識別する内部アプリケーション部に伝送するように、当該加工された要求メッセージを前記第1共通バスに送出する送出手段と、
前記各内部アプリケーション部のうち、いずれかの内部アプリケーション部から前記バス接続アダプタ及び前記第1共通バスを介して送信メッセージを受けると、当該送信メッセージを前記外部アプリケーション部に送信する送信手段と
を含んでいることを特徴とするセキュリティアダプタプログラム。 - 請求項1に記載のセキュリティアダプタプログラムにおいて、
前記監視装置は、
前記外部アプリケーション部を操作するユーザを識別するユーザIDと、前記ユーザを認証するパスワードとを関連付けて記憶した第2記憶手段と、
前記ユーザIDと、前記サービス名と、前記ユーザの権限を示す権限情報とを関連付けて記憶した第3記憶手段と、を更に備えており、
前記セキュリティアダプタ手段は、
前記ユーザID、前記パスワード及び前記サービス名を含む要求メッセージを前記受信手段が受信した場合に、前記受信した要求メッセージ内の前記ユーザID及び前記パスワードを前記第2記憶手段内のユーザID及びパスワードに照合することにより、当該要求メッセージの正当性を認証する認証手段と、
前記認証に成功した要求メッセージ内のサービス名に基づいて前記第3記憶手段を検索し、当該検索により得られた権限情報を含むように前記要求メッセージを加工する第2加工手段と、
前記認証に失敗した場合に、前記第1加工手段及び前記送出手段の実行を阻止する阻止手段と
を更に含んでいることを特徴とするセキュリティアダプタプログラム。 - 請求項1又は請求項2に記載のセキュリティアダプタプログラムにおいて、
前記監視装置は、前記受信手段及び前記送信手段と前記外部アプリケーション部との間で前記要求メッセージ及び前記送信メッセージを個別に伝送可能な第2共通バスを更に備えており、
前記受信手段は、前記要求メッセージを前記外部アプリケーション部から前記第2共通バスを介して受信し、
前記送信手段は、前記送信メッセージを前記第2共通バスを介して前記外部アプリケーション部に送信することを特徴とするセキュリティアダプタプログラム。 - 請求項1乃至請求項3のいずれか1項に記載のセキュリティアダプタプログラムにおいて、
前記送信手段は、
前記送信メッセージを受けると、当該送信メッセージが前記要求メッセージにより要求された結果を含むか否かを判定する判定手段と、
前記判定の結果、前記要求された結果を含む場合には当該送信メッセージを所定の外部クラウド記憶手段に送信する第1送信手段と、
前記判定の結果、前記否の場合には当該送信メッセージを前記外部アプリケーション部に送信する第2送信手段と
を含んでいることを特徴とするセキュリティアダプタプログラム。 - 複数の機器から受信したデータを記憶するデータ記憶部と、前記データ記憶部内のデータを含むメッセージを互いに送受信する複数の内部アプリケーション部と、前記各内部アプリケーション間でメッセージを伝送可能な第1共通バスと、前記各内部アプリケーション部と前記第1共通バスとを個別に接続する複数のバス接続アダプタとを備えた監視装置に用いられ、前記各内部アプリケーション部と前記外部アプリケーション部との間の通信に介在するセキュリティアダプタ手段を備えたセキュリティアダプタ装置であって、
前記監視装置は、前記各内部アプリケーション部による処理の種類を示すサービス名と、前記各内部アプリケーション部を識別するアプリケーション名とを関連付けて記憶した第1記憶手段を更に備えており、
前記セキュリティアダプタ手段は、
前記サービス名を指定した要求メッセージを外部アプリケーション部から受信する受信手段と、
前記受信した要求メッセージ内のサービス名に基づいて前記第1記憶手段を検索し、当該検索により得られたアプリケーション名を宛先に含むように前記要求メッセージを加工する第1加工手段と、
前記加工された要求メッセージを前記宛先のアプリケーション名が識別する内部アプリケーション部に伝送するように、当該加工された要求メッセージを前記第1共通バスに送出する送出手段と、
前記各内部アプリケーション部のうち、いずれかの内部アプリケーション部から前記バス接続アダプタ及び前記第1共通バスを介して送信メッセージを受けると、当該送信メッセージを前記外部アプリケーション部に送信する送信手段と
を備えたことを特徴とするセキュリティアダプタ装置。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2012/064715 WO2013183150A1 (ja) | 2012-06-07 | 2012-06-07 | セキュリティアダプタプログラム及び装置 |
EP12878309.9A EP2860653A4 (en) | 2012-06-07 | 2012-06-07 | SECURITY ADAPTER PROGRAM AND DEVICE |
JP2012542254A JP5398919B1 (ja) | 2012-06-07 | 2012-06-07 | セキュリティアダプタプログラム及び装置 |
US14/553,239 US20150082464A1 (en) | 2012-06-07 | 2014-11-25 | Security adapter program and security adapter apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2012/064715 WO2013183150A1 (ja) | 2012-06-07 | 2012-06-07 | セキュリティアダプタプログラム及び装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/553,239 Continuation US20150082464A1 (en) | 2012-06-07 | 2014-11-25 | Security adapter program and security adapter apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013183150A1 true WO2013183150A1 (ja) | 2013-12-12 |
Family
ID=49711567
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/064715 WO2013183150A1 (ja) | 2012-06-07 | 2012-06-07 | セキュリティアダプタプログラム及び装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20150082464A1 (ja) |
EP (1) | EP2860653A4 (ja) |
JP (1) | JP5398919B1 (ja) |
WO (1) | WO2013183150A1 (ja) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10075514B2 (en) | 2015-08-28 | 2018-09-11 | Vmware, Inc. | Scalable monitoring of long running multi-step data intensive workloads |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07244639A (ja) * | 1994-03-03 | 1995-09-19 | Fujitsu Ltd | アクセス権管理装置 |
JP2002269059A (ja) * | 2001-03-08 | 2002-09-20 | Ntt Comware Corp | クライアントサーバシステム、中継サーバ、クライアント端末装置の接続先サーバ決定方法 |
JP2009213238A (ja) | 2008-03-04 | 2009-09-17 | Tokyo Electric Power Co Inc:The | 電力情報統合管理システム |
JP2012069057A (ja) * | 2010-09-27 | 2012-04-05 | Nec Corp | 情報処理装置、情報処理システム、メッセージ処理方法およびメッセージ処理プログラム |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101303717B (zh) * | 1995-02-13 | 2015-04-29 | 英特特拉斯特技术公司 | 用于安全交易管理和电子权利保护的系统和方法 |
FI20010828A (fi) * | 2001-04-23 | 2002-10-24 | Nokia Corp | Erilaisten palveluversioiden käsitteleminen palvelimessa |
US7165256B2 (en) * | 2001-09-11 | 2007-01-16 | Sun Microsystems, Inc. | Task grouping in a distributed processing framework system and methods for implementing the same |
CA2404602C (en) * | 2001-09-21 | 2009-07-14 | Corel Corporation | Web services gateway |
US7743257B2 (en) * | 2002-06-27 | 2010-06-22 | Nxp B.V. | Security processor with bus configuration |
AP2005003476A0 (en) * | 2003-06-05 | 2005-12-31 | Intertrust Tech Corp | Interoperable systems and methods for peer-to-peerservice orchestration. |
JP5205965B2 (ja) * | 2004-04-28 | 2013-06-05 | 富士通株式会社 | コンピュータシステム、サーバー処理装置、端末装置及び方法 |
US20060116138A1 (en) * | 2004-11-29 | 2006-06-01 | Argela Technologies | Value added services creation (vasc) platform |
US7920583B2 (en) * | 2005-10-28 | 2011-04-05 | Accenture Global Services Limited | Message sequencing and data translation architecture for telecommunication services |
US20090164738A1 (en) * | 2007-12-21 | 2009-06-25 | Microsoft Corporation | Process Based Cache-Write Through For Protected Storage In Embedded Devices |
US8219595B2 (en) * | 2008-02-14 | 2012-07-10 | Hewlett-Packard Development Company, L.P. | System and method for efficient remote data access for server management |
JP5371613B2 (ja) * | 2009-08-03 | 2013-12-18 | 三菱電機株式会社 | サービス連携装置 |
US9852150B2 (en) * | 2010-05-03 | 2017-12-26 | Panzura, Inc. | Avoiding client timeouts in a distributed filesystem |
US8903891B2 (en) * | 2010-06-24 | 2014-12-02 | Sap Se | User interface communication utilizing service request identification to manage service requests |
WO2012042509A1 (en) * | 2010-10-01 | 2012-04-05 | Peter Chacko | A distributed virtual storage cloud architecture and a method thereof |
-
2012
- 2012-06-07 JP JP2012542254A patent/JP5398919B1/ja active Active
- 2012-06-07 EP EP12878309.9A patent/EP2860653A4/en not_active Withdrawn
- 2012-06-07 WO PCT/JP2012/064715 patent/WO2013183150A1/ja active Application Filing
-
2014
- 2014-11-25 US US14/553,239 patent/US20150082464A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07244639A (ja) * | 1994-03-03 | 1995-09-19 | Fujitsu Ltd | アクセス権管理装置 |
JP2002269059A (ja) * | 2001-03-08 | 2002-09-20 | Ntt Comware Corp | クライアントサーバシステム、中継サーバ、クライアント端末装置の接続先サーバ決定方法 |
JP2009213238A (ja) | 2008-03-04 | 2009-09-17 | Tokyo Electric Power Co Inc:The | 電力情報統合管理システム |
JP2012069057A (ja) * | 2010-09-27 | 2012-04-05 | Nec Corp | 情報処理装置、情報処理システム、メッセージ処理方法およびメッセージ処理プログラム |
Non-Patent Citations (1)
Title |
---|
See also references of EP2860653A4 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2013183150A1 (ja) | 2016-01-21 |
EP2860653A4 (en) | 2016-01-27 |
US20150082464A1 (en) | 2015-03-19 |
EP2860653A1 (en) | 2015-04-15 |
JP5398919B1 (ja) | 2014-01-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111898153B (zh) | 调用合约的方法及装置 | |
US20240048376A1 (en) | Methods and systems implemented in a network architecture with nodes capable of performing message-based transactions | |
JP4892093B1 (ja) | 認証連携システム及びidプロバイダ装置 | |
US10819701B2 (en) | Autonomous secrets management for a managed service identity | |
CN101196974B (zh) | 用于软件应用程序的自动配置的方法和系统 | |
US8549326B2 (en) | Method and system for extending encrypting file system | |
US9106406B2 (en) | Communication apparatus and key managing method | |
US8549112B2 (en) | Computer-readable medium storing access control program, access control method, and access control device | |
JP4257785B2 (ja) | キャッシュストレージ装置 | |
CN108289098B (zh) | 分布式文件系统的权限管理方法和装置、服务器、介质 | |
US10691790B2 (en) | Autonomous secrets management for a temporary shared access signature service | |
US20110138475A1 (en) | Systems and method for providing trusted system functionalities in a cluster based system | |
KR20020001190A (ko) | 네트워크망에서 내부자원의 보호기능이 강화된 보안장치및 그 운용방법 | |
CN102546664A (zh) | 用于分布式文件系统的用户与权限管理方法及系统 | |
US11399013B2 (en) | Secure service mesh | |
CN114679274A (zh) | 跨子网交互的权限控制方法及装置、电子设备、存储介质 | |
JP7194212B2 (ja) | 認証方法及び装置、コンピューティング機器、並びに媒体 | |
US20200272708A1 (en) | Computer system, computer apparatus, and license management method | |
JP5398919B1 (ja) | セキュリティアダプタプログラム及び装置 | |
US11715079B2 (en) | Maintaining secure access to a self-service terminal (SST) | |
KR20210082481A (ko) | 데이터베이스 관리 서비스 제공 시스템 | |
US20110093582A1 (en) | Transparent resource administration using a read-only domain controller | |
JP5537668B2 (ja) | バス接続プログラム及び装置 | |
CN115001707B (zh) | 基于区块链的设备认证方法和相关设备 | |
US20220300597A1 (en) | Authenticator management device, computer readable medium and authenticator management method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2012542254 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12878309 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2012878309 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012878309 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |