Loading...
Loading...
In the Instance Security Dashboard, Logging/Errors > Managing Failed Login Attempts is shown as compliant, when all 3 script actions are active. However, as confirmed with the development team, only one of the following scripts need to be active at the same time. 'SNC User Lockout Check' 'SNC User Lockout Check with Auto Unlock' If we activate only one of them, e.g. 'SNC User Lockout Check with Auto Unlock', 'Managing Failed Login Attempts' will show as non-complaint. On the other side, if we activate both of them to ensure compliance, the 'User failed login attempt' gets incremented by 2, instead of the expected 1.
Open the Instance Security Dashboard Review Logging/Errors > Managing Failed Login Attempts Notice all 3 of the scripts need to be active for compliance. SNC User Lockout Check with Auto Unlock SNC User Lockout Check SNC User Clear
After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided to not address this issue in any current or future releases. The affected plugin 'com.glide.security.dashboard' will be deprecated in Madrid. The London replacement (com.snc.pa.instance_sec_dash), and the Madrid enhancement 'com.glide.instance_sec_center', already have a fix for this issue. If you have any questions regarding this problem, contact ServiceNow Customer Support.
PRB1249418
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.