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
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" lang="en">
<title> CAcert -- TTP-Assisted Assurance Policy </title>
<style type="text/css">
<!--
.comment {
color : steelblue;
}
-->
</style>
</head>
<body>
<div class="comment">
<table width="100%">
<tbody>
<tr>
<td rowspan="2">
Name: TTP-Assist <a style="color: steelblue" href="https://svn.cacert.org/CAcert/Policies/ControlledDocumentList.html">COD13.2</a>
<br>
Status: POLICY <a href="https://wiki.cacert.org/PolicyDecisions#p20140731">p20140731</a>
<br>
Editor: <a style="color: steelblue" href="https://wiki.cacert.org/UlrichSchroeter">Ulrich Schroeter</a>
<br>
Licence: <a style="color: steelblue" href="https://wiki.cacert.org/Policy#Licence" title="this document is Copyright © CAcert Inc., licensed openly under CC-by-sa with all disputes resolved under DRP. More at wiki.cacert.org/Policy"> CC-by-sa+DRP </a>
<br>
</td>
<td align="right" valign="top">
<a href="https://www.cacert.org/policy/PolicyOnPolicy.php">
<img src="images/cacert-policy.png" alt="TTP-Assist Status - POLICY" style="border-style: none;" height="31" width="88">
</a>
</td>
</tr>
</tbody>
</table>
</div>
<h1> TTP-Assisted Assurance Policy </h1>
<h2 id="g0.1">0. Preliminaries </h2>
<p>
This sub-policy extends the
<a href="https://www.cacert.org/policy/AssurancePolicy.php">
Assurance Policy</a> ("AP" => COD13)
by specifying how Assurers can be assisted by
outsourcing the identity documents verification
component of assurance to trusted third parties (TTPs).
Other definitions and terms can be found in AP or in
<a href="https://wiki.cacert.org/AssuranceHandbook">Assurance Handbook</a>
("AH").
</p>
<h2 id="g0.2">1. Scope </h2>
<p>
This sub-policy is restricted to members located
in areas not well-served with Assurers.
It serves a goal of promoting both Assurers and Members in those areas.
</p>
<h2 id="g0.3">2. Roles </h2>
<h3 id="g0.3.1">2.1 Trusted Third Party </h3>
<p>
A Trusted Third Party ("TTP") is a person who is traditionally respected
for making reliable statements to others, especially over identification
documents. Typically, notaries public (anglo),
Notaries (European), bank managers, accountants
and lawyers.
</p>
<h3 id="g0.3.2">2.2 The Assurer (aka TTP-admin) </h3>
<p>
To employ a TTP in an assurance,
the Assurer must be a <a href="https://wiki.cacert.org/SeniorAssurer">Senior Assurer</a>.
The Assurer must be familiar with the local
language and customs.
</p>
<h3 id="g0.3.3">2.3 Member </h3>
<p>
A Member ("assuree") who is located in a place not well-served
by Assurers may use the TTP-assisted assurance.
</p>
<h2 id="g0.4">3. The Assurance </h2>
<p>
Assurance assisted by TTP must meet these requirements:
</p>
<ol style="list-style-type: lower-alpha;">
<li id="s3.a">
The Assurer must positively confirm the identity and
suitability of the TTP.
</li>
<li id="s3.b">
The TTP and the Member must meet face-to-face.
</li>
<li id="s3.c">
The TTP confirms the details supporting the Assurance Statement.
</li>
<li id="s3.d">
The Assurer makes a reliable statement to confirm the
Assurance Statement.
</li>
<li id="s3.e">
Assurance must be marked as TTP-Assisted
(e.g., by use of TTPAdmin flag).
</li>
</ol>
<h2 id="g0.5">4. Assurance Officer ("AO") </h2>
<p>
The Board routinely delegates its responsibilities to the
Assurance Officer (and this section assumes that, but does
not require it).
</p>
<p>
A report is requested annually from the Assurance Officer
on performance of this policy for the association's
annual report.
</p>
<h3 id="g0.5.1">4.1 Practice </h3>
<p>
Assurance Officer should prepare a
<a href="https://wiki.cacert.org/TTP">detailed documentation</a>
under
<a href="https://wiki.cacert.org/AssuranceHandbook">AH</a>
that meets the needs of this policy, including:
</p>
<ul>
<li>
Form for TTPs
</li>
<li>
Guide for TTPs.
</li>
<li>
Form for TTP-assisted assurance (used by Assurer)
</li>
<li>
Guide and protocol for Assurers.
</li>
<li>
Mechanisms for contacting Assurers available for
TTP-assisted assurances.
</li>
<li>
Definition of
<a href="https://wiki.cacert.org/SeniorAssurer">
Senior Assurer</a>.
</li>
</ul>
<h3 id="g0.5.2">4.2 Deserts </h3>
<p>
The Assurance Officer maintains a
<a href="https://wiki.cacert.org/deserts">list of regions</a>
that are designated as '<i>deserts,</i>' being areas that are so short
of Assurers as to render face-to-face Assurance impractical.
In each region, approved types of TTP are listed (e.g., Notary).
The list is expected to vary according to the
different juridical traditions of different regions.
Changes to the regional lists are prepared by
either an Organisation Assurer for that region
(as described by OAP)
or by two Assurers familiar with the traditions
in that region.
Changes are then submitted to the Board for approval.
</p>
<p>
Use of a type of TTP not on the list must be approved by
AO and notified to Board.
It is an explicit goal to reduce the usage of
TTP-assisted assurances in favour of face-to-face Assurance.
</p>
<p>
In coordination with internal and external auditors,
the Assurance Officer shall design and implement a
suitable programme to meet the needs of audit.
Where approved by auditors or Board, the Assurance
Officer may document and implement minor variations to this policy.
</p>
<h2 id="g0.6">5. Topup Assurance </h2>
<p>
AO is to operate a <cite>Topup Assurance Programme</cite>
to help seed deserts with Assurers.
A topup assurance will add additional Assurance Points
to those gained from two previously conducted TTP-assisted assurances,
in order for a Member to reach 100 Assurance Points
for the express purpose of becoming an Assurer.
</p>
<p>
A topup assurance is conducted by a third Senior Assurer
according to the following requirements:
</p>
<ol>
<li id="s5.1">
Assurer Challenge must be completed as passed by Member.
</li>
<li id="s5.2">
The topup must be requested by Member for
purpose of enabling the Member to reach Assurer level.
</li>
<li id="s5.3">
Topup Assurer must be a Senior Assurer,
and must be independent of the TTP-assist Assurers.
</li>
<li id="s5.4">
The Topup Assurer reviews the two TTP-assisted assurances,
and conducts other checks as set by the Assurance Officer.
The normal face-to-face meeting is not conducted.
</li>
<li id="s5.5">
Topup Assurer may award up to 35 points.
</li>
<li id="s5.6">
Assurance must be marked as Topup
(e.g., by use of new feature with TTPAdmin flag).
</li>
</ol>
<p>
Each topup is to be reported to AO.
Topup is only available in designated deserts.
</p>
</body>
</html>
|
