I agree with Craig.
You need to know
the requirements, not try to guess them. Your guesses may be right, but if they are wrong you can easily spend time doing something that is not necessary, or missing something that is necessary.
Personally, I would prepare a compliance document. This could identify each requirement as a section heading, followed by a description of the requirement followed by what you have done to satisfy the requirement. This becomes a document that can be audited for completeness, and gives you a base to work from if a requirement changes.
Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017
: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara