Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Network Diagram Guidance:

Step 1: Identify the components that make up your system

  • What devices?
    • Servers, workstations, and printers (including hostnames and IP addresses)
    • Routers and firewalls
  • Where are those devices located?
      • Physically - IT Data Center, UCI building, AWS cloud, etc.
      • What network/sub-net do the devices sit on?
      • Are there any test environments used?
      • Are there any 3rd party networks that support your system?
        • cloud services, other non-UCI networks

Step 2: Group together devices and locations and draw out all components.

  • Components:
    • Servers, workstations, printers
    • Firewalls
    • Subnets
    • Data centers
    • 3rd party network
    • Test environments
    •  For better visibility you can use different colors to illustrate what devices are internal or external to UCI. 

Step 3: Draw lines connecting different components together.

 

Example Network Diagram

The below example has key information highlighted. (This example is "based" on a real system, but the hostnames/IP addresses and some of the details were made up to protect the innocent).  Your diagrams may not look exactly like this, but it should convey the same level of detail and amount of information to aid in the review process.  

  • Key pieces: Network segment subnet definitions, relevant hostnames/IPs, building routers and firewalls names if exist (switches unnecessary), OS/type of host, relationship to campus, Internet, or 3rd party networks.
  • Visio Format

Data Flow Diagram Guidance:

  • Coming soon....

Example Data Flow Diagram (for sensitive and restricted information)

  • Key pieces: The hosts in your system that store or allow sensitive/restricted information to be transmitted through them, as well as all entry points of that data into the system, and all exit points of that data out of the system, and any flow of data within subsystems.  Arrows should denote the direction of data flow.  The type of data should be noted. The type of transport protocol, encryption, and any relevant access controls of data in transit should be noted.  The type of data storage, encryption, and any relevant access controls of data at rest should be noted.  Lines denoting boundaries of firewalled segments should be noted.
  • Visio Format

 

 

  • No labels