Source: https://git.cacert.org/cacert-devel.git/commit/?id=6b5b8453d250a0ec96724b4da5b2f907d3a22512
Timestamp: 2020-07-11 15:30:44
Document Index: 15386505

Matched Legal Cases: ['§1', '§7', '§8', '§2', '§4', '§1', '§9', '§3', '§6', '§2', '§4', '§5', '§9', '§10', '§3', '§3', '§1', '§10', '§3']

Benny Baumann <BenBE@geshi.org> 2014-09-23 22:21:59 +0200
6b5b8453d250a0ec96724b4da5b2f907d3a22512 (patch)
0d497b9b18130ff3cbe4b4b9f395ca069ae56d44
6df5cec76f53a0edc54567ea7cc0a65f14712927 (diff)
b5d6b4b5c7d3b46767d9141970952c420c67f885 (diff)
cacert-devel-6b5b8453d250a0ec96724b4da5b2f907d3a22512.tar.gz
cacert-devel-6b5b8453d250a0ec96724b4da5b2f907d3a22512.tar.xz
cacert-devel-6b5b8453d250a0ec96724b4da5b2f907d3a22512.zip
Merge branch 'bug-1131' into testserver-stable
-rw-r--r-- www/policy/SecurityPolicy.html 699
1 files changed, 277 insertions, 422 deletions
index 632ac5e..f85a35d 100644
@@ -33,63 +33,54 @@ body {
-<img src="images/cacert-policy.png" alt="SP Status - POLICY" style="border-style: none;" height="31" width="88">
+	<img src="images/cacert-policy.png" alt="SP Status - POLICY" style="border-style: none;" height="31" width="88">
-<h2 id="g0.1">INTRODUCTION</h2>
+<h2 id="s1">1. INTRODUCTION</h2>
-<h3 id="g0.1.1">Motivation and Scope </h3>
+<h3 id="s1.1">1.1. Motivation and Scope </h3>
This Security Policy sets out the policy
for the secure operation of the CAcert critical computer systems.
The Committee of CAcert, Inc. (hereafter, "Board")
may add additional components into the Security Manual.
-<h4 id="g0.1.1.1">Covered Personnel </h4>
+<h4 id="s1.1.1">1.1.1. Covered Personnel </h4>
Critical roles are covered.
-<h4 id="g0.1.1.2">Out of Scope </h4>
+<h4 id="s1.1.2">1.1.2. Out of Scope </h4>
Non-critical systems are not covered by this manual,
@@ -98,62 +89,53 @@ found within the security context.
Architecture is out of scope, see CPS#6.2.
-<h3 id="g0.1.2">Principles </h3>
+<h3 id="s1.2">1.2. Principles </h3>
<i>dual control</i> -- at least two individuals must control a task
<i>four eyes</i> -- at least two individuals must participate in a task,
one to execute and one to observe.
<i>redundancy</i> -- no single individual is the only one authorized
<i>escrow</i> -- where critical information (backups, passphrases)
is kept with other parties
<i>logging</i> -- where events are recorded in a file
<i>separation of concerns</i> -- when a core task is split between
two people from different areas
<i>Audit</i> -- where external reviewers do checks on practices and policies
<i>Authority</i> -- every action is authorised by either a policy or by the Arbitrator.
Each task or asset is covered by a variety of protections
deriving from the above principles.
-<h3 id="g0.1.3">Definition of Terms</h3>
+<h3 id="s1.3">1.3. Definition of Terms</h3>
<dt><i>Access Engineer</i> </dt>
A Member who manages the critical hardware,
including maintenance, access control and physical security.
- See §1.1.
+ See &sect;1.1.
<dt><i>Software Assessor</i> </dt>
A Member who reviews patches for security and workability,
signs-off on them, and incorporates them into the repository.
- See §7.2.
+ See &sect;7.2.
<dt><i>Support Engineer</i> </dt>
@@ -161,7 +143,7 @@ deriving from the above principles.
A Member who mans the support list,
and has access to restricted
data through the online interface.
- See §8.
+ See &sect;8.
<dt><i>Systems Administrator</i> </dt>
@@ -172,9 +154,9 @@ deriving from the above principles.
-<h3 id="g0.1.4">Documents and Version control</h3>
+<h3 id="s1.4">1.4. Documents and Version control</h3>
-<h4 id="g0.1.4.1">The Security Policy Document </h4>
+<h4 id="s1.4.1">1.4.1. The Security Policy Document </h4>
This Security Policy is part of the Configuration-Control Specification
for audit purposes (DRC-A.1).
@@ -186,7 +168,7 @@ This policy document says what is done, rather than how to do it.
<b>Some sections are empty, which means "refer to the Manual."</b>
-<h4 id="g0.1.4.2">The Security Manual (Practices) Document </h4>
+<h4 id="s1.4.2">1.4.2. The Security Manual (Practices) Document </h4>
This Policy explicitly defers detailed security practices to the
@@ -208,7 +190,7 @@ they are expected to be documented in the other.
any section heading in the Policy.
-<h4 id="g0.1.4.3">The Security Procedures </h4>
+<h4 id="s1.4.3">1.4.3. The Security Procedures </h4>
The team leaders may from time to time
@@ -221,9 +203,9 @@ SystemAdministration/Procedures</a>.
Each procedure must be referenced explicitly in the Security Manual.
-<h2 id="g0.2">PHYSICAL SECURITY</h2>
+<h2 id="s2">2. PHYSICAL SECURITY</h2>
-<h3 id="g0.2.1">Facility </h3>
+<h3 id="s2.1">2.1. Facility </h3>
CAcert shall host critical servers in a highly secure facility.
@@ -231,9 +213,9 @@ There shall be independent verification of the physical and
-<h3 id="g0.2.2">Physical Assets </h3>
+<h3 id="s2.2">2.2. Physical Assets </h3>
-<h4 id="g0.2.2.1">Computers </h4>
+<h4 id="s2.2.1">2.2.1. Computers </h4>
Computers shall be inventoried before being put into service.
Inventory list shall be available to all
@@ -246,23 +228,23 @@ Each unit shall be distinctly and uniquely identified on all visible sides.
Machines shall be housed in secured facilities (cages and/or locked racks).
-<h4 id="g0.2.2.2">Acquisition </h4>
+<h4 id="s2.2.1.1">2.2.1.1 Acquisition </h4>
Equipment for critical purposes should be acquired
in a way to minimise pre-acquisition security risks.
-<h4 id="g0.2.2.3">Service </h4>
+<h4 id="s2.2.2">2.2.2. Service </h4>
Equipment that is subject to a service security risk
must be retired if service is required.
-See also §2.2.3.3.
+See also &sect;2.2.3.3.
-<h4 id="g0.2.2.4">Media </h4>
+<h4 id="s2.2.3">2.2.3. Media </h4>
-<h4 id="g0.2.2.5">Provisioning </h4>
+<h4 id="s2.2.3.1">2.2.3.1 Provisioning </h4>
Storage media (disk drives, tapes, removable media)
@@ -274,7 +256,7 @@ New storage media (whether disk or removable) shall be
securely erased and reformatted before use.
-<h4 id="g0.2.2.6">Storage </h4>
+<h4 id="s2.2.3.2">2.2.3.2 Storage </h4>
Removable media shall be securely stored at all times,
@@ -289,7 +271,7 @@ When there is a change to status of media,
a report is made to the log specifying the new status.
-<h4 id="g0.2.2.7">Retirement </h4>
+<h4 id="s2.2.3.3">2.2.3.3 Retirement </h4>
Storage media that is exposed to critical data and is
@@ -297,15 +279,12 @@ to be retired from service shall be destroyed or otherwise secured.
The media is securely destroyed, <b>or</b>
the media is securely erased,
and stored securely.
Records of secure erasure and method of final disposal
@@ -314,7 +293,7 @@ Where critical data is involved,
two Systems Administrators must sign-off on each step.
-<h3 id="g0.2.3">Physical Access </h3>
+<h3 id="s2.3">2.3. Physical Access </h3>
In accordance with the principle of dual control,
@@ -322,13 +301,13 @@ at least two persons authorized for access must
be on-site at the same time for physical access to be granted.
-<h4 id="g0.2.3.1">Access Authorisation </h4>
+<h4 id="s2.3.1">2.3.1. Access Authorisation </h4>
-<h4 id="g0.2.3.2">Access Profiles </h4>
+<h4 id="s2.3.2">2.3.2. Access Profiles </h4>
The Security Manual must present the different access profiles.
@@ -349,13 +328,13 @@ All are responsible for protecting the data
from access by those not authorised.
-<h4 id="g0.2.3.3">Access Logging </h4>
+<h4 id="s2.3.3">2.3.3. Access Logging </h4>
-<h4 id="g0.2.3.4">Emergency Access </h4>
+<h4 id="s2.3.4">2.3.4. Emergency Access </h4>
There must not be a procedure for emergency access.
@@ -367,7 +346,7 @@ Arbitrator must be sought as soon as possible.
See DRP.
-<h4 id="g0.2.3.5">Physical Security codes &amp; devices </h4>
+<h4 id="s2.3.5">2.3.5. Physical Security codes &amp; devices </h4>
All personel who are in possession of physical security
@@ -375,10 +354,10 @@ codes and devices (keys) are to be authorised and documented.
-<h2 id="g0.3">LOGICAL SECURITY</h2>
+<h2 id="s3">3. LOGICAL SECURITY</h2>
-<h3 id="g0.3.1">Network </h3>
-<h4 id="g0.3.1.1">Infrastructure </h4>
+<h3 id="s3.1">3.1. Network </h3>
+<h4 id="s3.1.1">3.1.1. Infrastructure </h4>
Current and complete diagrams of the physical and logical
@@ -393,7 +372,7 @@ Diagrams should be revision controlled,
and must be updated when any change is made.
-<h5 id="g0.3.1.1.1">External connectivity </h5>
+<h5 id="s3.1.1.1"> 3.1.1.1. External connectivity </h5>
Only such services as are required for normal operation
@@ -407,93 +386,65 @@ such access may be granted under the procedures of the SM
and must be reported and logged.
-<h5 id="g0.3.1.1.2">Internal connectivity </h5>
+<h5 id="s3.1.1.2"> 3.1.1.2. Internal connectivity </h5>
-System and server connections internal to the CAcert infrastructure
-should be kept to the minimum required for routine operations. Any new
-connectivity desired must be requested and approved by System
-administration team leader and then must be reflected in the appropriate
- infrastructure diagram(s).
+System and server connections internal to the CAcert infrastructure should be kept to the minimum required for routine operations. Any new connectivity desired must be requested and approved by System administration team leader and then must be reflected in the appropriate infrastructure diagram(s).
-<h4 id="g0.3.1.2">Operating Configuration </h4>
+<h4 id="s3.1.2">3.1.2. Operating Configuration </h4>
-<h5 id="g0.3.1.2.1">Ingress </h5>
+<h5 id="s3.1.2.1"> 3.1.2.1. Ingress </h5>
-All ports on which incoming traffic is expected shall be documented;
-traffic to other ports must be blocked. Unexpected traffic must be
-logged as an exception.
+All ports on which incoming traffic is expected shall be documented; traffic to other ports must be blocked. Unexpected traffic must be logged as an exception.
-<h5 id="g0.3.1.2.2">Egress </h5>
+<h5 id="s3.1.2.2"> 3.1.2.2. Egress </h5>
-All outbound traffic that is initiated shall be documented; traffic to
-other destinations must be blocked. Unexpected traffic must be logged as
+All outbound traffic that is initiated shall be documented; traffic to other destinations must be blocked. Unexpected traffic must be logged as an exception.
-<h4 id="g0.3.1.3">Intrusion detection </h4>
+<h4 id="s3.1.3">3.1.3. Intrusion detection </h4>
-Logs should be examined regularly (by manual or automatic means) for
-unusual patterns and/or traffic; anomalies should be investigated as
-they are discovered and should be reported to appropriate personnel in
-near-real-time (e.g. text message, email) and investigated as soon as
-possible. Suspicious activity which may indicate an actual system
-intrusion or compromise should trigger the incident response protocol
-described in section 5.1.
+Logs should be examined regularly (by manual or automatic means) for unusual patterns and/or traffic; anomalies should be investigated as they are discovered and should be reported to appropriate personnel in near-real-time (e.g. text message, email) and investigated as soon as possible. Suspicious activity which may indicate an actual system intrusion or compromise should trigger the incident response protocol described in section 5.1.
-<h3 id="g0.3.2">Operating System </h3>
+<h3 id="s3.2">3.2. Operating System </h3>
-<h4 id="g0.3.2.1">Disk Encryption </h4>
+<h4 id="s3.2.1"> 3.2.1. Disk Encryption </h4>
-Any operating system used for critical server machines must support
-software full-disk or disk volume encryption, and this encryption option
- must be enabled for all relevant disks/volumes when the operating
-system is first installed on the machine.
+Any operating system used for critical server machines must support software full-disk or disk volume encryption, and this encryption option must be enabled for all relevant disks/volumes when the operating system is first installed on the machine.
-<h4 id="g0.3.2.2">Operating configuration </h4>
+<h4 id="s3.2.2"> 3.2.2. Operating configuration </h4>
-Servers must enable only the operating system functions required to
-support the necessary services. Options and packages chosen at OS
-install shall be documented, and newly-installed systems must be
-inspected to ensure that only required services are active, and their
-functionality is limited through configuration options. Any required
-application software must follow similar techniques to ensure minimal
-exposure footprint.
+Servers must enable only the operating system functions required to support the necessary services. Options and packages chosen at OS install shall be documented, and newly-installed systems must be inspected to ensure that only required services are active, and their functionality is limited through configuration options. Any required application software must follow similar techniques to ensure minimal exposure footprint.
-Documentation for installing and configuring servers with the
-appropriate software packages and configurations will be maintained by
-the System Administrators.
+Documentation for installing and configuring servers with the appropriate software packages and configurations will be maintained by the System Administrators.
-<h4 id="g0.3.2.3">Patching </h4>
+<h4 id="s3.2.3"> 3.2.3. Patching </h4>
-Software used on production servers must be kept current with respect to
- patches affecting software security. Patch application
-must be approved by the Systems Administration team leader, fully
-documented in the logs and reported by email to the Systems
-Administration list on completion (see §4.2).
+Software used on production servers must be kept current with respect to patches affecting software security. Patch application
+must be approved by the Systems Administration team leader, fully documented in the logs and reported by email to the Systems Administration list on completion (see &sect;4.2).
-<h5 id="g0.3.2.3.1">“emergency” patching </h5>
+<h5 id="s3.2.3.1"> 3.2.3.1. “emergency” patching </h5>
Application of a patch is deemed an <i>emergency</i>
@@ -517,21 +468,21 @@ by the team leader to Board
independent of filed disputes.
-<h3 id="g0.3.3">Application </h3>
+<h3 id="s3.3"> 3.3. Application </h3>
Requests for ad hoc queries over the application database for business
or similar purposes must be approved by the Arbitrator.
-<h3 id="g0.3.4">Access control </h3>
+<h3 id="s3.4"> 3.4. Access control </h3>
All access to critical data and services shall be
controlled and logged.
-<h4 id="g0.3.4.1">Application Access </h4>
+<h4 id="s3.4.1"> 3.4.1. Application Access </h4>
General access for Members shall be provided via
@@ -541,97 +492,58 @@ Assurance Points and similar methods controlled in
-<h4 id="g0.3.4.2">Special Authorisation </h4>
+<h4 id="s3.4.2"> 3.4.2. Special Authorisation </h4>
Additional or special access is granted according to the
authorisations on the below access control lists
-(see §1.1.1):
-<table style="text-align: center" border="1">
-<td>List Name</td>
-<td>Who</td>
-<td>Purpose of access</td>
-<td>Relationship</td>
-<td> Manager </td>
-<td>Physical Control List</td>
-<td>Access Engineers</td>
-<td>control of access by personnel to hardware</td>
-<td>exclusive of all other roles </td>
-<td>Access team leader</td>
-<td>Physical Access List</td>
-<td>Systems Administrators</td>
-<td>hardware-level for installation and recovery</td>
-<td>exclusive with Access Engineers and Software Assessors</td>
-<td>Systems Administration team leader </td>
-<td>SSH Access List</td>
-<td>Systems Administrators </td>
-<td>Unix / account / shell level</td>
-<td> includes by default all on Physical Access List </td>
-<td>Systems Administration team leader</td>
-<td>Repository Access List</td>
-<td>Software Assessors</td>
-<td>change the source code repository </td>
-<td>exclusive with Access Engineers and Systems Administrators</td>
-<td>Software Assessment team leader</td>
-<td>Support Access List</td>
-<td>Support Engineer</td>
-<td>support features in the web application</td>
-<td> exclusive with Access Engineers and Systems Administrators </td>
-<td>Support team leader</td>
+(see &sect;1.1.1):
+<table style="text-align: center" border="1"> <tr>
+ <td>List Name</td>
+ <td>Who</td>
+ <td>Purpose of access</td>
+ <td>Relationship</td>
+ <td> Manager </td>
+ <td>Physical Control List</td>
+ <td>Access Engineers</td>
+ <td>control of access by personnel to hardware</td>
+ <td>exclusive of all other roles </td>
+ <td>Access team leader</td>
+ <td>Physical Access List</td>
+ <td>Systems Administrators</td>
+ <td>hardware-level for installation and recovery</td>
+ <td>exclusive with Access Engineers and Software Assessors</td>
+ <td>Systems Administration team leader </td>
+ <td>SSH Access List</td>
+ <td>Systems Administrators </td>
+ <td>Unix / account / shell level</td>
+ <td> includes by default all on Physical Access List </td>
+ <td>Systems Administration team leader</td>
+ <td>Repository Access List</td>
+ <td>Software Assessors</td>
+ <td>change the source code repository </td>
+ <td>exclusive with Access Engineers and Systems Administrators</td>
+ <td>Software Assessment team leader</td>
+ <td>Support Access List</td>
+ <td>Support Engineer</td>
+ <td>support features in the web application</td>
+ <td> exclusive with Access Engineers and Systems Administrators </td>
+ <td>Support team leader</td>
All changes of personnel to the above lists are
-<h4 id="g0.3.4.3">Authentication </h4>
+<h4 id="s3.4.3"> 3.4.3. Authentication </h4>
Strong methods of authentication shall be used
@@ -639,19 +551,19 @@ wherever possible.
All authentication schemes must be documented.
-<h4 id="g0.3.4.4">Removing access </h4>
+<h4 id="s3.4.4"> 3.4.4. Removing access </h4>
Follow-up actions to termination must be documented.
-See §9.1.7.
+See &sect;9.1.7.
-<h2 id="g0.4">OPERATIONAL SECURITY </h2>
+<h2 id="s4">4. OPERATIONAL SECURITY </h2>
-<h3 id="g0.4.1">System administration </h3>
+<h3 id="s4.1">4.1. System administration </h3>
Primary Systems Administration tasks
@@ -662,7 +574,7 @@ account creation and deletion,
and hardware maintenance.
-<h4 id="g0.4.1.1">Privileged accounts and passphrases </h4>
+<h4 id="s4.1.1">4.1.1. Privileged accounts and passphrases </h4>
(root and user via SSH or console)
@@ -673,11 +585,11 @@ to CAcert sysadmins
-<h5 id="g0.4.1.1.1">Authorized users </h5>
+<h5 id="s4.1.1.1">4.1.1.1. Authorized users </h5>
Only Systems Administrators
designated on the Access Lists
-in §3.4.2 are authorized to access accounts.
+in &sect;3.4.2 are authorized to access accounts.
Systems Administration team leader may temporarily permit Software
Assessors access to the application via SSH in order to do advanced
debugging, or as specifically directed by the Arbitrator.
@@ -686,33 +598,33 @@ debugging, or as specifically directed by the Arbitrator.
-<h5 id="g0.4.1.1.2">Access to Systems</h5>
+<h5 id="s4.1.1.2">4.1.1.2. Access to Systems</h5>
-<h5 id="g0.4.1.1.3">Changing </h5>
+<h5 id="s4.1.1.3">4.1.1.3. Changing </h5>
-<h4 id="g0.4.1.2">Required staff response time </h4>
+<h4 id="s4.1.2">4.1.2. Required staff response time </h4>
-Response times should be documented for Disaster Recovery planning. See §6.
+Response times should be documented for Disaster Recovery planning. See &sect;6.
-<h4 id="g0.4.1.3">Change management procedures </h4>
+<h4 id="s4.1.3">4.1.3. Change management procedures </h4>
All changes made to system configuration must be recorded
and reported in regular summaries to the Board of CAcert.
-<h4 id="g0.4.1.4">Outsourcing </h4>
+<h4 id="s4.1.4">4.1.4. Outsourcing </h4>
-<h3 id="g0.4.2">Logging </h3>
+<h3 id="s4.2">4.2. Logging </h3>
-<h4 id="g0.4.2.1">Coverage </h4>
+<h4 id="s4.2.1">4.2.1. Coverage </h4>
All sensitive events should be logged reliably.
@@ -720,7 +632,7 @@ Logs should be deleted after an appropriate amount of time
as documented in the Security Manual.
-<h4 id="g0.4.2.2">Access and Security </h4>
+<h4 id="s4.2.2">4.2.2. Access and Security </h4>
Access to logs must be restricted.
@@ -728,7 +640,7 @@ The security of the logs should be documented.
The records retention should be documented.
-<h4 id="g0.4.2.3">Automated logs </h4>
+<h4 id="s4.2.3">4.2.3. Automated logs </h4>
Logging should be automated,
and use should be made of appropriate system-provided automated tools.
@@ -736,7 +648,7 @@ Automated logs should be reviewed periodically;
suspicious events should be flagged and investigated in a timely fashion.
-<h4 id="g0.4.2.4">Operational (manual) logs </h4>
+<h4 id="s4.2.4">4.2.4. Operational (manual) logs </h4>
@@ -747,14 +659,14 @@ report provided by the accessor and by
the Access Engineer.
-<h3 id="g0.4.3">Backup </h3>
+<h3 id="s4.3">4.3. Backup </h3>
The procedure for all backups must be documented,
according to the following sub-headings.
-<h4 id="g0.4.3.1">Type </h4>
+<h4 id="s4.3.1">4.3.1. Type </h4>
Backups must be taken for operational
and for disaster recovery purposes.
@@ -762,26 +674,26 @@ Operational backups may be online and local.
Disaster recovery backups must be offline and remote.
-<h4 id="g0.4.3.2">Frequency </h4>
+<h4 id="s4.3.2">4.3.2. Frequency </h4>
-<h4 id="g0.4.3.3">Storage </h4>
+<h4 id="s4.3.3">4.3.3. Storage </h4>
Backups must be protected to the same level as the critical systems themselves.
Disaster recovery backups may be distributed.
-<h4 id="g0.4.3.4">Retention period and Re-use </h4>
+<h4 id="s4.3.4">4.3.4. Retention period and Re-use </h4>
-See §2.2.3.
+See &sect;2.2.3.
-<h4 id="g0.4.3.5">Encryption </h4>
+<h4 id="s4.3.5">4.3.5. Encryption </h4>
Backups must be encrypted and must only be transmitted via secured channels.
Off-site backups must be dual-encrypted using divergent methods.
-<h4 id="g0.4.3.6">Verifying Backups </h4>
+<h4 id="s4.3.6">4.3.6. Verifying Backups </h4>
Two CAcert System Administrators must be
present for verification of a backup.
@@ -789,14 +701,14 @@ Four eyes principle must be maintained when the key and backup are together.
For any other purpose than verification of the success of the backup, see next.
-<h4 id="g0.4.3.7">Key Management </h4>
+<h4 id="s4.3.7">4.3.7. Key Management </h4>
The encryption keys must be stored securely by the
CAcert Systems Administrators.
Paper documentation must be stored with manual backups.
-<h4 id="g0.4.3.8">Reading Backups </h4>
+<h4 id="s4.3.8">4.3.8. Reading Backups </h4>
Conditions and procedures for examining the backups
@@ -804,45 +716,45 @@ and must be under Arbitrator control for purposes
other than verification and recovery.
-<h3 id="g0.4.4">Data retention </h3>
+<h3 id="s4.4">4.4. Data retention </h3>
-<h4 id="g0.4.4.1">User data </h4>
+<h4 id="s4.4.1">4.4.1. User data </h4>
Termination of user data is under direction of the Arbitrator.
See CCA.
-<h4 id="g0.4.4.2">System logs </h4>
+<h4 id="s4.4.2">4.4.2. System logs </h4>
-See §4.2.1.
+See &sect;4.2.1.
-<h4 id="g0.4.4.3">Incident reports </h4>
+<h4 id="s4.4.3">4.4.3. Incident reports </h4>
-See §5.6.
+See &sect;5.6.
-<h2 id="g0.5">INCIDENT RESPONSE</h2>
+<h2 id="s5">5. INCIDENT RESPONSE</h2>
-<h3 id="g0.5.1">Incidents </h3>
+<h3 id="s5.1">5.1. Incidents </h3>
-<h3 id="g0.5.2">Detection </h3>
+<h3 id="s5.2">5.2. Detection </h3>
-<h3 id="g0.5.3">Immediate Action </h3>
-<h4 id="g0.5.3.1">Severity and Priority </h4>
+<h3 id="s5.3">5.3. Immediate Action </h3>
+<h4 id="s5.3.1">5.3.1. Severity and Priority </h4>
On discovery of an incident,
an initial assessment of severity and priority must be made.
-<h4 id="g0.5.3.2">Communications </h4>
+<h4 id="s5.3.2">5.3.2. Communications </h4>
@@ -852,7 +764,7 @@ A communications forum should be established for direct
support of high priority or high severity incidents.
-<h4 id="g0.5.3.3">Escalation </h4>
+<h4 id="s5.3.3">5.3.3. Escalation </h4>
A process of escalation should be established
for oversight and management purposes,
@@ -861,7 +773,7 @@ Oversight starts with four eyes and ends with the Arbitrator.
Management starts with the team leader and ends with the Board.
-<h3 id="g0.5.4">Investigation </h3>
+<h3 id="s5.4">5.4. Investigation </h3>
Incidents must be investigated.
The investigation must be documented.
@@ -869,9 +781,9 @@ If the severity is high,
evidence must be secured and escalated to Arbitration.
-<h3 id="g0.5.5">Response </h3>
+<h3 id="s5.5">5.5. Response </h3>
-<h3 id="g0.5.6">Report </h3>
+<h3 id="s5.6">5.6. Report </h3>
Incident reports shall be be published.
@@ -890,88 +802,83 @@ and progress information should be published as soon as
The knowledge of the existence of the event must not be kept
secret, nor the manner and methods be kept confidential.
-See §9.5.
+See &sect;9.5.
-<h2 id="g0.6">DISASTER RECOVERY</h2>
+<h2 id="s6">6. DISASTER RECOVERY</h2>
-<h3 id="g0.6.1">Business Processes </h3>
+<h3 id="s6.1"> 6.1. Business Processes </h3>
Board must develop and maintain documentation on Business Processes.
From this list, Core Processes for business continuity / disaster recovery
purposes must be identified.
-<h3 id="g0.6.2">Recovery Times </h3>
+<h3 id="s6.2"> 6.2. Recovery Times </h3>
Board should identify standard process times for all processes,
and must designate Maximum Acceptable Outages
and Recovery Time Objectives for the Core Processes.
-<h3 id="g0.6.3">Plan </h3>
+<h3 id="s6.3"> 6.3. Plan </h3>
-<h3 id="g0.6.4">Key Persons List </h3>
+<h3 id="s6.4"> 6.4. Key Persons List </h3>
Board must maintain a Key Persons List with all the
-See §10.1.
+See &sect;10.1.
The list shall be accessible even if CAcert's
infrastructure is not available.
-<h2 id="g0.7">SOFTWARE ASSESSMENT</h2>
+<h2 id="s7">7. SOFTWARE ASSESSMENT</h2>
Software assessment team is responsible
for the security and maintenance of the code.
-<h3 id="g0.7.1">Authority </h3>
+<h3 id="s7.1"> 7.1. Authority </h3>
The source code is under CCS.
Additions to the team are
-See §3.4.2.
+See &sect;3.4.2.
-<h3 id="g0.7.2">Tasks </h3>
+<h3 id="s7.2"> 7.2. Tasks </h3>
Software assessment is not primarily tasked to write the code.
In principle, anyone can submit code changes for approval.
-<h3 id="g0.7.3">Repository </h3>
+<h3 id="s7.3"> 7.3. Repository </h3>
-<h3 id="g0.7.4">Review </h3>
+<h3 id="s7.4"> 7.4. Review </h3>
@@ -983,7 +890,7 @@ Author and signers-off must be logged.
The riskier the source is, the more reviews have to be done.
-<h3 id="g0.7.5">Test and Bugs </h3>
+<h3 id="s7.5"> 7.5. Test and Bugs </h3>
Software assessment team maintains a test system.
@@ -1000,18 +907,18 @@ Bug submission access should be provided to
any Member that requests it.
-<h3 id="g0.7.6">Production </h3>
+<h3 id="s7.6"> 7.6. Production </h3>
-<h2 id="g0.8">SUPPORT</h2>
+<h2 id="s8">8. SUPPORT</h2>
-<h3 id="g0.8.1">Authority </h3>
+<h3 id="s8.1"> 8.1. Authority </h3>
The software interface gives features to Support Engineer.
Access to the special features is under tight control.
Additions to the team are subject to Board approval,
and the software features are under CCS.
@@ -1031,27 +938,23 @@ Support Engineers are responsible to follow the
-<h3 id="g0.8.2">Responsibilities </h3>
+<h3 id="s8.2"> 8.2. Responsibilities </h3>
Respond to general requests for information or explanation by Members.
Support Engineers cannot make a binding statement.
Responses must be based on policies and practices.
-<h3 id="g0.8.3">Channels </h3>
+<h3 id="s8.3"> 8.3. Channels </h3>
Support may always be contacted by email at
@@ -1060,18 +963,15 @@ Other channels may be made available and documented
in Security Manual.
-<h3 id="g0.8.4">Records and Logs </h3>
+<h3 id="s8.4"> 8.4. Records and Logs </h3>
-<li> use of restricted interfaces must be logged. </li>
-<li> all support channels should be logged. </li>
-<li> private requests for support should be referred to proper channels and logged there (e.g., by CCs) </li>
+ <li> use of restricted interfaces must be logged. </li>
+ <li> all support channels should be logged. </li>
+ <li> private requests for support should be referred to proper channels and logged there (e.g., by CCs) </li>
-<h3 id="g0.8.5">Arbitration </h3>
+<h3 id="s8.5"> 8.5. Arbitration </h3>
Support Engineers refer questions requiring authority
to Arbitration, and may also be called upon to act as
@@ -1083,43 +983,35 @@ these topics, even if not listed as Arbitrators
or Case Managers.
-<h3 id="g0.8.6">References </h3>
+<h3 id="s8.6"> 8.6. References </h3>
-<h2 id="g0.9">ADMINISTRATIVE</h2>
+<h2 id="s9">9. ADMINISTRATIVE</h2>
-<h3 id="g0.9.1">Staffing</h3>
+<h3 id="s9.1"> 9.1. Staffing</h3>
-<h4 id="g0.9.1.1">Roles and responsibilities</h4>
+<h4 id="s9.1.1"> 9.1.1. Roles and responsibilities</h4>
-<li> Access Engineer: responsible for controlling access to hardware, and maintaining hardware. </li>
-<li> System Administrator: responsible for maintaining core services and integrity. </li>
-<li> Software Assessor: maintain the code base and confirm security ("sign-off") of patches and releases.</li>
-<li> Support Engineer: human interface with users.</li>
-<li> Team leaders: coordinate with teams, report to Board.</li>
-<li> All: respond to Arbitrator's rulings on changes. Respond to critical security issues. Observe.</li>
-<li> Board: authorise new individuals and accesses. Coordinate overall. </li>
-<li> Arbitrator: conducts ABCs. Authorises exceptions to policy. </li>
+ <li> Access Engineer: responsible for controlling access to hardware, and maintaining hardware. </li>
+ <li> System Administrator: responsible for maintaining core services and integrity. </li>
+ <li> Software Assessor: maintain the code base and confirm security ("sign-off") of patches and releases.</li>
+ <li> Support Engineer: human interface with users.</li>
+ <li> Team leaders: coordinate with teams, report to Board.</li>
+ <li> All: respond to Arbitrator's rulings on changes. Respond to critical security issues. Observe.</li>
+ <li> Board: authorise new individuals and accesses. Coordinate overall. </li>
+ <li> Arbitrator: conducts ABCs. Authorises exceptions to policy. </li>
-<h4 id="g0.9.1.2">Staffing levels</h4>
+<h4 id="s9.1.2"> 9.1.2. Staffing levels</h4>
Each team should have a minimum of two members available at any time.
Individuals should not be active
in more than one team at any one time,
but are expected to observe the other teams.
-See §3.4.2 for exclusivities.
+See &sect;3.4.2 for exclusivities.
@@ -1127,26 +1019,23 @@ One individual in each team is designated team leader
and reports to Board.
-<h4 id="g0.9.1.3">Process of new Team Members</h4>
+<h4 id="s9.1.3"> 9.1.3. Process of new Team Members</h4>
-<li> Recommendation by team leader </li>
-<li> Arbitrated Background Check ("ABC") </li>
-<li> Authorisation by Board </li>
+ <li> Recommendation by team leader </li>
+ <li> Arbitrated Background Check ("ABC") </li>
+ <li> Authorisation by Board </li>
-<h4 id="g0.9.1.4">Arbitrated Background Check - Procedures</h4>
+<h4 id="s9.1.4"> 9.1.4. Arbitrated Background Check - Procedures</h4>
@@ -1154,33 +1043,27 @@ with a separate Case Manager to provide four eyes.
-<h4 id="g0.9.1.5">Scope </h4>
+<h4 id="s9.1.4.1"> 9.1.4.1. Scope </h4>
-<li> realm-specific knowledge </li>
-<li> realm-specific understanding of good security practice </li>
-<li> history of activity within Community </li>
-<li> reputation and standing within Community </li>
-<li> provided references </li>
-<li> conflicts of interest </li>
+ <li> realm-specific knowledge </li>
+ <li> realm-specific understanding of good security practice </li>
+ <li> history of activity within Community </li>
+ <li> reputation and standing within Community </li>
+ <li> provided references </li>
+ <li> conflicts of interest </li>
-<h4 id="g0.9.1.6">Coverage </h4>
+<h4 id="s9.1.4.2"> 9.1.4.2. Coverage </h4>
-See §1.1.1.
+See &sect;1.1.1.
-<h4 id="g0.9.1.7">Documentation </h4>
+<h4 id="s9.1.4.3"> 9.1.4.3. Documentation </h4>
@@ -1193,36 +1076,29 @@ It must include:
-<li> Agreement with appropriate policies, etc. </li>
-<li> Contact information. See §10.1. </li>
+ <li> Agreement with appropriate policies, etc. </li>
+ <li> Contact information. See &sect;10.1. </li>
-<h4 id="g0.9.1.8">Privacy for Critical Roles</h4>
+<h4 id="s9.1.4.4"> 9.1.4.4. Privacy for Critical Roles</h4>
-<li> procedure and ruling (recommendation) should be public </li>
-<li> interview, documents should not be public, </li>
-<li> summary of evidence should be in the ruling. </li>
-<li> Arbitrator can rule on the escrow questions of evidence </li>
-<li> contact information goes into the contact addressbook </li>
+ <li> procedure and ruling (recommendation) should be public </li>
+ <li> interview, documents should not be public, </li>
+ <li> summary of evidence should be in the ruling. </li>
+ <li> Arbitrator can rule on the escrow questions of evidence </li>
+ <li> contact information goes into the contact addressbook </li>
-<h4 id="g0.9.1.9">Authorisation </h4>
+<h4 id="s9.1.5"> 9.1.5. Authorisation </h4>
Individuals and access (both) must be authorised by the Board.
@@ -1240,7 +1116,7 @@ Deliberations and decisions should be documented.
All conflicts of interest should be examined.
-<h4 id="g0.9.1.10">Security</h4>
+<h4 id="s9.1.6"> 9.1.6. Security</h4>
It is the responsibility of all individuals to
@@ -1251,16 +1127,16 @@ issues satisfactorily, or to ensure that they are reported fully.
-<h4 id="g0.9.1.11">Termination of staff</h4>
+<h4 id="s9.1.7"> 9.1.7. Termination of staff</h4>
Termination of access may be for resignation, Arbitration ruling,
or decision of Board or team leader.
On termination (for any reason), access and information must be secured.
-See §3.4.4.
+See &sect;3.4.4.
@@ -1272,7 +1148,7 @@ and the Arbitrator may reinstate any provision
of this agreement or bind the person to a ruling.
-<h4 id="g0.9.1.12">HR and Training</h4>
+<h4 id="s9.1.8"> 9.1.8. HR and Training</h4>
It is the responsibility of the team leaders
@@ -1280,9 +1156,9 @@ to coordinate technical testing and training,
especially of new team members.
-<h3 id="g0.9.2">Root Key Management</h3>
+<h3 id="s9.2"> 9.2. Root Key Management</h3>
-<h4 id="g0.9.2.1">Root Key generation</h4>
+<h4 id="s9.2.1"> 9.2.1. Root Key generation</h4>
Root keys are generated only on instruction from Board.
@@ -1291,22 +1167,16 @@ The procedure must include:
-<li> Use of hardware built securely for the purpose
+ <li> Use of hardware built securely for the purpose
only and cleaned/erased/destroyed immediately afterwards. </li>
-<li> Dual control over all phases, including by Board. </li>
-<li> Strong collection of primary entropy, separated from use of entropy. </li>
-<li> Test cycles of the process on the day. </li>
-<li> Documentation of each step as it happens against the procedure. </li>
-<li> Confirmation by each participant over the process and the results. </li>
+ <li> Dual control over all phases, including by Board. </li>
+ <li> Strong collection of primary entropy, separated from use of entropy. </li>
+ <li> Test cycles of the process on the day. </li>
+ <li> Documentation of each step as it happens against the procedure. </li>
+ <li> Confirmation by each participant over the process and the results. </li>
-<h4 id="g0.9.2.2">Backup and escrow</h4>
+<h4 id="s9.2.2"> 9.2.2. Backup and escrow</h4>
@@ -1320,24 +1190,24 @@ The top-level root must be escrowed under Board control.
-<h4 id="g0.9.2.3">Recovery</h4>
+<h4 id="s9.2.3"> 9.2.3. Recovery</h4>
-<h4 id="g0.9.2.4">Revocation </h4>
+<h4 id="s9.2.4"> 9.2.4. Revocation </h4>
-<h3 id="g0.9.3">Legal</h3>
+<h3 id="s9.3"> 9.3. Legal</h3>
-<h4 id="g0.9.3.1">Responsibility</h4>
+<h4 id="s9.3.1"> 9.3.1. Responsibility</h4>
Board is responsible to the Community to manage
the CA at the executive level.
-<h4 id="g0.9.3.2">Response to external (legal) inquiry</h4>
+<h4 id="s9.3.2"> 9.3.2. Response to external (legal) inquiry</h4>
@@ -1355,7 +1225,7 @@ The Arbitrator's ruling may instruct individuals,
and becomes your authority to act.
-<h3 id="g0.9.4">Outsourcing </h3>
+<h3 id="s9.4">9.4. Outsourcing </h3>
Components may be outsourced.
@@ -1363,47 +1233,35 @@ Any outsourcing arrangements must be documented.
All arrangements must be:
Assured Organisations, in which
all involved personnel are Assurers,
with Members that have the requisite knowledge
and in good contact with the team leader(s),
Contracts should be written with the above in mind.
Outsourcing of critical components must be approved by the Board.
-<h3 id="g0.9.5">Confidentiality, Secrecy </h3>
+<h3 id="s9.5">9.5 Confidentiality, Secrecy </h3>
CAcert is an open organisation and adopts a principle
@@ -1428,26 +1286,23 @@ All should strive to reduce or remove any such
-<h2 id="g0.10">REFERENCES</h2>
+<h2 id="s10">10. REFERENCES</h2>
-<h3 id="g0.10.1">Contacts </h3>
+<h3 id="s10.1">10.1 Contacts </h3>
-<h3 id="g0.10.2">Documents </h3>
+<h3 id="s10.2">10.2 Documents </h3>
-<h3 id="g0.10.3">Related Documents </h3>
+<h3 id="s10.3">10.3 Related Documents </h3>
generated by cgit v1.2.1 (git 2.18.0) at 2020-07-11 15:30:44 +0000