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