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