JP2017188121A - Management device, control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management device capable of managing a security policy safely so that the security policy may not be changed carelessly, and suitably and simultaneously distributing to a plurality of devices on a network to reflect the security policy.SOLUTION: A device management device includes: setting a first password that is required for reflecting a security policy managed by itself on the device or changing on the device; generating distribution data containing the security policy and the set first password; and distributing the generated distribution data to a selected device.SELECTED DRAWING: Figure 8

Description

  The present invention relates to a technology for distributing setting information (security policy) for security to devices via a network.

  Conventionally, there is a technique for distributing setting information to devices such as image forming apparatuses existing on a network. The setting information includes information related to a user who uses the device, address book information, a setting value of an application operating on the device, and the like. For example, Patent Document 1 discloses a technique for distributing a part of setting information acquired by a management apparatus from a device before replacement to the device after replacement when the device is replaced.

JP 2013-243488 A

  In recent years, it has been required for various devices to be set in accordance with security guidelines in line with network environments and office operations. Settings related to security guidelines are generally called security policies.

  A security policy is a setting used to ensure security. If there is a difference in security policy between devices in the same organization, there is a risk of a security hole. Therefore, it is considered that the security policy should be distributed to all devices on the network at once to reflect the setting.

  However, the security policy is not a simple setting assumed in Patent Document 1 described above, but serves as a guideline for organizational security. Therefore, it is a big problem if it can be changed on each device after distribution. Therefore, a security policy needs to be distributed on the network in consideration of convenience while taking a management system different from normal setting information.

  In order to solve the above-described problem, the present invention is a management apparatus that manages devices that can communicate over a network, and is a first management that manages a security policy that indicates a setting value of a setting item related to device security. Means, a selecting means for selecting a device to which the managed security policy is to be distributed, and a first password required for reflecting the security policy on the device or changing the security policy on the device. Setting means for setting, generating means for generating distribution data including the security policy and the set first password, and distribution means for distributing the generated distribution data to the selected device; It is characterized by having.

  According to the present invention, it is possible to safely manage the security policy so that it is not inadvertently changed, and simultaneously distribute the security policy to a plurality of devices on the network to reflect the security policy.

The figure which shows the structural example of the network system in this invention. The figure explaining the example of the hardware constitutions of the management apparatus 101. FIG. The figure explaining the example of the hardware constitutions of a device. The figure explaining the module structural example of the software of the management apparatus 101. FIG. The figure which shows an example of the operation screen of the security policy which a device provides. The figure which shows an example of the operation screen of the device in which the security policy was reflected. 6 is a diagram showing an example of a security policy setting screen provided by the management apparatus 101. FIG. 6 is a flowchart for explaining a process in which the management apparatus 101 distributes setting information to a device. The figure which shows an example of the screen for selecting a security policy. The figure which shows an example of the screen for selecting the device used as delivery object. The figure which shows an example of the screen for receiving the input of a policy password. The figure which shows an example of the setting information which the management apparatus 101 delivers to a device. The figure showing an example of the setting content of a security policy. 6 is a flowchart for explaining setting information export processing of the management apparatus 101; The figure which shows an example of the screen which inputs the various information required for export. The figure explaining the module structural example of the software of the devices 102-104. The flowchart for demonstrating the process which the devices 102-104 receive setting information. The figure which shows the example of the content of the device information database 409 which the management apparatus 101 manages. 9 is a flowchart for explaining processing for acquiring setting information from a device of the management apparatus 101 according to the second embodiment. FIG. 10 is a diagram illustrating an example of setting information acquired by the management apparatus 101 according to the second embodiment. FIG. 10 is a diagram illustrating a security policy managed by a setting information database 408 according to the second embodiment. 10 is a flowchart for explaining processing in which the management apparatus 101 according to the second embodiment distributes setting information to a device. FIG. 10 is a diagram illustrating an example of a screen for accepting an input of a policy password in the second embodiment.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

