Suggested changes incorp[orated. Main one is added 50 assurancde points max and deleted sentence about minimal twice and 100 assurance points. Still those are strike through, to be deleted fully on vote Aye.

git-svn-id: http://svn.cacert.org/CAcert/Policies@876 14b1bab8-4ef6-0310-b690-991c95c89dfd
This commit is contained in:
Teus Hagen 2008-07-07 13:32:49 +00:00
parent e7f2cbc419
commit 633983da05

View file

@ -2,13 +2,13 @@
<html><head>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title>Assurance Policy</title>
<meta name="GENERATOR" content="OpenOffice.org 2.3 (Unix)">
<meta name="CREATED" content="20080530;0">
<meta name="CHANGEDBY" content="Teus Hagen">
<meta name="CHANGED" content="20080707;15011800">
<meta name="CREATEDBY" content="Ian Grigg">
<meta name="CHANGEDBY" content="Teus Hagen">
<meta name="CHANGEDBY" content="Robert Cruikshank">
<meta name="CHANGEDBY" content="Teus Hagen">
<meta name="CHANGED" content="20080703;16423900">
<style type="text/css">
<!--
P { color: #000000 }
@ -22,6 +22,7 @@ TH P { color: #000000 }
-->
</style>
</head>
<body style="direction: ltr; color: rgb(0, 0, 0);" lang="en-GB">
<h1>Assurance Policy for CAcert Community Members</h1>
<p><a href="PolicyOnPolicy.html"><img src="Images/cacert-wip.png" name="graphics1" alt="CAcert Policy Status" align="bottom" border="0" height="33" width="90"></a>
@ -29,37 +30,36 @@ TH P { color: #000000 }
Author: Ian Grigg<br>
Creation date: 2008-05-30<br>
Last change by: Teus Hagen<br>
Last change date: 2008-07-03 21:12 MET<br>
Status: WIP
2008-05-30<br>
Last change date: 2008-07-07 15:03 MET<br>
Status: WIP 2008-05-30<br>
Next status: DRAFT June 2008 </p>
<h2 class="western">0. Preamble</h2>
<h2>0. Preamble</h2>
<p>Definitions of terms: </p>
<dl>
<dt><em>Member</em> </dt>
<dd> A Member is an individual who has agreed to the CAcert
Community Agreement (<a href="http://www.cacert.org/policy/CAcertCommunityAgreement.php" target="_blank">CCA</a>) and has created successfully
a CAcert login
account on the CAcert web site.</dd>
a CAcert login account on the CAcert web site. </dd>
<dt> <em>Assurance</em> </dt>
<dd> Assurance is the process by which a Member of CAcert
Community (Assurer) identifies an individual (<span lang="en-US">Assuree</span>).</dd>
<dt style="font-style: italic;">Prospective Member</dt>
<dd>An individual who has been assured in an Assurance process,
but has not yet created successfully a CAcert login account.</dd>
Community (Assurer) identifies an individual (<span lang="en-US">Assuree</span>).
</dd>
<dt> <i>Prospective Member</i> </dt>
<dd> An individual who has been assured in an Assurance
process, but has not yet created successfully a CAcert login account. </dd>
<dt> <em>Name</em> </dt>
<dd> A Name is the full name of an individual: first name(s),
family name(s), name extensions, abbreviation of name(s), etc. <br>
The Name
is technically spoken a string exactly taken e.g. from a governmental
issued
photo ID. </dd>
<dd> A Name is the full name of an individual, with all
components of that name.</dd>
<dd> (Title(s), first name(s), family name(s), name extensions,
abbreviation of name(s), etc. <br>
The Name is technically spoken a string exactly taken e.g. from a
governmental issued photo ID.) </dd>
<dt> <em>Secondary Distinguishing Feature</em>
(DoB) </dt>
<dd style="margin-bottom: 0.5cm;"> A Name for an
individual is discriminated from similar full names by a secondary
distinguished feature, as recorded on the on-line CAcert (web) account.
<br>Currently this is the date of birth (DoB) of the individual. </dd>
<dd> A Name for an individual is discriminated from similar
full names by a secondary distinguished feature, as recorded on the
on-line CAcert (web) account. <br>
(Currently this is the date of birth (DoB) of the individual. )</dd>
</dl>
<h3>
The CAcert Web of Trust</h3>
@ -89,41 +89,38 @@ experience and circumstances. It is also more readable. </p>
and CAcert Policy Statement (<a href="http://svn.cacert.org/CAcert/policy.htm" target="_blank">CPS</a>).
</p>
<h2>1. Assurance Purpose</h2>
<p>The purpose of Assurance is to add <i>confidence</i>
in the
Assurance Statement made by the CAcert Community of a Member. </p>
<p>The purpose of Assurance is to add <span style="font-style: normal;">confidence</span>
in the Assurance Statement made by the CAcert Community of a Member. </p>
<p>With sufficient assurances, a Member may: (a) issue
certificates
with their assured Name included, (b) participate in assuring others,
and (c)
other related activities. The strength of these activities is based
on the strength of the assurance. </p>
and (c) other related activities. The strength of these activities is
based on the strength of the assurance. </p>
<h3>The Assurance Statement</h3>
<p>The following claims can be made about a person who is
assured: </p>
<ol>
<li>
<p>The person is a bona
fide Member. In other words, the person is a member of the CAcert
Community as defined by the CAcert Community Agreement (<a href="http://www.cacert.org/policy/CAcertCommunityAgreement.php" target="_blank">CCA</a>); </p>
<p>The person is a bona fide Member. In other words, the
person is a member of the CAcert Community as defined by the CAcert
Community Agreement (<a href="http://www.cacert.org/policy/CAcertCommunityAgreement.php" target="_blank">CCA</a>); </p>
</li>
<li>
<p>The Member has a
(login) account with CAcert's on-line registration and service system; </p>
<p>The Member has a (login) account with CAcert's on-line
registration and service system; </p>
</li>
<li>
<p>The Member can be
determined from any CAcert certificate issued by the Account; </p>
<p>The Member can be determined from any CAcert certificate
issued by the Account; </p>
</li>
<li>
<p>The Member is bound
into CAcert's Arbitration as defined by the CCA agreement; </p>
<p>The Member is bound into CAcert's Arbitration as defined
by the Community Agreement; </p>
</li>
<li>
<p>Some personal details of the Member are known to CAcert:
the personal Name(s), primary and other listed email address(es),
secondary
distinguished feature (e.g. DoB). </p>
the individual Name(s), primary and other listed individual email
address(es), secondary distinguished feature (e.g. DoB). </p>
</li>
</ol>
<p>The confidence level of the Assurance Statement is expressed
@ -131,20 +128,20 @@ by
the Assurance Points. </p>
<h3>Relying Party Statement</h3>
<p>The primary goal of the Assurance Statement is for the express
purpose of certificates to meet the
needs
of the <em>Relying Party Statement</em>, which latter is
found in the
Certification Practice Statement (<a href="http://svn.cacert.org/CAcert/policy.htm" target="_blank">CPS</a>).
purpose of certificates to meet the needs of the <em>Relying
Party
Statement</em>, which latter is found in the Certification
Practice
Statement (<a href="http://svn.cacert.org/CAcert/policy.htm" target="_blank">CPS</a>).
</p>
<p>When a certificate is issued, some of the Assurance Statement
may
be incorporated, e.g. Name. Other parts may be implied, e.g.
Membership, exact account and status. They all are part of the <em>Relying
Party Statement</em>. In short, this means that other Members of
the
Community may rely on the information verified by Assurance and found
in the certificate. </p>
Membership, exact account and status. They all are part of the
<em>Relying Party Statement</em>. In short, this means that
other
Members of the Community may rely on the information verified by
Assurance and found in the certificate. </p>
<p>In particular, certificates are sometimes considered to
provide
reliable indications of e.g. the Member's Name and email address. The
@ -153,31 +150,31 @@ policies and processes should be understood as limitations on any
reliance. </p>
<h2>2. The Member</h2>
<h3>The Name in the CAcert login account</h3>
<p lang="en-AU">At least one Name is recorded in the
CAcert login
account. The Name is recorded as a string of (encoded) characters.</p>
<p lang="en-AU">At least one individual Name is recorded
in the
CAcert login account. The Name is recorded as a string of characters,
encoded in <span lang="en-US">unicode</span>
transformation format.</p>
<p lang="en-AU">A Name should be as fully written in a
government-issued identity document (ID). A Name should be as complete
as possible, e.g. not abbreviated, no transliteration of characters in
the Name.</p>
government-issued identity document (ID). A Name should be as
complete as possible, that is not abbreviated, no transliteration of
characters in the Name.</p>
<p lang="en-AU">A Name in the CAcert login account, which
has reached the applicable level of 50 Assurance Point is defined as an
Assured Name. AN Assured Name can be used in a certificate issued by
CAcert. A Member with at least one Assured Name has reached the Assured
has reached
the applicable level of 50 Assurance Point is defined as an Assured
Name. An Assured Name can be used in a certificate issued by CAcert.
A Member with at least one Assured Name has reached the Assured
Member status.</p>
<h3>Multiple Names and variations</h3>
<p>A Member may have multiple Names or multiple variations of a
Name.
For example, married name, variations of initials of first or middle
names, abbreviation of a first name, different language or country
variations and transliterations of characters in a name.&nbsp;</p>
<p>The login
account may record multiple Names.&nbsp;Each of the Assured Names
can be selected to be used in a
certificate issued by CAcert.</p>
<h3><strike>FOLLOWING GOES TO
ASSURER
HANDBOOK</strike></h3>
variations and transliterations of characters in a name.</p>
<p>The login account may record multiple Names. Each of the
Assured
Names can be selected to be used in a certificate issued by CAcert.</p>
<h3><strike>FOLLOWING GOES TO ASSURER HANDBOOK</strike></h3>
<h3><strike>Comparison of names</strike></h3>
<p><strike><a href="http://en.wikipedia.org/wiki/Transliteration" target="_blank">Transliteration</a>
of characters as defined in the transliteration character table (<a href="http://svn.cacert.org/CAcert/Policies/transtab.utf" target="_blank">UTF
@ -185,7 +182,7 @@ Transtab</a>) for names is permitted, but the result must be
7-bit
ASCII for the full name. Transliteration is one way and is towards
7-bit ASCII. Transliteration is a way to compare two names. However
transliteration of a Name makes the Name less discriminative.&nbsp;</strike></p>
transliteration of a Name makes the Name less discriminative.</strike></p>
<p><strike>In general names are handled case insensitively.</strike></p>
<p><strike>Abbreviation of second given name(s), middle
name(s),
@ -195,24 +192,22 @@ the first given name in the ID document is abbreviated, the first
given name in the web account Name may be abbreviated. Abbreviation
of a name makes the name less discriminative.</strike></p>
<p><strike>A Name on an ID which has initials
(abbreviations) for titles,
name extensions and given names, and/or transliterations as defined in
the transliteration table can be taken into account for assurance for a
Name in the account which is not abbreviated or transliterated.</strike></p>
(abbreviations) for
titles, name extensions and given names, and/or transliterations as
defined in the transliteration table can be taken into account for
assurance for a Name in the account which is not abbreviated or
transliterated.</strike></p>
<p><strike>Titles and name extensions in the name of an
individual
may be omitted.</strike></p>
<p><strike>The assurance ambition is to <font color="#000000">pursue</font>
a highly discriminative assured Name in the account. The ambition is to
have only a Name
in the account which has no abbreviation(s), no transliteration and is
case
<font color="#000000">sensitive</font>.</strike></p>
<h3><strike>FOLLOWING GOES TO
Certficate Implementation Policy </strike>
<p><strike>The assurance ambition is to pursue
a highly discriminative assured Name in the account. The ambition is
to have only a Name in the account which has no abbreviation(s), no
transliteration and is case sensitive.</strike></p>
<h3><strike>FOLLOWING GOES TO Certficate
Implementation Policy </strike>
</h3>
<h3><strike>Names on the certificate
issued by CAcert</strike></h3>
<h3><strike>Names on the certificate issued by CAcert</strike></h3>
<p><strike>The Certificate Implementation Policy (<a href="http://svn.cacert.org/CAcert/Policies/CertificateImplementationPolicy.html" target="_blank">CIP</a>)
will define the fields added by CAcert on the issued certificate on
request of the Member.</strike></p>
@ -222,13 +217,11 @@ issued certificate is dependent on the assurance of the Name in the
web account. Abbreviation and transliteration handling in the CN is
defined in the Certificate Implementation Policy and is similar to
the name comparison as defined in this policy. However the Common
Name may become less discriminative <font color="#000000">as</font><font color="#000000">
than</font> the assured Name as the unique certificate serial
number
will lead to the account of the individual in a unique way, and in
this way to the Name and email address of the individual or
organisation. The first given name in the Common Name may be
abbreviated on request.</strike></p>
Name may become less discriminative as than
the assured Name as the unique certificate serial number will lead to
the account of the individual in a unique way, and in this way to the
Name and email address of the individual or organisation. The first
given name in the Common Name may be abbreviated on request.</strike></p>
<p><strike>The certificate issued by CAcert can have on
request of
the Member the SubjAltName field. The name as defined by the Member
@ -322,25 +315,25 @@ is not checked by CAcert.</strike></p>
</tbody>
</table>
<p align="center"><strike><font size="2">table
Examples of names in different contexts</font></strike></p>
Examples of names in
different contexts</font></strike></p>
<h3>Status and Capabilities</h3>
<p>A Member has the following capabilities derived from an
Assurance:
</p>
<p>A Member has the following capabilities derived from
Assurance: </p>
<table border="1" cellpadding="5" cellspacing="0">
<tbody>
<tr>
<td width="10%">
<p align="left"><em>Minimum Assurance Points</em></p>
<p align="left"><i>Minimum Assurance Points</i></p>
</td>
<td width="15%">
<p align="left"><em>Capability</em></p>
<p align="left"><i>Capability</i></p>
</td>
<td width="15%">
<p align="left"><i>Status</i></p>
</td>
<td width="60">
<p align="left"><em>Comment</em></p>
<td width="60%">
<p align="left"><i>Comment</i></p>
</td>
</tr>
<tr valign="top">
@ -348,7 +341,7 @@ Assurance:
<p align="center">0</p>
</td>
<td>
<p align="left">assurance of a Name</p>
<p align="left">Request Assurance</p>
</td>
<td>
<p align="left">Prospective Member</p>
@ -397,7 +390,7 @@ assured to 50 Assurance Points or more</p>
<p align="left">become an Assurer</p>
</td>
<td>
<p align="left">prospective Assurer</p>
<p align="left">Prospective Assurer</p>
</td>
<td>
<p align="left">Assured to 100 Assurance Points (or
@ -412,17 +405,13 @@ Assurance Capability</i></font></p>
for an
assurance process.</p>
<p>The CAcert Policy Statement (<a href="http://svn.cacert.org/CAcert/policy.htm" target="_blank">CPS</a>)
and other policies may list
other capabilities that rely on Assurance Points. </p>
<p>If there is negative confidence the Assurer should consider
filing
a dispute.</p>
and other policies may list other capabilities that rely on Assurance
Points. </p>
<h2>3. The Assurer</h2>
<p>An Assurer is a Member with the following: </p>
<ul>
<li>
<p>Is assured to a minimum
of 100 Assurance Points; </p>
<p>Is assured to a minimum of 100 Assurance Points; </p>
</li>
<li>
<p>Has passed the CAcert Assurer Challenge. </p>
@ -434,28 +423,26 @@ behalf of the Assurance Officer. </p>
<p>The Assurer is obliged to: </p>
<ul>
<li>
<p>Follow this Assurance
Policy; </p>
<p>Follow this Assurance Policy; </p>
</li>
<li>
<p>Follow any additional
rules of detail laid out by the CAcert Assurance Officer; </p>
<p>Follow any additional rules of detail laid out by the
CAcert Assurance Officer; </p>
</li>
<li>
<p>Be guided by the CAcert <a href="http://wiki.cacert.org/wiki/AssuranceHandbook2" target="_blank">Assurance Handbook</a> in their
judgement; </p>
</li>
<li>
<p>Make a good faith
effort at identifying and verifying Members; </p>
<p>Make a good faith effort at identifying and verifying
Members; </p>
</li>
<li>
<p>Maintain the
documentation on each Assurance; </p>
<p>Maintain the documentation on each Assurance; </p>
</li>
<li>
<p>Deliver documentation
to Arbitration, or as otherwise directed by the Arbitrator; </p>
<p>Deliver documentation to Arbitration, or as otherwise
directed by the Arbitrator; </p>
</li>
<li>
<p>Keep up-to-date with developments within the CAcert
@ -469,37 +456,32 @@ Member. </p>
<p>The process consists of: </p>
<ol>
<li>
<p>Voluntary agreement by
both Assurer and Member or <font color="#000000">Prospective</font>
Member to conduct
the Assurance; </p>
<p>Voluntary agreement by both Assurer and Member or
Prospective Member to conduct the Assurance; </p>
</li>
<li>
<p>Personal meeting of
Assurer and Member or <font color="#000000">Prospective</font>
<p>Personal meeting of Assurer and Member or Prospective
Member; </p>
</li>
<li>
<p>Recording of essential
details on CAcert Assurance Programme form; </p>
<p>Recording of essential details on CAcert Assurance
Programme form; </p>
</li>
<li>
<p>Examination of Identity
documents by Assurer and verification of recorded details (the Name(s)
and
Secondary Distinguishing Feature, e.g., DoB); </p>
<p>Examination of Identity documents by Assurer and
verification of recorded details (the Name(s) and Secondary
Distinguishing Feature, e.g., DoB); </p>
</li>
<li>
<p>Allocation of Assurance
Points by Assurer; </p>
<p>Allocation of Assurance Points by Assurer; </p>
</li>
<li>
<p>Optional: supervision
of reciprocal Assurance made by Assuree (Mutual Assurance); </p>
<p>Optional: supervision of reciprocal Assurance made by
Assuree (Mutual Assurance); </p>
</li>
<li>
<p>Safe keeping of the CAcert Assurance Programme forms by
Assurer. </p>
<p>Safe keeping of the CAcert Assurance Programme (<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>)
forms by Assurer. </p>
</li>
</ol>
<h3>Mutual Assurance</h3>
@ -516,9 +498,8 @@ the
Assurer, and reduces any sense of power. It is also an important aid
to the assurance training for future Assurers. </p>
<h3>Evidence of Assurer status</h3>
<p>On the
question of providing evidence that one is an Assurer, CAcert Policy
Statement (<a href="http://svn.cacert.org/CAcert/policy.htm#p3.2" target="_blank">CPS</a>)
<p>On the question of providing evidence that one is an Assurer,
CAcert Policy Statement (<a href="http://svn.cacert.org/CAcert/policy.htm#p3.2" target="_blank">CPS</a>)
says:<em> "The level at which each Member is Assured is public
data. The number of Assurance Points for each Member is not
published.</em>.".</p>
@ -538,16 +519,13 @@ the maximum means that the Assurer is 100% confident in the
information presented: </p>
<ul>
<li>
<p>Detail on form, system,
documents, person in accordance; </p>
<p>Detail on form, system, documents, person in accordance; </p>
</li>
<li>
<p>Sufficient quality
identity documents have been checked; </p>
<p>Sufficient quality identity documents have been checked; </p>
</li>
<li>
<p>Assurer's familiarity
with identity documents; </p>
<p>Assurer's familiarity with identity documents; </p>
</li>
<li>
<p>The Assurance Statement is confirmed. </p>
@ -573,13 +551,19 @@ maximum of Assurance Points per Name; a (new) Member new to the
assurance process should allocate <em>zero</em> Assurance
Points
until they get some confidence in what is happening.</p>
<p>To
reach 50 Assurance Points for a Name the Member must have had at least
two assurances on that Name: the Assured Member has an Assured
Name.&nbsp; To reach 100 Assurance Points, at
least one Name of the Assured Member must have been assured at least
three
times. </p>
<p><strike>To reach 50 Assurance Points for a Name the
Member must
have had at least two assurances on that Name: the Assured Member has
at least one Name assured, the Assured Name. To reach 100 Assurance
Points, at least one Name of the Assured Member must have been
assured at least three times.</strike></p>
<p style="text-decoration: none;">The maximum number of
Assurance
Points, which can be allocated for a Name assurance under this policy
and subsidiary policies is 50 Assurance Points.</p>
<p>If there is negative confidence the Assurer should consider
filing
a dispute.</p>
<h3>Experience Points</h3>
<p>The maximum number of Assurance Points that may be awarded by
an
@ -663,31 +647,28 @@ recommendation from the Assurance Officer. </p>
<p>Experience Points are not to be confused with Assurance
Points. </p>
<h3>CAcert Assurance Programme (CAP) form</h3>
<p>The CAcert Assurance Programme&nbsp;(<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>)
form requests the
following
details of each Member or Prospective Member: </p>
<p>The CAcert Assurance Programme (<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>)
form requests the following details of each Member or Prospective
Member: </p>
<ul>
<li>
<p>Name(s), as recorded in
the on-line account; </p>
<p>Name(s), as recorded in the on-line account; </p>
</li>
<li>
<p>Primary email address,
as recorded in the on-line account; </p>
<p>Primary email address, as recorded in the on-line account;
</p>
</li>
<li>
<p>Secondary
Distinguishing Feature, as recorded in the on-line account (normally,
date of birth); </p>
<p>Secondary Distinguishing Feature, as recorded in the
on-line account (normally, date of birth); </p>
</li>
<li>
<p>Statement of agreement
with the CAcert Community Agreement (CCA); </p>
<p>Statement of agreement with the CAcert Community
Agreement; </p>
</li>
<li>
<p>Permission to the
Assurer to conduct the Assurance (required for privacy reasons); </p>
<p>Permission to the Assurer to conduct the Assurance
(required for privacy reasons); </p>
</li>
<li>
<p>Date and signature of the Assuree. </p>
@ -696,21 +677,20 @@ Assurer to conduct the Assurance (required for privacy reasons); </p>
<p>The CAP form requests the following details of the Assurer: </p>
<ul>
<li>
<p>At least one Name as
recorded in the on-line account of the Assurer; </p>
<p>At least one Name as recorded in the on-line account of
the Assurer; </p>
</li>
<li>
<p>Assurance Points for
each Name in the identity document(s); </p>
<p>Assurance Points for each Name in the identity
document(s); </p>
</li>
<li>
<p>Statement of Assurance;
</p>
<p>Statement of Assurance; </p>
</li>
<li>
<p>Optional: If the
Assurance is reciprocal, then the Assurer's email address and Secondary
Distinguishing Feature are required as well; </p>
<p>Optional: If the Assurance is reciprocal, then the
Assurer's email address and Secondary Distinguishing Feature are
required as well; </p>
</li>
<li>
<p>Date, location of Assurance and signature of Assurer. </p>
@ -724,37 +704,34 @@ Officer
with the following responsibilities: </p>
<ul>
<li>
<p>Reporting to the
Committee and advising on all matters to do with Assurance; </p>
<p>Reporting to the Committee and advising on all matters to
do with Assurance; </p>
</li>
<li>
<p>Training and testing of
Assurers, in association with the Education Team; </p>
<p>Training and testing of Assurers, in association with the
Education Team; </p>
</li>
<li>
<p>Updating this Assurance
Policy, under the process established by Policy on Policy (<a href="https://www.cacert.org/policy/PolicyOnPolicy.php" target="_blank">PoP</a>); </p>
<p>Updating this Assurance Policy, under the process
established by Policy on Policy (<a href="https://www.cacert.org/policy/PolicyOnPolicy.php" target="_blank">PoP</a>); </p>
</li>
<li>
<p>Management of all
Subsidiary Policies (see below) for Assurances, under Policy on Policy;
</p>
<p>Management of all Subsidiary Policies (see below) for
Assurances, under Policy on Policy; </p>
</li>
<li>
<p>Managing and creating
rules of detail or procedure where inappropriate for policies; </p>
<p>Managing and creating rules of detail or procedure where
inappropriate for policies; </p>
</li>
<li>
<p>Incorporating rulings
from Arbitration into policies, procedures or guidelines; </p>
<p>Incorporating rulings from Arbitration into policies,
procedures or guidelines; </p>
</li>
<li>
<p>Assisting the
Arbitrator in any requests; </p>
<p>Assisting the Arbitrator in any requests; </p>
</li>
<li>
<p>Managing the Assurer
Handbook; </p>
<p>Managing the Assurer Handbook; </p>
</li>
<li>
<p>Maintaining a sufficient strength in the Assurance process
@ -766,9 +743,9 @@ Handbook; </p>
additional
processes. Each must be covered by an approved Subsidiary Policy
(refer to Policy on Policy =&gt; CAcert Official Document COD1).
Subsidiary Policies specify
any additional tests of knowledge required and variations to process
and documentation, within the general standard stated here. </p>
Subsidiary Policies specify any additional tests of knowledge
required and variations to process and documentation, within the
general standard stated here. </p>
<h3>Standard</h3>
<p>Each Subsidiary Policy must augment and improve the general
standards in this Assurance Policy. It is the responsibility of each
@ -778,9 +755,10 @@ areas of risk. </p>
<h3>High Risk Applications</h3>
<p>In addition to the Assurance or Experience Points ratings set
here
in and in other policies, Assurance Officer or policies can designate
certain applications as high risk. If so, additional measures may be
added to the Assurance process that specifically address the risks.</p>
in and in other policies, Assurance Officer or policies can
designate certain applications as high risk. If so, additional
measures may be added to the Assurance process that specifically
address the risks.</p>
<p>Additional measures may include additional information.
Additional
information can be required in process of assurance: </p>
@ -791,13 +769,12 @@ information can be required in process of assurance: </p>
</li>
<li><dd> photo of User; </dd>
</li>
<li><dd style="margin-bottom: 0.5cm;"> address of
User. </dd>
<li><dd> address of User. </dd>
</li>
</ul>
<p>Additional Information is to be kept by Assurer, attached to
CAcert Assurance Programme (<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>) form. Assurance Points
allocation by this assurance is unchanged.
CAcert Assurance Programme (<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>)
form. Assurance Points allocation by this assurance is unchanged.
User's CAcert login account should be annotated to record type of
additional information: </p>
<ul>
@ -805,14 +782,13 @@ additional information: </p>
<p>Arbitration: </p>
<ul>
<li>
<p>Member to
participate in Arbitration. This confirms their acceptance of the forum
as well as trains in the process and import </p>
<p>Member to participate in Arbitration. This confirms
their acceptance of the forum as well as trains in the process and
import </p>
</li>
<li>
<p>Member to file
Arbitration to present case. This allows Arbitrator as final authority;
</p>
<p>Member to file Arbitration to present case. This
allows Arbitrator as final authority; </p>
</li>
</ul>
</li>
@ -820,12 +796,11 @@ Arbitration to present case. This allows Arbitrator as final authority;
<p>Additional training; </p>
</li>
<li>
<p>Member to be Assurer
(at least 100 Assurance Points and passed Assurer Challenge); </p>
<p>Member to be Assurer (at least 100 Assurance Points and
passed Assurer Challenge); </p>
</li>
<li>
<p>Member agrees to
additional specific agreement(s); </p>
<p>Member agrees to additional specific agreement(s); </p>
</li>
<li>
<p>Additional checking/auditing of systems data by CAcert
@ -846,14 +821,13 @@ internal purposes. </p>
circumstances: </p>
<ul>
<li>
<p>Under Arbitrator
ruling, in a duly filed dispute (<a href="http://www.cacert.org/policy/DisputeResolutionPolicy.html" target="_blank">Dispute Resolution Policy</a>
<p>Under Arbitrator ruling, in a duly filed dispute (<a href="http://www.cacert.org/policy/DisputeResolutionPolicy.html" target="_blank">Dispute Resolution Policy</a>
=&gt; COD7); </p>
</li>
<li>
<p>An Assurer in the
process of an Assurance, as permitted on the CAcert Assurance Programme
(CAP) form; </p>
<p>An Assurer in the process of an Assurance, as permitted on
the CAcert Assurance Programme (<a href="http://www.cacert.org/cap.php" target="_blank">CAP</a>)
form; </p>
</li>
<li>
<p>CAcert support administration and CAcert systems