From 1f30d7fd39d72511619de2a5e3d95a87d6a14208 Mon Sep 17 00:00:00 2001 From: Ian Grigg Date: Mon, 23 Feb 2009 23:36:11 +0000 Subject: [PATCH] html errors git-svn-id: http://svn.cacert.org/CAcert/Policies@1187 14b1bab8-4ef6-0310-b690-991c95c89dfd --- SecurityPolicy.html | 54 ++++++++++++++++++++++----------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/SecurityPolicy.html b/SecurityPolicy.html index fc04e05..0714553 100644 --- a/SecurityPolicy.html +++ b/SecurityPolicy.html @@ -513,9 +513,9 @@ Upon resignation from systems administration team, or determination by two membe -

4. OPERATIONAL SECURITY

+

4. OPERATIONAL SECURITY

-

4.1. System administration

+

4.1. System administration

Primary systems administration tasks shall be conducted under four eyes principle. @@ -531,14 +531,14 @@ and hardware maintenance. System administrators must pass a background check and comply with all applicable policies in force.

-

4.1.1. Privileged accounts and passwords

+

4.1.1. Privileged accounts and passwords

Access to Accounts (root and user via SSH or console) must be strictly controlled. Passwords and passphrases entered into the systems will be kept private to CAcert sysadmins in all cases.

-
4.1.1.1. Authorized users
+
4.1.1.1. Authorized users

Only system administrators designated on the Access List shall be authorized to access accounts. @@ -547,32 +547,32 @@ shall be authorized to access accounts.

Assumes above that there is no reason to have access to a Unix-level account on the critical machines unless on the Access List.

-
4.1.1.2. Access to
+
4.1.1.2. Access to

All remote communications for systems administration purposes is encrypted, logged and monitored.

-
4.1.1.3. Changing
+
4.1.1.3. Changing

Passwords must be kept secure. The procedure for changing passwords should be documented.

-

4.1.2. Required staff response time

+

4.1.2. Required staff response time

Response times should be documented.

-

4.1.3. Change management procedures

+

4.1.3. Change management procedures

All changes made to system configuration must be recorded.

-

4.2. Logging

+

4.2. Logging

-

4.2.1. Coverage

+

4.2.1. Coverage

Logs shall be maintained for: @@ -587,7 +587,7 @@ Logs shall be maintained for:

  • configuration changes.
    • -

    4.2.2. Access and Security

    +

    4.2.2. Access and Security

    Access to logs must be restricted. @@ -595,7 +595,7 @@ The security of the logs should be documented. The records retention should be documented.

    -

    4.2.3. Automated logs

    +

    4.2.3. Automated logs

    Logging should be automated, and use should be made of appropriate system-provided automated tools. @@ -603,7 +603,7 @@ Automated logs should be reviewed periodically; suspicious events should be flagged and investigated in a timely fashion.

    -

    4.2.4. Operational (manual) logs

    +

    4.2.4. Operational (manual) logs

    Configuration changes, no matter how small, must be logged. Access to this log shall be restricted. @@ -613,14 +613,14 @@ Access to this log shall be restricted. All physical visits will be logged and a report provided by the accessor.

    -

    4.3. Backup

    +

    4.3. Backup

    The procedure for all backups must be documented, according to the following sub-headings.

    -

    4.3.1. Type

    +

    4.3.1. Type

    Backups must be taken for operational and for disaster recovery purposes ("offline"). @@ -628,25 +628,25 @@ Disaster recovery backups must be offline and remote. Operational backups may be online and local.

    -

    4.3.2. Frequency

    +

    4.3.2. Frequency

    Document.

    -

    4.3.3. Storage

    +

    4.3.3. Storage

    Backups must be protected to the same level as the critical systems themselves. Offline backups should be distributed.

    -

    4.3.4. Retention period and Re-use

    +

    4.3.4. Retention period and Re-use

    Document.

    -

    4.3.5. Encryption

    +

    4.3.5. Encryption

    Backups must be encrypted and must only be transmitted via secured channels. Off-site backups must be dual-encrypted using divergent methods.

    -

    4.3.6. Verifying Backups

    +

    4.3.6. Verifying Backups

    Two CAcert system administrators must be present for verification of a backup. @@ -654,39 +654,39 @@ 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.

    -

    4.3.7. Key Management

    +

    4.3.7. Key Management

    The encryption keys must be stored securely by the CAcert systems administrators. Paper documentation must be stored with manual backups.

    -

    4.3.8. Reading Backups

    +

    4.3.8. Reading Backups

    Conditions and procedures for examining the backups for purposes other than for verification must be documented and must be under Arbitrator control.

    -

    4.4. Data retention

    +

    4.4. Data retention

    -

    4.4.1. User data

    +

    4.4.1. User data

    Termination of user data is under direction of the Arbitrator. See CCA.

    -

    4.4.2. System logs

    +

    4.4.2. System logs

    Document.

    -

    4.4.3. Incident reports

    +

    4.4.3. Incident reports

    The systems administration team leader is to maintain incident reports securely. Access to incident reports is restricted.

    -

    4.5. Cycling

    +

    4.5. Cycling

    Document.