[Example 1]
FIG. 1 shows a network system to which the present invention is applicable. In this system, a management apparatus 101 that manages devices on a network operates.

  Reference numerals 102, 103, and 104 denote devices to be managed by the management apparatus that exist on a network such as the LAN 100. Examples of the device include an image forming apparatus including a printer, a copier, a scanner, a camera, and the like, a smartphone, a tablet, and the like.

  FIG. 2 is a diagram illustrating a hardware configuration example of the management apparatus 101. In the present invention, the management device can be realized by a general PC (personal computer).

  The hard disk (HDD) 212 stores a device management software program according to the present embodiment, which is an operation subject in all the descriptions below. Reference numeral 201 denotes a CPU, which is an execution subject on hardware unless otherwise specified in all the descriptions below. On the other hand, the control subject in software is device management software (program) stored in the hard disk (HDD) 212 as described above. That is, the CPU 201 reads out and executes a device management program recorded in the HDD 212 so as to be readable by a computer, thereby realizing the function of the management apparatus 101 described later. A ROM 202 stores a BIOS and a boot program. Reference numeral 203 denotes a RAM that functions as a main memory, work area, and the like for the CPU 201. A keyboard controller (KBC) 205 controls instruction input from the keyboard (KB) 209, the pointing device (PD) 210, and the like. A display controller (DSPC) 206 controls display on the display (DSP) 211. A disk controller (DKC) 207 controls access to a storage device such as a hard disk (HDD) 212 or a CD-ROM (CD) 213. A hard disk (HDD) 212, a CD-ROM (CD) 213, and the like store a boot program, an operating system, a database, a device management program, data thereof, and the like. An interface controller (IFC) 208 transmits and receives information to and from other network devices via a LAN (Local Area Network). The connection with the network may be wired / wireless. Each of these components is arranged on the system bus 204.

  In this embodiment, the OS (operating system) is assumed to be, for example, Windows (registered trademark) manufactured by Microsoft Corporation, but is not limited thereto.

  FIG. 3 is a diagram illustrating the internal configuration of the devices 102, 103, and 104. FIG. 3 illustrates an image forming apparatus having a printing function, a scanning function, a network communication function, and the like as an example of a device.

  A CPU 301 controls the entire image forming apparatus. A ROM 302 stores a print processing program executed by the CPU 301 and font data. Reference numeral 303 denotes a work area of the CPU 301, a reception buffer, and a RAM used for image drawing. A hard disk (HDD) 304 records setting values of the image forming apparatus 300. An operation panel 305 includes various switches and buttons, a touch panel, and a liquid crystal display unit for displaying messages. On the operation panel 305, a user can operate setting values of the image forming apparatus. Reference numeral 306 denotes a network interface for connecting to a network. A printer engine 307 performs printing on recording paper. Reference numeral 308 denotes a scanner for reading a document. Reference numeral 309 denotes a communication unit for performing facsimile transmission / reception.

  FIG. 4 is a diagram illustrating an example of a module configuration realized by executing the device management software 400 operating on the management apparatus 101. As described above, the device management software 400 is read from the HDD 212 and executed by the CPU 201.

  The UI control unit 401 provides a graphical user interface (GUI) for accepting the operation of the device administrator. The GUI is configured to be displayed on a display 211 provided in the management apparatus 101. Alternatively, the GUI can be configured as a Web application that can be used from another client PC by using HTTP (HyperText Transfer Protocol). In that case, the administrator performs an operation via a GUI displayed on a web browser of the client PC.

  The device management unit 402 searches for a device connected to the LAN 100 via the search unit 406. The device search by the search unit 406 can be realized by transmitting a search request packet such as SLP (Service Location Protocol) or SNMP (Simple Network Management Protocol). Further, the device management unit 402 further provides device information (device name, model name, serial number, capability, etc.) indicating details about the device discovered by the search of the search unit 406 via the communication unit 407. Status etc.) can also be obtained. The device management unit 402 also stores and manages device address information (IP address, MAC address, GPS information, etc.) and device information acquired from the device in the device information database 409. Information registered in the database can be browsed by the user in the form of a device list or the like via the UI control unit 401.

  The setting information management unit 403 instructs the setting information acquisition unit 404 to acquire setting information from the device via the communication unit 407 and store it in the setting information database 408. The setting information stored in the setting information database 408 can be browsed by the user via the UI control unit 401. Also, the setting information management unit 403 can control distribution of the setting information stored in the setting information database 408 to the devices via the setting information distribution unit 405. In addition, setting information acquired from another management apparatus other than the device, and setting information imported by a file when the administrator manually operates the device management unit, are stored in the setting information database 408 and managed. Is possible. The setting information distribution unit 405 distributes setting information to the device via the communication unit 407.

  Here, in the present invention, the setting information acquisition unit 404 and the setting information distribution unit 405 realize acquisition and distribution of device setting information through a communication unit 407 using a Web service using HTTP / SOAP. Note that acquisition and distribution of device setting information may be realized using other communication protocols.

  In addition, when setting information is acquired by the setting information acquisition unit 404, only setting values of predetermined setting items can be acquired. Further, it is also possible to configure to acquire the setting value of the setting item selected by the user via the UI control unit 401. Similarly, when setting information is distributed by the setting information distribution unit 405, a setting value of a predetermined setting item or a setting item selected by the user can be distributed.

  FIG. 5 is an explanatory diagram illustrating an example of an operation screen related to a security policy provided by a device. The device security policy setting screen can be displayed on the operation panel 305 of the device, or can be displayed by accessing a device web server (not shown) from a PC such as the management apparatus 101 using a web browser. .

  FIG. 5A shows a confirmation screen for the security policy. FIG. 5A shows the current security policy. The illustrated policy version is version information corresponding to the contents of the security policy. Each security policy having a different policy version has different items that can be set in the security policy. In FIG. 5A, the user is prompted to enter a password for changing the security policy. In this embodiment, this password is called a “policy password”. The policy password is a dedicated password used only for changing the security policy, unlike the login password for the login process that is performed in order to perform the normal operation of the device. That is, even a user who can log in and operate the device cannot change the security policy without knowing the policy password.

  FIG. 5B is an example of a security policy setting screen displayed when the correct policy password is input in FIG. In FIG. 5B, setting values of various security policy items defined as policy version 1.00 can be changed. When an “OK” button is pressed after an input for enabling or disabling is performed for the item shown in the figure, the change of the setting value is reflected.

  FIG. 6 is a diagram illustrating an example of an operation screen on the operation panel 305 of the device.

  The security policy shown in FIG. 5 is reflected on the operation screen shown in FIG. In the example of FIG. 5, FAX transmission and use of the USB interface are prohibited as security policies. Therefore, in FIG. 6A, the menus for operations relating to “scan and fax transmission” and “USB memory” are invalidated, and the user cannot operate them. When the user selects an invalid menu, a message indicating that the function cannot be executed according to the security policy may be displayed as shown in FIG. In the security policy, there are setting items for restrictions on the function of transmitting data to the outside such as FAX and e-mail, and the function of the interface part such as USB and panel unit. In addition, there may be setting items such as function restrictions related to the authentication function of the device.

  FIG. 7 is a diagram illustrating an example of a setting screen for a security policy provided by the management apparatus 101.

  In this figure, unlike FIG. 5, the policy name and policy version can be further specified. Since the management apparatus 101 may manage a plurality of security policies in consideration of each department or organization, the policy name is managed to identify each security policy.

  The security policy can be newly created or edited using the setting screen of the management apparatus 101 shown in FIG. Also, a new security policy can be created by importing an exported setting file, which will be described later with reference to FIG.

  FIG. 8 is a flowchart for explaining processing in which the management apparatus 101 distributes setting information to the devices 102 to 104. The process shown in the flowchart of FIG. 8 is realized by executing the device management software 400 of the management apparatus 101.

  In step S801, the setting information distribution unit 405 executes a security policy selection process to be distributed. Specifically, first, the setting information distribution unit 405 acquires a security policy list from the setting information database 408 via the setting information management unit 403. Then, a list of security policies acquired by the UI control unit 401 is displayed using the GUI (FIG. 9), and a user's selection is accepted.

  FIG. 9 is a diagram showing an example of a screen for selecting a security policy displayed in S801. The list of security policies shown in FIG. 9 includes, for example, two security policies whose policy names are “public space” and “head office department”. Information such as the policy version of each security policy and the last update date is also displayed. Only one security policy can be selected via this screen. In the example of FIG. 9, the “public space” security policy is selected with a radio button.

  In step S <b> 802, the setting information distribution unit 405 executes processing for selecting a device that is a security policy distribution target. Specifically, first, the setting information distribution unit 405 acquires a list of devices from the device information database 409 via the setting information management unit 403. Then, a list of devices acquired by the UI control unit 401 is displayed using the GUI (FIG. 10), and a user's selection is accepted. The user is assumed to be an administrator in charge of network device maintenance, asset management, or a policy administrator who manages organizational policies.

  FIG. 10 is a diagram illustrating an example of a screen for selecting a device displayed in S802. The device list shown in FIG. 10 includes three devices whose device names are “device A”, “device B”, and “device C”. This screen also displays device information such as the device model name and installation location in addition to the policy version supported by each device. One or a plurality of devices to be distributed as a security policy can be selected. In the example of FIG. 10, device A and device B are selected.

  Note that the devices displayed in a list in FIG. 10 may be narrowed down to only those that can distribute the security policy selected in S801. Whether the distribution is possible is determined by comparing the policy version of the security policy selected in S801 with the policy version supported by each device stored in the device information database 409. In the example of FIG. 10, since it is assumed that the security policy is backward compatible, the policy version V1.00 in the device list is different from the policy version V1.00 of the security policy “public space” to be distributed. The following are displayed. That is, devices that support only policy version V0.50 are not displayed in this list, while device B that supports policy version V1.10 is included in this list and displayed. become.

  In step S803, the setting information distribution unit 405 checks whether the security policy has been distributed to all the devices selected in step S802. Here, if the distribution of the security policy has been completed for all the devices, this distribution processing is terminated. If there is a device to which no security policy is distributed, the processing from S804 onward is executed with one device as a processing target device.

  In step S804, the setting information distribution unit 405 checks whether the policy password information of the target device exists in the device information database 409 through the setting information management unit 403. If the policy password of the target device exists in the database, the process proceeds to S805, and if not, the process proceeds to S806. In step S805, the setting information distribution unit 405 reads and acquires the policy password information of the target device from the device information database 409 via the setting information management unit 403.

  In step S806, the setting information distribution unit 405 receives an input of a policy password for a security policy to be distributed to the target device. Here, as shown in FIG. 11, the UI control unit 401 uses the GUI to display and accepts user input. FIG. 11A shows a setting screen for accepting an input of a policy password by the user. When the policy password can be acquired in S805, the policy password is displayed in advance. The user can also edit the policy password.

  In step S807, the setting information distribution unit 405 stores the policy password received in step S806 in the device information database 409 via the setting information management unit 403 as the device information. In step S808, the setting information distribution unit 405 generates setting information as distribution data based on the security policy selected in step S801 and the policy password set in steps S805 to S807. In step S809, the setting information distribution unit 405 distributes the setting information generated in step S808 to the target device via the communication unit 407.

  In the process shown in FIG. 8, the policy password is set for each of a plurality of distribution target devices, the setting information is generated, and the distribution process is performed. However, it is also possible to set the policy password for all the devices selected in S802, generate setting information, and perform distribution processing all at once. Specifically, in S806, as shown in FIG. 11B, a screen for accepting the input of a policy password is provided to all the selected delivery target devices.

  In FIG. 11B, for the device A for which the security policy has not been distributed before, the policy password is not stored in the device information database 409, so the text box is blank. On the other hand, since the policy password at the time of distributing the security policy in the past is stored in the device information database 409, the device B is in a state in which the policy password is input in advance in the text box. Since policy passwords for a plurality of devices are input on this screen, setting information distribution processing for the plurality of devices can be performed by the processing in S807 to S809.

  In FIG. 11B, when a policy password is entered in any one of the text boxes, an instruction unit for collectively setting the same policy password may be provided in another device. As a result, the same policy password can be easily set for a plurality of devices at once.

  FIG. 18 is a diagram showing the contents included in the device information database 409 managed by the management apparatus 101. It includes identification information for each device, security policy version information, policy password information, and the like.

  More specifically, as the device information, information such as the device name and serial number of each device acquired by the setting information acquisition unit 404 and the policy version to be supported is stored. There is also an area for holding a policy password for each device.

  In S804 described above, it is confirmed whether or not the policy password of the target device of interest exists in the device information database 409. Further, in the above-described S807, the policy password entered by lending the screen shown in FIG. 11 by the user is stored in the device information database 409.

  FIG. 12 is a diagram illustrating an example of setting information that the management apparatus 101 distributes to a device in step S809. This setting information is described in XML. The setting information is an example of setting information when the security policy named “public space” illustrated in FIGS. 9 and 10 is distributed to two devices named “device A” and “device B”. It is.

  FIG. 12A is an example of setting information to be distributed to “device A” generated using a security policy whose policy name is “public space”.

  Reference numeral 1201 denotes an element representing security policy setting. The management apparatus 101 includes identification information (ID) for identifying a security policy, a policy version, and a policy name as attributes. An element 1202 represents a policy password, and holds a password necessary for applying a setting related to the security policy to the device A. An element 1203 represents a setting relating to the security policy, and includes a plurality of child elements (Item tags). One Item tag corresponds to one policy item and has an attribute of identification information (ID) for identifying each item. “True” and “false” mean values indicating whether or not the policy relating to each item is valid.

  FIG. 12B is an example of setting information to be distributed to “device B” generated using a security policy whose policy name is “public space”. The element representing the policy password indicated by 1204 is different from that in FIG.

  In FIG. 12, different passwords are set for 1202 and 1204, but when the same policy password is set for device A and device B, the passwords for 1202 and 1204 are also the same.

  Note that the setting information shown in FIG. 12 may further include setting information (not shown) other than the security policy. For example, in the above-described S808, the user is further inquired whether other setting information is to be distributed. When the user inputs that other setting information is to be distributed, a screen for adding setting information as a distribution target is further displayed by the UI control unit 401 using the GUI. Here, the setting information to be added includes, for example, setting information that is not very related to security, such as address book information and user information. This additional setting information is not restricted by the above policy password. That is, even if this additional setting information is further changed via the operation screen of the device, the device does not request the input of the policy password as shown in FIG.

  FIG. 13 is a diagram illustrating an example of security policy setting contents that can be held by the management apparatus 101 and the devices 102 to 104.

  The management apparatus 101 manages a plurality of security policies as shown in FIG. More specifically, the setting contents of the security policy as shown in FIG. 13 are managed for each security policy. In the devices 102 to 104, when this security policy is distributed as setting information and applied, function restriction as shown in FIG. 6 is performed accordingly. FIG. 5 is also a setting screen for a security policy of a device having the setting contents of the security policy shown in FIG. Here, the item having the setting value “TRUE” in FIG. 13 indicates that the corresponding policy is valid. For example, since the policy item ID “I0001” is valid, the use of the user for the function for FAX transmission in the device is restricted.

  Note that the setting screen for the security policy displayed on the management apparatus 101 and each device may differ depending on the supported policy version. For example, the setting information shown in FIG. 12 includes a security policy of policy version V1.00. Only the setting items included in the security policy of the policy version V1.00 are displayed on the setting screen for the security policy provided by the device that supports the policy version V1.00. On the other hand, in a device that supports a newer version such as policy version V1.10 or the like, there may be many setting items displayed on the setting screen even when a security policy of policy version V1.00 is applied. . This is because setting items related to security have increased due to the upgrade of the security policy. Therefore, when a device that supports a newer version of the policy version or a security policy of an older version is applied, only the matching item reflects the setting value.

  FIG. 14 is a flowchart for explaining a process in which the management apparatus 101 exports setting information as a file on the file system. This process is also realized by executing the device management software 400 in the management apparatus 101.

  Here, the content of the setting information to be exported as a file is in the XML format equivalent to the setting information shown in FIG. 12, but includes information that should be treated as confidential, such as a policy password and policy settings, and is different from the policy password. Encrypt with password. In this embodiment, this password is called an encrypted password, and is handled separately from the policy password.

  First, in step S1401, the setting information distribution unit 405 executes processing for selecting a security policy to be exported. Specifically, first, the setting information distribution unit 405 acquires a security policy list from the setting information database 408 via the setting information management unit 403. Then, a list of security policies acquired by the UI control unit 401 is displayed using the GUI, and a user's selection is accepted.

  In step S1402, the setting information distribution unit 405 receives an input of a policy password for applying a security policy. Here, the input of the user's policy password is accepted using the GUI (FIG. 15) displayed by the UI control unit 401. In step S1403, the setting information distribution unit 405 receives an input of an encrypted password for encrypting the setting information. Here, the input of the user's encrypted password is further accepted using the above-described GUI ((FIG. 15)). In step S <b> 1404, the setting information distribution unit 405 receives an input of a file path that is a file output destination of setting information. Here, the user's file path input is further received using the above-described GUI ((FIG. 15)).

  In step S1405, the setting information distribution unit 405 generates setting information using the security policy and policy password in steps S1401 and S1402. In step S1406, the setting information distribution unit 405 performs export by encrypting the generated setting information and outputting it to the file path set in step S1404. Here, the exported file is decrypted by using the encryption password set in S1403.

  FIG. 15 is a diagram showing an example of a screen for inputting various information necessary for the export process of FIG. Specifically, it prompts for the policy password, encryption password, and output destination file path.

  FIG. 16 illustrates a module configuration example of software of the devices 102, 103, and 104. Here, a configuration related to software necessary for management of setting information and security policy related to the present invention will be described.

  The policy management unit 1601 controls restrictions on various functions of the device according to the security policy settings stored in the setting information database 1605.

  The analysis unit 1602 analyzes the setting information received from the management apparatus 101 via the communication unit 1604. It is determined whether the policy password included in the received setting information matches the policy password stored in the setting information database 1605. Here, only when it is determined that they match, the analysis unit 1602 updates the security policy setting stored in the setting information database 1605 with the security policy included in the received setting information. The analysis unit 1602 also updates the setting values stored in the setting information database 1605 for settings other than the security policy included in the received setting information. Here, the setting value to be updated is a setting other than the security policy included in the setting information, and only a setting within a range that does not violate the security policy already stored in the setting information database 1605. Even for settings other than the security policy included in the setting information received from the management apparatus 101, setting values that violate the security policy are ignored by the analysis unit 1602 and not reflected when the setting information database 1605 is updated.

  The setting information management unit 1603 stores or reads various setting values related to setting information including security policy settings in the setting information database 1605. Storage in the setting information database 1605 is performed according to the analysis unit 1602.

  The UI control unit 1606 provides a graphical user interface (GUI) for operating the device. The GUI is displayed on the operation panel 305 or displayed on a web browser of another PC via a web server (not shown).

  FIG. 17 is a flowchart for explaining processing when the devices 102 to 104 receive setting information. This process is realized by the CPU 301 of the device reading and executing a program related to this process recorded in the HDD 304.

  In step S <b> 1701, the communication unit 1604 receives setting information from the management apparatus 101. In step S1702, the analysis unit 1602 confirms whether the setting information received in step S1701 is encrypted. If it has been encrypted, the process proceeds to S1703. If it has not been encrypted, the process proceeds to S1704.

  Here, as a case where the setting information received from the management apparatus 101 is encrypted, the setting information once exported in the process described with reference to FIG. 14 is delivered to the devices 102 to 104 as they are. It is.

  In step S <b> 1703, the analysis unit 1602 receives a password input for decryption via the GUI displayed by the UI control unit 1606. Here, only when the input password matches the encrypted password set in the setting information, the analysis unit 1602 decrypts the setting information received from the management apparatus 101.

  In step S1704, the analysis unit 1602 determines whether the policy password included in the setting information matches the policy password stored in the setting information database 1605. If the policy passwords match, the process proceeds to S1705. If the policy passwords do not match, the process proceeds to S1706.

  In step S1705, the analysis unit 1602 executes update processing of the setting information database 1605 using the setting value related to the security policy included in the setting information received in step S1701. Specifically, the setting value of the setting item related to the security policy stored in the setting information database 1605 is updated with the setting value of the same item included in the received setting information via the setting information management unit 1603. Among the setting items related to the security policy included in the received setting information, setting items not managed by the setting information database 1605 are ignored and not reflected.

  In step S1706, the analysis unit 1602 determines whether processing for setting values of setting items other than the security policy included in the setting information received in step S1701 has been completed. If unprocessed, the process advances to step S1707. If completed, the process ends.

  In step S1707, the analysis unit 1602 reads one of the setting values of setting items other than the security policy included in the setting information received in step S1701 as a target setting value, and performs determination. Specifically, it is confirmed whether or not the target setting value violates the security policy according to the setting value stored in the setting information database 1605. For example, if the received setting information includes a setting value indicating that FAX is used as a communication method for exception notification even though FAX transmission / reception is prohibited as a security policy, it is considered a violation. Determined. If the setting value violates the security policy, the process returns to S1706. If there is no violation, the process advances to step S1708, and the analysis unit 1602 updates the setting information database 1605 using the target setting value via the setting information management unit 1603.

  Here, in S1707, the setting value determined by the analysis unit 1602 to violate the security policy is not reflected in the setting information database 1605.

  In this embodiment, a policy password is set for each device when an instruction to distribute setting information including a security policy in the management apparatus is given. The device security policy is updated only when the policy password already managed by the distribution destination device matches the password included in the distributed setting information. With this configuration, setting information including security policies for a plurality of devices can be easily distributed while preventing the security policy of each device from being easily changed.

