Configuration-Control Specification

Configuration-Control Specification Status == work-in-progress

Creation date: 20091214
Editor: Iang
Status: 20100227 WIP

1 Introduction

The Configuration-Control Specification (CCS) controls and tracks those documents, processes and assets which are critical to the business, security and governance of the CAcert operations.

This document is the procedure for CCS. This document itself is a component of the CCS. All other documentation and process specified within is derivative and is ruled by the CCS.

2 Documents

2.1 Controlled Document List

This CCS creates a list of Primary or "root" documents.

Primary Documents may authorise other secondary documents under the same process (PoP). Policy Officer manages the controlled documents list containing numbers, locations and versions of all controlled documents. The list is part of this CCS, and is located at

2.2 Change

Overall responsibility for change to documents resides with the policy mailgroup, as specified in Policy on Policy. CAcert Inc., board maintains a veto on new policies while in DRAFT. Fully approved documents (POLICY status) are published on the CAcert website at in plain HTML format.

Pre-approval work (DRAFT status) and working documents (work-in-progress status) are made available on publically-accessible version management systems (rooted at Subversion: wiki:

2.3 Control

CAcert policies are required to be owned / transferred to CAcert. See PoP 6.2.

3 Hardware

3.1 Controlled Hardware List

Critical systems are defined by Security Policy.

3.2 Change

See Security Policy.

3.3 Control

Control of Hardware is the ultimate responsibility of the Board of CAcert Inc. The responsibility for acts with hardware is delegated to Access Engineers and Systems Administrators as per Security Policy. The ownership responsibility is delegated by agreement to Oophaga.

4 Software

4.1 Controlled Software List

Critical software is defined by Security Policy.

4.2 Change

See Security Policy.

4.3 Control

CAcert owns its code, or requires control over open source code in use by means of an approved free and open licence. Such code must be identified and managed by Software Assessment.

Developers transfer full rights to CAcert (in a similar fashion to documents), or organise their contributions under a proper free and open source code regime, as approved by Board. Where code is published (beyond scope of this document) care must be taken not to infringe licence conditions. For example, mingling issues with GPL.

The Software Assessment Team Leader maintains a registry of assignments of title or full licence, and a registry of software under approved open source licences.

5 Logs

5.1 Controlled Logs List

Logs are defined by Security Policy.

5.2 Changes

Changes to Hardware and Software are logged according to Security Policy.

5.3 Archive

See Security Policy.