Monday, March 26, 2012

Policy Enforcement

I understand that SQL 2000 does not have security policy enforcement, but is
there any work-around solution for this (disregard Windows NT Authority)?
like checking for users' passwords if they meet the requirement of number of
characters, digits, or even must be changed when they are expired.
Thank you in advance
PaulHi
If you are using a trusted connection this task is deligated to Windows.
That is why in general it is better to use this type of connection. If you
are using SQL Server authentication and have a had written application that
allows the user to change a password then your rules can be implemented
there. If you want to check existing users then you may want to check out
MBSA or the SQL Server Security advisor
http://www.microsoft.com/technet/se...s/mbsahome.mspx
http://www.microsoft.com/downloads/...&displaylang=en
Other products mentioned at
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=30 may also help.
John
"PaulManh" wrote:

> I understand that SQL 2000 does not have security policy enforcement, but
is
> there any work-around solution for this (disregard Windows NT Authority)?
> like checking for users' passwords if they meet the requirement of number
of
> characters, digits, or even must be changed when they are expired.
> Thank you in advance
> Paul

No comments:

Post a Comment