Answered by:
SOX and SQL Server

Question
-
Does anyone have any documentation or links pertaining to the granting of unnecessary rights outside of application needs and SOX compliance?
John M. CouchTuesday, October 12, 2010 2:59 AM
Answers
-
Please refer the SQL Server White Paper: SQL Server 2008 Compliance Guide
It may helps you on where to begin or how to automate the program using technology, specifically SQL Server.
It address the complaiance of SOX, PCI, HIPAA and GLBA using SQL Server 2008.
Sivaprasad S http://sivasql.blogspot.com Please click the Mark as Answer button if a post solves your problem!- Marked as answer by Il-Sung Lee - MSFT Friday, October 15, 2010 4:56 AM
Wednesday, October 13, 2010 12:30 AM -
There's also a case study describing Credit Suisse's efforts to become SOX compliant with SQL Server 2005.
Il-Sung.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked as answer by Il-Sung Lee - MSFT Friday, October 15, 2010 4:56 AM
Friday, October 15, 2010 4:56 AM
All replies
-
As per my knowledge, Sarbannes –Oxley (SOX) is rather general in the description of what needs to be done and does not really say what companies need to do for a database to ensure the requirements are satisfied.
SQL 2005 (onwards) provides many data integration, data protection and security features that can help comply with various regulations including SOX but SOX does not dictate any specific feature to exist in a db platform so there isn’t really any such thing as db being compliant with SOX.
Improving Data Security by Using SQL Server 2005
This article looks at how Microsoft IT uses SQL Server 2005 to protect sensitive data. http://www.microsoft.com/technet/itsolutions/msit/security/sqldatsec.mspx
Balmukund Lakhani | Please mark solved if I've answered your question
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog: http://blogs.msdn.com/blakhani
Team Blog: http://blogs.msdn.com/sqlserverfaqTuesday, October 12, 2010 7:16 AM -
The link didn't work. Outside of that, all the SOX integrations I have been involved with in the past have included data security in order to be compliant. This included procedures for providing access to the data, encrypting CC numbers..etc as well as restricting access to only needed functionality. This was done through SQL Server and Oracle. The problem is I no longer have the documentation I used during those audits...etc.
John M. CouchTuesday, October 12, 2010 7:46 PM -
Please refer the SQL Server White Paper: SQL Server 2008 Compliance Guide
It may helps you on where to begin or how to automate the program using technology, specifically SQL Server.
It address the complaiance of SOX, PCI, HIPAA and GLBA using SQL Server 2008.
Sivaprasad S http://sivasql.blogspot.com Please click the Mark as Answer button if a post solves your problem!- Marked as answer by Il-Sung Lee - MSFT Friday, October 15, 2010 4:56 AM
Wednesday, October 13, 2010 12:30 AM -
There's also a case study describing Credit Suisse's efforts to become SOX compliant with SQL Server 2005.
Il-Sung.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked as answer by Il-Sung Lee - MSFT Friday, October 15, 2010 4:56 AM
Friday, October 15, 2010 4:56 AM -
From my experience, dealing SOX compliance can easily turn into a nightmare as it’s creators had nothing related to technology in mind, at all. Common opinion about it, I found on several online resources, is that it is written by lawyers, for lawyers.
Here are some resources that helped me understand it better, along with some implementation tips:
https://www.sec.gov/rules/proposed/s74002/card941503.pdf
http://solutioncenter.apexsql.com/how-to-implement-sox-compliance-requirements-for-sql-server-part-1/
http://solutioncenter.apexsql.com/how-to-implement-sox-compliance-requirements-for-sql-server-part-2/
Hope this helps
- Edited by JakeSTurner Tuesday, January 31, 2017 3:03 PM
Tuesday, January 31, 2017 3:01 PM