How can I prevent identification/authentication failures? (Is passwordless the only way?)

316 views3 Comments

Head of Information Security in Finance (non-banking), 1,001 - 5,000 employees
If your company is using Active directory for for Windows, there is a lot of authentication false positive generated on SIEM or other log management. Then security admin and sysadmin are working closely on that to reduce failures on AD.
VP of Information Security in Finance (non-banking), 201 - 500 employees
You can't prevent it, you can minimize it somehow using alternative approaches and modern strong authentication methods, biometric, app based logins or one time password. However, you will end up managing additional anomalies (impossible travel, infrequent country...)
Your concern should be overall security and ease of use, balancing the two could be difficult, but with ZTN innovations, it's closer to reality now. 
Director of Information Security in Telecommunication, 10,001+ employees
Passwordless is surely a way to limit (not prevent completely) identification and authentication failures, but there are many other ways you can consider utilizing: 1. password management processes, such as securing password data stores, password resets, and login/logout sessions 2. tools for your internal customers (employees) to help them manage passwords such as passwords vaults 3. multi-factor authentication (MFA) capabilities across your environment together with multi-steps login processes 4. Zero Trust Identity management across your enterprise. Last, but not least, from the OWASP guidelines, regular web application penetration testing.

Content you might like

No plans on undergoing a migration yet34%

Currently deploying SAP S/4HANA28%

Migrating to SAP S/4HANA within the next 1-2 years18%

Migrating to SAP S/4HANA within the next 3-6 years9%

Already have SAP S/4HANA in production8%


30.9k views154 Upvotes32 Comments

Disruption via ransomware46%

Exploitation via phishing62%

Exfiltration of PII (Personally identifiable information)45%

Disruption via DDoS attacks34%

Disruption of a business-critical application21%

Other (comment below)1%


1.5k views1 Upvote

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
48.5k views133 Upvotes326 Comments