2.3.25.R.04.
Rationale
Developing a strategy that outlines how an agency will look to exploit the opportunities presented by cloud while managing the risks and
change required in ICT governance and management processes is essential to the successful adoption of cloud services for agencies.
2.3.25.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:7045]
Agencies intending to adopt public cloud technologies or services MUST develop a plan for how they intend to use these services. This plan can
be standalone or part of an overarching ICT strategy.
2.3.25.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:7046]
An agency’s cloud adoption plan SHOULD cover:
Outcomes and benefits that the adoption of cloud technologies will bring;
Risks introduced or mitigated through the use of cloud, and the agency’s risk tolerance;
Financial and cost accounting models;
Shared responsibility models;
Cloud deployment models;
Cloud security strategy;
Resilience and recovery approaches;
Data recovery on contract termination;
Cloud exit strategy and other contractual arrangements; and
A high level description of the foundation services that enable cloud adoption, including:
User, device and system identity;
Encryption and key management;
Information management;
Logging and alerting;
Incident management;
Managing privileged activities; and
Cost management.
2.3.26.
Zero Trust
2.3.26.R.01.
Rationale
Zero Trust is becoming the de-facto approach to ICT system security and is recommended by GCSB as the approach agencies should take,
particularly as part of the adoption of cloud services.
Zero Trust is a set of principles and outcomes, not an architecture or a solution. You cannot ‘buy’ Zero Trust.
Zero Trust is compatible with other ICT outcomes, such as improved access to information, increased agility and better security.
Key aspects of Zero Trust focus on:
Visibility (through telemetry) and analytics of how services are functioning – this comes through as focus on monitoring, event gathering
and machine learning based analysis; and
Automation of service delivery and security actions.
2.3.26.R.02.
Rationale
Public cloud services are often built following Zero Trust principles, and agencies will find adoption of this approach will lead to more successful
security outcomes than trying to recreate legacy perimeter security controls in the cloud.
2.3.26.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:7049]
Agencies intending to adopt public cloud technologies or services SHOULD incorporate Zero Trust philosophies and concepts.
2.3.26.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:7050]
Agencies SHOULD leverage public cloud environment native security services as part of legacy system migrations, in preference to recreating
application architectures that rely on legacy perimeter controls for security.
2.3.27.
Risk Assessment
2.3.27.R.01.
Rationale
The adoption of cloud technologies will introduce a wide range of technology and information system risksin addition to the risks that already
exist for agency systems. It is vital that these additional risks are identified and assessed in order to select appropriate controls and
countermeasures. Trust boundaries must be defined to assist in determining effective controls and where these controls can best be applied.
The geographic location of agency data should be identified as this may include offshore data centres.
2.3.27.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:255]
Agencies intending to adopt cloud technologies or services MUST conduct a comprehensive risk assessment, in accordance with the guidance
provided by the Government Chief Digital Officer (GCDO) before implementation or adoption.
2.3.27.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:256]
Agencies MUST ensure cloud risks for any cloud service adopted are identified, understood and formally accepted by the Agency Head or Chief
Executive and the agency’s Accreditation Authority.
2.3.28.
17
Security Architecture
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents