From 9b03bee76e3f26e07eda3346ad92e6d07c9e5d2e Mon Sep 17 00:00:00 2001
From: Ian Grigg
Date: Mon, 16 Feb 2009 15:43:33 +0000
Subject: [PATCH] html errors
git-svn-id: http://svn.cacert.org/CAcert/Policies@1175 14b1bab8-4ef6-0310-b690-991c95c89dfd
---
SecurityPolicy.html | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/SecurityPolicy.html b/SecurityPolicy.html
index cbc4ea4..807778e 100644
--- a/SecurityPolicy.html
+++ b/SecurityPolicy.html
@@ -29,6 +29,7 @@ Status: work-in-progress
This Security Manual sets out required procedures
for the secure operation of the CAcert critical computer systems.
These systems include:
+
-
Physical hardware mounting the logical services
-
@@ -40,10 +41,10 @@ These systems include:
-
Source code (changes and patches)
-
1.1.1. Effected Personnel
+
These roles and teams are effected:
-
@@ -104,15 +105,18 @@ deriving from the above principles.
1.3. Definition of Terms
+
- Systems Administrator
-
A Member who manages a critial system, and has access
to security-sensitive functions or data.
+
+
1.4. Version control
-1.4.1. The Security Policy Document
+1.4.1. The Security Policy Document
This Security Policy is part of the configuration-control specification
for audit purposes (DRC).
@@ -123,7 +127,7 @@ It is under the control of Policy on Policy for version purposes.
This policy document says what is done, rather than how to do it.
-1.4.2. The Security Manual (Practices) Document
+1.4.2. The Security Manual (Practices) Document
This Policy explicitly defers detailed security practices to the
@@ -136,7 +140,7 @@ the SM is under the direct control of the Systems Administration team.
It is located and version-controlled on the CAcert wiki.
-1.4.3. The Security Procedures
+1.4.3. The Security Procedures
The Systems Administration team may from time to time
@@ -155,4 +159,3 @@ Each procedure must be referenced explicitly in the Security Manual.