This page is part of the [[Roots/NewRootsTaskForce|New Roots Task Force]] collection.

== 1. Procedures ==

 1.  technical organisation of roots:
   * [[Roots/Structure]] describes the hierarchy and relationship between the roots
   * [[Roots/Contents]] describes the internal fields in each Roots.
 1.  ceremony for creation of root (s)
   * [[Roots/CreationCeremony]] is open as a place to develop this need
   * [[Roots/TechScript]] is where the geeky arcania can be collected
 1.  storage securely on signing server
 1.  escrow root securely for disaster recovery
   * [[Roots/EscrowAndRecovery]] is open for jotting notes...
 1.  finally, when all is good, start the rollout procedure
   * [[Roots/RolloutProcedure]] is open for jotting notes...
   * of which an important part is [[Roots/TestNewRootCerts]]

The ''works-in-progress'' procedures and guidelines above are included by reference and authorised by SP/SM.  ''If not, fix the SM.''

== 2. Policy ==

There are three major documents:
 1. The [[http://svn.cacert.org/CAcert/Policies/SecurityPolicy.html#9.2|DRAFT Security Policy]] is managed by policy group.
 1. The [[SecurityManual#RootKeyManagement|wip Security Manual]] is the major practices manual containing the detail, authorised by SP.  Team leaders are responsible for it.
 1. The [[http://www.cacert.org/policy/CertificationPracticeStatement.php|CPS]] is managed by policy group.  It defers most issues of Roots to SP.
 1. (not policies but) [[Risk|Risk Assessment Work]] underpins and supports policies and procedures.

== 3. Motions & Decisions ==

The following decisions are additional to the policies (which means they generally do not change the policies, more clarify the practical issues).  They are primarily made by the Board, which has responsibility for the Roots under SP.

 1. [[https://community.cacert.org/board/motions.php?motion=m20100117.3|m20100117.3]]
   . ''RESOLVED, that the existing root may not be used to sign any new sub-roots, and that the board receive reports from affected teams with a view to the issuing of a new offline root with multiple sub-roots.''
 1. [[https://wiki.cacert.org/EmailBoardDecisions2008-09#m20090109.1|m20090109.1]]
   . ''On security measurements on the issue of MD5 use in signature algorithm: ...''
     1. ''stop signing certificates with the Class 3 CAcert Root cert with serial nr 01;''
     1. ''to generate a new Class 3 CAcert root key using the SHA-1 signing algorithm and start signing (intermediate) class 3 certificates with this certificate.''
 1. [[https://wiki.cacert.org/EmailBoardDecisionsUpdateFeb2008#m20081008.1|m20081008.1]]
   . ''Motion to install Root Key Task Force CAcert Sub-Committee: task to have CAcert Root Key and 2 sub keys for assured members and for members certificate signing generated and installed by end of November 2008.''
 1. [[https://wiki.cacert.org/EmailBoardDecisionsUpdateFeb2008#m20080903.3|m20080903.3]]
   . ''If auditor requires or advises a new Root Key for CAcert to be issued, this will take place as soon as appropriate.''
 1. [[https://wiki.cacert.org/EmailBoardDecisionsUpdateFeb2008#m20080901.1|m20080901.1]] notes included ''"reissue CAcert Root Key"''
 1. [[https://wiki.cacert.org/EmailBoardDecisionsUpdateFeb2008#m20080710.2|m20080710.2]]
   . ''have arrangement for critical system access and password to root keys at third party with disclosure instructions such that two signatures of board are required to disclose this information by the third party.''
 1. [[https://wiki.cacert.org/TopMinutes-20070917|TOP 20070917]] This decision had no motion:
   . ''We agree that we have to put in procedures that guarantee the security of the root keys. These procedures are more strict than the previously applied procedures, and obviously did not apply to the old root keys. Therefore, once the new procedures are in place, we will create new root keys and deprecate use of the old keys.''

Note the above is summarised and the full motions may include more important parts.

----
 . CategoryAudit
 . CategoryNewRootsTaskForce