How often should an enterprise update its network topology documentation; what security-related information should we include, and are there any tools that can help automate this process?
Ask the expert
Got a vexing problem for Mike Chapple or any of our other experts? Ask your enterprise-specific questions today! (All questions are anonymous.)
You should update your network documentation as often as your network topology changes. Hopefully, the high-level details of your network don’t change often enough for this to be a major concern. While you might be adding and removing devices from your network daily, don’t expect the documentation to go down to the individual device level. Instead, you’ll probably end it at the network edge – the switches and wireless access points to which end-user devices connect. The network beyond the switch (at least outside of the data center) is simply too dynamic to document.
Here’s what I’d suggest collecting as a basic set of network documentation:
- Diagrams that include all of your routers, firewalls, switches and security devices. Depending upon the size of your network, you may need to break this up into pieces. The diagram should include basic information about the devices: including names, IP addresses, connections and port assignments.
- Detailed network diagrams of your data center that include the individual servers connected to your network.
- Configuration files from each of your network devices that would enable you to rebuild the device in the event of a failure.
To try to automate network documentation to some degree, consider the use of network management tools to help with the tactical details of documenting your network. There are many network management tools on the market that are capable of gathering information directly from network devices and keeping up-to-date records of device configurations and monitoring changes to those configurations. It’s a lot easier to automate this task than to perform it by hand!
Dig deeper on Monitoring Network Traffic and Network Forensics
Related Q&A from Mike Chapple, Enterprise Compliance
The HHS security risk assessment tool is designed to help healthcare providers meet the HIPAA security requirement. Expert Mike Chapple explains how ...continue reading
PCI DSS requirement 6.6 demands application security compliance through one of two options: an application firewall or a code review. Expert Mike ...continue reading
Are HIPAA-compliant hosting services a better option for compliance than a secure storage API? Expert Mike Chapple analyzes.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.