I am an IT consultant (I just started as a independent consultant), I am confident in my knowledge solving problems. Can anybody recommend me a book or online paper about which are the step to follow when auditing a network? I have a new clients who wants me to solve the few problems that they have and also to do a report of things that could be improve. IT is a windows 2000/2003 network with several satellite offices, so I know that I should check router, AD sites configuration, etc, I know already things I would have to check but I am wondering is there is a book or paper that gives you an organize step by step of things to do when auditing a network... I could work on my own protocol of auditing a network but I would prefer to see if somebody has already done this.
Thank you very much
Rezuma
This conversation is currently closed to new comments.
What does the company need? How critical is the IT? If you look at the IT from a business perspective rather than a technical challenge you can assign priorities, risk exposure and real value to your recommendations. Remember to check with the client that this work is really wanted .. maybe they just want someone to 'fix their lan'
The first thing I normally do is define the audit. Do they want software/hardware audit? Do they need things like hd/ram/os. Is this more of a pen. test? (ports/firewall config etc).
Define the critical areas of data. Users, Accting files, SQL db, whatever. Then find out who 'owns' or is in charge of that data. This will help you define your criteria.
If all you are looking for is a simple hw/sw grab some of the low end software apps and you can get a quick snapshot. Ask the customer to purchase the software required as it is theirs to keep.
You have already received good feedback from the two earlier respondants. (Biz needs and definition of body of work)
Define the scope of your Audit, 'what it will cover' (ie; what will be delivered), and 'what it will not cover'.
Get buy-in from your client on your proposed direction. (Your work might include doing a topology map, (Visio is fine for this exercise), of hw, networking and software), defining user group(s), monitoring / redundancy / security rendered under deployed architecture and the resources required to maintain the 'As Is' configuration.
Then you can get to work showing off how you can improve their setup AFTER your client imparts a clear vision of their IT needs as it supports their core business and their plans for growth in near future. Be sure to contemplate ROI considerations before you make recommendations to change their existing real estate.
If penetration testing is defined as being in scope, it would be a good idea to have the proper legal documentation, especially if they want you to test agsinst denial of service attacks.
You should also get them to define whether or not the IT department will be aware of the security audit. Part of the audit might be to test response strategies, where only a few people are in-the-know.
You can download a free monitoring tool called Nagios ( URL : www.nagios.com ) install on a linux server to proceed detail service monitoring. Besides, you can also download a security scanner ( URL: www.nexus.com )
While going through all the techie stuff, it may be a good idea (well, at least, I do this...) to include some business scope in the audit.
I presume your audience will not be exclusively IT people. Therefore, the audit results would be easier to understand from their point of view if you include some points about asset depreciation, projections of costs for replacement machines/parts/software over the next 12-24 months, etc. Break it down my whatever category is convenient (i.e. function, department, satellite office location, etc.) It will be a good bonus to put in because A) most IT audits focus only on the tech angle or only on the business angle, but very rarely does one cover both and B) it will show you are aware of costs and are not treating the client like they have a blank check for future IT purchases.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
NETWORK AUDIT
I am an IT consultant (I just started as a independent consultant), I am confident in my knowledge solving problems.
Can anybody recommend me a book or online paper about which are the step to follow when auditing a network? I have a new clients who wants me to solve the few problems that they have and also to do a report of things that could be improve. IT is a windows 2000/2003 network with several satellite offices, so I know that I should check router, AD sites configuration, etc, I know already things I would have to check but I am wondering is there is a book or paper that gives you an organize step by step of things to do when auditing a network... I could work on my own protocol of auditing a network but I would prefer to see if somebody has already done this.
Thank you very much
Rezuma