July 7, 2009 at 3:45 am
Hello Friends,
I dont no how to do SQL 2005 Server Auditing. Anybody can help me how i can do the auditing of my server.
My manager has assigned me the task to Audit the our Production Server.
And he told me to monitor this things and dosen't change anything.
Surface Area Reduction
Sample Databases
Sample Code
SQL Surface area configuration tool
Services
SQL Server Active Directory Helper
SQL Server Browser Service
SQL Server VSS Writer
Service Account Selection and Management
Accounts
Management
Service Password Expiration
Privileges
Authentication Mode
Network Connectivity
Lockdown of System Stored Procedures
Password Policy
Administrator Priveleges
Database Ownership and Trust
Ownership
Trust
Schemas
Authorisation
Catalog Security
Remote Data Source Execution
Encryption
Auditing
Patching
Pleas help me out....
Thanks in Advance.
Regards,
M.I.
________________________________________
M.I.
[font="Times New Roman"]
July 7, 2009 at 9:06 am
This is almost like a list of features rather than audit! Sounds like you need to write down all the settings on the server and then fix anything that looks wrong and set up monitoring, it's a huge task.
When I first audited SQL it was quite daunting and took a while, your just going to have to start with a blank spreadsheet and work your way through the server. It's also a very good way to learn about all the features of SQL Server.
Get the list you have and work your way through the things you know.
Start simple, write down the properties of the server.
Write down the settings in the Surface Area Configuration tool.
Use system stored procedurs such as sp_helpdb to list various parts of the server, you'll be supprised how much information some commands will tell you like sp_helpdb gives you the database name, size, owner, settings etc.
You'll need to do some research into how to list settings for various parts such as who has sysadmin access to the server, it's best to get scripts rather than doing things manually as you might need to do it again in the future.
You just need to work through each part and then just ask this forum if you need any more pointers as who knows what you will find.
July 7, 2009 at 10:09 am
If by "audit", he means, "take an inventory of the state of affairs with regards to..." and that list, then what you would need to do is take that list and go through each item, listing things that need to be handled on each one, and listing things that are already in good shape on each one.
THAT definition of "audit" would make sense in this case, and would be a good way to start a DBA job.
The reason you won't easily find data on "auditing SQL 2005" that applies to those things is that most DBAs define "auditing" a database as setting up something to track CRUD operations in the databases. Which has nothing to do with most of that list.
What you'll need to do is study each subject on that list, figure out what needs to be done with each, and then compare that to the servers you have and how they are set up.
It's not going to be easy, not going to be fast, and will be very, very useful.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 19, 2014 at 5:29 am
Hi
There are a few tools you can use that will assist you with that.
The tools I use are NGS Squirrel and Nessus. These are based on the CIS (Centre for Internet Security) standards.
You can download a copy of the standard and use that to manually perform audit.
Hope this helps
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply