Anonymous_User Absent Member.
Absent Member.

intruder lockout


the eDirectory collector classifies intruder lockout events that occur if a
login attempt with an invalid password was performed too often as
XDAS_AE_CREATE_SESSION with an outcome of XDAS_OUT_FAILURE. I don't think
this taxonomy correctly describes the action. From the list of action
taxonomies XDAS_AE_DISABLE_ACCOUNT with a success outcome seems the best fit
("An action that prevents a principal account from being used within a
Would this choice conflict with Disable Login using the same taxonomy?
Is this also used for audit events generated by Sentinel's Intruder
Detection and Lockout Mechanisms?


The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.