-Author: Ian Grigg
Creation date: 2008-05-30
Status: WIP -2008-05-30
Next status: DRAFT June 2008 -
-
Author: Ian Grigg
Creation date: 2008-05-30
Status: WIP
-2008-05-30
Next status: DRAFT June 2008
-
Definitions of terms: -
-Each Assurance claims a number of Assurance Points, applied to the -assured Member or Member prospect. By combining the Assurances, and -the Assurance Points, CAcert constructs a global Web-of-Trust - or "WoT". -
-CAcert explicitly chooses to meet its various goals by +
+
+
+Author: Ian Grigg
+Creation date: 2008-05-30
+Last change by: Teus Hagen
+Last change date: 2008-07-03 21:12 MET
+Status: WIP
+2008-05-30
+Next status: DRAFT June 2008
Definitions of terms:
+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 +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 for the Web-of-Trust is a -high-level objective of the Assurance process. -
-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)
-policy document regime.
Because Assurance is an active area, much
+high-level objective of the Assurance process.
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)
+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) -and CAcert Policy Statement (CPS). -
-The purpose of Assurance is to add confidence in the -Assurance Statement made by a Member of the CAcert Community. -
-The following claims can be made about a person who is assured: -
-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 (CCA). -
-The Member has a (login) - (web)Account with CAcert's on-line registration and service system. -
-The Member can be determined from - any CAcert certificate issued by the Account. -
-The Member is bound into CAcert's - Arbitration, as defined by the CCA. -
-Some personal details of the Member (Name(s), primary and - other listed email address(es), secondary distinguished feature (eg - DoB)) are known to CAcert. -
-The confidence level of the Assurance Statement is expressed by -the Assurance Points. -
-The primary goal of the Assurance Statement is to meet the needs -of the Relying Party Statement, which latter is found in the -Certification Practice Statement (CPS) -for the express purpose of certificates. -
-When a certificate is issued, some or all of the Assurance -Statement may be incorporated (e.g. full name) or implied (e.g. -comparable name, unique certificate serial number, membership or -status) into the certificate and be part of the Relying Party -Statement. In short, this means that other Members of the +experience and circumstances. It is also more readable.
+See also Organisation Assurance Policy (OAP) +and CAcert Policy Statement (CPS). +
+The purpose of Assurance is to add confidence +in the +Assurance Statement made by the CAcert Community of a Member.
+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.
+The following claims can be made about a person who is +assured:
+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 (CCA);
+The Member has a +(login) account with CAcert's on-line registration and service system;
+The Member can be +determined from any CAcert certificate issued by the Account;
+The Member is bound +into CAcert's Arbitration as defined by the CCA agreement;
+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).
+The confidence level of the Assurance Statement is expressed +by +the Assurance Points.
+The primary goal of the Assurance Statement is for the express +purpose of certificates to meet the +needs +of the Relying Party Statement, which latter is +found in the +Certification Practice Statement (CPS). +
+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 Relying +Party Statement. In short, this means that other Members of +the Community may rely on the information verified by Assurance and found -in the certificate. -
-In particular, certificates are sometimes considered to provide -reliable indications of the Member's Name and eg. email address. The +in the certificate.
+In particular, certificates are sometimes considered to +provide +reliable indications of e.g. the Member's Name and email address. The nature of Assurance, the number of Assurance Points, and other policies and processes should be understood as limitations on any -reliance. -
-In principle the Name in the CAcert web account is
-identical to the name in at least one of the ID document of that
-individual. Names in an ID can differ, so a CAcert account can have
-more as
-than one Name.
The technical form of a Name is a
-string of characters. Each Name should be exactly copied once from a
-governmental-issued photo ID.
A Member can have multiple individual names. 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. Each individual Name -originating from a governmental ID must be assured to the applicable -level of 50 Assurance Points before the (comparable) name can be used -as Common Name in a certificate.
-Transliteration -of characters as defined in the transliteration character table (UTF -Transtab) for names is permitted, but the result must be 7-bit +reliance.
+At least one Name is recorded in the +CAcert login +account. The Name is recorded as a string of (encoded) characters.
+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.
+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 +Member status.
+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.
+Transliteration
+of characters as defined in the transliteration character table (UTF
+Transtab) 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.
In general names are handled case insensitively.
-Abbreviation of second given name(s), middle name(s), titles and -name extensions in the name of an individual to one character and the -dot indicating the abbreviation, is permitted. If 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.
-Titles and name extensions in the name of an individual may be -omitted.
-The assurance ambition is to pursuit
-for pursue a highly
-discriminative assured Name. The ambition is to have a Name in the
-account with no abbreviation(s), no transliteration and case
-sensitive sensitivity.
The Certificate Implementation Policy (CIP) +transliteration of a Name makes the Name less discriminative.
+In general names are handled case insensitively.
Abbreviation of second given name(s), middle
+name(s),
+titles and name extensions in the name of an individual to one
+character and the dot indicating the abbreviation, is permitted. If
+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.
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.
Titles and name extensions in the name of an
+individual
+may be omitted.
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.
The Certificate Implementation Policy (CIP)
will define the fields added by CAcert on the issued certificate on
-request of the Member.
The Common Name and related certificate fields in the issued -certificate is dependent on the assurance of the Name in the web -account. Abbreviation and transliteration handling in the CN is +request of the Member.
+The Common Name and related certificate fields
+in the
+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 as
-than the assured Name as the unique certificate serial number
+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.
The certificate issued by CAcert can have on request of the Member - the SubjAltName field. The name as defined by the Member is not -checked by CAcert.
-|
- name on the ID - |
-
- assured Name in the account - |
-
- name in the certificate request - |
-
- name on the issued certificate - |
-
|---|---|---|---|
|
- Maria Kate Märvel-Java sr - |
-
- Maria K. Maervel-Java - |
-
- M. K. Märvel-Java - |
-
- Maria K. Maervel-Java - |
-
|
- prof. dr. John K. Marvel sr - |
-
- John K. Marvel - |
-
- John K. Marvel - |
-
- John K. Marvel - |
-
|
- Moeria Koete v. Java - |
-
- Möria Kœté von Java - |
-
- Möria K. v. Java - |
-
- Möria K. v. Java - |
-
|
- Jamé de Häring - |
-
- Jame de Haering - |
-
- J. d. Häring - |
-
- J. d. Haering - |
-
|
- Jame d. Haering - |
-
- dr Jamé de Häring - |
-
- John de Haering - |
-
- dr Jamé de Häring - |
-
table -Examples of names in different contexts
-If the governmental ID indicates for part of the Name a
-type (title, first given name, secondary given name(s),
-middlename(s), family name, and/or name extensions) and the Name in
-the web account provides the type of name field attribute, this will
-be assured in the Name account administration.
-
A Member has the following capabilities derived from an Assurance: -
-|
- Minimum Assurance Points - |
-
- Capability - |
-
- Comment - |
-
|
- 0 - |
-
- request unnamed certificates - |
-
- although the Member's details are recorded in the - account, they are not highly assured. - |
-
|
- 50 - |
-
- request named certificates - |
-
- the name and Assurance Statement is assured to 50 - Assurance Points or more - |
-
|
- 100 - |
-
- become an Assurer - |
-
- assured to 100 Assurance Points or more, and other - requirements listed below - |
-
table -Assurance Capability
-The CAcert Policy Statement (CPS) and other policies may list -other capabilities that rely on Assurance Points. -
-An Assurer is a Member with the following: -
-Is assured to a minimum of 100 - Assurance Points; -
-Has passed the Assurer Challenge. -
-The Assurer Challenge is administered by the Education Team on -behalf of the Assurance Officer. -
-The Assurer is obliged to: -
-Follow this Assurance Policy; -
-Follow any additional rules of - detail laid out by the Assurance Officer; -
-Be guided by the Assurance - Handbook in their judgement; -
-Make a good faith effort at - identifying and verifying Members; -
-Maintain the documentation on each - Assurance; -
-Deliver documentation to - Arbitration, or as otherwise directed by the Arbitrator; -
-Keep up-to-date with developments within the CAcert - Community. -
-The Assurer conducts the process of Assurance with each Member. -
-The process consists of: -
-Voluntary agreement by both
- Assurer and Member or prospect
- prospective Member to conduct the Assurance;
-
Personal meeting of Assurer and
- Member or prospect
- prospective Member;
-
Recording of essential details on - CAP form (below); -
-Examination of Identity documents - by Assurer and verification of recorded details (Name(s) and - Secondary Distinguishing Feature, e.g., DoB); -
-Allocation of Assurance Points by - Assurer; -
-Optional: supervision of - reciprocal Assurance made by Assuree (Mutual Assurance); -
-Safe keeping of the CAP forms by Assurer. -
-Mutual Assurance follows the principle of reciprocity. This means +abbreviated on request.
+The certificate issued by CAcert can have on
+request of
+the Member the SubjAltName field. The name as defined by the Member
+is not checked by CAcert.
|
+
|
+
+
|
+
+
|
+
+
|
+
|---|---|---|---|
|
+
|
+
+
|
+
+
|
+
+
|
+
|
+
|
+
+
|
+
+
|
+
+
|
+
|
+
|
+
+
|
+
+
|
+
+
|
+
|
+
|
+
+
|
+
+
|
+
+
|
+
|
+
|
+
+
|
+
+
|
+
+
|
+
table
+Examples of names in different contexts
A Member has the following capabilities derived from an +Assurance: +
+|
+ Minimum Assurance Points + |
+
+ Capability + |
+
+ Status + |
+
+ Comment + |
+
|
+ 0 + |
+
+ assurance of a Name + |
+
+ Prospective Member + |
+
+ Individual taking part of an +Assurance, who does not have created a CAcert login account (yet). The +allocation of Assurance Points is awaiting login account creation. + |
+
|
+ 0 + |
+
+ request unnamed certificates + |
+
+ Member + |
+
+ Although the Member's details are +recorded in the account, they are not highly assured. + |
+
|
+ 50 + |
+
+ request named certificates + |
+
+ Assured Member + |
+
+ Statements of Assurance: the Name is +assured to 50 Assurance Points or more + |
+
|
+ 100 + |
+
+ become an Assurer + |
+
+ prospective Assurer + |
+
+ Assured to 100 Assurance Points (or +more) on at least one Name, and passing the Assurer Challenge. + |
+
table +Assurance Capability
+A Member may check the status of another Member, especially +for an +assurance process.
+The CAcert Policy Statement (CPS) +and other policies may list +other capabilities that rely on Assurance Points.
+If there is negative confidence the Assurer should consider +filing +a dispute.
+An Assurer is a Member with the following:
+Is assured to a minimum +of 100 Assurance Points;
+Has passed the CAcert Assurer Challenge.
+The Assurer Challenge is administered by the Education Team on +behalf of the Assurance Officer.
+The Assurer is obliged to:
+Follow this Assurance +Policy;
+Follow any additional +rules of detail laid out by the CAcert Assurance Officer;
+Be guided by the CAcert Assurance Handbook in their +judgement;
+Make a good faith +effort at identifying and verifying Members;
+Maintain the +documentation on each Assurance;
+Deliver documentation +to Arbitration, or as otherwise directed by the Arbitrator;
+Keep up-to-date with developments within the CAcert +Community.
+The Assurer conducts the process of Assurance with each +Member.
+The process consists of:
+Voluntary agreement by +both Assurer and Member or Prospective +Member to conduct +the Assurance;
+Personal meeting of +Assurer and Member or Prospective +Member;
+Recording of essential +details on CAcert Assurance Programme form;
+Examination of Identity +documents by Assurer and verification of recorded details (the Name(s) +and +Secondary Distinguishing Feature, e.g., DoB);
+Allocation of Assurance +Points by Assurer;
+Optional: supervision +of reciprocal Assurance made by Assuree (Mutual Assurance);
+Safe keeping of the CAcert Assurance Programme forms by +Assurer.
+Mutual Assurance follows the principle of reciprocity. This +means that the Assurance may be two-way, and that each member participating in the Assurance procedure should be able to show evidence of their -identity to the other. -
-In the event that an Assurer is assured by a Member who is not +identity to the other.
+In the event that an Assurer is assured by a Member who is not certified as an Assurer, the Assurer supervises the Assurance -procedure and process, and is responsible for the results. -
-Reciprocity maintains a balance between the (new) member and the +procedure and process, and is responsible for the results.
+Reciprocity maintains a balance between the (new) member and +the Assurer, and reduces any sense of power. It is also an important aid -to the assurance training for future Assurers. -
-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
+to the assurance training for future Assurers.
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..". -
-The Assurance applies Assurance Points to each Member which +published..".
+The Assurance applies Assurance Points to each Member which measure the increase of confidence in the Statement (above). Assurance Points should not be interpreted for any other purpose. -Note that, even though they are sometimes referred to as Web-of-Trust -(Assurance) Points, or Trust Points, the meaning of the word -'Trust' is not well defined. -
-Assurance Points Allocation.
An Assurer can allocate
-a number of Assurance Points to the Member according to the Assurer's
+Note that, even though they are sometimes referred to as Web-of-Trust
+(Assurance) Points, or Trust Points, the meaning
+of the word
+'Trust' is not well defined.
Assurance Points Allocation
+An Assurer can allocate a
+number of Assurance Points to the Member according to the Assurer's
experience (Experience Point system, see below). The allocation of
the maximum means that the Assurer is 100% confident in the
-information presented:
-
Detail on form, system, documents, - person in accordance; -
-Sufficient quality identity - documents have been checked; -
-Assurer's familiarity with - identity documents; -
-The Assurance Statement is confirmed. -
-Any lesser confidence should result in less Assurance Points for a +information presented:
+Detail on form, system, +documents, person in accordance;
+Sufficient quality +identity documents have been checked;
+Assurer's familiarity +with identity documents;
+The Assurance Statement is confirmed.
+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 and the judgement of the Assurer. -
-Multiple Names should be allocated separately in a single
-Assurance. That is, the Assurer may allocate the maximum to
-one Name, half that amount to another Name, and zero to a third Name.
-
A (new) Member who is not an Assurer may award an Assurer in a +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 +and the +judgement of the Assurer.
+Multiple Names should be allocated separately in a single +Assurance.
+A (new) Member who is not an Assurer may award an Assurer in a reciprocal process a maximum of 2 Assurance Points, according to 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 Assurance Points per Name; a (new) Member new to the -assurance process should allocate zero Assurance Points -until they get some confidence in what is happening.
-Each Name of a Member must have had at least two assurances to -reach 50 Assurance Points per Name. To reach 100 Assurance Points, at -least one Name of the Member must have been assured at least three -times. -
-No Assurance process can give more than 50 Assurance
-Points per Name. This means that to reach 50 Assurance Points
-(certificate with a Name), a Member must have been assured at least
-once. To reach 100 Assurance Points, at least one Name of the Member
-must have been assured at least twice.
-
The maximum number of Assurance Points that may be awarded by an -Assurer is determined by the Experience Points of the Assurer. -
-|
- Assurer's Experience Points - |
-
- Allocatable Assurance Points - |
-
|
- 0 - |
-
- 10 - |
-
|
- 10 - |
-
- 15 - |
-
|
- 20 - |
-
- 20 - |
-
|
- 30 - |
-
- 25 - |
-
|
- 40 - |
-
- 30 - |
-
|
- >=50 - |
-
- 35 - |
-
table -Maximum of Assurance Points
-
-
An Assurer is given a maximum of 2 Experience Points for every +assurance process should allocate zero Assurance +Points +until they get some confidence in what is happening.
+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. 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 that may be awarded by +an +Assurer is determined by the Experience Points of the Assurer.
+|
+ Assurer's Experience Points + |
+
+ Allocatable Assurance Points + |
+
|
+ 0 + |
+
+ 10 + |
+
|
+ 10 + |
+
+ 15 + |
+
|
+ 20 + |
+
+ 20 + |
+
|
+ 30 + |
+
+ 25 + |
+
|
+ 40 + |
+
+ 30 + |
+
|
+ >=50 + |
+
+ 35 + |
+
table +Maximum of Assurance Points +
+An Assurer is given a maximum of 2 Experience Points for every completed Assurance. On reaching Assurer status, the Experience -Points start at 0 (zero). -
-Less Experience Points (1) may be given for mass Assurance events, -where each Assurance is quicker. -
-Additional Experience Points may be granted temporarily or +Points start at 0 (zero).
+Less Experience Points (1) may be given for mass Assurance +events, +where each Assurance is quicker.
+Additional Experience Points may be granted temporarily or permanently to an Assurer by CAcert Inc.'s Committee (board), on -recommendation from the Assurance Officer. -
-Experience Points are not to be confused with Assurance Points. -
-The CAcert Assurance Programme (CAP) form requests the following -details of each Member or prospect Member: -
-Name(s), as recorded in the - on-line account; -
-Primary email address, as recorded - in the on-line account; -
-Secondary Distinguishing Feature, - as recorded in the on-line account (normally, date of birth); -
-Statement of agreement with the - CAcert Community Agreement (CCA); -
-Permission to the Assurer to - conduct the Assurance (required for privacy reasons); -
-Date and signature of the Assuree. -
-The CAP form requests the following details of the Assurer: -
-At least one Name as recorded in - the on-line account of the Assurer; -
-Assurance Points for each Name in - the identity document(s); -
-Statement of Assurance; -
-Optional: If the Assurance is - reciprocal, then the Assurer's email address and Secondary - Distinguishing Feature are required as well. -
-Date, location of Assurance and signature of Assurer. -
-The CAP forms are to be kept at least for 7 years by the Assurer. -
-The Committee (board) of CAcert Inc. appoints an Assurance Officer -with the following responsibilities: -
-Reporting to the Committee and - advising on all matters to do with Assurance; -
-Training and testing of Assurers, - in association with the Education Team; -
-Updating this Assurance Policy, - under the process established by Policy on Policy (PoP); -
-Management of all Subsidiary - Policies (see below) for Assurances, under Policy on Policy ( PoP); -
-Managing and creating rules of - detail or procedure where inappropriate for policies; -
-Incorporating rulings from - Arbitration into policies, procedures or guidelines; -
-Assisting the Arbitrator in any - requests; -
-Managing the Assurer Handbook; -
-Maintaining a sufficient strength in the Assurance process - (web-of-trust) to meet the agreed needs of the Community. -
-The Assurance Officer manages various exceptions and additional +recommendation from the Assurance Officer.
+Experience Points are not to be confused with Assurance +Points.
+The CAcert Assurance Programme (CAP) +form requests the +following +details of each Member or Prospective Member:
+Name(s), as recorded in +the on-line account;
+Primary email address, +as recorded in the on-line account;
+Secondary +Distinguishing Feature, as recorded in the on-line account (normally, +date of birth);
+Statement of agreement +with the CAcert Community Agreement (CCA);
+Permission to the +Assurer to conduct the Assurance (required for privacy reasons);
+Date and signature of the Assuree.
+The CAP form requests the following details of the Assurer:
+At least one Name as +recorded in the on-line account of the Assurer;
+Assurance Points for +each Name in the identity document(s);
+Statement of Assurance; +
+Optional: If the +Assurance is reciprocal, then the Assurer's email address and Secondary +Distinguishing Feature are required as well;
+Date, location of Assurance and signature of Assurer.
+The CAP forms are to be kept at least for 7 years by the +Assurer.
+The Committee (board) of CAcert Inc. appoints an Assurance +Officer +with the following responsibilities:
+Reporting to the +Committee and advising on all matters to do with Assurance;
+Training and testing of +Assurers, in association with the Education Team;
+Updating this Assurance +Policy, under the process established by Policy on Policy (PoP);
+Management of all +Subsidiary Policies (see below) for Assurances, under Policy on Policy; +
+Managing and creating +rules of detail or procedure where inappropriate for policies;
+Incorporating rulings +from Arbitration into policies, procedures or guidelines;
+Assisting the +Arbitrator in any requests;
+Managing the Assurer +Handbook;
+Maintaining a sufficient strength in the Assurance process +(web-of-trust) to meet the agreed needs of the Community.
+The Assurance Officer manages various exceptions and +additional processes. Each must be covered by an approved Subsidiary Policy -(refer to Policy on Policy => COD1). Subsidiary Policies specify +(refer to Policy on Policy => 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. -
-Examples of expected subsidiary policies are these: -
-Remote Assurance Check - (policy); -
-Super Assurer Policy; -
-Junior Assurer Policy; -
-Code Signing Policy; -
-Organisation Assurance Policy and sub-policies per - country or region. -
-Each Subsidiary Policy must augment and improve the general +and documentation, within the general standard stated here.
+Each Subsidiary Policy must augment and improve the general 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. -
-In addition to the Assurance or Experience Points ratings set here +areas of risk.
+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.
-Additional measures may include additional information. Additional -information can be required in process of assurance: -
-Additional Information is to be kept by Assurer, attached to CAP -form. Assurance Points allocation by this assurance is unchanged. -User's CAcert (web)account should be annotated to record type of -additional information: -
-Arbitration: -
-Member to participate in - Arbitration. This confirms their acceptance of the forum as well as - trains in the process and import. -
-Member to file Arbitration to - present case. This allows Arbitrator as final authority. -
-Additional training; -
-Member to be Assurer (>= 100 - Assurance Points and passed Assurer Challenge); -
-Member agrees to additional - specific agreement(s); -
-Additional checking/auditing of systems data by CAcert - support administrators; -
-Applications that might attract additional measures include -code-signing certificates and administration roles. -
-CAcert is a "privacy" organisation, and takes the +added to the Assurance process that specifically address the risks.
+Additional measures may include additional information. +Additional +information can be required in process of assurance:
+Additional Information is to be kept by Assurer, attached to +CAcert Assurance Programme (CAP) form. Assurance Points +allocation by this assurance is unchanged. +User's CAcert login account should be annotated to record type of +additional information:
+Arbitration:
+Member to +participate in Arbitration. This confirms their acceptance of the forum +as well as trains in the process and import
+Member to file +Arbitration to present case. This allows Arbitrator as final authority; +
+Additional training;
+Member to be Assurer +(at least 100 Assurance Points and passed Assurer Challenge);
+Member agrees to +additional specific agreement(s);
+Additional checking/auditing of systems data by CAcert +support administrators.
+Applications that might attract additional measures include +code-signing certificates and administration roles.
+CAcert is a "privacy" organisation, and takes the privacy of its Members seriously. The process maintains the security -and privacy of both parties. -
-Information is collected primarily to make claims within the +and privacy of both parties.
+Information is collected primarily to make claims within the certificates requested by users and to contact the Members. It is used secondarily for training, testing, administration and other -internal purposes. -
-The Member's information can be accessed under these -circumstances: -
-Under Arbitrator ruling, in a duly - filed dispute (Dispute - Resolution Policy => COD7) -
-An Assurer in the process of an - Assurance, as permitted on the CAP form. -
-CAcert support administration and CAcert systems - administration when operating under the authority of Arbitrator or - under CAcert policy. -
-
The Member's information can be accessed under these +circumstances:
+Under Arbitrator +ruling, in a duly filed dispute (Dispute Resolution Policy +=> COD7);
+An Assurer in the +process of an Assurance, as permitted on the CAcert Assurance Programme +(CAP) form;
+CAcert support administration and CAcert systems +administration when operating under the authority of Arbitrator or +under CAcert policy.
+