cacert
/
cacert-policies
8
1
Fork 0
Code Issues 3 Pull Requests 1 Packages Projects Releases Wiki Activity

committed the last block of changes as per rough consensus on policy group

Browse Source 
git-svn-id: http://svn.cacert.org/CAcert/Policies@911 14b1bab8-4ef6-0310-b690-991c95c89dfd
pull/1/head
Ian Grigg 16 years ago
parent a4d8807339
commit c6dba8bd4d
1 changed files with 88 additions and 107 deletions
Show Stats Download Patch File Download Diff File

195
AssurancePolicy.html
Unescape Escape View File

@ -23,12 +23,12 @@ 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>
<p><a href="PolicyOnPolicy.html"><img src="Images/cacert-draft.png" name="graphics1" alt="CAcert Policy Status" align="bottom" border="0" height="33" width="90"></a>
<br>
Editor: Teus Hagen<br>
Creation date: 2008-05-30<br>
Last change by: Iang<br>
Last change date: 2008-07-14 18:00 MET<br>
Last change date: 2008-08-18 14:00 MET<br>
Status: DRAFT p20080712.1<br>
Next status: POLICY 2008-10-12 </p>
@ -47,57 +47,51 @@ Community (Assurer) identifies an individual (<span lang="en-US">Assuree</span>)
</dd>
<dt> <i>Prospective Member</i> </dt>
<dd> An individual who participates in the process of Assurance,
but has not yet created <s>successfully</s> a CAcert login account. </dd>
but has not yet created a CAcert login account. </dd>
<dt> <i>Name</i> </dt>
<dd> A Name is the full name of an individual.
<s> <br> with all
components of that name.
(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.) </s>
</dd>
<dt> <i>Secondary Distinguishing Feature</i>
</dt>
<dd> <b> An additional personal data item of the Member
<dd> An additional personal data item of the Member
that assists discrimination from Members with similar full names.
(Currently this is the Date of Birth (DoB).) </b>
<s> 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. )</s>
(Currently this is the Date of Birth (DoB).)
</dd>
</dl>
<h3><a name="0.2">0.2.</a> The CAcert Web of Trust</h3>
<p><b>In face-to-face meetings,
<p>
In face-to-face meetings,
an Assurer allocates a number of Assurance Points
to the Member being Assured.
CAcert combines the Assurance Points
into a global <i>Web-of-Trust</i> (or "WoT").</b>
<s><br> At each Assurance one allocates a number of Assurance Points,
-applied to the assured Member. By combining the Assurances, and the
-Assurance Points, CAcert constructs a global <i>Web-of-Trust</i> </s> </p>
<p>CAcert explicitly chooses to meet its various goals by
into a global <i>Web-of-Trust</i> (or "WoT").
</p>
<p>
CAcert explicitly chooses to meet its various goals by
construction of a Web-of-Trust of all Members.
<s> This is done by
-face-to-face meetings, identifying and sharing claims in a network.</s>
Maintaining a sufficient strength of the Web-of-Trust is a
high-level objective of the Assurance process. </p>
</p>
<h3><a name="0.3">0.3.</a> Related Documentation</h3>
<p>Documentation on Assurance is split between this Assurance
Policy
(AP) and the <a href="http://wiki.cacert.org/wiki/AssuranceHandbook2" target="_blank">Assurance
<p>
Documentation on Assurance is split between this
Assurance Policy (AP) and the
<a href="http://wiki.cacert.org/wiki/AssuranceHandbook2" target="_blank">Assurance
Handbook</a>. The policy is controlled by Configuration Control
Specification (<a href="http://wiki.cacert.org/wiki/PolicyDrafts/ConfigurationControlSpecification" target="_blank">CCS</a>)
under Policy on Policy (<a href="http://www.cacert.org/policy/PolicyOnPolicy.php" target="_blank">PoP</a>)
Specification
(<a href="http://wiki.cacert.org/wiki/PolicyDrafts/ConfigurationControlSpecification" target="_blank">CCS</a>)
under Policy on Policy
(<a href="http://www.cacert.org/policy/PolicyOnPolicy.php" target="_blank">PoP</a>)
policy document regime. Because Assurance is an active area, much
of the practice is handed over to the Assurance Handbook, which is
not a controlled policy document, and can more easily respond to
experience and circumstances. It is also more readable. </p>
<p>See also Organisation Assurance Policy (<a href="http://www.cacert.org/policy/OrganisationAssurancePolicy.php" target="_blank">OAP</a>)
experience and circumstances. It is also more readable.
</p>
<p>
See also Organisation Assurance Policy (<a href="http://www.cacert.org/policy/OrganisationAssurancePolicy.php" target="_blank">OAP</a>)
and CAcert Policy Statement (<a href="http://svn.cacert.org/CAcert/policy.htm" target="_blank">CPS</a>).
</p>
<h2><a name="1">1.</a> Assurance Purpose</h2>
<p>The purpose of Assurance is to add confidence
in the Assurance Statement made by the CAcert Community of a Member. </p>
@ -105,11 +99,11 @@ in the Assurance Statement made by the CAcert Community of a Member. </p>
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>
<h3><a name="1.1">1.1.</a>The Assurance Statement</h3>
<p><b>The Assurance Statement makes the following claims
about a person</b>:
<s><br>The following claims can be made about a person who is
assured:</s>
<p>
The Assurance Statement makes the following claims
about a person:
</p>
<ol>
<li>
@ -132,7 +126,7 @@ by the CAcert Community Agreement; </p>
<li>
<p>Some personal details of the Member are known to CAcert:
the individual Name(s), primary and other listed individual email
address(es), secondary distinguish<b>ing</b><s>ed</s> feature (e.g. DoB). </p>
address(es), secondary distinguishing feature (e.g. DoB). </p>
</li>
</ol>
<p>The confidence level of the Assurance Statement is expressed by
@ -155,26 +149,24 @@ nature of Assurance, the number of Assurance Points, and other
policies and processes should be understood as limitations on any
reliance. </p>
<h2><a name="2">2.</a> The Member</h2>
<h3><a name="2.1">2.1.</a> The <b>Member's</b> Name <s>in the CAcert login account</s> </h3>
<p>At least one individual Name is recorded in the Member's
CAcert login account. <b>The general standard of a Name is:</b>
<h3><a name="2.1">2.1.</a> The Member's Name </h3>
<p>
At least one individual Name is recorded in the Member's
CAcert login account. The general standard of a Name is:
</p>
<ul>
<li>
<p>The Name should be <b>recorded</b> as <s>fully</s> written in a
government-issued <b>photo</b> identity document (ID).</p>
<p>
The Name should be recorded as written in a
government-issued photo identity document (ID).
</p>
</li>
<li>
<p> <b>The Name should be recorded as completely as possible.
<p>
The Name should be recorded as completely as possible.
That is, including all middle names, any titles and extensions,
without abbreviations, and without transliteration of characters.
</b>
<s><br>
A Name should be as fully written in a
government-issued identity document (ID). A Name should be as
complete as possible, that is not abbreviated, no transliteration of
characters in the Name.
</s></p>
</p>
</li>
<li>
<p>The Name is recorded as a string of characters,
@ -184,7 +176,6 @@ transformation format.</p>
</ul>
<h3><a name="2.2">2.2.</a> Multiple Names and variations</h3>
<p>
<b>
In order to handle the contradictions in the above general standard,
a Member may record multiple Names or multiple variations of a Name
in her CAcert online Account.
@ -192,18 +183,10 @@ Examples of variations include married names,
variations of initials of first or middle names,
abbreviations of a first name,
different language or country variations,
and transliterations of characters in a name.</b></p>
and transliterations of characters in a name.
</p>
<s> <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.</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> </s>
<!--
FOLLOWING GOES TO ASSURER HANDBOOK
<h3><a name=""> </a>Comparison of names</h3>
@ -343,19 +326,18 @@ is not checked by CAcert.</p>
Examples of names in
different contexts</font></p>
-->
<h3><a name="2.3">2.3.</a> Status and Capabilities</h3>
<b>
<p>A Name which has reached
<p>
A Name which has reached
the level of 50 Assurance Points 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.
Additional capabilities are described in Table 1.</p>
</b>
<s><p>
A Member has the following capabilities derived from
Assurance: </p></s>
Additional capabilities are described in Table 1.
</p>
<blockquote>
<p align="left"><font size="2"><i>Table 1:
@ -440,17 +422,21 @@ more) on at least one Name, and passing the Assurer Challenge.</p>
</tbody>
</table>
</blockquote>
<p>A Member may check the status of another Member, especially
<p>
A Member may check the status of another Member, especially
for an assurance process.
<b>
Status may be implied from information in a certificate.
The number of Assurance Points for each Member is not published.
</b>
</p>
<p>The CAcert Policy Statement
<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>
Points.
</p>
<h2><a name="3">3.</a> The Assurer</h2>
<p>An Assurer is a Member with the following: </p>
@ -543,15 +529,6 @@ the
Assurer, and reduces any sense of power. It is also an important aid
to the assurance training for future Assurers. </p>
<s>
<h3>4.3. 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>)
says:<i> "The level at which each Member is Assured is public
data. The number of Assurance Points for each Member is not
published.</i>.".</p>
</s>
<h3><a name="4.3">4.3.</a> Assurance Points</h3>
<p>The Assurance applies Assurance Points to each Member which
measure the increase of confidence in the Statement (above).
@ -580,42 +557,45 @@ information presented: </p>
<p>The Assurance Statement is confirmed. </p>
</li>
</ul>
<p>Any lesser confidence should result in less Assurance Points for a
<p>
Any lesser confidence should result in less Assurance Points for a
Name. If the Assurer has no confidence in the information presented,
then <i>zero</i> Assurance Points may be allocated by the Assurer.
For example, this may happen if the identity documents are totally
unfamiliar to the Assurer. The number of Assurance Points from <i>zero</i>
to <i>maximum </i>is guided by the Assurance Handbook
to <i>maximum</i> is guided by the Assurance Handbook
and the judgement of the Assurer.
<b>
If there is negative confidence the Assurer should consider
filing a dispute.</b></p>
filing a dispute.
</p>
<p>Multiple Names should be allocated Assurance Points
independently within a single Assurance. </p>
<p>A <s>(new)</s> Member who is not an Assurer may award an Assurer in a
<p>
A Member who is not an Assurer may award an Assurer in a
reciprocal process a maximum of 2 Assurance Points, according to
<b>her</b> <s>his</s>
judgement. The Assurer should strive to have the Member allocate
according to the Member's judgement, and stay on the cautious side
<s>a maximum of AssurancePoints per Name</s> ;
the <s>(new)</s> Member new to the assurance process
her judgement. The Assurer should strive to have the Member allocate
according to the Member's judgement, and stay on the cautious side;
the Member new to the assurance process
should allocate <i>zero</i> Assurance Points
until <b>she gains</b> <s>they gets</s> some confidence in what is happening.</p>
<p><b>In general, for a Member to reach 50 Assurance Points, the Member must
until she gains some confidence in what is happening.
</p>
<p>
In general, for a Member to reach 50 Assurance Points, the Member must
have participated in at least two assurances, and
at least one Name will have been assured to that level.</b>
<s><br> 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.</s>
at least one Name will have been assured to that level.
</p>
<p>To reach 100 Assurance
<p>
To reach 100 Assurance
Points, at least one Name of the Assured Member must have been
assured at least three times.</p>
<p>The maximum number of Assurance
Points which can be allocated for an <s>Name</s> Assurance under this policy
and <b>under any act under any</b>
Subsidiary Policy (below) is 50 Assurance Points.</p>
assured at least three times.
</p>
<p>
The maximum number of Assurance
Points which can be allocated for an Assurance under this policy
and under any act under any
Subsidiary Policy (below) is 50 Assurance Points.
</p>
<h3><a name="4.4">4.4.</a> Experience Points</h3>
<p>The maximum number of Assurance Points that may be awarded by
an
@ -801,13 +781,14 @@ standards in this Assurance Policy. It is the responsibility of each
Subsidiary Policy to describe how it maintains and improves the
specific and overall goals. It must describe exceptions and potential
areas of risk. </p>
<h3><a name="6.2">6.2.</a> High Risk Applications</h3>
<p>In addition to the Assurance or Experience Points ratings set
here and in other subsidiary policies, the 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 <s>additional information</s>:
<p>Additional measures may include:
</p>
<ul>
<li>

Write Preview
Loading…
Cancel
Save