asked on
Audit mandates MS SQL service accounts expiration: whats practice out there
Audit mandated we must enable password expiry for MS SQL accounts though we say they're service accounts:
from DBA: change cannot be implemented as it will expire service accounts
Set the 'CHECK_EXPIRATION' Option to ON for All SQL Authenticated Logins Within the Sysadmin Role
What's the practice out there?
Can we automate changing the password quarterly & yet not affect service accounts (which I assume
do not need to know the password)? One of them is nagios
Or set the accounts to non-interactive & how to do it for MS SQL?
from DBA: change cannot be implemented as it will expire service accounts
Set the 'CHECK_EXPIRATION' Option to ON for All SQL Authenticated Logins Within the Sysadmin Role
What's the practice out there?
Can we automate changing the password quarterly & yet not affect service accounts (which I assume
do not need to know the password)? One of them is nagios
Or set the accounts to non-interactive & how to do it for MS SQL?
DatabasesMicrosoft SQL ServerOS SecuritySecurity
Last Comment
Chris Geraghty
ASKER
Thanks, we're fully aware of what you've suggested but there are numerous
such service accounts which if the password are not changed (manually)
in time, will cause disruption ... too risky
such service accounts which if the password are not changed (manually)
in time, will cause disruption ... too risky
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
So what exactly you want
ASKER
Is there such thing as 'non-interactive accounts for MS SQL'
that Windows have & in Unix, we set the SHELL to /bin/nologin?
that Windows have & in Unix, we set the SHELL to /bin/nologin?
ASKER
Chris' solution is almost there, just that we're on MS SQL 2012
ASKER
On reading the full content of the link from Chris, noted:
"This implementation is done using Windows Server 2012 Active Directory domain controllers (DCs), all servers running Windows Server 2012 or Windows Server 2012 R2, and SQL Server 2016 CTP 3.2."
Just that we are still on Win2008 R2 AD (support expiring on Jan 2020) & we're
struggling to upgrade our AD to Win2016
"This implementation is done using Windows Server 2012 Active Directory domain controllers (DCs), all servers running Windows Server 2012 or Windows Server 2012 R2, and SQL Server 2016 CTP 3.2."
Just that we are still on Win2008 R2 AD (support expiring on Jan 2020) & we're
struggling to upgrade our AD to Win2016
ASKER
Another remark from the link:
"Passwords are very complex and changed automatically as often as desired (by default every 30 days). ..
In addition, they cannot be used to interactively logon"
Is there any way in my MS SQL 2012 on Win 2008 R2 AD to make those service accounts "non-interactive";
it's fine if they don't expire periodically
"Passwords are very complex and changed automatically as often as desired (by default every 30 days). ..
In addition, they cannot be used to interactively logon"
Is there any way in my MS SQL 2012 on Win 2008 R2 AD to make those service accounts "non-interactive";
it's fine if they don't expire periodically
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
https://www.mssqltips.com/sqlservertip/1088/sql-server-login-properties-to-enforce-password-policies-and-expiration/