bug-1131: AssurancePolicy.html HTML 4.01 TransitionalHTML doctype & charset
[cacert-devel.git] / www / policy / AssurancePolicy.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
3 <html><head>
4 <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
5 <title>Assurance Policy</title>
6
7 <!--meta name="CREATED" content="20080530;0" -->
8 <!--meta name="CHANGEDBY" content="Teus Hagen" -->
9 <!--meta name="CHANGED" content="20080709;12381800" -->
10 <!--meta name="CREATEDBY" content="Ian Grigg" -->
11 <!--meta name="CHANGEDBY" content="Teus Hagen" -->
12 <!--meta name="CHANGEDBY" content="Robert Cruikshank" -->
13 <!--meta name="CHANGEDBY" content="Teus Hagen" -->
14 <style type="text/css">
15 <!--
16 P { color: #000000 }
17 TD P { color: #000000 }
18 H1 { color: #000000 }
19 H2 { color: #000000 }
20 DT { color: #000000 }
21 DD { color: #000000 }
22 H3 { color: #000000 }
23 TH P { color: #000000 }
24 -->
25 </style></head>
26 <body style="direction: ltr; color: rgb(0, 0, 0);" lang="en-GB">
27
28 <div class="comment">
29 <table width="100%">
30
31 <tr>
32 <td rowspan="2">
33 Name: AP <a style="color: steelblue" href="https://svn.cacert.org/CAcert/Policies/ControlledDocumentList.html">COD13</a><br>
34 Status: POLICY <a style="color: steelblue" href="https://wiki.cacert.org/PolicyDecisions#p20090105.2">p20090105.2</a><br>
35 Editor: <a style="color: steelblue" href="https://wiki.cacert.org/TeusHagen">Teus Hagen</a><br>
36 Creation date: 2008-05-30<br>
37 Last change by: Iang<br>
38 Last change date: 2009-01-08<br>
39 Licence: <a style="color: steelblue" href="https://wiki.cacert.org/Policy#Licence" title="this document is Copyright &copy; 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>
40
41 </td>
42 <td valign="top" align="right">
43 <a href="https://www.cacert.org/policy/PolicyOnPolicy.html"><img src="images/cacert-policy.png" alt="AP Status - POLICY" height="31" width="88" style="border-style: none;"></a>
44
45 </td>
46 </tr>
47 </table>
48 </div>
49
50
51 <h1>Assurance Policy for CAcert Community Members</h1>
52
53 <h2><a name="s0">0.</a> Preamble</h2>
54 <h3><a name="s0.1">0.1.</a> Definition of Terms</h3>
55 <dl>
56 <dt><i>Member</i> </dt>
57 <dd> A Member is an individual who has agreed to the CAcert
58 Community Agreement
59 (<a href="https://www.cacert.org/policy/CAcertCommunityAgreement.html" target="_blank">CCA</a>)
60 and has created successfully
61 a CAcert login account on the CAcert web site. </dd>
62 <dt> <i>Assurance</i> </dt>
63 <dd> Assurance is the process by which a Member of CAcert
64 Community (Assurer) identifies an individual (<span lang="en-US">Assuree</span>).
65 </dd>
66 <dt> <i>Prospective Member</i> </dt>
67 <dd> An individual who participates in the process of Assurance,
68 but has not yet created a CAcert login account. </dd>
69 <dt> <i>Name</i> </dt>
70 <dd> A Name is the full name of an individual.
71 </dd>
72 <dt> <i>Secondary Distinguishing Feature</i>
73 </dt>
74 <dd> An additional personal data item of the Member
75 that assists discrimination from Members with similar full names.
76 (Currently this is the Date of Birth (DoB).)
77 </dd>
78 </dl>
79
80 <h3><a name="s0.2">0.2.</a> The CAcert Web of Trust</h3>
81 <p>
82 In face-to-face meetings,
83 an Assurer allocates a number of Assurance Points
84 to the Member being Assured.
85 CAcert combines the Assurance Points
86 into a global <i>Web-of-Trust</i> (or "WoT").
87 </p>
88 <p>
89 CAcert explicitly chooses to meet its various goals by
90 construction of a Web-of-Trust of all Members.
91 </p>
92
93 <h3><a name="s0.3">0.3.</a> Related Documentation</h3>
94 <p>
95 Documentation on Assurance is split between this
96 Assurance Policy (AP) and the
97 <a href="https://wiki.cacert.org/AssuranceHandbook2" target="_blank">Assurance
98 Handbook</a>. The policy is controlled by Configuration Control
99 Specification
100 (<a href="https://svn.cacert.org/CAcert/Policies/ConfigurationControlSpecification.html" target="_blank">CCS</a>)
101 under Policy on Policy
102 (<a href="https://www.cacert.org/policy/PolicyOnPolicy.html" target="_blank">PoP</a>)
103 policy document regime. Because Assurance is an active area, much
104 of the practice is handed over to the Assurance Handbook, which is
105 not a controlled policy document, and can more easily respond to
106 experience and circumstances. It is also more readable.
107 </p>
108 <p>
109 See also Organisation Assurance Policy (<a href="https://www.cacert.org/policy/OrganisationAssurancePolicy.html" target="_blank">OAP</a>)
110 and CAcert Policy Statement (<a href="https://www.cacert.org/policy/CertificationPracticeStatement.html" target="_blank">CPS</a>).
111 </p>
112
113 <h2><a name="s1">1.</a> Assurance Purpose</h2>
114 <p>The purpose of Assurance is to add confidence
115 in the Assurance Statement made by the CAcert Community of a Member. </p>
116 <p>With sufficient assurances, a Member may: (a) issue certificates
117 with their assured Name included, (b) participate in assuring others,
118 and (c) other related activities. The strength of these activities is
119 based on the strength of the assurance. </p>
120
121 <h3><a name="s1.1">1.1.</a>The Assurance Statement</h3>
122 <p>
123 The Assurance Statement makes the following claims
124 about a person:
125 </p>
126 <ol>
127 <li>
128 <p>The person is a bona fide Member. In other words, the
129 person is a member of the CAcert Community as defined by the CAcert
130 Community Agreement (<a href="https://www.cacert.org/policy/CAcertCommunityAgreement.html" target="_blank">CCA</a>); </p>
131 </li>
132 <li>
133 <p>The Member has a (login) account with CAcert's on-line
134 registration and service system; </p>
135 </li>
136 <li>
137 <p>The Member can be determined from any CAcert certificate
138 issued by the Account; </p>
139 </li>
140 <li>
141 <p>The Member is bound into CAcert's Arbitration as defined
142 by the CAcert Community Agreement; </p>
143 </li>
144 <li>
145 <p>Some personal details of the Member are known to CAcert:
146 the individual Name(s), primary and other listed individual email
147 address(es), secondary distinguishing feature (e.g. DoB). </p>
148 </li>
149 </ol>
150 <p>The confidence level of the Assurance Statement is expressed by
151 the Assurance Points. </p>
152 <h3><a name="s1.2">1.2.</a>Relying Party Statement</h3>
153 <p>The primary goal of the Assurance Statement is for the express
154 purpose of certificates to meet the needs of the <i>Relying Party
155 Statement</i>, which latter is found in the Certification Practice
156 Statement (<a href="https://www.cacert.org/policy/CertificationPracticeStatement.html" target="_blank">CPS</a>).
157 </p>
158 <p>When a certificate is issued, some of the Assurance Statement may
159 be incorporated, e.g. Name. Other parts may be implied, e.g.
160 Membership, exact account and status. They all are part of the
161 <i>Relying Party Statement</i>. In short, this means that other
162 Members of the Community may rely on the information verified by
163 Assurance and found in the certificate.</p>
164 <p>In particular, certificates are sometimes considered to provide
165 reliable indications of e.g. the Member's Name and email address. The
166 nature of Assurance, the number of Assurance Points, and other
167 policies and processes should be understood as limitations on any
168 reliance. </p>
169 <h2><a name="s2">2.</a> The Member</h2>
170 <h3><a name="s2.1">2.1.</a> The Member's Name </h3>
171 <p>
172 At least one individual Name is recorded in the Member's
173 CAcert login account. The general standard of a Name is:
174 </p>
175 <ul>
176 <li>
177 <p>
178 The Name should be recorded as written in a
179 government-issued photo identity document (ID).
180 </p>
181 </li>
182 <li>
183 <p>
184 The Name should be recorded as completely as possible.
185 That is, including all middle names, any titles and extensions,
186 without abbreviations, and without transliteration of characters.
187 </p>
188 </li>
189 <li>
190 <p>The Name is recorded as a string of characters,
191 encoded in <span lang="en-US">unicode</span>
192 transformation format.</p>
193 </li>
194 </ul>
195 <h3><a name="s2.2">2.2.</a> Multiple Names and variations</h3>
196 <p>
197 In order to handle the contradictions in the above general standard,
198 a Member may record multiple Names or multiple variations of a Name
199 in her CAcert online Account.
200 Examples of variations include married names,
201 variations of initials of first or middle names,
202 abbreviations of a first name,
203 different language or country variations,
204 and transliterations of characters in a name.
205 </p>
206
207 <h3><a name="s2.3">2.3.</a> Status and Capabilities</h3>
208 <p>
209 A Name which has reached
210 the level of 50 Assurance Points is defined as an Assured
211 Name. An Assured Name can be used in a certificate issued by CAcert.
212 A Member with at least one Assured Name has reached the Assured
213 Member status.
214 Additional capabilities are described in Table 1.
215 </p>
216
217 <blockquote>
218 <p align="left"><font size="2"><i>Table 1:
219 Assurance Capability</i></font></p>
220 <table border="1" cellpadding="5" cellspacing="0">
221 <tbody>
222 <tr>
223 <td width="10%">
224 <p align="left"><i>Minimum Assurance Points</i></p>
225 </td>
226 <td width="15%">
227 <p align="left"><i>Capability</i></p>
228 </td>
229 <td width="15%">
230 <p align="left"><i>Status</i></p>
231 </td>
232 <td width="60%">
233 <p align="left"><i>Comment</i></p>
234 </td>
235 </tr>
236 <tr valign="top">
237 <td>
238 <p align="center">0</p>
239 </td>
240 <td>
241 <p align="left">Request Assurance</p>
242 </td>
243 <td>
244 <p align="left">Prospective Member</p>
245 </td>
246 <td>
247 <p align="left">Individual taking part of an
248 Assurance, who does not have created a CAcert login account (yet). The
249 allocation of Assurance Points is awaiting login account creation.</p>
250 </td>
251 </tr>
252 <tr valign="top">
253 <td>
254 <p align="center">0</p>
255 </td>
256 <td>
257 <p align="left">Request unnamed certificates</p>
258 </td>
259 <td>
260 <p align="left">Member</p>
261 </td>
262 <td>
263 <p align="left">Although the Member's details are
264 recorded in the account, they are not highly assured.</p>
265 </td>
266 </tr>
267 <tr valign="top">
268 <td>
269 <p align="center">50</p>
270 </td>
271 <td>
272 <p align="left">Request named certificates</p>
273 </td>
274 <td>
275 <p align="left">Assured Member</p>
276 </td>
277 <td>
278 <p align="left">Statements of Assurance: the Name is
279 assured to 50 Assurance Points or more</p>
280 </td>
281 </tr>
282 <tr valign="top">
283 <td>
284 <p align="center">100</p>
285 </td>
286 <td>
287 <p align="left">Become an Assurer</p>
288 </td>
289 <td>
290 <p align="left">Prospective Assurer</p>
291 </td>
292 <td>
293 <p align="left">Assured to 100 Assurance Points (or
294 more) on at least one Name, and passing the Assurer Challenge.</p>
295 </td>
296 </tr>
297 </tbody>
298 </table>
299 </blockquote>
300
301
302 <p>
303 A Member may check the status of another Member, especially
304 for an assurance process.
305 Status may be implied from information in a certificate.
306 The number of Assurance Points for each Member is not published.
307 </p>
308
309 <p>
310 The CAcert Policy Statement
311 (<a href="https://www.cacert.org/policy/CertificationPracticeStatement.html" target="_blank">CPS</a>)
312 and other policies may list other capabilities that rely on Assurance
313 Points.
314 </p>
315
316 <h2><a name="s3">3.</a> The Assurer</h2>
317 <p>An Assurer is a Member with the following: </p>
318 <ul>
319 <li>
320 <p>Is assured to a minimum of 100 Assurance Points; </p>
321 </li>
322 <li>
323 <p>Has passed the CAcert Assurer Challenge. </p>
324 </li>
325 </ul>
326 <p>The Assurer Challenge is administered by the Education Team on
327 behalf of the Assurance Officer. </p>
328 <h3><a name="s3.1">3.1.</a> The Obligations of the Assurer</h3>
329 <p>The Assurer is obliged to: </p>
330 <ul>
331 <li>
332 <p>Follow this Assurance Policy; </p>
333 </li>
334 <li>
335 <p>Follow any additional rules of detail laid out by the
336 CAcert Assurance Officer; </p>
337 </li>
338 <li>
339 <p>Be guided by the CAcert <a href="https://wiki.cacert.org/AssuranceHandbook2" target="_blank">Assurance Handbook</a> in their
340 judgement; </p>
341 </li>
342 <li>
343 <p>Make a good faith effort at identifying and verifying
344 Members; </p>
345 </li>
346 <li>
347 <p>Maintain the documentation on each Assurance; </p>
348 </li>
349 <li>
350 <p>Deliver documentation to Arbitration, or as otherwise
351 directed by the Arbitrator; </p>
352 </li>
353 <li>
354 <p>Keep up-to-date with developments within the CAcert
355 Community. </p>
356 </li>
357 </ul>
358 <h2><a name="s4">4.</a> The Assurance</h2>
359 <h3><a name="s4.1">4.1.</a> The Assurance Process</h3>
360 <p>The Assurer conducts the process of Assurance with each
361 Member. </p>
362 <p>The process consists of: </p>
363 <ol>
364 <li>
365 <p>Voluntary agreement by both Assurer and Member or
366 Prospective Member to conduct the Assurance; </p>
367 </li>
368 <li>
369 <p>Personal meeting of Assurer and Member or Prospective
370 Member; </p>
371 </li>
372 <li>
373 <p>Recording of essential details on CAcert Assurance
374 Programme form; </p>
375 </li>
376 <li>
377 <p>Examination of Identity documents by Assurer and
378 verification of recorded details (the Name(s) and Secondary
379 Distinguishing Feature, e.g., DoB); </p>
380 </li>
381 <li>
382 <p>Allocation of Assurance Points by Assurer; </p>
383 </li>
384 <li>
385 <p>Optional: supervision of reciprocal Assurance made by
386 Assuree (Mutual Assurance); </p>
387 </li>
388 <li>
389 <p>Safekeeping of the CAcert Assurance Programme (<a href="https://www.cacert.org/cap.php" target="_blank">CAP</a>)
390 forms by Assurer. </p>
391 </li>
392 </ol>
393 <h3><a name="s4.2">4.2.</a> Mutual Assurance</h3>
394 <p>Mutual Assurance follows the principle of reciprocity. This
395 means
396 that the Assurance may be two-way, and that each member participating
397 in the Assurance procedure should be able to show evidence of their
398 identity to the other. </p>
399 <p>In the event that an Assurer is assured by a Member who is not
400 certified as an Assurer, the Assurer supervises the Assurance
401 procedure and process, and is responsible for the results. </p>
402 <p>Reciprocity maintains a balance between the (new) member and
403 the
404 Assurer, and reduces any sense of power. It is also an important aid
405 to the assurance training for future Assurers. </p>
406
407 <h3><a name="s4.3">4.3.</a> Assurance Points</h3>
408 <p>The Assurance applies Assurance Points to each Member which
409 measure the increase of confidence in the Statement (above).
410 Assurance Points should not be interpreted for any other purpose.
411 Note that, even though they are sometimes referred to as <i>Web-of-Trust</i>
412 (Assurance) Points, or <i>Trust</i> Points, the meaning
413 of the word
414 'Trust' is not well defined. </p>
415 <p><i>Assurance Points Allocation</i><br>
416 An Assurer can allocate a
417 number of Assurance Points to the Member according to the Assurer's
418 experience (Experience Point system, see below). The allocation of
419 the maximum means that the Assurer is 100% confident in the
420 information presented: </p>
421 <ul>
422 <li>
423 <p>Detail on form, system, documents, person in accordance; </p>
424 </li>
425 <li>
426 <p>Sufficient quality identity documents have been checked; </p>
427 </li>
428 <li>
429 <p>Assurer's familiarity with identity documents; </p>
430 </li>
431 <li>
432 <p>The Assurance Statement is confirmed. </p>
433 </li>
434 </ul>
435 <p>
436 Any lesser confidence should result in less Assurance Points for a
437 Name. If the Assurer has no confidence in the information presented,
438 then <i>zero</i> Assurance Points may be allocated by the Assurer.
439 For example, this may happen if the identity documents are totally
440 unfamiliar to the Assurer. The number of Assurance Points from <i>zero</i>
441 to <i>maximum</i> is guided by the Assurance Handbook
442 and the judgement of the Assurer.
443 If there is negative confidence the Assurer should consider
444 filing a dispute.
445 </p>
446 <p>Multiple Names should be allocated Assurance Points
447 independently within a single Assurance. </p>
448 <p>
449 A Member who is not an Assurer may award an Assurer in a
450 reciprocal process a maximum of 2 Assurance Points, according to
451 her judgement. The Assurer should strive to have the Member allocate
452 according to the Member's judgement, and stay on the cautious side;
453 the Member new to the assurance process
454 should allocate <i>zero</i> Assurance Points
455 until she gains some confidence in what is happening.
456 </p>
457 <p>
458 In general, for a Member to reach 50 Assurance Points, the Member must
459 have participated in at least two assurances, and
460 at least one Name will have been assured to that level.
461 </p>
462 <p>
463 To reach 100 Assurance
464 Points, at least one Name of the Assured Member must have been
465 assured at least three times.
466 </p>
467 <p>
468 The maximum number of Assurance
469 Points which can be allocated for an Assurance under this policy
470 and under any act under any
471 Subsidiary Policy (below) is 50 Assurance Points.
472 </p>
473
474 <h3><a name="s4.4">4.4.</a> Experience Points</h3>
475 <p>The maximum number of Assurance Points that may be awarded by
476 an
477 Assurer is determined by the Experience Points of the Assurer. </p>
478 <blockquote>
479 <p align="left"><font size="2"><i>Table 2:
480 Maximum of Assurance Points </i></font>
481 </p>
482 <table border="1" cellpadding="2" cellspacing="0" width="15%">
483 <tbody>
484 <tr>
485 <td>
486 <p><i>Assurer's Experience Points</i></p>
487 </td>
488 <td>
489 <p><i>Allocatable Assurance Points</i></p>
490 </td>
491 </tr>
492 <tr>
493 <td>
494 <p align="center">0</p>
495 </td>
496 <td>
497 <p align="center">10</p>
498 </td>
499 </tr>
500 <tr>
501 <td>
502 <p align="center">10</p>
503 </td>
504 <td>
505 <p align="center">15</p>
506 </td>
507 </tr>
508 <tr>
509 <td>
510 <p align="center">20</p>
511 </td>
512 <td>
513 <p align="center">20</p>
514 </td>
515 </tr>
516 <tr>
517 <td>
518 <p align="center">30</p>
519 </td>
520 <td>
521 <p align="center">25</p>
522 </td>
523 </tr>
524 <tr>
525 <td>
526 <p align="center">40</p>
527 </td>
528 <td>
529 <p align="center">30</p>
530 </td>
531 </tr>
532 <tr>
533 <td>
534 <p align="center">&gt;=50</p>
535 </td>
536 <td>
537 <p align="center">35</p>
538 </td>
539 </tr>
540 </tbody>
541 </table>
542 </blockquote>
543 <p>An Assurer is given a maximum of 2 Experience Points for every
544 completed Assurance. On reaching Assurer status, the Experience
545 Points start at 0 (zero). </p>
546 <p>Less Experience Points (1) may be given for mass Assurance
547 events,
548 where each Assurance is quicker. </p>
549 <p>Additional Experience Points may be granted temporarily or
550 permanently to an Assurer by CAcert Inc.'s Committee (board), on
551 recommendation from the Assurance Officer. </p>
552 <p>Experience Points are not to be confused with Assurance
553 Points. </p>
554 <h3><a name="s4.5">4.5.</a> CAcert Assurance Programme (CAP) form</h3>
555 <p>The CAcert Assurance Programme (<a href="https://www.cacert.org/cap.php" target="_blank">CAP</a>)
556 form requests the following details of each Member or Prospective
557 Member: </p>
558 <ul>
559 <li>
560 <p>Name(s), as recorded in the on-line account; </p>
561 </li>
562 <li>
563 <p>Primary email address, as recorded in the on-line account;
564 </p>
565 </li>
566 <li>
567 <p>Secondary Distinguishing Feature, as recorded in the
568 on-line account (normally, date of birth); </p>
569 </li>
570 <li>
571 <p>Statement of agreement with the CAcert Community
572 Agreement; </p>
573 </li>
574 <li>
575 <p>Permission to the Assurer to conduct the Assurance
576 (required for privacy reasons); </p>
577 </li>
578 <li>
579 <p>Date and signature of the Assuree. </p>
580 </li>
581 </ul>
582 <p>The CAP form requests the following details of the Assurer: </p>
583 <ul>
584 <li>
585 <p>At least one Name as recorded in the on-line account of
586 the Assurer; </p>
587 </li>
588 <li>
589 <p>Assurance Points for each Name in the identity
590 document(s); </p>
591 </li>
592 <li>
593 <p>Statement of Assurance; </p>
594 </li>
595 <li>
596 <p>Optional: If the Assurance is reciprocal, then the
597 Assurer's email address and Secondary Distinguishing Feature are
598 required as well; </p>
599 </li>
600 <li>
601 <p>Date, location of Assurance and signature of Assurer. </p>
602 </li>
603 </ul>
604 <p>The CAP forms are to be kept at least for 7 years by the
605 Assurer. </p>
606 <h2><a name="s5">5.</a> The Assurance Officer</h2>
607 <p>The Committee (board) of CAcert Inc. appoints an Assurance
608 Officer
609 with the following responsibilities: </p>
610 <ul>
611 <li>
612 <p>Reporting to the Committee and advising on all matters to
613 do with Assurance; </p>
614 </li>
615 <li>
616 <p>Training and testing of Assurers, in association with the
617 Education Team; </p>
618 </li>
619 <li>
620 <p>Updating this Assurance Policy, under the process
621 established by Policy on Policy (<a href="https://www.cacert.org/policy/PolicyOnPolicy.html" target="_blank">PoP</a>); </p>
622 </li>
623 <li>
624 <p>Management of all Subsidiary Policies (see below) for
625 Assurances, under Policy on Policy; </p>
626 </li>
627 <li>
628 <p>Managing and creating rules of detail or procedure where
629 inappropriate for policies; </p>
630 </li>
631 <li>
632 <p>Incorporating rulings from Arbitration into policies,
633 procedures or guidelines; </p>
634 </li>
635 <li>
636 <p>Assisting the Arbitrator in any requests; </p>
637 </li>
638 <li>
639 <p>Managing the Assurer Handbook; </p>
640 </li>
641 <li>
642 <p>Maintaining a sufficient strength in the Assurance process
643 (web-of-trust) to meet the agreed needs of the Community. </p>
644 </li>
645 </ul>
646 <h2><a name="s6">6.</a> Subsidiary Policies</h2>
647 <p>The Assurance Officer manages various exceptions and additional
648 processes. Each must be covered by an approved Subsidiary Policy
649 (refer to Policy on Policy =&gt; CAcert Official Document COD1).
650 Subsidiary Policies specify any additional tests of knowledge
651 required and variations to process and documentation, within the
652 general standard stated here. </p>
653 <h3><a name="s6.1">6.1.</a> Standard</h3>
654 <p>Each Subsidiary Policy must augment and improve the general
655 standards in this Assurance Policy. It is the responsibility of each
656 Subsidiary Policy to describe how it maintains and improves the
657 specific and overall goals. It must describe exceptions and potential
658 areas of risk. </p>
659
660 <h3><a name="s6.2">6.2.</a> High Risk Applications</h3>
661 <p>In addition to the Assurance or Experience Points ratings set
662 here and in other subsidiary policies, the Assurance Officer or policies can
663 designate certain applications as high risk. If so, additional
664 measures may be added to the Assurance process that specifically
665 address the risks.</p>
666 <p>Additional measures may include:
667 </p>
668 <ul>
669 <li>
670 <p>Additional information can be required in process of assurance: </p>
671 <ul>
672 <li>unique numbers of identity documents,</li>
673 <li>photocopy of identity documents,</li>
674 <li>photo of User,</li>
675 <li>address of User.</li>
676 </ul>
677 <p>Additional Information is to be kept by Assurer, attached to
678 CAcert Assurance Programme (<a href="https://www.cacert.org/cap.php" target="_blank">CAP</a>)
679 form. Assurance Points allocation by this assurance is unchanged.
680 User's CAcert login account should be annotated to record type of
681 additional information;</p>
682 </li>
683 <li>
684 <p>Arbitration: </p>
685 <ul>
686 <li> Member to participate in Arbitration. This confirms
687 their acceptance of the forum as well as trains in the process and
688 import,
689 </li>
690 <li> Member to file Arbitration to present case. This
691 allows Arbitrator as final authority;
692 </li>
693 </ul>
694 </li>
695 <li>
696 <p>Additional training; </p>
697 </li>
698 <li>
699 <p>Member to be Assurer (at least 100 Assurance Points and
700 passed Assurer Challenge); </p>
701 </li>
702 <li>
703 <p>Member agrees to additional specific agreement(s); </p>
704 </li>
705 <li>
706 <p>Additional checking/auditing of systems data by CAcert
707 support administrators. </p>
708 </li>
709 </ul>
710 <p>Applications that might attract additional measures include
711 code-signing certificates and administration roles. </p>
712 <h2><a name="s7">7.</a> Privacy</h2>
713 <p>CAcert is a "privacy" organisation, and takes the
714 privacy of its Members seriously. The process maintains the security
715 and privacy of both parties. </p>
716 <p>Information is collected primarily to make claims within the
717 certificates requested by users and to contact the Members. It is
718 used secondarily for training, testing, administration and other
719 internal purposes. </p>
720 <p>The Member's information can be accessed under these
721 circumstances: </p>
722 <ul>
723 <li>
724 <p>Under Arbitrator ruling, in a duly filed dispute (<a href="https://www.cacert.org/policy/DisputeResolutionPolicy.html" target="_blank">Dispute Resolution Policy</a>
725 =&gt; COD7); </p>
726 </li>
727 <li>
728 <p>An Assurer in the process of an Assurance, as permitted on
729 the CAcert Assurance Programme (<a href="https://www.cacert.org/cap.php" target="_blank">CAP</a>)
730 form; </p>
731 </li>
732 <li>
733 <p>CAcert support administration and CAcert systems
734 administration when operating under the authority of Arbitrator or
735 under CAcert policy. </p>
736 </li>
737 </ul>
738 <p><a href="http://validator.w3.org/check?uri=referer"><img src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" align="bottom" border="0" height="31" width="88"></a></p>
739 </body></html>
740