[Example 2]
In the present embodiment, an embodiment will be described in which the management apparatus 101 acquires setting information from a specific device to be used as a backup or used as distribution data to other devices. At this time, the management apparatus 101 of the present embodiment stores and manages the security policy and policy password included in the setting information separately. When the security policy is distributed, if a predetermined condition is satisfied, the policy password that has been managed is diverted to save the trouble of inputting the password and improve the convenience.

  In the present embodiment, the same parts as those in the first embodiment are denoted by the same reference numerals, and detailed description thereof is omitted. Only differences from the first embodiment will be described below.

  FIG. 19 is a flowchart for explaining processing in which the management apparatus 101 acquires setting information from any of the devices 102 to 104. This processing is realized by the device management software 400 being executed by the management apparatus 101.

  In step S1901, the setting information acquisition unit 404 acquires setting information by making a predetermined request to the device. Here, in the request, it is also possible to acquire desired setting information of the user by specifying necessary setting items and the like.

  FIG. 20 is a diagram illustrating setting information that the management apparatus 101 acquires from a device. Basically, it is equivalent to the setting information shown in FIG. 12, but a detailed difference will be described below.

  Reference numeral 2001 denotes an element representing a security policy setting. Since this is a security policy held by the device, there is no ID or policy name existing in 1201 in FIG. An element 2002 represents a policy password, and a password stored in the setting information database 1605 on the device side is set. 2003 is an element that represents the setting contents of the security policy, and describes the setting values of each item relating to the current security policy of the device. 2004 is an element representing various types of device information different from the security policy. In the example of FIG. 20, a device name, serial number, model name, and the like are described. As in FIG. 12, the setting information shown in FIG. 20 may include various settings (not shown), address book information, and the like other than the security policy and device information.

  In step S1902, the setting information management unit 403 creates a new security policy using the setting value included in the acquired setting information, and stores the security policy in the setting information database 408. Here, the policy name of the created security policy is automatically set temporarily as “Diversion security policy” or the like in order to display a list of security policies on the setting screen of the management apparatus 101 as shown in FIG. It ’s fine. Note that no policy password is set in the security policy file created here. That is, here, the security policy in a state where the policy password indicated by 2002 in FIG. 20 is deleted is managed using a policy name such as “Diversion security policy”.

  If the policy version indicated by 2001 in FIG. 20 cannot be handled by the management apparatus 101 (unknown to the management apparatus 101), the policy version of the security policy created in S1902 is the latest one that can be handled by the management apparatus 101. The policy version. Also, among the contents of the security policy described in 2003 in FIG. 20, setting items that cannot be handled by the management apparatus 101 are ignored. Conversely, if an item included in the latest policy version that can be handled by the management apparatus 101 does not exist in 2003 in FIG. 20, a predetermined initial value is set for the policy item.

  In step S1903, the setting information acquisition unit 404 determines whether the acquired setting information includes a policy password. If the policy password is included, the process advances to step S1904. If the policy password is not included, the process ends.

  In step S1904, the setting information management unit 403 stores the policy password included in the acquired setting information in the setting information database 408. In this embodiment, as shown in FIG. 21, the setting information database 408 manages the identification information of the acquisition source device and the policy password in association with the security policy (policy ID: P0003) created in S1902. ing.

  In FIG. 21, in the security policies indicated by policy IDs P0001 and P0002, the acquisition source device ID is blank. This indicates that these security policies are not acquired from the device, but are created on the setting screen of the management apparatus 101.

  FIG. 22 is a flowchart illustrating a processing flow in which the management apparatus 101 distributes setting information to the devices 102, 103, and 104. The process shown in the flowchart of FIG. 22 is executed by the device management software 400 of the management apparatus 101. That is, the processing of the flowchart in FIG. 22 is realized by the CPU 201 reading and executing a program recorded in the HDD 212. Description of processing equivalent to that in FIG. 8 is omitted by using the same reference numerals.

  In S2201, the setting information distribution unit 405 determines whether the policy password information of the target device exists in the device information database 409, as in S804 of FIG. If the policy password exists, the process advances to step S805; otherwise, the process advances to step S2202.

  In step S2202, the setting information management unit 403 determines whether or not the policy password at the time of acquisition is managed in the setting information database 408 in association with the security policy selected in step S801. If the corresponding policy password is managed, the process proceeds to S2203, and if it is not managed, the process proceeds to S806.

  In step S2203, the setting information management unit 403 determines whether the target device is the same as the acquisition source device managed in association with the security policy selected in step S801. If they are the same, the process proceeds to S2204. If they are not the same, the process proceeds to S806.

  In step S2204, the setting information management unit 403 reads the acquisition policy password confirmed in step S2202 from the setting information database 408 and acquires it.

  FIG. 23 is a diagram illustrating an example of a screen that accepts an input of a policy password displayed by the UI control unit 401 in step S <b> 806 through the processing of FIG. 22. This is a modification of the screen shown in FIG. This is an example in the case where the user selects the above-mentioned “diversion security policy” as the security policy to be distributed. Here, “device A”, “device B”, and “device D” are selected as the devices to be distributed.

  In FIG. 23, for device B, the policy password stored in the device information database read out in step S805 is already input in the text box. Regarding the device D, the policy password at the time of acquisition managed in the setting information database 408 read in S2204 is in a state in which the policy password is input in advance in the text box.

  Note that the determination condition in S2203 may be set to an appropriate condition in consideration of the danger and convenience of using a password, and is not limited to the condition shown in the present embodiment. For example, there may be a condition that “Yes” is determined when the model information of the distribution target device and the acquisition source device are the same. In addition, when the password at the time of acquisition is managed (“Yes” in S2202), it is also possible to perform processing such as using the password without fail.

