-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathCSW-APRA-CPS234-Technical-Runbook.html
More file actions
1201 lines (1195 loc) · 38 KB
/
Copy pathCSW-APRA-CPS234-Technical-Runbook.html
File metadata and controls
1201 lines (1195 loc) · 38 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 xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>APRA CPS 234 — Technical Runbook</title>
<style>
html {
color: #1a1a1a;
background-color: #fdfdfd;
}
body {
margin: 0 auto;
max-width: 36em;
padding-left: 50px;
padding-right: 50px;
padding-top: 50px;
padding-bottom: 50px;
hyphens: auto;
overflow-wrap: break-word;
text-rendering: optimizeLegibility;
font-kerning: normal;
}
@media (max-width: 600px) {
body {
font-size: 0.9em;
padding: 12px;
}
h1 {
font-size: 1.8em;
}
}
@media print {
html {
background-color: white;
}
body {
background-color: transparent;
color: black;
font-size: 12pt;
}
p, h2, h3 {
orphans: 3;
widows: 3;
}
h2, h3, h4 {
page-break-after: avoid;
}
}
p {
margin: 1em 0;
}
a {
color: #1a1a1a;
}
a:visited {
color: #1a1a1a;
}
img {
max-width: 100%;
}
svg {
height: auto;
max-width: 100%;
}
h1, h2, h3, h4, h5, h6 {
margin-top: 1.4em;
}
h5, h6 {
font-size: 1em;
font-style: italic;
}
h6 {
font-weight: normal;
}
ol, ul {
padding-left: 1.7em;
margin-top: 1em;
}
li > ol, li > ul {
margin-top: 0;
}
blockquote {
margin: 1em 0 1em 1.7em;
padding-left: 1em;
border-left: 2px solid #e6e6e6;
color: #606060;
}
code {
white-space: pre-wrap;
font-family: Menlo, Monaco, Consolas, 'Lucida Console', monospace;
font-size: 85%;
margin: 0;
hyphens: manual;
}
pre {
margin: 1em 0;
overflow: auto;
}
pre code {
padding: 0;
overflow: visible;
overflow-wrap: normal;
}
.sourceCode {
background-color: transparent;
overflow: visible;
}
hr {
border: none;
border-top: 1px solid #1a1a1a;
height: 1px;
margin: 1em 0;
}
table {
margin: 1em 0;
border-collapse: collapse;
width: 100%;
overflow-x: auto;
display: block;
font-variant-numeric: lining-nums tabular-nums;
}
table caption {
margin-bottom: 0.75em;
}
tbody {
margin-top: 0.5em;
border-top: 1px solid #1a1a1a;
border-bottom: 1px solid #1a1a1a;
}
th {
border-top: 1px solid #1a1a1a;
padding: 0.25em 0.5em 0.25em 0.5em;
}
td {
padding: 0.125em 0.5em 0.25em 0.5em;
}
header {
margin-bottom: 4em;
text-align: center;
}
#TOC li {
list-style: none;
}
#TOC ul {
padding-left: 1.3em;
}
#TOC > ul {
padding-left: 0;
}
#TOC a:not(:hover) {
text-decoration: none;
}
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: min(4vw, 1.5em);}
div.column{flex: auto; overflow-x: auto;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list[class]{list-style: none;}
ul.task-list li input[type="checkbox"] {
font-size: inherit;
width: 0.8em;
margin: 0 0.8em 0.2em -1.6em;
vertical-align: middle;
}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<style>
:root {
--fg: #1f2328;
--fg-muted: #59636e;
--bg: #ffffff;
--bg-muted: #f6f8fa;
--border: #d1d9e0;
--link: #0969da;
--link-hover: #0349b4;
--code-bg: #f6f8fa;
--accent: #cf222e;
--max-width: 920px;
}
@media (prefers-color-scheme: dark) {
:root {
--fg: #e6edf3;
--fg-muted: #9198a1;
--bg: #0d1117;
--bg-muted: #151b23;
--border: #3d444d;
--link: #4493f8;
--link-hover: #6cb6ff;
--code-bg: #151b23;
--accent: #ff7b72;
}
}
* { box-sizing: border-box; }
html { -webkit-text-size-adjust: 100%; }
body {
margin: 0 auto;
max-width: var(--max-width);
padding: 2rem 1.25rem 4rem;
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "Helvetica Neue",
Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";
font-size: 16px;
line-height: 1.6;
color: var(--fg);
background: var(--bg);
}
h1, h2, h3, h4, h5, h6 {
margin-top: 2rem;
margin-bottom: 1rem;
font-weight: 600;
line-height: 1.25;
}
h1 { font-size: 2rem; border-bottom: 1px solid var(--border); padding-bottom: .35rem; }
h2 { font-size: 1.5rem; border-bottom: 1px solid var(--border); padding-bottom: .3rem; }
h3 { font-size: 1.25rem; }
h4 { font-size: 1rem; }
h5, h6 { font-size: .875rem; color: var(--fg-muted); }
p, ul, ol, blockquote, pre, table { margin: 0 0 1rem; }
a { color: var(--link); text-decoration: none; }
a:hover { color: var(--link-hover); text-decoration: underline; }
ul, ol { padding-left: 1.6rem; }
li + li { margin-top: .15rem; }
blockquote {
margin: 0 0 1rem;
padding: .5rem 1rem;
color: var(--fg-muted);
border-left: .25rem solid var(--border);
background: var(--bg-muted);
border-radius: 0 6px 6px 0;
}
code, pre, kbd, samp {
font-family: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, monospace;
font-size: .9em;
}
code {
background: var(--code-bg);
padding: .15rem .35rem;
border-radius: 4px;
}
pre {
background: var(--code-bg);
padding: 1rem;
border-radius: 6px;
overflow: auto;
font-size: .85rem;
line-height: 1.45;
}
pre code { background: transparent; padding: 0; font-size: inherit; }
table {
display: block;
width: 100%;
overflow: auto;
border-collapse: collapse;
}
th, td {
border: 1px solid var(--border);
padding: .5rem .75rem;
vertical-align: top;
text-align: left;
}
th {
background: var(--bg-muted);
font-weight: 600;
}
tbody tr:nth-child(2n) { background: var(--bg-muted); }
hr {
border: 0;
height: 1px;
background: var(--border);
margin: 2rem 0;
}
img { max-width: 100%; height: auto; }
.doc-meta {
margin: 0 0 2rem;
padding: .75rem 1rem;
border: 1px solid var(--border);
border-radius: 6px;
background: var(--bg-muted);
font-size: .9rem;
color: var(--fg-muted);
}
.doc-meta a { font-weight: 500; }
@media print {
body { max-width: none; padding: 0; color: #000; background: #fff; }
a { color: #000; text-decoration: underline; }
pre, code, blockquote { background: #f5f5f5; }
}
</style>
</head>
<body>
<div class="doc-meta">Source: <a href="CSW-APRA-CPS234-Technical-Runbook.html">CSW-APRA-CPS234-Technical-Runbook.md</a> · <a href="../index.html">repository index</a> · Build: 2026-08-11T04:20:48Z UTC · Repository commit: 463f586</div>
<header id="title-block-header">
<h1 class="title">APRA CPS 234 — Technical Runbook</h1>
</header>
<nav id="TOC" role="doc-toc">
<ul>
<li><a href="#cisco-secure-workload-apra-cps-234" id="toc-cisco-secure-workload-apra-cps-234">Cisco Secure Workload — APRA
CPS 234</a>
<ul>
<li><a href="#technical-runbook-australian-apra-regulated-entities" id="toc-technical-runbook-australian-apra-regulated-entities">Technical
Runbook | Australian APRA-Regulated Entities</a></li>
<li><a href="#readers-guide" id="toc-readers-guide">Reader’s
Guide</a></li>
<li><a href="#csw-primer-if-you-are-new-to-cisco-secure-workload" id="toc-csw-primer-if-you-are-new-to-cisco-secure-workload">CSW primer —
if you are new to Cisco Secure Workload</a></li>
<li><a href="#universal-evidence-workflow" id="toc-universal-evidence-workflow">Universal evidence workflow</a>
<ul>
<li><a href="#phase-1-checklist-coverage" id="toc-phase-1-checklist-coverage">Phase 1 checklist
(coverage)</a></li>
<li><a href="#phase-2-checklist-baseline" id="toc-phase-2-checklist-baseline">Phase 2 checklist
(baseline)</a></li>
<li><a href="#phase-3-checklist-policy" id="toc-phase-3-checklist-policy">Phase 3 checklist (policy)</a></li>
<li><a href="#phase-4-checklist-operate" id="toc-phase-4-checklist-operate">Phase 4 checklist (operate)</a></li>
<li><a href="#what-csw-evidence-does-not-replace" id="toc-what-csw-evidence-does-not-replace">What CSW evidence does not
replace</a></li>
</ul></li>
<li><a href="#csw-effectiveness-for-this-framework" id="toc-csw-effectiveness-for-this-framework">CSW effectiveness for this
framework</a></li>
<li><a href="#overview" id="toc-overview">1. Overview</a>
<ul>
<li><a href="#cps-234-paragraph-map-and-csw-relevance" id="toc-cps-234-paragraph-map-and-csw-relevance">CPS 234 Paragraph Map
and CSW Relevance</a></li>
</ul></li>
<li><a href="#pre-deployment-checklist" id="toc-pre-deployment-checklist">2. Pre-Deployment Checklist</a></li>
<li><a href="#phase-1-sensor-connector-deployment-days-15" id="toc-phase-1-sensor-connector-deployment-days-15">3. Phase 1 — Sensor
& Connector Deployment (Days 1–5)</a></li>
<li><a href="#phase-2-scope-inventory-and-information-asset-classification-days-610" id="toc-phase-2-scope-inventory-and-information-asset-classification-days-610">4.
Phase 2 — Scope, Inventory, and Information Asset Classification (Days
6–10)</a>
<ul>
<li><a href="#suggested-scope-architecture" id="toc-suggested-scope-architecture">4.1 Suggested Scope
Architecture</a></li>
<li><a href="#inventory-filters" id="toc-inventory-filters">4.2
Inventory Filters</a></li>
<li><a href="#labeling-strategy" id="toc-labeling-strategy">4.3 Labeling
Strategy</a></li>
</ul></li>
<li><a href="#phase-3-application-dependency-mapping-days-1121" id="toc-phase-3-application-dependency-mapping-days-1121">5. Phase 3 —
Application Dependency Mapping (Days 11–21)</a>
<ul>
<li><a href="#adm-configuration" id="toc-adm-configuration">5.1 ADM
Configuration</a></li>
<li><a href="#adm-analysis-for-cps-234" id="toc-adm-analysis-for-cps-234">5.2 ADM Analysis for CPS 234</a></li>
<li><a href="#classification-and-re-scoping" id="toc-classification-and-re-scoping">5.3 Classification and
Re-Scoping</a></li>
</ul></li>
<li><a href="#phase-4-policy-development-days-2235" id="toc-phase-4-policy-development-days-2235">6. Phase 4 — Policy
Development (Days 22–35)</a>
<ul>
<li><a href="#cps-234-aligned-policy-framework" id="toc-cps-234-aligned-policy-framework">6.1 CPS-234-Aligned Policy
Framework</a></li>
<li><a href="#policy-workspace-lifecycle" id="toc-policy-workspace-lifecycle">6.2 Policy Workspace
Lifecycle</a></li>
</ul></li>
<li><a href="#phase-5-paragraph-mapping-with-csw-evidence" id="toc-phase-5-paragraph-mapping-with-csw-evidence">7. Phase 5 —
Paragraph Mapping with CSW Evidence</a></li>
<li><a href="#phase-6-vulnerability-risk-management" id="toc-phase-6-vulnerability-risk-management">8. Phase 6 —
Vulnerability & Risk Management</a></li>
<li><a href="#phase-7-monitoring-alerting" id="toc-phase-7-monitoring-alerting">9. Phase 7 — Monitoring &
Alerting</a>
<ul>
<li><a href="#forensic-telemetry" id="toc-forensic-telemetry">9.2
Forensic Telemetry</a></li>
</ul></li>
<li><a href="#reporting-evidence-collection" id="toc-reporting-evidence-collection">10. Reporting & Evidence
Collection</a>
<ul>
<li><a href="#evidence-per-audit-assurance-cycle-quarterly-recommended" id="toc-evidence-per-audit-assurance-cycle-quarterly-recommended">10.1
Evidence per Audit / Assurance Cycle (quarterly recommended)</a></li>
<li><a href="#ongoing-compliance-posture" id="toc-ongoing-compliance-posture">10.2 Ongoing Compliance
Posture</a></li>
</ul></li>
<li><a href="#common-pitfalls" id="toc-common-pitfalls">11. Common
Pitfalls</a></li>
<li><a href="#related-frameworks-in-this-repository" id="toc-related-frameworks-in-this-repository">Related Frameworks in
This Repository</a></li>
</ul></li>
</ul>
</nav>
<h1 id="cisco-secure-workload-apra-cps-234">Cisco Secure Workload — APRA
CPS 234</h1>
<h2 id="technical-runbook-australian-apra-regulated-entities">Technical
Runbook | Australian APRA-Regulated Entities</h2>
<p><strong>Version:</strong> 1.0<br />
<strong>Framework:</strong> APRA Prudential Standard CPS 234 —
Information Security (effective 1 July 2019)<br />
<strong>Use Case:</strong> Information asset segmentation, control
implementation evidence, control testing inputs, incident management,
third-party service-provider visibility</p>
<blockquote>
<p><strong>Framework version note.</strong> This runbook references CPS
234 as published in 2019. CPS 234 paragraph numbers are stable; APRA
also operates additional related standards (e.g. CPS 230 — Operational
Risk Management) which are not addressed here. Validate against APRA’s
published version before use in a supervisory or assurance
engagement.</p>
<p><strong>CSW UI navigation note.</strong> Cisco has not yet published
CPS 234-specific CSW UI navigation; framework-specific paths are on the
product roadmap. This runbook describes CSW <em>capabilities</em> and
the <em>evidence artifacts</em> they produce.</p>
</blockquote>
<hr />
<h2 id="readers-guide">Reader’s Guide</h2>
<p><strong>Who this is for.</strong> Australian banks, insurers,
superannuation trustees, and other APRA-regulated entities; their CISO
function, technology risk and information security teams, internal
audit, and the business owners who must attest to information asset
control effectiveness under CPS 234.</p>
<p><strong>Questions this runbook helps you answer:</strong></p>
<ul>
<li><em>Are information assets classified, and can I evidence which
workloads support material business operations?</em> (Para. 20)</li>
<li><em>Are information security controls implemented in a manner
commensurate with the assessed information security vulnerabilities and
threats?</em> (Para. 21–23)</li>
<li><em>Can I produce control-testing evidence (Para. 29–33) from
continuous workload telemetry rather than point-in-time
samples?</em></li>
<li><em>If a material information security incident occurs, can I
rebuild the workload-level timeline needed for Para. 24–28 incident
management and Para. 36–37 APRA notification scoping?</em></li>
<li><em>Can I identify communication paths to third-party service
providers that handle material information assets?</em> (Para. 21–23 in
conjunction with related-party arrangements)</li>
</ul>
<p><strong>What you’ll need.</strong> Information asset register,
business operations criticality classification, supplier / related-party
register, CMDB or cloud inventory, vulnerability management process,
incident response runbook, internal audit plan, and application owner
contacts.</p>
<p><strong>Where to start.</strong> Sections 1–4 if you are scoping; 5–7
if you are designing and simulating policy; 9–10 if you are preparing
for internal audit, external assurance, or APRA tripartite review within
the quarter.</p>
<hr />
<!-- CSW-RUNBOOK-PRIMER:v1 -->
<h2 id="csw-primer-if-you-are-new-to-cisco-secure-workload">CSW primer —
if you are new to Cisco Secure Workload</h2>
<p>Cisco Secure Workload (CSW) is a <strong>workload protection
platform</strong>. A lightweight <strong>agent</strong> on each
server/VM/container observes processes and network flows; <strong>cloud
connectors</strong> add AWS/Azure/GCP inventory where agents are not
deployed.</p>
<table>
<colgroup>
<col style="width: 21%" />
<col style="width: 19%" />
<col style="width: 58%" />
</colgroup>
<thead>
<tr>
<th>CSW term</th>
<th>Meaning</th>
<th>Why compliance teams care</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Scope</strong></td>
<td>Logical boundary (CDE, PHI zone, CUI enclave)</td>
<td>Defines the systems you must prove are isolated</td>
</tr>
<tr>
<td><strong>Label / filter</strong></td>
<td>Tag or query assigning workloads to scopes</td>
<td>Automates scope membership — reduces drift</td>
</tr>
<tr>
<td><strong>ADM</strong></td>
<td>Application Dependency Mapping from observed traffic</td>
<td><strong>Live</strong> network/data-flow diagram for assessors</td>
</tr>
<tr>
<td><strong>Workspace</strong></td>
<td>Policy container for one scope or application</td>
<td>Where allow/deny rules are authored</td>
</tr>
<tr>
<td><strong>Monitor → Simulation → Enforce</strong></td>
<td>Safe rollout sequence</td>
<td>Simulation = change-board evidence before blocking traffic</td>
</tr>
<tr>
<td><strong>Denied Connections</strong></td>
<td>Log of flows blocked by policy</td>
<td>Primary proof that enforcement <strong>operates</strong></td>
</tr>
</tbody>
</table>
<p><strong>Console areas:</strong> Investigate (inventory, flows, vulns)
· Defend/Segmentation (policy) · Manage (agents) · Platform (connectors)
· Administration (audit log)</p>
<p><strong>Read next:</strong> <a href="../docs/compliance-evidence-playbook.html">Compliance evidence
playbook</a> (full step-by-step) · <a href="../docs/about-csw.html">About
CSW</a> (platform intro)</p>
<hr />
<h2 id="universal-evidence-workflow">Universal evidence workflow</h2>
<p>Execute these phases for <strong>this framework’s</strong> compliance
boundary. Map exports to control IDs in the <strong>Reporting &
Evidence</strong> section below.</p>
<table>
<colgroup>
<col style="width: 14%" />
<col style="width: 12%" />
<col style="width: 35%" />
<col style="width: 37%" />
</colgroup>
<thead>
<tr>
<th>Phase</th>
<th>Goal</th>
<th>Key CSW actions</th>
<th>Typical duration</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>1 — Coverage</strong></td>
<td>Every in-scope workload in CSW</td>
<td>Install agents/connectors; apply compliance labels; create
scope</td>
<td>Days 1–10</td>
</tr>
<tr>
<td><strong>2 — Baseline</strong></td>
<td>Machine-generated flow map</td>
<td>Run ADM ≥2 weeks; export clusters; app-owner signoff</td>
<td>Days 11–28</td>
</tr>
<tr>
<td><strong>3 — Policy</strong></td>
<td>Designed isolation before enforce</td>
<td>Build workspace; Simulation mode; fix false positives</td>
<td>Days 29–45</td>
</tr>
<tr>
<td><strong>4 — Operate</strong></td>
<td>Continuous proof between audits</td>
<td>Enforce; quarterly export pack; ADM refresh every 90 days</td>
<td>Ongoing</td>
</tr>
</tbody>
</table>
<h3 id="phase-1-checklist-coverage">Phase 1 checklist (coverage)</h3>
<ul class="task-list">
<li><label><input type="checkbox"></input>In-scope host list reconciled to CSW
Inventory (100% or documented exceptions)</label></li>
<li><label><input type="checkbox"></input>Labels applied:
<code>compliance:<framework></code>,
<code>data:<classification></code>,
<code>env:<tier></code></label></li>
<li><label><input type="checkbox"></input>CSW scope created matching
compliance boundary</label></li>
<li><label><input type="checkbox"></input><strong>Export:</strong> inventory
CSV + agent status screenshot</label></li>
</ul>
<h3 id="phase-2-checklist-baseline">Phase 2 checklist (baseline)</h3>
<ul class="task-list">
<li><label><input type="checkbox"></input>ADM running on compliance scope for
full business cycle (≥2 weeks)</label></li>
<li><label><input type="checkbox"></input>Unexpected flows documented (shadow
IT, vendor egress, scope creep)</label></li>
<li><label><input type="checkbox"></input>App owners signed
cluster-to-application mapping</label></li>
<li><label><input type="checkbox"></input><strong>Export:</strong> ADM diagram
+ flow samples with process context</label></li>
</ul>
<h3 id="phase-3-checklist-policy">Phase 3 checklist (policy)</h3>
<ul class="task-list">
<li><label><input type="checkbox"></input>Default-deny posture defined for
sensitive scope</label></li>
<li><label><input type="checkbox"></input>ADM-imported rules refined;
Simulation run ≥1 week</label></li>
<li><label><input type="checkbox"></input>Change tickets for false-positive
fixes; exception register updated</label></li>
<li><label><input type="checkbox"></input><strong>Export:</strong> policy
export + simulation report</label></li>
</ul>
<h3 id="phase-4-checklist-operate">Phase 4 checklist (operate)</h3>
<ul class="task-list">
<li><label><input type="checkbox"></input>Enforcement enabled on pilot scope;
negative test recorded in Denied Connections</label></li>
<li><label><input type="checkbox"></input>Quarterly pack: inventory, policy,
denies, vulns, audit log (see playbook)</label></li>
<li><label><input type="checkbox"></input>SIEM integration verified (sample
events)</label></li>
<li><label><input type="checkbox"></input><strong>Export:</strong> enforcement
screenshot + quarterly binder</label></li>
</ul>
<h3 id="what-csw-evidence-does-not-replace">What CSW evidence does not
replace</h3>
<p>Physical access, HR/training records, encryption key management,
signed BAAs/vendor contracts, formal pen tests, and assessor attestation
still require separate programmes. CSW addresses the
<strong>workload-resident</strong> slice: segmentation, flows, process
context, vuln reachability, and change drift.</p>
<hr />
<h2 id="csw-effectiveness-for-this-framework">CSW effectiveness for this
framework</h2>
<ul>
<li>Critical information asset visibility</li>
<li>Control testing evidence from simulation/enforce cadence</li>
<li>Service-provider dependency flows</li>
</ul>
<p><strong>Compared to manual programmes:</strong> static diagrams and
annual firewall samples age immediately; CSW ties evidence to
<strong>live workload behaviour</strong> and produces queryable exports
on demand — supporting “operating effectively” language in PCI v4.0, SOC
2 CC7, and HIPAA risk analysis.</p>
<hr />
<h2 id="overview">1. Overview</h2>
<p>CPS 234 is an outcome-based prudential standard. Its core obligations
are: classify information assets by criticality and sensitivity (Para.
20), implement controls commensurate with the assessed threat (Para.
21–23), notify APRA of material information security control weaknesses
and incidents (Para. 36–37), and systematically test the effectiveness
of controls (Para. 29–33).</p>
<p>CSW can support <strong>technical evidence</strong> for the
technology-control-effectiveness, information-asset-classification,
network-segmentation, vulnerability-context, and incident-scoping
dimensions of CPS 234. CSW does <strong>not</strong> replace board
accountability for information security (Para. 13–14), the policy
framework (Para. 16–19), the related-party assurance process, IAM/PAM,
cryptography, BCP/DR, or APRA notification decisions.</p>
<h3 id="cps-234-paragraph-map-and-csw-relevance">CPS 234 Paragraph Map
and CSW Relevance</h3>
<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />
<col style="width: 33%" />
</colgroup>
<thead>
<tr>
<th>CPS 234 paragraph</th>
<th>Topic</th>
<th>CSW relevance</th>
</tr>
</thead>
<tbody>
<tr>
<td>13–15</td>
<td>Information security capability</td>
<td>Out of scope for CSW evidence directly; CSW outputs feed capability
reporting</td>
</tr>
<tr>
<td>16–19</td>
<td>Policy framework</td>
<td>Out of scope (governance artefact)</td>
</tr>
<tr>
<td>20</td>
<td>Information asset identification and classification</td>
<td>Workload inventory; scope and label evidence; reachability
mapping</td>
</tr>
<tr>
<td>21–23</td>
<td>Implementation of controls</td>
<td>Workload-level segmentation; ADM-derived allowlists; policy
workspace</td>
</tr>
<tr>
<td>24–28</td>
<td>Incident management</td>
<td>Flow + process telemetry; forensic timeline; impact-scoping
evidence</td>
</tr>
<tr>
<td>29–33</td>
<td>Testing of control effectiveness</td>
<td>Continuous flow + policy data; drift detection; policy-violation
samples</td>
</tr>
<tr>
<td>34–35</td>
<td>Internal audit</td>
<td>Periodic evidence packs (Section 10)</td>
</tr>
<tr>
<td>36–37</td>
<td>APRA notification</td>
<td>Incident scoping inputs only; the notification decision is
governance</td>
</tr>
</tbody>
</table>
<p>Topics <strong>out of scope</strong> for CSW evidence: board
oversight, policy framework, related-party contractual arrangements, IAM
lifecycle, cryptography assurance, BCP/DR test outcomes, and APRA
reporting decisions.</p>
<hr />
<h2 id="pre-deployment-checklist">2. Pre-Deployment Checklist</h2>
<ul class="task-list">
<li><label><input type="checkbox"></input>CSW cluster (SaaS or on-prem)
provisioned</label></li>
<li><label><input type="checkbox"></input>Network reachability from in-scope
workloads to the CSW cluster confirmed</label></li>
<li><label><input type="checkbox"></input>Linux / Windows agent compatibility
verified across representative critical workloads</label></li>
<li><label><input type="checkbox"></input>Cloud accounts (AWS / Azure / GCP)
connected for any in-scope cloud workloads</label></li>
<li><label><input type="checkbox"></input>Information asset register reviewed;
“material” asset classification confirmed</label></li>
<li><label><input type="checkbox"></input>Stakeholders identified: CISO,
Information Security Manager, Information Asset Owners, Internal Audit
lead</label></li>
<li><label><input type="checkbox"></input>Change management window
approved</label></li>
<li><label><input type="checkbox"></input>Evidence retention agreed with
internal audit and the assurance partner</label></li>
</ul>
<hr />
<h2 id="phase-1-sensor-connector-deployment-days-15">3. Phase 1 — Sensor
& Connector Deployment (Days 1–5)</h2>
<p>Deploy CSW telemetry sources in monitoring mode only.</p>
<ul>
<li>Install software sensors on representative workloads supporting
material information assets</li>
<li>Connect cloud accounts as read-only CSW cloud connectors where
in-scope workloads run in cloud</li>
<li>Apply Day-1 labels: <code>application</code>, <code>env</code>,
<code>data_class</code>, <code>asset_criticality</code>,
<code>owner</code>, <code>compliance=cps234</code></li>
<li>Document any workloads that cannot be instrumented (managed SaaS,
certain appliances) in a <code>cannot-instrument</code> register; this
register is evidence in its own right</li>
</ul>
<p><strong>Sensor validation evidence:</strong> sensor inventory with
status, version, last-checkin timestamp — retained as the Phase 1
baseline for control-testing comparisons later.</p>
<hr />
<h2 id="phase-2-scope-inventory-and-information-asset-classification-days-610">4.
Phase 2 — Scope, Inventory, and Information Asset Classification (Days
6–10)</h2>
<p>CPS 234 Para. 20 obliges entities to classify information assets by
criticality and sensitivity. The CSW scope architecture should mirror
that classification, not duplicate it.</p>
<h3 id="suggested-scope-architecture">4.1 Suggested Scope
Architecture</h3>
<pre><code>Root Scope
└── CPS-234
├── Critical-Information-Assets
│ ├── Customer-Records
│ ├── Payments-and-Ledger
│ ├── Trading-Settlement
│ └── Policy-and-Claims
├── Material-Operations
│ ├── Online-Channels
│ └── Operational-Core
├── Service-Providers
│ └── Outsourced-Connectivity
└── Incident-Evidence</code></pre>
<h3 id="inventory-filters">4.2 Inventory Filters</h3>
<pre><code>Filter: Customer-Records-Candidates
- Tag (from asset register): data_class = customer
- Listening process: mysqld, postgres, oracle, sqlserver, mongod
- Listening port: 1521, 3306, 5432, 1433, 27017
Filter: Service-Provider-Edges
- Destination outside on-prem and cloud allow-lists
- Tag: managed_by = vendor
Filter: Operational-Core-Candidates
- Tag: asset_criticality = critical</code></pre>
<h3 id="labeling-strategy">4.3 Labeling Strategy</h3>
<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />
<col style="width: 33%" />
</colgroup>
<thead>
<tr>
<th>Label key</th>
<th>Example values</th>
<th>Why it matters for CPS 234</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>asset_criticality</code></td>
<td>critical, material, supporting</td>
<td>Maps to Para. 20 classification</td>
</tr>
<tr>
<td><code>data_class</code></td>
<td>customer, internal, public</td>
<td>Sensitivity dimension of Para. 20</td>
</tr>
<tr>
<td><code>application</code></td>
<td><named application></td>
<td>Connects workload to information asset</td>
</tr>
<tr>
<td><code>env</code></td>
<td>production, uat, dev</td>
<td>Required for environment segregation evidence</td>
</tr>
<tr>
<td><code>owner</code></td>
<td><named function></td>
<td>Accountability under Para. 14</td>
</tr>
<tr>
<td><code>compliance</code></td>
<td>cps234</td>
<td>Filters CSW evidence to the CPS 234 scope</td>
</tr>
</tbody>
</table>
<hr />
<h2 id="phase-3-application-dependency-mapping-days-1121">5. Phase 3 —
Application Dependency Mapping (Days 11–21)</h2>
<h3 id="adm-configuration">5.1 ADM Configuration</h3>
<p>For each scope in 4.1, create an ADM workspace; run across a
representative business window that covers month-end and any quarterly
reporting cycles. Minimum 2 weeks.</p>
<h3 id="adm-analysis-for-cps-234">5.2 ADM Analysis for CPS 234</h3>
<p>For each cluster, document:</p>
<table>
<colgroup>
<col style="width: 50%" />
<col style="width: 50%" />
</colgroup>
<thead>
<tr>
<th>Question</th>
<th>CPS 234 paragraph</th>
</tr>
</thead>
<tbody>
<tr>
<td>Which workloads receive connections from outside the
Critical-Information-Assets scope?</td>
<td>21–23</td>
</tr>
<tr>
<td>Are database connections encrypted?</td>
<td>21–23 (controls commensurate with threat)</td>
</tr>
<tr>
<td>Which workloads reach Service-Providers?</td>
<td>21–23 (third-party paths)</td>
</tr>
<tr>
<td>Are there unexpected lateral connections within
Material-Operations?</td>
<td>24–28 (early indicator for incidents)</td>
</tr>
<tr>
<td>Which workloads are reached by administrative paths?</td>
<td>21–23 (privileged access surface)</td>
</tr>
</tbody>
</table>
<h3 id="classification-and-re-scoping">5.3 Classification and
Re-Scoping</h3>
<ol type="1">
<li>Export ADM clusters and review with information asset owners.</li>
<li>Confirm classification (<code>asset_criticality</code>,
<code>data_class</code>) for each cluster.</li>
<li>Apply or correct labels.</li>
<li>Move workloads into the correct scope.</li>
<li>Re-run ADM to produce the candidate policy.</li>
</ol>
<hr />
<h2 id="phase-4-policy-development-days-2235">6. Phase 4 — Policy
Development (Days 22–35)</h2>
<h3 id="cps-234-aligned-policy-framework">6.1 CPS-234-Aligned Policy
Framework</h3>
<p><strong>Absolute policies:</strong></p>
<pre><code>DENY Any → Critical-Information-Assets (default deny inbound)
DENY Critical-Information-Assets → Internet (no direct internet egress)
DENY Corporate-IT → Critical-Information-Assets (admin only via approved jump paths)</code></pre>
<p><strong>Allowlist policies (examples to adapt per
application):</strong></p>
<pre><code>ALLOW Channel-Layer → Payments-and-Ledger tcp/443
ALLOW Payments-and-Ledger → Customer-Records-DB tcp/<db-port-tls>
ALLOW Material-Operations → Identity-Adjacent tcp/636, tcp/88
ALLOW Jump-Hosts → Critical-Information-Assets tcp/22, tcp/3389
ALLOW Critical-Information-Assets → Monitoring-Stack tcp/443</code></pre>
<p><strong>Catch-all (audit everything else):</strong></p>
<pre><code>LOG Any → Critical-Information-Assets (unmatched flows trigger alert)
LOG Critical-Information-Assets → Any (unmatched outbound)</code></pre>
<h3 id="policy-workspace-lifecycle">6.2 Policy Workspace Lifecycle</h3>
<table>
<colgroup>
<col style="width: 25%" />
<col style="width: 25%" />
<col style="width: 25%" />
<col style="width: 25%" />
</colgroup>
<thead>
<tr>
<th>Phase</th>
<th>Mode</th>
<th>Duration</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td>
<td>Simulation</td>
<td>2 weeks</td>
<td>Validate against live traffic; tune false positives</td>
</tr>
<tr>
<td>2</td>
<td>Enforcement (high-confidence rules)</td>
<td>1 week</td>
<td>Internet egress deny; obvious deny rules</td>
</tr>
<tr>
<td>3</td>
<td>Full Enforcement</td>
<td>Ongoing</td>
<td>Workload allowlist enforced; monthly exception review</td>
</tr>
</tbody>
</table>
<p>Treat the policy workspace itself as control-implementation evidence
(Para. 21–23) and snapshot it at each transition.</p>
<hr />
<h2 id="phase-5-paragraph-mapping-with-csw-evidence">7. Phase 5 —
Paragraph Mapping with CSW Evidence</h2>
<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />
<col style="width: 33%" />
</colgroup>
<thead>
<tr>
<th>CPS 234 paragraph</th>
<th>What CSW produces</th>
<th>How to use it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Para. 20</td>
<td>Workload inventory; scope + label export; reachability mapping</td>
<td>Evidence of asset identification and classification</td>
</tr>
<tr>
<td>Para. 21–23</td>
<td>Policy workspace; ADM-derived allowlist; vulnerability +
reachability data</td>
<td>Evidence that controls are implemented and commensurate with
threat</td>
</tr>
<tr>
<td>Para. 24–28</td>
<td>Flow + process search across the incident window</td>
<td>Incident impact scoping and timeline</td>
</tr>
<tr>
<td>Para. 29–33</td>
<td>Continuous flow data; policy-violation log; policy drift report</td>
<td>Control-effectiveness testing evidence (continuous, not
point-in-time)</td>
</tr>
<tr>
<td>Para. 34–35</td>
<td>Periodic evidence pack (Section 10.1)</td>
<td>Internal audit work-paper input</td>
</tr>
<tr>
<td>Para. 36–37</td>
<td>Affected-workload list with timestamps and paths</td>
<td>Input to APRA notification scoping (decision is governance)</td>
</tr>
</tbody>
</table>
<hr />
<h2 id="phase-6-vulnerability-risk-management">8. Phase 6 —
Vulnerability & Risk Management</h2>
<p>CSW vulnerability data is reachability-weighted. Use it to prioritise
patching of internet-exposed and critical-information-asset-reachable
workloads.</p>
<p><strong>Compensating controls in CSW (when patch is
delayed):</strong> restrict the vulnerable port to approved sources, add
an anomaly alert on the affected process, log all connections, and
record the exception in the workspace exception register (this register
is itself evidence for Para. 21–23 risk acceptance).</p>
<hr />
<h2 id="phase-7-monitoring-alerting">9. Phase 7 — Monitoring &
Alerting</h2>
<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />