Guidelines for Gateways Gateways Introduction to gateways This section describes security controls applicable to all types of gateways. In applying these security controls, gateways take on the highest sensitivity or classification of connected security domains. Additional sections of these guidelines should also be consulted depending on the types of gateways being deployed and the security domains involved. For example, the Cross Domain Solutions section should be consulted for gateways between different security domains where at least one security domain is classified SECRET or TOP SECRET. Implementing gateways Gateways are critical for an organisation to reduce the security risks associated with providing external parties with access to their networks. In doing so, it is important that gateways are used not only between an organisation’s networks and public network infrastructure, but also between an organisation’s networks that belong to different security domains and between an organisation’s networks and other organisations’ networks that are connected via means other than public network infrastructure. When implementing gateways between an organisation’s networks and public network infrastructure, an organisation should place any services that external parties require access to within a demilitarised zone. This can mitigate security risks for an organisation when hosting such services in an internet-accessible manner. Finally, in architecting gateways, it is important that they only allow explicitly authorised data flows. In support of this, gateways should inspect and filter data flows at the transport and above network layers. Furthermore, gateways should be capable of performing ingress traffic filtering to detect and prevent Internet Protocol (IP) source address spoofing. Security Control: ISM-0628; Revision: 6; Updated: Mar-22; Applicability: All; Essential Eight: N/A Gateways are implemented between networks belonging to different security domains. Security Control: ISM-0637; Revision: 6; Updated: Mar-22; Applicability: All; Essential Eight: N/A Gateways implement a demilitarised zone if external parties require access to an organisation’s services. Security Control: ISM-0631; Revision: 7; Updated: Mar-22; Applicability: All; Essential Eight: N/A Gateways only allow explicitly authorised data flows. Security Control: ISM-1192; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A Gateways inspect and filter data flows at the transport and above network layers. Security Control: ISM-1427; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A Gateways perform ingress traffic filtering to detect and prevent IP source address spoofing. System administrators for gateways In identifying suitable system administrators for gateways, it is important that individuals comply with any citizenship requirements, undergo appropriate employment screening and, where necessary, hold an appropriate security clearance based on the sensitivity or classification of gateways. For example, all systems administrators for gateways between OFFICIAL and PROTECTED networks will need to hold baseline security clearances. In addition, when creating privileged accounts for performing administrative activities, it is important that the principle of least privilege is followed. In turn, this should be supported by the principle of separation of duties. Adhering to 139

Select target paragraph3

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