HP M527dn

HP Inc.
HP LaserJet Enterprise MFP M527 Series,
Color LaserJet Enterprise MFP M577 Series, and
PageWide Enterprise Color MFP 586 Series
Firmware with Jetdirect Inside Security Target
Version: 2.0 Copyright © 2008-2016 by atsec information security corporation and HP Inc. Page 60 of 98
Last update: 2016-06-07 or its wholly owned subsidiaries
Sign In method
Number
Event
Action
Local Device
Sign In:
User Access
Code
6
the last successful
authentication for User
Access Code sign in
method (i.e., per
method, not per
Access Code)
insert a 10 second delay between all User
Access Code authentication attempts until:
 any successful User Access Code
authentication occurs, or
 5 minutes elapses after the last failed
authentication of all User Access
Codes
LDAP Sign In
6
the last successful
authentication for the
indicated LDAP Sign In
user
insert a 10 second delay between
authentication attempts of the indicated user
until:
 a successful authentication of the
indicated user occurs, or
 5 minutes elapses after the last failed
authentication attempt of the indicated
user
Windows Sign In
6
the last successful
authentication for the
indicated Windows
Sign In user
insert a 10 second delay between
authentication attempts of the indicated user
until:
 a successful authentication of indicated
user occurs, or
 5 minutes elapses after the last failed
authentication attempt of the indicated
user
Table 30: Simplified Account Lockout for each sign in method
Local user attribute definition (FIA_ATD.1) 6.1.4.2
FIA_ATD.1.1
The TSF shall maintain the following list of security attributes belonging to individual users:
 Control Panel users:
o User Identifier (Access Code and Display Name) for Local Device Sign
In
o User Role (defined by Permission Set)
 IPsec users:
o User Identifier (defined by IP address)
o User Role (defined by IPsec/Firewall service template)
Application Note: The LDAP and Windows Sign In method security attributes belonging to individual
users are not in FIA_ATD.1 because these attributes are "maintained" independently by the LDAP server
and Windows domain controller, respectively, which are part of the Operational Environment.