RFC 7619 The NULL Authentication IETF Method https://datatracker.ietf.org/doc/html/ rfc7619 in the Internet Key Exchange Protocol Version 2 (IKEv2) RFC 8012 Label Switched Path IETF (LSP) and Pseudowire https://datatracker.ietf.org/doc/html/ rfc8012 (PW) Ping/Trace over MPLS Networks Using Entropy Labels (ELs) RFC 8190 Updates to the Special- IETF Purpose IP Address https://datatracker.ietf.org/doc/html/ rfc8190 Registries Rationale & Controls 10.8.34. Risk Assessment 10.8.34.R.01. Rationale A risk assessment is a fundamental tool in the architecture and design of a network. 10.8.34.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:5815] Agencies MUST conduct and document a risk assessment before creating an architecture, and designing an agency network. 10.8.34.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:5816] The principles of separation and segregation as well as the system classification MUST be incorporated into the risk assessment. 10.8.35. Security Architecture 10.8.35.R.01. Rationale It is important that the principles of separation and segregation as well as the system classification are incorporated into the overall security architecture to maximise design and operational efficiency and to provide and support essential security to the network design. 10.8.35.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:5820] Security architectures MUST apply the principles of separation and segregation. 10.8.36. Identification of major classifications/categories of network segments 10.8.36.R.01. Rationale Identified in the risk assessment, it is essential that the classification of systems is clearly identified and is apparent in all architecture and design elements and systems documentation. 10.8.36.R.02. Rationale Clear distinction of networks of different classifications is reinforced through the use of different IP addressing schemes as well as the application of Red/Black, separation and segregation concepts and principles. Refer also to section 10.1. 10.8.36.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:5825] The classification and other restrictions on the security and control of information MUST be clearly identified for each part of the Agency network. 10.8.37. Visibility 10.8.37.R.01. Rationale Clear identification and visibility of the classifications or category of a network segment is essential in minimising accidental cross-connections, incident management and in limiting the propagation of errors form one segment to others. This also assists in network maintenance and management. 10.8.37.R.02. Rationale Clear visual identification is supported by the use of IP addressing and cable colour schemes as well as the use of different types of cable connectors for different network segments. 10.8.37.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:5843] Systems of different classifications MUST be visually distinct. 10.8.38. Information Repository 10.8.38.R.01. Rationale Clear documentation and records of changes to the architecture and construct of a network are essential in change management, planning, design of network modifications, incident management and maintenance of a strong security posture. 10.8.38.R.02. Rationale 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 119 Version_3.5__January-2022

Select target paragraph3

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