-
Notifications
You must be signed in to change notification settings - Fork 0
/
NZISM-3.3-to-3.4.html
347 lines (304 loc) · 13.2 KB
/
NZISM-3.3-to-3.4.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
<!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.3-February 2020.xml</strong> and <strong>nzism-data/NZISM-FullDoc-V.3.4-September 2020.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>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>
</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>
</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>6019</td>
<td>15.2.22.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Before implementing DMARC agencies SHOULD:
Create a DMARC policy;
List all domains<span class="delete"> </span><span class="insert">, in partic</span>u<span class="delete">sed for the sending</span><span class="insert">lar those used for the sending and/or receiving of</span> email;
Review the configuration of SPF and DKIM for all active domains<span class="insert"> and all published domains</span>; and
Establish one or more monitored inboxes to receive <span class="insert">DMARC </span>reports.
</td>
</tr>
<tr>
<td>6020</td>
<td>15.2.22.C.02.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD enable DMARC for all email originating from or received by their domain(s), including:
sending domain owners SHOULD publish a DMARC record <span class="insert">with a related DNS entry </span>advising mail receivers<span class="insert"> of</span> the characteristics of messages purporting to originate from the sender’s domain;
received<span class="insert"> DMARC</span> messages SHOULD be managed in accordance with the agency’s published DMARC policy; and
agencies SHOULD produce failure reports and aggregate reports according to the agency’s DMARC policies.
</td>
</tr>
<tr>
<td>1827</td>
<td>16.1.31.C.01.</td>
<td>All Classifications</td>
<td>Must</td>
<td>Agencies MUST:
develop<span class="insert">, implement</span> and maintain a set of policies and procedures covering<span class="insert"> all</span> system users’:
identification;
authentication;
authorisation;<span class="insert">
privileged access identification and management;</span> and
make their system users aware of the agency’s policies and procedures.
</td>
</tr>
<tr>
<td>2598</td>
<td>17.4.16.C.01.</td>
<td>All Classifications</td>
<td>Should</td>
<td>Agencies SHOULD use the current version of TLS (version 1.<span class="delete">2</span><span class="insert">3</span>).</td>
</tr>
<tr>
<td>4675</td>
<td>21.4.11.C.20.</td>
<td>All Classifications</td>
<td>Should</td>
<td>BYOD devices and systems SHOULD use Multi<span class="insert">-</span>factor (at least two-factor) authentication to connect to agency systems and prior to being permitted access to agency data.</td>
</tr>
</tbody>
</table>
</section>
<body>
</html>