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