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