(Other examples)
The present invention includes an apparatus or system configured by appropriately combining the above-described embodiments and a method thereof.

  Here, the present invention is an apparatus or system that is a main body that executes one or more software (programs) that realize the functions of the above-described embodiments. Further, a method for realizing the above-described embodiment executed by the apparatus or system is also one aspect of the present invention. The program is supplied to the system or apparatus via a network or various storage media, and the program is read and executed by one or more computers (CPU, MPU, etc.) of the system or apparatus. That is, as one aspect of the present invention, the program itself or various storage media readable by a computer storing the program are included. The present invention can also be realized by a circuit (for example, ASIC) that realizes the functions of the above-described embodiments.

100 LAN
101 management apparatus 102-104 device

Claims (10)

A management device that manages devices that can communicate over a network,
First management means for managing a security policy indicating a setting value of a setting item related to device security;
Selecting means for selecting a device to which the managed security policy is distributed;
A setting means for setting a first password required for reflecting the security policy on the device or changing the security policy on the device;
Generating means for generating distribution data including the security policy and the set first password;
And a distribution unit that distributes the generated distribution data to the selected device. A second management unit for managing device information of a device to be managed;
When the first password of the selected device is managed by the second management unit, the setting unit distributes the first password that has been managed by the generation unit. The management apparatus according to claim 1, wherein the management apparatus is set as a password to be used for the password. The generating means generates distribution data further including setting information including setting values of setting items different from the security policy;
In the device to which the generated distribution data is distributed, if the first password managed by the device matches the first password included in the generated distribution data, the generated distribution The security policy included in the data and the setting value of the setting item that does not violate the security policy in the setting information are reflected,
On the other hand, in the device to which the generated distribution data is distributed, if the first password managed by the device does not match the first password included in the generated distribution data, the device is generated. 3. The management apparatus according to claim 1, wherein the setting value included in the setting information is reflected without reflecting the security policy included in the distributed data. Obtaining means for obtaining a security policy in which a first password is set from a device;
Deleting means for deleting the first password from the acquired security policy,
The management apparatus according to claim 1, wherein the management unit manages the security policy from which the first password has been deleted. The management means associates and manages the security policy from which the first password has been deleted and the first password set in the security policy,
The setting means sets the first password managed in association with the security policy when a predetermined condition is satisfied when generating the distribution data using the acquired security policy. The management apparatus according to claim 4. Accepting means for accepting input of a first password and a second password related to encryption and decryption when the security policy managed by the first management means is exported as a file;
Encryption means for encrypting information including the security policy and the input first password so that the input second password can be decrypted;
The management apparatus according to claim 1, further comprising an output unit that exports the encrypted information as a file.   The management apparatus according to any one of claims 1 to 6, wherein a function is restricted in the device according to the security policy.   8. The management apparatus according to claim 1, wherein the security policy includes a setting item related to a device transmission function or an interface restriction. A control method of a management apparatus that manages devices that can communicate over a network,
A first management step of managing as a security policy indicating a setting value of a setting item related to device security;
A selection step of selecting a device as a delivery destination of the managed security policy;
A setting step for setting a first password required for reflecting the security policy to the device or changing the security policy on the device;
A generation step of generating distribution data including the security policy and the set first password;
And a distribution step of distributing the generated distribution data to the selected device.   The program for functioning a computer as a means of any one of Claims 1 thru | or 8.

Images