Repository navigation
Expand file tree
/
Copy pathNZISM-3.6-to-3.9.html
More file actions
2441 lines (1903 loc) · 126 KB
/
Copy pathNZISM-3.6-to-3.9.html
File metadata and controls
2441 lines (1903 loc) · 126 KB
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>
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.6-September-2022.xml</strong> and <strong>nzism-data/NZISM-ISM Document-V.-3.9-April-2025.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>7536</td>
<td>7.2.20.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD formally share post-incident review reports by emailing them to <a title="NCSC incidents" href="mailto:incidents@ncsc.govt.nz">incidents@ncsc.govt.nz</a>.</p></td>
</tr>
<tr>
<td>7524</td>
<td>11.1.15.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies wishing to permit the use of Bluetooth MUST develop a policy that details the circumstances under which Bluetooth usage is permitted, and situations where it is not to be used.</p></td>
</tr>
<tr>
<td>7525</td>
<td>11.1.15.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>The policy position MUST include information about Bluetooth security controls that are to be used, and methods for verifying that the controls are in place and are effective.</p></td>
</tr>
<tr>
<td>7526</td>
<td>11.1.16.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST ensure that Bluetooth pairing is only established between authorised devices. (Unless a gateway is being used, paired devices are considered to operate at the same security classification level).</p></td>
</tr>
<tr>
<td>7527</td>
<td>11.1.16.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD ensure that Bluetooth discovery of devices is disabled unless a new pairing connection is being established.</p></td>
</tr>
<tr>
<td>7528</td>
<td>11.1.16.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD ensure that Bluetooth device pairing only occurs at a location where only authorised persons have access.</p></td>
</tr>
<tr>
<td>7529</td>
<td>11.1.16.C.04.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD ensure that Bluetooth pairings are removed when they are no longer required.</p></td>
</tr>
<tr>
<td>7530</td>
<td>11.1.17.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies using Bluetooth MUST use the most secure configuration supported by the paired devices.</p></td>
</tr>
<tr>
<td>7531</td>
<td>11.1.17.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD identify the:</p>
<ul>
<li>Bluetooth type (BR/EDR or LE), </li>
<li>version, and</li>
<li>security capabilities;</li>
</ul>
<p>for devices used to form Bluetooth connections, and ensure they are used to inform risk decisions on the use of Bluetooth.</p></td>
</tr>
<tr>
<td>7532</td>
<td>11.1.17.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD ensure that new Bluetooth connections between devices are authenticated using explicit user actions, such as entry of a numeric code, confirmation of a matching PIN, or other affirming action, such as challenge-response process.</p></td>
</tr>
<tr>
<td>7533</td>
<td>11.1.18.C.01.</td>
<td>Unclassified/In-Confidence</td>
<td>Should</td>
<td><p>Agencies using Bluetooth between devices to transfer UNCLASSIFIED or IN-CONFIDENCE information SHOULD ensure that connections meet NZISM standards for authentication and use Approved Cryptographic Algorithms for encryption and message integrity. </p></td>
</tr>
<tr>
<td>7534</td>
<td>11.1.18.C.02.</td>
<td>Restricted/Sensitive</td>
<td>Must</td>
<td><p>Agencies using Bluetooth between devices to transfer RESTRICTED or SENSITIVE information MUST ensure that connections meet NZISM standards for authentication and use Approved Cryptographic Algorithms for encryption and message integrity.</p></td>
</tr>
<tr>
<td>7535</td>
<td>11.1.18.C.03.</td>
<td>Restricted/Sensitive</td>
<td>Must</td>
<td><p>If Bluetooth specifications do not support these approved encryption methods, organisations MUST do a risk assessment and use the exception or waiver process to accept this risk.</p></td>
</tr>
<tr>
<td>7537</td>
<td>11.8.13.C.01.</td>
<td>Top Secret, Secret, Confidential</td>
<td>Should</td>
<td><p>Use of MFDs for printing, scanning, and copying purposes SHOULD be centrally logged.</p></td>
</tr>
<tr>
<td>7519</td>
<td>15.2.36.C.03</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST manage “received DMARC messages” in accordance with the agency’s published DMARC policy.</p></td>
</tr>
<tr>
<td>7520</td>
<td>15.2.36.C.05</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD produce failure reports and aggregate reports according to the agency’s DMARC policies.</p></td>
</tr>
<tr>
<td>7521</td>
<td>15.2.48.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD enable MTA-STS to prevent the unencrypted transfer of emails between complying servers.</p></td>
</tr>
<tr>
<td>7522</td>
<td>15.2.48.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST use TLS 1.2 or above when implementing MTA-STS.</p></td>
</tr>
<tr>
<td>7523</td>
<td>15.2.48.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD enable TLS reporting when implementing MTA-STS.</p></td>
</tr>
<tr>
<td>7541</td>
<td>16.1.25.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD design and implement Zero Trust principles and architecture to strengthen identification management.</p></td>
</tr>
<tr>
<td>7542</td>
<td>16.1.27.C.02.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td><p>Agencies MUST NOT use shared credentials to access administrator or privileged access accounts.</p>
<p>NB: Break Glass accounts are exempt from this control. For further guidance on Break Glass accounts see Emergency accounts (Break Glass accounts section).</p></td>
</tr>
<tr>
<td>7543</td>
<td>16.1.30.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD assess and determine the risk of centralised access management systems, including SSO, to safely manage integration into systems and when using FIM.</p></td>
</tr>
<tr>
<td>7544</td>
<td>16.1.31.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST ensure adequate password policies are implemented and enforced across all systems.</p></td>
</tr>
<tr>
<td>7545</td>
<td>16.1.31.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST implement a password policy enforcing <strong>at least annual</strong> password changes on systems that <strong>have not</strong> implemented MFA or passwordless authentication.</p></td>
</tr>
<tr>
<td>7546</td>
<td>16.1.31.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST implement a password policy enforcing:</p>
<ul>
<li>A minimum password length of 16 characters (e.g four words).</li>
<li>Passwords must be <strong>long, strong and unique</strong>. This means passwords must be a minimum character length, and are a combination of unique random words, characters or numbers.</li>
</ul>
<p>NB: no explicit complexity requirements are enforced (e.g. numbers or special characters), however passwords must be unique, or random and <strong>may</strong> include special characters and numbers to achieve this.</p></td>
</tr>
<tr>
<td>7547</td>
<td>16.1.31.C.04.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>To ensure security of systems are not weakened through authentication mechanisms, at a minimum, agencies MUST:</p>
<ul>
<li>apply MFA appropriately (refer to controls in Section 16.7);</li>
<li>ensure authentication secrets (including passwords) are securely stored;</li>
<li>remove knowledge-based questions from authentication process (eg, dog’s name, first school etc.);</li>
<li>new passwords are screened to reduce the likelihood of previously compromised passwords;</li>
<li>remove hints from authentication process; and</li>
<li>change passwords when a suspected or known compromise of an account has occurred.</li>
</ul></td>
</tr>
<tr>
<td>7548</td>
<td>16.1.31.C.06.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD consider the use of location-based factors in the authentication process, (e.g., Users must be at an expected location (city, country, IP address) and provide the correct credentials for the authentication to succeed).</p></td>
</tr>
<tr>
<td>7549</td>
<td>16.1.31.C.07.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>When creating password policies, agencies SHOULD consider implementing annual password changes.</p></td>
</tr>
<tr>
<td>7562</td>
<td>16.1.34.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Passwords and other authentication secrets MUST be stored securely including being:</p>
<ul>
<li>salted (32 bits or more),
<ul>
<li>salts should be unique to each password and should be randomly generated.</li>
</ul>
</li>
<li>hashed (HMAC using SHA-2/3), and</li>
<li>“stretched” (such as PBKDF2 with at least:
<ul>
<li>600k iterations with internal hash function of HMAC-SHA-256; or</li>
<li>210k iterations with internal hash function of HMAC-SHA-512).</li>
</ul>
</li>
</ul></td>
</tr>
<tr>
<td>7551</td>
<td>16.1.36.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Where passwords are not set by the account holder, agencies MUST use temporary passwords when resetting system user accounts.</p></td>
</tr>
<tr>
<td>7552</td>
<td>16.1.36.C.03.</td>
<td>All Classifications</td>
<td>Should Not</td>
<td><p>Agencies SHOULD NOT use single factor authentication when changing users’ Multi-Factor Authentication details.</p></td>
</tr>
<tr>
<td>7558</td>
<td>16.1.37.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Password managers provide no additional security to the sign-in password. Agencies using password managers MUST ensure sign-in passwords adhere to the password security policies used by the organisation.</p></td>
</tr>
<tr>
<td>7559</td>
<td>16.1.37.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies using password managers SHOULD consider the use of MFA to access the password manager.</p></td>
</tr>
<tr>
<td>7556</td>
<td>16.1.38.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>When moving to passwordless authentication, agencies SHOULD carry out a risk assessment and evaluate passwordless authentication models to choose authentication mechanisms and factors that best fit the organisation’s security and authentication requirements.</p></td>
</tr>
<tr>
<td>7554</td>
<td>16.1.39.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST ensure authentication methods that are susceptible to replay attacks are disabled.</p></td>
</tr>
<tr>
<td>7550</td>
<td>16.4.37.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p><span class="NormalTextRun SCXW132241447 BCX8">Agencies</span> <span class="NormalTextRun SCXW132241447 BCX8">SHOULD</span><span class="NormalTextRun SCXW132241447 BCX8"> consider the use of </span><span class="NormalTextRun SCXW132241447 BCX8">time bound revocation to privileged accounts.</span></p></td>
</tr>
<tr>
<td>7553</td>
<td>16.4.39.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p><span class="TextRun Highlight SCXW17435025 BCX8"><span class="NormalTextRun SCXW17435025 BCX8">Agencies</span> </span><span class="TextRun Highlight SCXW17435025 BCX8"><span class="NormalTextRun SCXW17435025 BCX8">MUST </span><span class="NormalTextRun SCXW17435025 BCX8">investigate any </span><span class="NormalTextRun SCXW17435025 BCX8">indication</span><span class="NormalTextRun SCXW17435025 BCX8"> of compromise or misuse </span><span class="NormalTextRun SCXW17435025 BCX8">of systems credentials or accounts</span></span><span class="TextRun Highlight SCXW17435025 BCX8"><span class="NormalTextRun SCXW17435025 BCX8">.</span></span></p></td>
</tr>
<tr>
<td>7555</td>
<td>16.5.12.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p><span class="TextRun Highlight SCXW162426022 BCX8"><span class="NormalTextRun SCXW162426022 BCX8">Agencies</span> <span class="NormalTextRun SCXW162426022 BCX8">SHOULD use Zero Trust principles alongside the use of VPN connections to enhance the security posture of the </span><span class="NormalTextRun SCXW162426022 BCX8">organisation</span><span class="NormalTextRun SCXW162426022 BCX8">.</span><span class="NormalTextRun SCXW162426022 BCX8"> This should include removing the ability for a standard user to disable the VPN connection.</span></span></p></td>
</tr>
<tr>
<td>7557</td>
<td>16.6.13.C.05.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p><span class="TextRun Highlight SCXW250297705 BCX8"><span class="NormalTextRun SCXW250297705 BCX8">Agencies</span><span class="NormalTextRun SCXW250297705 BCX8"> should prioritise their log retention </span><span class="NormalTextRun SCXW250297705 BCX8">requirements based on the risks surrounding their most sensitive systems</span><span class="NormalTextRun SCXW250297705 BCX8">.</span></span></p></td>
</tr>
<tr>
<td>7560</td>
<td>16.6.15.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p><span class="TextRun Highlight SCXW245238288 BCX8"><span class="NormalTextRun SCXW245238288 BCX8">Agencies</span><span class="NormalTextRun SCXW245238288 BCX8"> SHOULD have a monitoring solution implemented that enables detection of incidents as they occur so that </span><span class="NormalTextRun SCXW245238288 BCX8">appropriate responses</span><span class="NormalTextRun SCXW245238288 BCX8"> can be taken in adequate </span><span class="NormalTextRun SCXW245238288 BCX8">timeframes</span><span class="NormalTextRun SCXW245238288 BCX8">.</span></span></p></td>
</tr>
<tr>
<td>7561</td>
<td>16.6.15.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p><span class="TextRun Highlight SCXW216480023 BCX8"><span class="NormalTextRun SCXW216480023 BCX8">Agencies</span><span class="NormalTextRun SCXW216480023 BCX8"> SHOULD have systems available for processing system event logs to </span><span class="NormalTextRun SCXW216480023 BCX8">identify</span><span class="NormalTextRun SCXW216480023 BCX8"> and correlate events which </span><span class="NormalTextRun SCXW216480023 BCX8">indicate</span><span class="NormalTextRun SCXW216480023 BCX8"> behavioural anomalies or potential security compromise in the systems, in a near real-time manner.</span></span></p></td>
</tr>
<tr>
<td>7563</td>
<td>16.7.42.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Where an agency has external facing systems, cloud-based services, or is authenticating to third-party services services, they MUST:</p>
<ul>
<li>require MFA for all user accounts; and</li>
<li>implement a secure, multi-factor process to allow entities to reset their standard user credentials.</li>
</ul></td>
</tr>
<tr>
<td>7564</td>
<td>16.7.42.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST implement MFA on all user accounts with <strong>remote</strong> access to organisational resources.</p></td>
</tr>
<tr>
<td>7565</td>
<td>16.7.42.C.04.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD implement MFA on all user accounts with access to organisational resources.<span style="font-size: 10.5pt; font-family: 'Open Sans',sans-serif; mso-bidi-font-family: 'Times New Roman'; color: windowtext; mso-ansi-language: EN-AU; mso-fareast-language: EN-AU;"> </span></p></td>
</tr>
<tr>
<td>7566</td>
<td>16.7.42.C.05.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Where agencies have implemented MFA, they SHOULD implement phishing-resistant MFA on administration accounts.<span style="font-size: 10.5pt; font-family: 'Open Sans',sans-serif; mso-bidi-font-family: 'Times New Roman'; color: windowtext; mso-ansi-language: EN-AU; mso-fareast-language: EN-AU;"> </span></p></td>
</tr>
<tr>
<td>7567</td>
<td>16.7.42.C.06.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD use phishing-resistant MFA when authenticating users to systems.</p></td>
</tr>
<tr>
<td>7538</td>
<td>18.2.9.C.01.</td>
<td>Secret, Confidential, Top Secret</td>
<td>Must</td>
<td><p>EAP-TLS or PEAP-EAP-TLS MUST be used on wireless networks to perform mutual authentication.</p></td>
</tr>
<tr>
<td>7539</td>
<td>18.2.19.C.01.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td><p>Agencies MUST NOT use Wi-Fi Protected Access (WPA) for wireless deployments.</p></td>
</tr>
<tr>
<td>7540</td>
<td>18.2.19.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td><p>Agencies SHOULD use Wi-Fi Protected Access 3 (WPA3) for wireless deployments with preference given to WPA3-Enterprise 192-bit mode.</p></td>
</tr>
<tr>
<td>7511</td>
<td>23.4.13.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p class="Normal-nonumbering"><span>Agencies MUST have a defined exit strategy for each public cloud service they consume, including a process by which their data can be retrieved and erased from the cloud service as part of contract termination.</span></p></td>
</tr>
<tr>
<td>7512</td>
<td>23.4.13.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p>Agencies MUST ensure all data they need to retain is retrieved from the cloud service provider prior to decommissioning.</p></td>
</tr>
<tr>
<td>7513</td>
<td>23.4.13.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td><p class="NormS17C2"><span>Agencies MUST have assurance that no agency-owned data is retained on the cloud service being decommissioned.</span></p></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>1223</td>
<td>7.2.21.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD formally report information security incidents using the NCSC on-line reporting form.</td>
</tr>
<tr>
<td>2557</td>
<td>11.2.5.C.01.</td>
<td>Confidential, Secret, Top Secret</td>
<td>Must</td>
<td>Agencies intending to use fax machines or MFDs to send classified information MUST comply with additional requirements. Contact the GCSB for further details.</td>
</tr>
<tr>
<td>3052</td>
<td>11.6.72.C.01.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td>Any RFID tags of class 3, 4, or 5 MUST NOT be permitted in secure spaces.</td>
</tr>
<tr>
<td>3054</td>
<td>11.6.72.C.02.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td>RFID readers MUST NOT be permitted in secure spaces.</td>
</tr>
<tr>
<td>3055</td>
<td>11.6.72.C.03.</td>
<td>All Classifications</td>
<td>Should Not</td>
<td>Class 2 RFID tags SHOULD NOT be permitted in secure spaces.</td>
</tr>
<tr>
<td>1857</td>
<td>16.1.40.C.01.</td>
<td>Confidential, Secret, Top Secret</td>
<td>Must</td>
<td>Agencies MUST implement a password policy enforcing:
a minimum password length of ten characters, consisting of at least three of the following character sets:
lowercase characters (a-z);
uppercase characters (A-Z);
digits (0-9); and
punctuation and special characters.
</td>
</tr>
<tr>
<td>1858</td>
<td>16.1.40.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD implement a password policy enforcing either:
a minimum password length of 16 characters with no complexity requirement; or
a minimum password length of ten characters, consisting of at least three of the following character sets:
lowercase characters (a-z);
uppercase characters (A-Z);
digits (0-9); and
punctuation and special characters.
</td>
</tr>
<tr>
<td>1868</td>
<td>16.1.41.C.01.</td>
<td>Confidential, Secret, Top Secret</td>
<td>Must</td>
<td>Agencies MUST:
ensure that passwords are changed at least every 90 days;
prevent system users from changing their password more than once a day;
check passwords for compliance with their password selection policy where the system cannot be configured to enforce complexity requirements; and
force the system user to change an expired password on initial logon or if reset.
</td>
</tr>
<tr>
<td>1870</td>
<td>16.1.41.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD:
ensure that passwords are changed at least every 90 days;
prevent system users from changing their password more than once a day;
check passwords for compliance with their password selection policy where the system cannot be configured to enforce complexity requirements; and
force the system user to change an expired password on initial logon or if the password is reset.
</td>
</tr>
<tr>
<td>1871</td>
<td>16.1.41.C.04.</td>
<td>All Classifications</td>
<td>Should Not</td>
<td>Agencies SHOULD NOT:
allow predictable reset passwords;
reuse passwords when resetting multiple accounts;
store passwords in the clear on the system;
allow passwords to be reused within eight password changes; and
allow system users to use sequential passwords.
</td>
</tr>
<tr>
<td>1893</td>
<td>16.1.46.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD:
lock system user accounts after three failed logon attempts;
have a system administrator reset locked accounts;
remove or suspend system user accounts as soon as possible when personnel no longer need access due to changing roles or leaving the agency; and
remove or suspend inactive accounts after a specified number of days.
</td>
</tr>
<tr>
<td>1904</td>
<td>16.1.49.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD configure systems to display the date and time of the system user’s previous login during the login process.</td>
</tr>
<tr>
<td>1909</td>
<td>16.1.50.C.01.</td>
<td>All Classifications</td>
<td>Should Not</td>
<td>Agencies SHOULD NOT permit the display of last logged on username, credentials or other identifying details.</td>
</tr>
<tr>
<td>1910</td>
<td>16.1.50.C.02.</td>
<td>All Classifications</td>
<td>Should Not</td>
<td>Agencies SHOULD NOT permit the caching of credentials unless specifically required.</td>
</tr>
<tr>
<td>1946</td>
<td>16.3.5.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD:
ensure strong change management practices are implemented;
ensure that the use of privileged accounts is controlled and accountable;
ensure that system administrators are assigned an individual account for the performance of their administration tasks;
keep privileged accounts to a minimum; and
allow the use of privileged accounts for administrative work only.
</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>177</td>
<td>1.2.15.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies undertaking system design activities for in-house or out-sourced projects MUST use the latest version of th<span class="delete">is</span><span class="insert">e</span> <span class="delete">manual</span><span class="insert">NZISM</span> for information security requirements.</td>
</tr>
<tr>
<td>178</td>
<td>1.2.15.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>When GCSB makes a determination that newly introduced standard, policy or guideline within th<span class="delete">is manual</span><span class="insert">e NZISM</span>, or any additional information security policy, is of particular importance, agencies MUST comply with any new specified requirements and implementation timeframes.</td>
</tr>
<tr>
<td>199</td>
<td>2.1.47.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Security personnel <span class="insert">MU</span>S<span class="delete">HOULD</span><span class="insert">T</span> familiarise themselves with the information security roles and services provided by New Zealand Government organisations.</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.<span class="insert">,</span> key stores, passwords, root keys, signing keys, personal<span class="delete">ly identifiable</span> 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>781</td>
<td>5.2.3.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>The Information Security Policy (SecPol) SHOULD include topics such as:<span class="delete">
accreditation processes;
</span><span class="insert">accreditation processes;</span>personnel responsibilities;configuration control;<span class="delete">
access control;
</span><span class="insert">access control;</span>networking and connections with other systems;<span class="delete">
physical security and media control;
</span><span class="insert">physical security and media control;</span>emergency procedures and information security incident management;vulnerability disclosure;<span class="delete">
change management; and
</span><span class="insert">change management; and</span>information security awareness and training.</td>
</tr>
<tr>
<td>1048</td>
<td>6.1.9.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD review the components detailed in the table below. Agencies SHOULD also ensure that any adjustments and changes as a result of any vulnerability analysis are consistent with the vulnerability disclosure policy.ComponentReviewInformation security documentationThe SecPol, Systems Architecture, SRMPs, SSPs, SitePlan, SOPs, the VDP, the IRP, and any third party assurance reports.DispensationsPrior to the identified expiry date.Operating environmentWhen an identified threat emerges or changes, an agency gains or loses a function or the operation of functions are moved to a new physical environment.ProceduresAfter an information security incident or test exercise.<span class="delete">
System security
</span><span class="insert">System security</span>Items that could affect the security of the system on a regular basis.ThreatsChanges in threat environment and risk profile.NZISMChanges to baseline or other controls, any new controls and guidance.</td>
</tr>
<tr>
<td>1153</td>
<td>7.1.7.C.01.</td>
<td>Top Secret, Confidential, Secret</td>
<td>Must</td>
<td>Agencies MUST develop, implement and maintain tools and procedures covering the detection of potential information security incidents, incorporating:user awareness and training;counter-measures against malicious code, known attack methods and types;<span class="delete">
intrusion detection strategies;
</span><span class="insert">intrusion detection strategies;</span>data egress monitoring & control;<span class="delete">
access control anomalies;
audit analysis;
</span><span class="insert">access control anomalies;audit analysis;</span>system integrity checking; andvulnerability assessments.</td>
</tr>
<tr>
<td>1154</td>
<td>7.1.7.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD develop, implement and maintain tools and procedures covering the detection of potential information security incidents, incorporating:user awareness and training;counter-measures against malicious code, known attack methods and types;<span class="delete">
intrusion detection strategies;
</span><span class="insert">intrusion detection strategies;dynamic network defence (i.e. protective DNS and/or NGFW)</span>data egress monitoring & control;<span class="delete">
access control anomalies;
audit analysis;
</span><span class="insert">access control anomalies;audit analysis;</span>system integrity checking; andvulnerability assessments.</td>
</tr>
<tr>
<td>1216</td>
<td>7.2.20.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>The Agency ITSM, MUST report information security incidents categorised as:Critical;Serious; orincidents related to multi-agency or government systems;to the NCSC <span class="delete">(see also </span><span class="insert">as soon as possi</span>b<span class="delete">elo</span><span class="insert">le.A Report Form is provided on the NCSC </span>w<span class="delete">) as soon as possi</span><span class="insert">e</span>b<span class="delete">le.</span><span class="insert">site under Reporting an Incident atReport an incident and request support | National Cyber Security Centre</span></td>
</tr>
<tr>
<td>1220</td>
<td>7.2.20.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD report information security incidents categorised asLowto the NCSC.<span class="insert">AReport Form is provided on the NCSC website under Reporting an Incident atReport an incident and request support | National Cyber Security Centre</span></td>
</tr>
<tr>
<td>1271</td>
<td>7.3.7.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST implement procedures and processes to detect data spills<span class="insert"> or data breach</span>.</td>
</tr>
<tr>
<td>1274</td>
<td>7.3.7.C.03.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agency SOPs MUST include procedure for:all personnel with access to system<span class="insert">s;notification to the ITSM of any data spillage or breache</span>s; <span class="delete">
</span><span class="insert">and</span>notification to the ITSM of a<span class="delete">ny data spillage; and
notification to the ITSM of a</span>ccess to any data which they are not authorised to access.</td>
</tr>
<tr>
<td>1275</td>
<td>7.3.7.C.04.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST document procedures for dealing with data spills<span class="insert"> or data breaches</span> in their IRP.</td>
</tr>
<tr>
<td>1276</td>
<td>7.3.7.C.05.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST treat any data spill<span class="insert"> or data breach</span> as an information security incident and follow the IRP to deal with it.</td>
</tr>
<tr>
<td>1277</td>
<td>7.3.7.C.06.</td>
<td>All Classifications</td>
<td>Must</td>
<td>When a data spill<span class="insert"> or data breach</span> occurs agencies MUST report the details <span class="delete">of the data spill </span>to the<span class="insert"> Privacy Commissioner and</span> information owner<span class="insert"> in accordance with thePrivacy Act 2020</span>.</td>
</tr>
<tr>
<td>1285</td>
<td>7.3.8.C.03.</td>
<td>All Classifications</td>
<td>Should</td>
<td>When a data spill <span class="delete">involving classified information or contaminating</span><span class="insert">or data breach involving classified or sensitive information or contaminationof</span> classified systems occurs and systems cannot be segregated<span class="insert">,</span> or isolated agencies SHOULD immediately contact theNCSCfor further advice.</td>
</tr>
<tr>
<td>1290</td>
<td>7.3.9.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD follow the steps described below when malicious code is detected:isolate the infected system;decide whether to request assistance fromNCSC;if such assistance is requested and agreed to, delay any further action until advised byNCSC;<span class="delete">
scan all</span><span class="insert">check connected systems and media including backups for malicious code;isolate all infected systems and media to</span> prev<span class="delete">iously connected systems and any media used within a set period leadi</span><span class="insert">ent reinfection;cha</span>ng<span class="delete"> up to the information security incident</span><span class="insert">e all passwords and key material stored or potentially accessed from compromised systems</span>, <span class="delete">for malicious code</span><span class="insert">including any websites with password controlled access</span>;<span class="delete">
isolate all infected systems and media to pre</span><span class="insert">ad</span>v<span class="delete">ent reinfection</span><span class="insert">ise system users of any relevant aspects of the compromise, including a recommendation to change all passwords on compromised systems</span>;<span class="delete">
change all passwords and </span><span class="insert">revo</span>ke<span class="delete">y material stored or potentially accessed from compromised systems, including any websites with password controlled access</span><span class="insert"> all session tokens associated with user and/or device</span>;<span class="delete">
ad</span><span class="insert">use up-to-date anti-malware software to remo</span>v<span class="delete">ise system users of any rele</span><span class="insert">e the malware from the systems or media;monitor network traffic for malicious acti</span>v<span class="delete">ant aspects of the compromise, including a recommendation to change all passwords on compromised systems</span><span class="insert">ity</span>;<span class="delete">
use up-to-date anti-malware software to remove the malware from the systems or media;
monitor network traffic for malicious activity;
</span><span class="insert">record and </span>report the information security incident and perform any other activities specified in the IRP; and<span class="delete">
in the worst case scenario,</span><span class="insert">in certain scenarios</span> rebuild<span class="delete"> and reinitialise the system</span><span class="insert">ing and reinitialising the system and/or user profile may be required</span>.</td>
</tr>
<tr>
<td>1294</td>
<td>7.3.10.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies considering allowing an attacker to continue some actions under controlled conditions for the purpose of seeking further information or evidence <span class="insert">MU</span>S<span class="delete">HOULD </span><span class="insert">T</span>seek legal advice.</td>
</tr>
<tr>
<td>1403</td>
<td>8.4.10.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST ensure that when secure areas are non-operational or when work areas are unoccupied IT equipment with media is secured in accordance with the minimum physical security requirements for storing classified information as specified in thePSR Management protocol for physical security<span class="insert">with supporting document</span> –<span class="delete"> Physical </span>S<span class="delete">ecurity of your</span><span class="insert">torage requirements for electronic information in</span> ICT <span class="delete">assets and facilities, with supporting document – Storage requirements for electronic information in ICT </span>facilities.</td>
</tr>
<tr>
<td>1458</td>
<td>9.1.6.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD ensure that information security awareness and training includes information on:the purpose of the training or awareness program;any legislative or regulatory mandates and requirements;any national or agency policy mandates and requirements;<span class="delete">
agency security appointments and contacts;
</span><span class="insert">agency security appointments and contacts;</span>the legitimate use of system accounts, software and classified information;the security of accounts, including shared passwords;authorisation requirements for applications, databases and data;the security risks associated with non-agency systems, particularly the Internet;<span class="delete">
reporting any suspected compromises or anomalies;
</span><span class="insert">reporting any suspected compromises or anomalies;</span>reporting requirements for information security incidents, suspected compromises or anomalies;classifying, marking, controlling, storing and sanitising media;protecting workstations from unauthorised access;informing the support section when access to a system is no longer needed;observing rules and regulations governing the secure operation and authorised use of systems; andsupporting documentation such as SOPs and user guides.</td>
</tr>
<tr>
<td>1487</td>
<td>9.2.12.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD:maintain a secure record of:<span class="delete">
all authorised system users;
their user identification;
</span><span class="insert">all authorised system users;their user identification;</span>why access is required;role and privilege level,who provided the authorisation to access the system;<span class="delete">
when the authorisation was granted; and
</span><span class="insert">when the authorisation was granted; and</span>keep a copy of the acknowledgement signed by the individual granted a clearance; andmaintain the record, for the life of the system or information to which access is granted, or the length of employment, whichever is the longer.</td>
</tr>
<tr>
<td>1491</td>
<td>9.2.13.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>All system users MUST:hold a security clearance <span class="delete">at least </span><span class="insert">or other authorisation appropriate for the system classification; orhave been granted access in accordance with the r</span>equ<span class="delete">al to the system classification; or
have been granted access in accordance with the requirements in the </span><span class="insert">irements in the</span>PSRfor emergency access.</td>
</tr>
<tr>
<td>1505</td>
<td>9.2.17.C.02.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies granting<span class="delete"> limited </span><span class="insert">limited</span>higher access to information or systems MUST ensure that:the requirement to grant limited higher access is temporary in nature and is an exception rather than the norm;an ITSM has recommended the limited higher access;a cessation date for limited higher access has been set;the access period does not exceed two months;the limited higher access is granted on an occasional NOT non-ongoing basis;the system user is not granted privileged access to the system;the system user’s access is formally documented; andthe system user’s access is approved by the CISO.</td>
</tr>
<tr>
<td>1508</td>
<td>9.2.18.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies granting<span class="delete"> limited </span><span class="insert">limited</span>higher access to a system MUST ensure that:the approval for access is formally acknowledged and recorded; and eithereffective controls are in place to restrict access<span class="delete"> only </span><span class="insert">only</span>to classified information that is necessary to undertake the system user’s duties; orthe system user is continually supervised by another system user who has the appropriate security clearances to access the system.</td>
</tr>
<tr>
<td>2230</td>
<td>10.1.45.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST comply with the cable and conduit colours specified in the following table.<span class="delete">
Classification
</span><span class="insert">Classification</span>Cable colourCompartmented Information (SCI)Orange/Yellow/Teal or other colourTOP SECRET<span class="delete">
Red
SECRET
</span><span class="insert">RedSECRET</span>BlueCONFIDENTIALGreenRESTRICTED and all lower classificationsBlack</td>
</tr>
<tr>
<td>2241</td>
<td>10.1.47.C.02.</td>
<td>All Classifications</td>
<td>Must Not</td>
<td>Agencies MUST NOT deviate from the approved fibre cable combinations for shared conduits and reticulation systems as indicated below.GroupApproved combination1UNCLASSIFIEDRESTRICTED2CONFIDENTIAL<span class="delete">
SECRET
</span><span class="insert">SECRET</span>3TOP SECRETOther Special Networks</td>
</tr>
<tr>
<td>2387</td>
<td>10.5.4.C.01.</td>
<td>All Classifications</td>