Defined network traffic rules.
10.8.18. A well-structured IP addressing scheme promotes the ability to quickly identify node properties from an IP address which assist in network management
and fault finding and rectification.
Address Block Allocation
10.8.19. There are two main difficulties when assigning address blocks for types of devices. First is that over time there is insufficient provision for additional
devices and network growth. When the allocated address block is exhausted, the addressing scheme is compromised (broken). The second is that you
have a small number of devices in an address block, but are running out of addresses in other parts of the network. If you “borrow” from a preassigned address range, the addressing scheme is also compromised.
10.8.20. Internal IP address ranges are defined by the IETF. Commonly known as RFC 1918 addresses, the most recent RFC is 6761. These RFC’s define private
IP address ranges which cannot be used for external (Internet) IP addressing. Three address ranges (blocks) are defined:
IPv4 Address Range
Network IPv4 address
Block
10.0.0.0 to
Directed Broadcast IPv4
IPv4 Addresses
address
10.0.0.0/8
10.255.255.255
16,777,216
172.16.0.0/12
172.31.255.255
1,048,576
192.168.0.0/16
192.168.255.255
65,536
10.255.255.255
172.16.0.0 to
172.31.255.255
192.168.0.0 to
192.168.255.255
10.8.21. IPv4 addresses are 32-bit binary addresses, divided into 4-Octets and normally represented in a decimal format. An example of IPv4 address is
192.168.100.10. IPv6 addresses are so much larger than IPv4 addresses and impractical to clearly represent in decimals. IPv6 addresses are usually
represented in hexadecimal numbers, separated by a colon. An example of an IPv6 address is 2001:0DB8:0000:0002:0022:2217:FF3B:118C. Private
IPv6 addresses are specified in RFC 4193
10.8.22. Private addressing is a means of distinguishing networks, assisting in separation and segregation.
Private use of reserved addresses
10.8.23. Some IP addresses have been reserved in IETF standards. Despite official warnings, some organisations use parts of the reserved IP address space for
their internal networks where address space is exhausted or poorly designed. This creates conflicts with devices and signalling traffic protocols which
can create network faults, anomalies and network outages. This practice is strongly discouraged.
Devices which have default IP addresses
10.8.24. Some devices are supplied with default IP addresses. If using the IETF RFC 1918 addressing protocol (e.g. 10.0.x.x) some devices may have been
allocated the same (duplicate) IP address.
10.8.25. It is important to change default addresses to new addresses that conform with the addressing scheme selected for the agency.
DHCP
10.8.26. In theory, there is only one network device that absolutely needs a true static address, the DHCP server. In practice, it is preferable to assign address
blocks to major groups of devices for control, fault isolation and security purposes. Traditionally static devices are provided with a reserved address.
These devices may include:
DCHP Server;
Gateway devices;
Firewalls;
Routers; and
Switches.
10.8.27. The majority of other devices can be allocated a DHCP address.
10.8.28. It is important to identify the essential device groups using a risk assessment, operational characteristics, level of security, system classification and
other relevant architectural features, business requirements and operational constraints.
Connector Types and Cable Colours
10.8.29. Cable management is discussed in detail earlier in this chapter. In particular note the discussion 1
( 0.1.4) of Red/Black concepts which includes
separation of electrical and electronic circuits, devices, equipment cables, connectors and systems that transmit store or process national security
information (Red) from non-national security information (Black)
10.8.30. Wherever practical and possible, connectors for systems of different classifications should be distinct and be selected to avoid accidental crossconnection of systems of different classifications. This can be achieved through the use of colour and keyed connectors where the colour and keying is
different for each classification level or compartment (refer also to 10.1.30 and 10.6.6).
Central Information Repository
10.8.31. Creating a central repository of all the information on networks, IP addresses and devices, is critical to maintaining control of the network. The
challenge with traditional tools is that there are often specific tools for each category of devices: one system to track virtual machines, one system to
track wireless users, one system to track Windows servers, one system to track Linux machines, etc.
10.8.32. A single repository where all the data relevant to networks, hosts, servers, dynamic clients, and virtual environments can be tracked and synchronised
is essential for larger networks. The ability to search across all this information will enable network teams to quickly track changing network
landscapes and rapidly troubleshoot issues as they arise. In addition, business data related to a network resource helps bind together the logical
network construct and the reality of IT resources.
116
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents