-
Notifications
You must be signed in to change notification settings - Fork 0
/
NZISM-3.2-to-3.6.html
2617 lines (2194 loc) · 131 KB
/
NZISM-3.2-to-3.6.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>NZISM Comparison</title>
<style type="text/css">
body {
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
}
h1 {
color: #040477;
}
table {
border: 1px solid black;
border-collapse: collapse;
}
thead {
background-color: #040477;
color: white;
}
th, td {
padding: 0.3em;
text-align: left;
}
td {
border: 1px solid black;
max-width: 800px;
overflow-wrap: break-word;
}
span.insert {
text-decoration: underline;
background-color: mediumseagreen;
}
span.delete {
text-decoration: line-through;
background-color: firebrick;
}
</style>
</head>
<body>
<section>
<p>This is a report of changes between <strong>nzism-data/NZISM-FullDoc-V.3.2-Jan-2019.xml</strong> and <strong>nzism-data/NZISM-FullDoc-V.3.6-September-2022.xml</strong>.</p>
<ul>
<li><a href="#controls_added">Controls Added</a></li>
<li><a href="#controls_removed">Controls Removed</a></li>
<li><a href="#controls_changed">Controls Changed</a></li>
</ul>
</section>
<section id="controls_added">
<h1>Controls Added</h1>
<table>
<thead>
<tr>
<th>CID</th>
<th>Title</th>
<th>Classifications</th>
<th>Compliances</th>
<th>Text</th>
</tr>
</thead>
<tbody>
<tr>
<td>7045</td>
<td>2.3.25.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>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.</td>
</tr>
<tr>
<td>7046</td>
<td>2.3.25.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>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.
</td>
</tr>
<tr>
<td>7049</td>
<td>2.3.26.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies intending to adopt public cloud technologies or services SHOULD incorporate Zero Trust philosophies and concepts.</td>
</tr>
<tr>
<td>7050</td>
<td>2.3.26.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>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.</td>
</tr>
<tr>
<td>7206</td>
<td>2.4.13.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD ensure they are aware of the latest developments in post-quantum cryptography. GCSB is tracking these developments and will continue to provide advice through the NZISM.</td>
</tr>
<tr>
<td>7207</td>
<td>2.4.13.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD maintain an inventory of sensitive and critical datasets that must be secured for an extended amount of time. This will ensure datasets that may be at risk now and decrypted once a cryptographically relevant quantum computer is available are not secured solely through the use of quantum vulnerable cryptography.</td>
</tr>
<tr>
<td>7208</td>
<td>2.4.13.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD conduct an inventory of systems using cryptographic technologies to determine the potential size and scope of future transition work once post-quantum cryptographic systems become available.</td>
</tr>
<tr>
<td>7209</td>
<td>2.4.13.C.04.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD identify which systems in their inventory rely on public key cryptography and note them as quantum vulnerable in agency risk assessments.</td>
</tr>
<tr>
<td>7210</td>
<td>2.4.13.C.05.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD determine a priority order for quantum vulnerable systems to be transitioned from classical cryptography to post-quantum cryptography.</td>
</tr>
<tr>
<td>7211</td>
<td>2.4.13.C.06.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD consider the following factors when prioritising the quantum vulnerable systems:
Is the system a high value asset based on agency requirements?
Does the system protect sensitive information (e.g. key stores, passwords, root keys, signing keys, personally identifiable information, and classified information)?
Do other systems (internal or external to the agency) depend on the cryptographic protections in place on the quantum vulnerable system?
How long does the data need to be protected?
</td>
</tr>
<tr>
<td>7212</td>
<td>2.4.13.C.07.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Using the inventory and prioritisation information, agencies SHOULD develop a plan for system transitions upon publication of the new post-quantum cryptographic standard.</td>
</tr>
<tr>
<td>7084</td>
<td>3.2.10.C.04.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The CISO SHOULD work with system owners, system certifiers and system accreditors to determine appropriate information security policies for their systems and ensure consistency with the Protective Security Requirements (PSR) and in particular the relevant NZISM components.</td>
</tr>
<tr>
<td>7130</td>
<td>5.9.23.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>An agency MUST undertake a risk assessment to determine which systems and services to include in the agency’s VDP.</td>
</tr>
<tr>
<td>7133</td>
<td>5.9.24.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>An agency MUST develop and publish a VDP.</td>
</tr>
<tr>
<td>7134</td>
<td>5.9.24.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>An agency’s VDP MUST contain at least the following core content:
A scoping statement listing the systems the policy applies to;
Contact details;
Secure communication options (including any public keys);
Information the finder should include in the report;
Acknowledgement of reports and a response time;
Guidance on what forms of vulnerability testing are out of scope for reporters/finders (permitted activities);
Reporters/finders agreeing to not share information about the vulnerability until the end of the disclosure period, in order to allow the agency to address any issues before they become public;
Illegal activities are not permitted (specifying the relevant legislation, such as the Crimes Act); and
Either that “Bug bounties” will not be paid for any discoveries, or it should provide information about the agency’s bug bounty programme.
</td>
</tr>
<tr>
<td>7136</td>
<td>5.9.25.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>An agency SHOULD publish a security.txt to permit secure communications and direct any reports to a specific agency resource, in accordance with the agency’s VDP.</td>
</tr>
<tr>
<td>7138</td>
<td>5.9.26.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>An agency MUST commit to addressing disclosed vulnerabilities within the timeframe it sets in its policy.</td>
</tr>
<tr>
<td>7139</td>
<td>5.9.26.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>An agency’s vulnerability disclosure timeframe SHOULD be set to no more than 90 days.</td>
</tr>
<tr>
<td>7141</td>
<td>5.9.27.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure they integrate their VDP with other elements of their information security policies.</td>
</tr>
<tr>
<td>6592</td>
<td>7.2.24.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST replace compromised cryptographic keys as a matter of urgency and record the replacement in the incident reporting.</td>
</tr>
<tr>
<td>6997</td>
<td>12.6.10.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Because of the risks that data can be recovered from monitors, it is essential that any redeployment or disposal of monitors MUST follow the guidance in the NZISM.</td>
</tr>
<tr>
<td>7165</td>
<td>13.5.24.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Where a facility is NOT an approved facility, agencies MUST ensure any incineration equipment is rated for the destruction of electronic waste (WEEE) and the operator is properly authorised or licensed.</td>
</tr>
<tr>
<td>7166</td>
<td>13.5.24.C.04.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Where a facility is NOT an approved facility, agencies MUST ensure processes are in place for the safe handling of electronic waste (WEEE), including any residual material from the destruction process.</td>
</tr>
<tr>
<td>6553</td>
<td>16.1.38.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Password and other authentication data SHOULD be hashed before storage using an approved cryptographic protocol and algorithm.</td>
</tr>
<tr>
<td>6835</td>
<td>16.4.30.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST establish a Privileged Access Management (PAM) policy.</td>
</tr>
<tr>
<td>6836</td>
<td>16.4.30.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Within the context of agency operations, the agency’s PAM policy MUST define:
a privileged account; and
privileged access.
</td>
</tr>
<tr>
<td>6837</td>
<td>16.4.30.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST manage Privileged Accounts in accordance with the Agency’s PAM Policy.</td>
</tr>
<tr>
<td>6842</td>
<td>16.4.31.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST apply the Principle of Least Privilege when developing and implementing a Privileged Access Management (PAM) policy.</td>
</tr>
<tr>
<td>6843</td>
<td>16.4.31.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD use two-factor or Multi-Factor Authentication to allow access to Privileged Accounts.</td>
</tr>
<tr>
<td>6846</td>
<td>16.4.32.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>As part of a Privileged Access Management (PAM) policy, agencies MUST establish and implement a strong approval and authorisation process before any privileged access credentials are issued.</td>
</tr>
<tr>
<td>6847</td>
<td>16.4.32.C.02.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td>Privileged Access credentials MUST NOT be issued until approval has been formally granted.</td>
</tr>
<tr>
<td>6852</td>
<td>16.4.33.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST establish robust credential suspension and revocation procedures as part of the agency’s Privileged Access Management (PAM) policy.</td>
</tr>
<tr>
<td>6855</td>
<td>16.4.34.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST create and maintain a comprehensive inventory of privileged accounts and the associated access rights and credentials.</td>
</tr>
<tr>
<td>6859</td>
<td>16.4.35.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST create, implement and maintain a robust system of continuous discovery, monitoring and review of privileged accounts and the access rights and credentials associated with those accounts.</td>
</tr>
<tr>
<td>6860</td>
<td>16.4.35.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Privileged account monitoring systems MUST monitor and record:
individual user activity, including exceptions such as out of hours access;
activity from unauthorised sources;
any unusual use patterns; and
any creation of unauthorised privileges access credentials.
</td>
</tr>
<tr>
<td>6861</td>
<td>16.4.35.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST protect and limit access to activity and audit logs and records.</td>
</tr>
<tr>
<td>6864</td>
<td>16.4.36.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST develop and implement a response and remediation policy and procedure as part of an agency’s Privileged Access Management (PAM) policy.</td>
</tr>
<tr>
<td>6868</td>
<td>16.4.37.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST implement a Privileged Access Management (PAM) policy training module as part of the agency’s overall user training and awareness requirement.</td>
</tr>
<tr>
<td>6948</td>
<td>16.7.33.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST undertake a risk analysis before designing and implementing MFA.</td>
</tr>
<tr>
<td>6952</td>
<td>16.7.34.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The design of an agency’s MFA SHOULD include consideration of:
Risk Identification;
Level of security and access control appropriate for each aspect of an agency’s information systems (data, devices, equipment, storage, cloud, etc.)
A formal authorisation process for user system access and entitlements;
Logging, monitoring and reporting of activity;
Review of logs for orphaned accounts and inappropriate user access;
Identification of error and anomalies which may indicate inappropriate or malicious activity;
Incident response;
Remediation of errors;
Suspension and/or revocation of access rights where policy violations occur;
Capacity planning.
</td>
</tr>
<tr>
<td>6953</td>
<td>16.7.34.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Where an agency has implemented MFA they SHOULD:
Require MFA for administrative or other high privileged users; and
Implement a secure, multi-factor process to allow users to reset their normal usage user credentials.
</td>
</tr>
<tr>
<td>6956</td>
<td>16.7.35.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The design of an agency’s MFA system SHOULD be integrated with the agency’s Information Security Policy and the agency’s Privileged Access Management (PAM) Policy.</td>
</tr>
<tr>
<td>6960</td>
<td>16.7.36.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>When agencies implement MFA they MUST ensure users have an understanding of the risks, and include appropriate usage and safeguards for MFA in the agency’s user training and awareness programmes.</td>
</tr>
<tr>
<td>7189</td>
<td>17.2.21.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies using DSA, for the approved use of digital signatures, MUST use a modulus of at least 1024 bits.</td>
</tr>
<tr>
<td>7181</td>
<td>17.2.24.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies using RSA, for the approved use of digital signatures and passing encryption session keys or similar keys, SHOULD use a modulus of at least 4096 bits.</td>
</tr>
<tr>
<td>7186</td>
<td>17.2.25.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies using RSA keys within internet X.509 Public Key Infrastructure certificates MUST use a modulus of at least 2048 bits.</td>
</tr>
<tr>
<td>7187</td>
<td>17.2.26.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>In all other cases when information requires integrity protection using hashing algorithms, Agencies MUST use a minimum of SHA-256.</td>
</tr>
<tr>
<td>6560</td>
<td>17.2.27.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Memorised secrets such as passwords MUST be stored in a form that is resistant to offline attacks.</td>
</tr>
<tr>
<td>6561</td>
<td>17.2.27.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Memorised secrets such as passwords SHOULD be salted and hashed using a suitable one-way key derivation function. See 17.2.24.</td>
</tr>
<tr>
<td>6562</td>
<td>17.2.27.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The salt SHOULD be at least 32 bits in length, be chosen arbitrarily, and each instance is unique so as to minimise salt value collisions among stored hashes.</td>
</tr>
<tr>
<td>7250</td>
<td>18.7.14.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST undertake a threat and risk assessment on the use of inverse split tunnelling prior to enabling the functionality in remote access VPN systems.</td>
</tr>
<tr>
<td>7251</td>
<td>18.7.14.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>When providing inverse split-tunnelled access to internet based services (“directly accessed services”), the following aspects SHOULD be considered as part of the threat and risk assessment:
How do directly accessed services authenticate agency device identities prior to granting access to the service?
How do agency devices securely resolve internet addresses for directly accessed services?
How are the communications between the devices and directly accessed services secured?
How does an agency monitor and account for access made to directly accessed services?
How does an agency protect devices from compromise if they are able to directly access internet based resources, or be directly accessed from the internet?
How do directly accessed services authenticate the user of the agency device prior to granting access to the service (this is separate to authenticating the agency device itself)?
How does an agency enforce the use of multi-factor authentication with directly accessed services?
How does an agency authorise access to directly accessed services, and does this include from devices that are not authorised to connect to agency remote access services (authorisation and authentication are separate activities)?
How is access to directly accessed cloud services removed when staff no longer require access or leave the agency?
</td>
</tr>
<tr>
<td>7349</td>
<td>23.1.53.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST clearly identify and understand where classification, security domain, and trust zone boundaries exist prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7350</td>
<td>23.1.53.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Where multiple identity systems under different security policies are used to control access to an agency’s instance of a public cloud service, the instance MUST be considered to be in a separate security domain from services where access control is managed solely by the agency’s identity system.</td>
</tr>
<tr>
<td>7353</td>
<td>23.1.54.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST clearly identify and understand their cloud service provider’s security responsibilities for each service consumed, and the aspects of security that the agency is responsible for, prior to implementation or adoption of the service.</td>
</tr>
<tr>
<td>7354</td>
<td>23.1.54.C.02.</td>
<td></td>
<td>Should</td>
<td>Agencies SHOULD clearly document the aspects of security they and their provider are responsible for.</td>
</tr>
<tr>
<td>7355</td>
<td>23.1.54.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD review existing security processes to ensure compatibility with their cloud service provider’s responsibilities.</td>
</tr>
<tr>
<td>7359</td>
<td>23.1.55.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD deploy and manage their cloud infrastructure using automation, version control, and infrastructure as code techniques where these are available.</td>
</tr>
<tr>
<td>7386</td>
<td>23.2.16.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST update their risk assessment process to account for public cloud specific risks, prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7387</td>
<td>23.2.16.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST undertake a cloud specific risk assessment in line with the process outlined by the GCDO for each public cloud service, prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7388</td>
<td>23.2.16.C.03.</td>
<td>Confidential, Secret, Top Secret</td>
<td>Must Not</td>
<td>Agencies MUST NOT accredit public cloud services for use with data classified CONFIDENTIAL, SECRET, or TOP SECRET.</td>
</tr>
<tr>
<td>7389</td>
<td>23.2.16.C.04.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td>Agencies MUST NOT accredit public cloud services to host, process, store, or transmit NZEO endorsed information.</td>
</tr>
<tr>
<td>7394</td>
<td>23.2.17.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST consider risks to the availability of systems and information in their design of cloud systems architectures, supporting controls, and governance processes prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7397</td>
<td>23.2.18.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD obtain regular assurance checks on cloud service providers, ensuring that they are undertaken by a suitably qualified assessor.</td>
</tr>
<tr>
<td>7400</td>
<td>23.2.19.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST obtain assurance that cloud service providers undertake appropriate software and operating system patching and maintenance.</td>
</tr>
<tr>
<td>7404</td>
<td>23.2.20.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST obtain assurance that technical protections exist to adequately isolate tenants.</td>
</tr>
<tr>
<td>7407</td>
<td>23.2.21.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD make use of the GCSB endorsed baseline security templates where applicable. </td>
</tr>
<tr>
<td>7433</td>
<td>23.3.18.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Accounts used to perform privileged actions SHOULD NOT be synchronised between environments.</td>
</tr>
<tr>
<td>7436</td>
<td>23.3.19.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Where administration interfaces or portals are accessible from the internet, privileged accounts MUST be configured to use multiple factors of authentication.</td>
</tr>
<tr>
<td>7437</td>
<td>23.3.19.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Where cloud service interfaces or portals are accessible from the internet, user accounts SHOULD be configured to use multiple factors of authentication.</td>
</tr>
<tr>
<td>7440</td>
<td>23.3.20.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Staff offboarding processes MUST be updated to include removing all access to public cloud based services, prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7443</td>
<td>23.3.21.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure that relying parties continually verify the authenticity of their identity provider’s responses, through for example, cryptographic signing of authentication requests and responses.</td>
</tr>
<tr>
<td>7446</td>
<td>23.3.22.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD ensure that relying parties use all available information from the identity provider to inform access control decisions.</td>
</tr>
<tr>
<td>7461</td>
<td>23.4.9.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>For each cloud service, agencies MUST ensure that the mechanisms used to protect data meet agency requirements.</td>
</tr>
<tr>
<td>7462</td>
<td>23.4.9.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST update key management plans to account for differences in public cloud before storing organisational data in a public cloud environment.</td>
</tr>
<tr>
<td>7463</td>
<td>23.4.9.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure their key management plan includes provision for migrating data from the cloud environment where it was created.</td>
</tr>
<tr>
<td>7466</td>
<td>23.4.10.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST apply the principle of least privilege and configure service endpoints to restrict access to authorised parties.</td>
</tr>
<tr>
<td>7469</td>
<td>23.4.11.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST identify where data used in conjunction with a public cloud service is stored or processed, including any replicas or backups that may be created.</td>
</tr>
<tr>
<td>7470</td>
<td>23.4.11.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agency risk assessments of public cloud services MUST include any risks arising from data location. Any actions required to mitigate these risks must be identified and documented prior to implementation or adoption of public cloud services.</td>
</tr>
<tr>
<td>7474</td>
<td>23.4.12.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST update their disaster recovery plans prior to storing or replicating data in public cloud services, to ensure these plans address any cloud-specific aspects of backup and recovery.</td>
</tr>
<tr>
<td>7475</td>
<td>23.4.12.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>When planning tests of disaster recovery processes in accordance with 6.4.6 Backup strategy, agencies MUST include tests of any cloud-specific data recovery processes.</td>
</tr>
<tr>
<td>7494</td>
<td>23.5.10.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST understand the range of logging capabilities provided by their cloud service providers and determine whether they are sufficient for agency needs.</td>
</tr>
<tr>
<td>7496</td>
<td>23.5.11.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure that logs associated with public cloud services are collected, protected, and that their integrity can be confirmed in accordance with the agency’s documented logging requirements.</td>
</tr>
<tr>
<td>7498</td>
<td>23.5.12.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure that cloud service provider logs are incorporated into overall enterprise logging and alerting systems or procedures in a timely manner to detect information security incidents.</td>
</tr>
<tr>
<td>7499</td>
<td>23.5.12.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD ensure that tools and procedures used to detect potential information security incidents account for the public cloud services being consumed by the agency.</td>
</tr>
</tbody>
</table>
</section>
<section id="controls_removed">
<h1>Controls Removed</h1>
<table>
<thead>
<tr>
<th>CID</th>
<th>Title</th>
<th>Classifications</th>
<th>Compliances</th>
<th>Text</th>
</tr>
</thead>
<tbody>
<tr>
<td>383</td>
<td>3.3.6.C.05.</td>
<td>All Classifications</td>
<td>Should</td>
<td>ITSMs SHOULD work with system owners, systems certifiers and systems accreditors to determine appropriate information security policies for their systems and ensure consistency with the Protective Security Requirements (PSR) and in particular the relevant NZISM components.</td>
</tr>
<tr>
<td>1263</td>
<td>7.3.5.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST follow the NZ implementation of the STIXX / TAXII and CyBox protocols and SHOULD include the following information in their register:
the date the information security incident was discovered;
the date the information security incident occurred;
a description of the information security incident, including the personnel, systems and locations involved;
the action taken;
to whom the information security incident was reported; and
the file reference.
</td>
</tr>
<tr>
<td>1350</td>
<td>8.2.5.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD use a secured server or communications room within a secured facility.</td>
</tr>
<tr>
<td>2141</td>
<td>17.2.17.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies using DSA, for the approved use of digital signatures, MUST use a modulus of at least 1024 bits.</td>
</tr>
<tr>
<td>2161</td>
<td>17.2.23.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>3DES MUST use either two distinct keys in the order key 1, key 2, key 1 or three distinct keys.</td>
</tr>
<tr>
<td>2170</td>
<td>17.2.24.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>AES implementations for symmetric encryption of data SHOULD use the Galois/Counter Mode (GCM).</td>
</tr>
</tbody>
</table>
</section>
<section id="controls_changed">
<h1>Controls Changed</h1>
<table>
<thead>
<tr>
<th>CID</th>
<th>Title</th>
<th>Classifications</th>
<th>Compliances</th>
<th>Text</th>
</tr>
</thead>
<tbody>
<tr>
<td>127</td>
<td>1.1.64.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>System owners seeking a dispensation for non-compliance with any <span class="delete">essential</span><span class="insert">baseline</span> controls in this manual MUST be granted a dispensation by their Accreditation Authority. Where High <span class="delete">Grad</span><span class="insert">Assuranc</span>e Cryptographic Systems (H<span class="insert">ACS) are implemented, the Accreditation Authority will be the Director-General </span>GCS<span class="delete">) are implemented, the Accreditation Authority will be the Director-General GCS</span>B or a formal delegate.</td>
</tr>
<tr>
<td>131</td>
<td>1.1.65.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>System owners seeking a dispensation for non-compliance with <span class="delete">essential</span><span class="insert">baseline</span> controls MUST complete an agency risk assessment which documents:
the reason(s) for not being able to comply with this manual;
the effect on any of their own, multi-agency or All-of-Government system;
the alternative mitigation measure(s) to be implemented;
The strength and applicability of the alternative mitigations;
an assessment of the residual security risk(s); and
a date by which to review the decision.
</td>
</tr>
<tr>
<td>143</td>
<td>1.1.67.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>If a system processes, stores or communicates data and information with multiple agencies or forms part of an All-of-Government system, interested parties MUST be formally consulted before non-compliance with any <span class="delete">essential</span><span class="insert">baseline</span> controls.</td>
</tr>
<tr>
<td>151</td>
<td>1.1.69.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST retain a copy and maintain a record of the supporting risk assessment and decisions to be non-compliant with any <span class="delete">es</span><span class="insert">ba</span>se<span class="insert">li</span>n<span class="delete">tial</span><span class="insert">e</span> controls from this manual.</td>
</tr>
<tr>
<td>255</td>
<td>2.3.27.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies intending to adopt cloud technologies or services MUST conduct a comprehensive risk assessment, in accordance with the guidance provided by the G<span class="insert">overnment </span>C<span class="delete">I</span><span class="insert">hief Digital </span>O<span class="insert">fficer (GCDO)</span> before implementation or adoption.</td>
</tr>
<tr>
<td>283</td>
<td>3.1.8.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>When the agency head de<span class="delete">vo</span>l<span class="delete">v</span><span class="insert">egat</span>es their authority<span class="insert">,</span> the delegate SHOULD be <span class="insert">a senior executive who understands </span>the <span class="delete">CISO</span><span class="insert">consequences and potential impact to the business of the acceptance of residual risk</span>.</td>
</tr>
<tr>
<td>284</td>
<td>3.1.8.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Where the head of a smaller agency is not able to satisfy all segregation of duty requirements because of scalability and small personnel numbers, all<span class="delete">,</span> potential conflicts of interest SHOULD be clearly identified, declared and actively managed.</td>
</tr>
<tr>
<td>311</td>
<td>3.2.8.C.05.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Where <span class="insert">mul</span>t<span class="delete">h</span><span class="insert">ipl</span>e role<span class="insert">s</span> <span class="delete">of</span><span class="insert">are held by</span> the CISO <span class="delete">is outsourced,</span><span class="insert">any</span> potential conflicts of interest<span class="delete"> in availability, response times or working with vendors</span> SHOULD be identified and carefully managed.</td>
</tr>
<tr>
<td>322</td>
<td>3.2.11.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The CISO SHOULD be responsible for e<span class="insert">stablishing mechanisms and programs to e</span>nsur<span class="delete">ing</span><span class="insert">e</span> compliance with the information security policies and standards within the agency.</td>
</tr>
<tr>
<td>323</td>
<td>3.2.11.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The CISO SHOULD be responsible for ensuring agency compliance with the NZISM through facilitating a continuous program of certification and accreditation <span class="delete">b</span><span class="insert">of </span>a<span class="delete">sed</span><span class="insert">ll</span> <span class="delete">on security risk man</span>age<span class="insert">ncy syste</span>m<span class="delete">ent</span><span class="insert">s</span>.</td>
</tr>