HP Imaging and Printing Security Center 2.0 - Instant-On Security

16
Use Case 4 – Filtered Discovery and Policy Conformance
A DAA enabled HP IPSC supported device is placed on the network without any staged
configuration. The IPSC server Instant-On feature is configured to “Accept Device
Announcements”, “Allow Automatic Remediation” and utilize device serial numbers as a
method of filtering Instant-On activity. The device acquires a DHCP address and attempts to
resolve the DNS hostname or alias of hp-print-mgmt. Once hp-print-mgmt is resolved
to the IPSC server IP address and IPSC communication is established, IPSC continues the
Instant-On process only if the device matches a serial number entry in the IPSC Instant-On
serial number list. If so, IPSC places the newly discovered device in the database, assigns a
license, and remediates the device in accordance with the established security policy. Upon
successful interaction, the serial number is then removed from the UI list, but the database
entry remains in order to continue the serial number filtering process for Instant-On. This use
case provides a filtering option for selective Instant-On processing.
Post-Install Device Announcement Use Cases
After the Secure at Install process is complete, Instant-On security continues with the Stay
Secure process via the DAA announcements that occur for device cold resets, IP address
changes and other device specific conditions that might place the device in a non-compliant
state. After receiving an announcement, Instant-On ensures the device is assessed and
remediated in accordance with the last security policy applied. Below, is a list of the most
common Stay Secure use cases.
Use Case 1 – Device Cold Reset
An HP IPSC managed device has experienced a condition where a return to a default
configuration (cold reset) is required. As a result of the cold reset, many of the security
settings applied through the original HP IPSC policy remediation are cleared. The cold reset
action produces a DAA announcement, thus prompting communication with HP IPSC. The
HP IPSC server processes the announcement, matches device identity with the existing
database entry, and applies the last policy the device was assessed with. The device
database entry is reconciled with any device identity attributes that might have changed
during the cold reset. Through this process, the device is immediately placed back into its
secure state.
Use Case 2 – Device Formatter or JetDirect Interface Replacement
An HP IPSC managed device has experienced a hardware failure, requiring a formatter or
Jetdirect interface replacement. After completing the repair, the service technician reloads
the original serial number into the device. Applying power to the device after placing unit