Guidelines for Networking Network design and configuration Network documentation It is important that network documentation is developed and accurately depicts the current state of networks, as this can assist in troubleshooting network problems as well as responding to and recovering from cyber security incidents. As such, network documentation should include, at a minimum, high-level network diagrams showing all connections into networks and logical network diagrams showing all critical servers, high-value servers, network devices and network security appliances. Finally, as network documentation could be used by an adversary to assist in compromising networks, it is important that it is appropriately protected. Security Control: ISM-0516; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A Network documentation includes high-level network diagrams showing all connections into networks and logical network diagrams showing all critical servers, high-value servers, network devices and network security appliances. Security Control: ISM-0518; Revision: 4; Updated: Sep-18; Applicability: All; Essential Eight: N/A Network documentation is updated as network configuration changes are made and includes a ‘current as at [date]’ or equivalent statement. Security Control: ISM-1178; Revision: 3; Updated: Sep-18; Applicability: All; Essential Eight: N/A Network documentation provided to a third party, or published in public tender documentation, only contains details necessary for other parties to undertake contractual services. Network segmentation and segregation Network segmentation and segregation is one of the most effective security controls in preventing an adversary from easily propagating throughout networks once initial access has been gained. To achieve this, networks can be segregated into multiple network zones in order to protect servers, services and data. For example, administrative infrastructure used for managing critical servers, high-value servers and regular servers should be segregated from each other. In addition, all administrative infrastructure should be segregated from other assets on networks. Security Control: ISM-1181; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A Networks are segregated into multiple network zones according to the criticality of servers, services and data. Security Control: ISM-1577; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A An organisation’s networks are segregated from their service providers’ networks. Using Virtual Local Area Networks Virtual Local Area Networks (VLANs) can be used to implement network segmentation and segregation as long as networks belong to the same security domain. In such cases, if a data spill occurs the impact will be less than if a data spill occurred between two networks of different classifications or between an organisation’s network and public network infrastructure. Should an organisation choose to risk manage implementing VLANs between networks belonging to different security domains, such as at the same classification, additional security controls for network devices will apply, such as not sharing VLAN trunks and terminating VLANs on separate physical network interfaces. For the purposes of this topic, Multiprotocol Label Switching is considered to be equivalent to VLANs and is subject to the same security controls. Security Control: ISM-1532; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A VLANs are not used to separate network traffic between an organisation’s networks and public network infrastructure. 115

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents