Audit mandates MS SQL service accounts  expiration: whats practice out there

sunhux
sunhux used Ask the Experts™
on
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?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Partha MandayamTechnical Director

Commented:
You can enforce password expiration quarterly and force the user to change password

https://www.mssqltips.com/sqlservertip/1088/sql-server-login-properties-to-enforce-password-policies-and-expiration/

Author

Commented:
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
For new versions of MSSQL you can utilise "managed service accounts" to ensure automatic password management.
https://blogs.msdn.microsoft.com/markweberblog/2016/05/25/group-managed-service-accounts-gmsa-and-sql-server-2016/
Acronis in Gartner 2019 MQ for datacenter backup

It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.

Partha MandayamTechnical Director

Commented:
So what exactly you want

Author

Commented:
Is there such thing as 'non-interactive accounts for MS SQL'
that Windows have & in Unix, we set the SHELL to /bin/nologin?

Author

Commented:
Chris' solution is almost there, just that we're on MS SQL 2012

Author

Commented:
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

Author

Commented:
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

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial