ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Rules for commentary
2
3
4
What are we looking for?
5
We are seeking input from industry and legal professionals with experience in cloud security and policy, and comment from FHE specialists on technical detail. In particular, where potential changes are currently identified in the CCM, we welcome counter examples, queries and rebuttals as to the changes in scope.
6
7
How we want comments to be oriented
8
Please comment on individual cells in column G, which contain assessments of the change to the scope or function of the CCM. Please do not create unique comments, but use existing comment threads where present. Please restrict discussion to the specific technical domain that each control applies to.
9
10
11
Provide Actionable Feedback
12
13
Be Specific:
14
Avoid vague comments like “This is unclear. Instead, explain why you believe a change is needed.” For specifications: “This description doesn’t clarify whether the control applies to all data lifecycle stages.”
15
Put the comment in the right place
16
Add your comment in the cell for which the comment is relevant.
17
If someone else has already included a comment, please continue the conversation from there.
18
For general structural comments, please reach out directly to [email protected]
19
20
Provide recommendations for changes:
21
Provide alternative text
22
Suggest alternative wordings or formats to make your feedback actionable.
23
24
Prioritize Changes:
25
Highlight critical issues that need immediate attention.
26
Mark minor or “nice-to-have” suggestions separately.
27
28
Make sure your name appears in the comment. If not, please write it in the comment.
29
30
Acknowledgements:
31
The leadership team will record all acknowledgements after the Peer Review process has ended.
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
OSZAR »