3

I have to configure account lock after N unsuccessful login attempts on MSSQL 2017 Linux. That is standalone server and is not in AD. I couln'd find any valuable information so far unfortunately. Perhaps because Linux platform is quite fresh for MSSQL Server. Thank you for any advice here.

  • 4
    I believe the lockout functionality depends on the NetValidatePasswordPolicyAPI, which is Windows only. – Dan Guzman Mar 25 at 10:30
  • Are you talking about locking a SQL Server login account? Theoretically if the instance is logging unsuccessful login events, you could periodically check the event log and count by login, as long as they all happen within the current error log cycle (which can fluctuate depending on activity and what you are logging, since it's a rolling log). – Aaron Bertrand Mar 25 at 11:57
  • The goal here is to pass internal audit. Defense mechanism is needed and exact threshold N need to be on place to pass it. – Radek Radek Mar 25 at 13:50
0

I think you need to use a server / login trigger. Aaron Bertrand wrote a cool little article about combining login triggers and extended events here - https://www.mssqltips.com/sqlservertip/3582/prevent-and-log-certain-sql-server-login-attempts/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.