Recently I posed a document to my boss suggesting the outline for creating a Best Practices guide for our network, and two issues came up.
Here is the Outline I created:
IT Department Best Practices Outline v0.2
Proposed core topics which *could* be contained in a Best Practices volume:
• The organizational purpose of network.
• Network Architecture design and implementation procedures.
o Expansion needs both current and in the future.
o Network quantification and measurement
o Network Topology assessment and implementation.
• Governance for acceptable use.
o Policies and procedures for network users
o Quantity of both users and computers on the network.
• Compatibility issues
• Hardware/Software Procurement
o Asset management and tracking
• Disaster recovery and management (see DRP)
• Fine tuning NB:
(Note: This is my first time writing one of these)
The first issue he (My Boss) had was this:
Boss: I would like you to start addressing the "Governance for acceptable use" section.
One issue that we have experienced is developers sharing passwords, who knows the root password to which server, etc. That needs to be addressed.
Anyone out there have any ideas? What has worked for you in this arena?
Some developers are remote, some are local, some need access to only a few servers but some need access to all. Another complication is that some of our software developers live in other countries.
The other issue he had was this:
Boss: We do not do fine tuning! write me a one paragraph essay on why we do not do any fine tuning.
To this I have no clue.
I would think that fine tuning a network was a good thing! anyone have a clue?
I thank you in advance for your wisdom on this matter.