From c6dba8bd4d121bdc0230dc030cbaff8d071c2f6c Mon Sep 17 00:00:00 2001 From: Ian Grigg Date: Mon, 18 Aug 2008 14:46:39 +0000 Subject: [PATCH] committed the last block of changes as per rough consensus on policy group git-svn-id: http://svn.cacert.org/CAcert/Policies@911 14b1bab8-4ef6-0310-b690-991c95c89dfd --- AssurancePolicy.html | 195 +++++++++++++++++++------------------------ 1 file changed, 88 insertions(+), 107 deletions(-) diff --git a/AssurancePolicy.html b/AssurancePolicy.html index c039788..d1adf69 100644 --- a/AssurancePolicy.html +++ b/AssurancePolicy.html @@ -23,12 +23,12 @@ TH P { color: #000000 }

Assurance Policy for CAcert Community Members

-

CAcert Policy Status +

CAcert Policy Status
Editor: Teus Hagen
Creation date: 2008-05-30
Last change by: Iang
-Last change date: 2008-07-14 18:00 MET
+Last change date: 2008-08-18 14:00 MET
Status: DRAFT p20080712.1
Next status: POLICY 2008-10-12

@@ -47,57 +47,51 @@ Community (Assurer) identifies an individual (Assuree)
Prospective Member
An individual who participates in the process of Assurance, -but has not yet created successfully a CAcert login account.
+but has not yet created a CAcert login account.
Name
A Name is the full name of an individual. -
with all -components of that name. -(Title(s), first name(s), family name(s), name extensions, -abbreviation of name(s), etc.
-The Name is technically spoken a string exactly taken e.g. from a -governmental issued photo ID.)
Secondary Distinguishing Feature
-
An additional personal data item of the Member +
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).) - 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.
-(Currently this is the date of birth (DoB) of the individual. ) +(Currently this is the Date of Birth (DoB).)

0.2. The CAcert Web of Trust

-

In face-to-face meetings, +

+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 Web-of-Trust (or "WoT"). -
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 Web-of-Trust

-

CAcert explicitly chooses to meet its various goals by +into a global Web-of-Trust (or "WoT"). +

+

+CAcert explicitly chooses to meet its various goals by construction of a Web-of-Trust of all Members. - This is done by --face-to-face meetings, identifying and sharing claims in a network. -Maintaining a sufficient strength of the Web-of-Trust is a -high-level objective of the Assurance process.

+

+

0.3. Related Documentation

-

Documentation on Assurance is split between this Assurance -Policy -(AP) and the Assurance +

+Documentation on Assurance is split between this +Assurance Policy (AP) and the +Assurance Handbook. The policy is controlled by Configuration Control -Specification (CCS) -under Policy on Policy (PoP) +Specification +(CCS) +under Policy on Policy +(PoP) 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.

-

See also Organisation Assurance Policy (OAP) +experience and circumstances. It is also more readable. +

+

+See also Organisation Assurance Policy (OAP) and CAcert Policy Statement (CPS).

+

1. Assurance Purpose

The purpose of Assurance is to add confidence in the Assurance Statement made by the CAcert Community of a Member.

@@ -105,11 +99,11 @@ in the Assurance Statement made by the CAcert Community of a Member.

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.

+

1.1.The Assurance Statement

-

The Assurance Statement makes the following claims -about a person: -
The following claims can be made about a person who is -assured: +

+The Assurance Statement makes the following claims +about a person:

  1. @@ -132,7 +126,7 @@ by the CAcert Community Agreement;

  2. Some personal details of the Member are known to CAcert: the individual Name(s), primary and other listed individual email -address(es), secondary distinguishinged feature (e.g. DoB).

    +address(es), secondary distinguishing feature (e.g. DoB).

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.

2. The Member

-

2.1. The Member's Name in the CAcert login account

-

At least one individual Name is recorded in the Member's -CAcert login account. The general standard of a Name is: +

2.1. The Member's Name

+

+At least one individual Name is recorded in the Member's +CAcert login account. The general standard of a Name is:

2.2. Multiple Names and variations

- 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.

+and transliterations of characters in a name. +

-

-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.

-

The login account may record multiple Names. Each of the Assured -Names can be selected to be used in a certificate issued by CAcert. -

 + + +

2.3. Status and Capabilities

- -

A Name which has reached +

+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.

- - -

-A Member has the following capabilities derived from -Assurance:

+Additional capabilities are described in Table 1. +

Table 1: @@ -440,17 +422,21 @@ more) on at least one Name, and passing the Assurer Challenge.

-

A Member may check the status of another Member, especially + + +

+A Member may check the status of another Member, especially for an assurance process. - Status may be implied from information in a certificate. The number of Assurance Points for each Member is not published. -

-

The CAcert Policy Statement + +

+The CAcert Policy Statement (CPS) and other policies may list other capabilities that rely on Assurance -Points.

+Points. +

3. The Assurer

An Assurer is a Member with the following:

@@ -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.

- -

4.3. Evidence of Assurer status

-

On the question of providing evidence that one is an Assurer, -CAcert Policy Statement (CPS) -says: "The level at which each Member is Assured is public -data. The number of Assurance Points for each Member is not -published..".

- -

4.3. Assurance Points

The Assurance applies Assurance Points to each Member which measure the increase of confidence in the Statement (above). @@ -580,42 +557,45 @@ information presented:

The Assurance Statement is confirmed.

-

Any lesser confidence should result in less Assurance Points for a +

+Any lesser confidence should result in less Assurance Points for a Name. If the Assurer has no confidence in the information presented, then zero 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 zero -to maximum is guided by the Assurance Handbook +to maximum is guided by the Assurance Handbook and the judgement of the Assurer. - If there is negative confidence the Assurer should consider -filing a dispute.

+filing a dispute. +

Multiple Names should be allocated Assurance Points independently within a single Assurance.

-

A (new) Member who is not an Assurer may award an Assurer in a +

+A Member who is not an Assurer may award an Assurer in a reciprocal process a maximum of 2 Assurance Points, according to -her his -judgement. The Assurer should strive to have the Member allocate -according to the Member's judgement, and stay on the cautious side -a maximum of AssurancePoints per Name ; -the (new) 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 zero Assurance Points -until she gains they gets some confidence in what is happening.

-

In general, for a Member to reach 50 Assurance Points, the Member must +until she gains some confidence in what is happening. +

+

+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. -
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. +at least one Name will have been assured to that level.

- -

To reach 100 Assurance +

+To reach 100 Assurance Points, at least one Name of the Assured Member must have been -assured at least three times.

-

The maximum number of Assurance -Points which can be allocated for an Name Assurance under this policy -and under any act under any -Subsidiary Policy (below) is 50 Assurance Points.

+assured at least three times. +

+

+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. +

+

4.4. Experience Points

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.

+

6.2. High Risk Applications

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.

-

Additional measures may include additional information: +

Additional measures may include: