From 57a16f61c8766d2173cd689cafc36f6a3d7ddf5e Mon Sep 17 00:00:00 2001
From: Ian Grigg
- 1 Introduction
+ 1 Introduction
@@ -76,11 +76,11 @@ DRC-A.1.
CCS may be seen as the index to systems audit under DRC.
This CCS creates a list of Primary or "root" documents known as Policies. @@ -101,7 +101,7 @@ http://wiki.cacert.org/PolicyDecisions.
-@@ -134,27 +134,27 @@ documents of higher status (DRAFT or POLICY). Copies should be eliminated where not being worked on.
-CAcert policies are required to be owned / transferred to CAcert. See PoP 6.2.
-Critical systems are defined by Security Policy.
-See Security Policy.
-Control of Hardware is the ultimate responsibility of the Board of CAcert Inc. @@ -165,9 +165,9 @@ The ownership responsibility is delegated by agreement to Oophaga.
-Critical software is defined by Security Policy. @@ -181,11 +181,11 @@ Critical software is defined by Security Policy.
See Security Policy.
-CAcert owns its code, or requires control over open source code in use @@ -219,35 +219,35 @@ and a registry of software under approved open source licences. -
Root Certificates are to be listed in the CPS.
-Creation and usage of Root Certificates is to be controlled by Security Policy.
-See Security Policy.
-Logs are defined by Security Policy.
-Changes to Hardware, Software and Root Certificates are logged according to Security Policy.
-See Security Policy.