Why Network Documentation Is So Important

Undocumented Network ------------ I can not tell you how many projects I worked on # wherein the client has little or no network documentation. Ilragione the lack of network documentation is varied. Inin many cases this is the fault of both customer and lafornitore / consultant who has designed and built ilrete. The seller simply does not do it and the press clientenon enough for this. In some cases, the tecnologiaconsulenti think it's important enough or you do not play in desiderabloccare the customer having to call "them" if qualcosava asset or configuration must be changed.Not this is just poor practice on the side dellaconsulente, can have a dramatic effect on Futurola growth of the customer, increase the costs of the future reteaggiornamenti and diagnostics, and can adversely affect the safety of the customers sullala network.The the results of a Undocumented ------------ Before tell the basic components that must be documentatiper regard to computer networks, I first want dartiesempi of what I "do not" seen documented, and that this has cosaproblemi caused.During one of my past projects, which should have principalmenteimplementare a new firewall and to provide many internosistema, I came across some incredible problems. No one in mainstream primary server systems have been documented. Nobody knew that cosaServer did what, how much memory, disk space, what kind diprocessore (s), and in some cases, did not know what operativoSistema was installed. And worse still, during my inizialerevisione, we identified three servers in a closet, in a diversapiano, that nobody knew existed! Due to lack of network documentation, no sapevaciò that suppose to be done to keep their impresaAnti virus-deterministically When I finally undermined what the amministratoreciò the password to access the services anti-virus, I do not trovatoche virus signatures had been updated in over seimesi. Then we discovered that the system was not nemmenofunzionamento and nearly 90% of networked systems with viruses and worms are statiinfettati (fastidiososia the child and not the destructive kind) We also found that there were four different backup server to tape, and yet, due to lack of network documentation, none of them had been maintained. The customer continuavala replacement of the belts. And you know what, none of backupposti work was under way for months. Talk about a false security DIRECTION! The last thing I want to talk about is how the lack of network didocumentazione and procedures can affect retesicurezza. In one case a client had a rather costosaControlla Point firewall in place. No documentation is statadisponibile and the customer was told that necessariaessere done to keep the firewall. The customer dettoche me recently, their access to the Internet had become moltopigro. It took two days to locate the console Check Pointpassword. When I logged on I discovered that the C: drive has avutoassolutamente free disk space because the firewall log avutoconsumato all could have been avoided if Ilche ​​This firewall setup correctly in the first place. The firewallCosì what about 4 service packs behind, and the rules inluogo were quite inadequate. Not to mention that none had been documented Deise same rules. And one thing dapensare. If this network had been attacked ecompromesso, how can we respond quickly to the attack potutoper if so much of the network has been documented? EssaSarebbe was a documentation network disaster.Basic ------------ Here is a basic set of elements that should be contained nelNetwork Documentation: All server hardware and operating systems should esseredocumentate, including places physical and qualiprimaria, secondary, etc.. purpose they serve. All principaliaccount service to access your user-id and password of usodevono be documented and maintained in a safe place, maybe unsocietà lockbox or time, or something like KeyPassmemorizzarli. A visual diagram of the network layout, ancheDa a high level, there must exist no matter how small or grandela network. Products like he conquered WhatsUpGold can help or you can create a Visio diagram of rete.Procedure on keeping the network technology, including the operating system, services related to security, backup and disaster recovery (business continuity), etecnologie firewall should exist . Additionally, you dovrebbedocumentare and secure all operating systems and applicazionilicenze. This is something that is very often trascuratoed is essential if you have to recover from a disaster situation # in which reconstruction of the systems is necessaria.Altre information you have documented is the contact chiaveInformazioni. For example, if you call your Internetil link goes down? Who to contact if your offsitei web services do not work? You have third chemantiene your Domain Name Service (DNS)? If you have diapplicazioni customized, it is not known exactly who is necessary chiamarese there is a problem The above is only the basic elements which must be documentataall'interno of a computer network. There are many more aspects adocumentation.Who network needs to document their network ------------ In other words, who has a computer network, to casaufficio, small office or large office size, are required aadeguato level of network documentation and procedureseguire to maintain the network. If you have diinvestito in networking technology, you do not want to keep vostroinvestimento safe, sound, and running at it's peak? Conclusion ------------ If you are a customer, and have a system integrator oconsulente working on a new network construction oaggiornare an existing one, the question I forniràcompletare your network documentation. Even though it costs PIUSI should ask. It saves you a lot of time and didenaro in the future. And, you can actually keep your businessdi experience long periods of low time.You may reprint or publish this article free of charge as long as the bylines are included. [ABSTRACT] Undocumented Network ------------ I can not tell you how many projects I have on, that has little to no documentation gearbeitetDer customer's network. DieGrund the lack of network documentation is varied. Invielen both cases, the fault lies with the customer and dieVerkäufer / consultant, designed and implemented dieNetzwerk. The seller and the customer does not only hard enough to press for them. In some cases, technology consultants do not think it is important enough or made contemptuous unbolt the customer to call with "them", when something is wrong or a configuration changed.Not just be this bad practice on derBerater hand, can have an impact dramatic impact on future growth of the customer, increase the cost of future upgrades and network diagnostics, and can adversely affect the customer network.The dieSicherheit the results of an Undocumented ------------ Before I tell you the basic elements that are documented müssenin over networks of computers, I would first IhnenBeispiele for what I documented in "not" seen and wasProbleme caused.During this one of my most recent projects, which was primarily a new aufImplementierung firewall and certainly many of the internal systems, I came across some incredible problems. Eder non-primary servers have been documented. Nobody knew, he turned to water, what, how much memory, disk space, vonProzessor what type (s), and in some cases, did not know what OS is installed. And worse still, in my first criticism, you are three servers in a closet on another floor that nobody knew existed, too! Due to lack of network documentation, no one quite knew what to do to keep their activities are on anti-virus. When I finally decided that the administrator password to access the services anti-virus, found ichdass virus signatures has not yet been updated for more than six months. Then we discovered that the system does not even have the test and nearly 90% of systems in the network are infected with viruses and worms (and not the kind of destructive Artentweder were annoying) We also found there four different backup servers tape, always due to the lack of network documentation, none of them had been maintained. The customer kept changing tapes. And you know what, none of the backup process has been ongoing for months. Talk about a false security Gefühlder! The last thing I want to talk about is how the lack of documentation anNetzwerk and procedures may relate to network security. In one case a customer has a very expensive checkpoint firewall in place. No documentation available and the customer was told that warzur benötigtzu doing anything to keep the firewall. The customer told me she recently had access to the Internet is very slow. It took two days to find a password to check the console. When I logged on I discovered that the C: hatabsolut disk free space, because the firewall log Hatt have never needed any. This could have been avoided if dieFirewall was installed properly in the first place. The Firewallwar also about 4 Service Packs behind, and the rules were totally inadequate on-site. Not to mention that none derRegeln himself had been documented. And yet that something zudarüber. If this network had been attacked undgefährdet is, how quickly would we respond in a position to attack the network habenzum when so much has been documented? ESware have disaster.Basic Network Documentation ------------ Here is a simple set of elements to be included in the documentation solltenNetzwerk: The server hardware and operating systems solltendokumentiert, including physical locations and wasPrimär, secondary, etc.. The purpose they serve. All services Dessollten Key Accounts an account login ID and password will be documented and maintained in a safe place, perhaps einUnternehmen lockbox or deposit, or something like KeyPass zuspeichern this. A visual representation of the network layout, metal ions have also been a high level should be in place, no matter how small or großDas network. Products such as WhatsUp Gold can help with this or you can create a Visio diagram of Netzwerks.Die procedure to obtain the network technology, including operating systems, services relating to security, backup and disaster recovery (business continuity) undFirewall technologies should not exist. Furthermore, should Siedokumentieren and secure throughout the operating system and application licenses. This is something that is often overlooked, is essential if you wirdund erholenSituation of a catastrophe in which the information must be documented ist.Weitere necessary processing information on key contacts. For example, to know who to call if your Internet connection goes down? Who to contact if your offsite web services do not work? Do you have a third dasspflegt the Domain Name Service (DNS)? If the user-defined application screens, you'll know exactly who to call if you have a problem? The above is only the basic elements that are documented müssenin a computer network. There are many other aspects zuNetzwerk documentation.Who must document their network ------------ In short, anyone with a computer network, home business, where the small office or offices of large size, einangemessenes level of network documentation and procedures zurfolgen to maintain the network. If Sieinvestiert in network technologies, you do not want IhreInvestition safe, sound and functions optimally? Conclusion ------------ If you are a customer, and have a systems integrator or consultant working on a new network construction or upgrading of an existing application that you mitkomplettes network documentation. Even if it costs you extraSie request them. It saves a lot of time in the future undGeld. It can actually keep your experience Unternehmenaus extended to time.You may reprint or publish this article free of charge, as long as the bylines are included.