--
- Console Access List,
- for physical access by System Administrators.
-
-
- SSH Access List,
- for access to Unix-level facilities of the online webserver.
-
-
- Support Access List,
- for access to the online support interface features.
-
All changes to the above lists are approved by the board of CAcert.
@@ -507,9 +540,8 @@ A strong method of authentication is used and documented.
3.4.3. Removing access
-Termination actions must be documented,
-including resignation, arbitration, or determination
-by team or board.
+Follow-up actions to termination must be documented.
+See §9.1.7.
@@ -523,46 +555,38 @@ by team or board.
Primary systems administration tasks
shall be conducted under four eyes principle.
These shall include backup performance verification,
-log inspection,
-software patch identification and application,
+software patch application,
account creation and deletion,
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 passphrases
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
+Passphrases and SSH private keys used for entering into the systems
+will be kept private
to CAcert sysadmins in all cases.
4.1.1.1. Authorized users
-Only system administrators designated on the Access List
+Only system administrators designated on the
+Access Lists
+in §3.4.1
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 Systems
-All remote communications for systems administration purposes is encrypted,
-logged and monitored.
+All access is secured, logged and monitored.
-Passwords must be kept secure.
-The procedure for changing passwords should be documented.
+The procedure for changing passphrases and SSH keys should be documented.
@@ -577,7 +601,7 @@ and are in good contact with team leader.
4.1.2. Required staff response time
-Response times should be documented.
+Response times should be documented for Disaster Recovery planning. See §6.
4.1.3. Change management procedures
@@ -594,20 +618,6 @@ All sensitive events should be logged.
Logs should be deleted after an appropriate amount of time.
-
-'''Move to SM:'''
-Logs shall be maintained for:
-
-
-
- - anomalous network traffic,
- - system activities and events,
- - application (certificate, web, mail, and database) events,
- - '''make generic''': "Comms Module" requests for certificate signing on both the cryptographic module (signing server) and the main online server,
- - login and root access,
- - configuration changes.
-
-
4.2.2. Access and Security
@@ -627,11 +637,12 @@ suspicious events should be flagged and investigated in a timely fashion.
4.2.4. Operational (manual) logs
Configuration changes, no matter how small, must be logged.
-Access to this log shall be restricted.
-All physical visits will be logged and a report provided by the accessor.
+All physical visits must be logged and a
+report provided by the accessor and by
+the Access Engineer.
@@ -644,9 +655,9 @@ according to the following sub-headings.
Backups must be taken for operational
-and for disaster recovery purposes ("offline").
-Disaster recovery backups must be offline and remote.
+and for disaster recovery purposes.
Operational backups may be online and local.
+Disaster recovery backups must be offline and remote.
@@ -654,7 +665,7 @@ Operational backups may be online and local.
Backups must be protected to the same level as the critical systems themselves.
-Offline backups should be distributed.
+Disaster recovery backups may be distributed.
4.3.4. Retention period and Re-use
@@ -682,9 +693,10 @@ Paper documentation must be stored with manual 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.
+Conditions and procedures for examining the backups
+must be documented,
+and must be under Arbitrator control for purposes
+other than verification and recovery.
4.4. Data retention
@@ -700,12 +712,10 @@ See CCA.
4.4.3. Incident reports
-The systems administration team leader is to maintain incident reports securely.
-Access to incident reports is restricted.
+Document.
+See §5.6.
-
-
@@ -755,18 +765,35 @@ Evidence must be secured if the severity is high.
5.5. Response
+
-A report should be appended to the documentation of the investigation,
-and distributed in the act of closing the investigation.
+Incident reports must be published.
+The Incident Report is written on closing the investigation.
+A full copy should be appended to the
+documentation of the investigation.
+Sensitive information may be pushed out into
+a restricted appendix of the report.
+The systems administration team leader is responsible
+for publication and maintenance.
-Incidents are not normally kept secret or confidential.
-Ony under a defined exception under policy,
+Incidents are not normally kept secret nor confidential.
+and progress information should be published as soon as
+possible.
+The knowledge of the existence of the event must not be kept
+secret, nor the manner and methods be kept confidential.
+
+
+
+The following is a general confidentiality and secrecy
+clause. Suggest moving this to new section 9.7.
+
+
+
+Only under a defined exception under policy,
or under the oversight of the Arbitrator,
may confidentiality be maintained.
-The knowledge of the existence of the event must not be kept
-secret, nor the manner in which it is kept confidential.
6. DISASTER RECOVERY
@@ -798,18 +825,19 @@ Board must have a basic plan to recover.
Board must maintain a key persons List with all the
contact information needed.
+See §10.1.
-7. SOFTWARE DEVELOPMENT
+7. SOFTWARE ASSESSMENT
Change name of this to Software Assessment.
-Software development team is responsible
+Software assessment team is responsible
for the security of the code.
@@ -817,7 +845,8 @@ for the security of the code.
The source code is under CCS.
-Additions to the team are approved by Board
+Additions to the team are approved by Board.
+See §3.4.1.
@@ -837,7 +866,7 @@ The primary tasks are:
-Software Development is not primarily tasked to write the code.
+Software assessment is not primarily tasked to write the code.
In principle, anyone can submit code changes for approval.
@@ -847,7 +876,7 @@ In principle, anyone can submit code changes for approval.
The application code and patches are maintained
in a central repository that is run by the
-software development team.
+software assessment team.
@@ -865,16 +894,16 @@ The riskier the source is, the more reviews have to be done.
7.5. Test and Bugs
-Software Development team maintains a test system.
+Software assessment team maintains a test system.
Each patch should be built and tested.
Test status of each patch must be logged.
-Software Development team maintains a bug system.
+Software assessment team maintains a bug system.
Primary communications should go through this system.
-Management access should be granted to all software developers,
-and systems administrators.
+Management access should be granted to all software assessors,
+software developers, and systems administrators.
Bug submission access should be provided to
any Member that requests it.
@@ -882,12 +911,12 @@ any Member that requests it.
7.6. Handover
-Once signed off, software development (team leader)
+Once signed off, software assessment (team leader)
coordinates with systems administration (team leader)
to offer the upgrade.
Upgrade format is to be negotiated,
but systems administration naturally has the last word.
-Software development people are not to have access
+Software assessors are not to have access
to the critical systems, providing a dual control
at the teams level.
@@ -903,7 +932,8 @@ system administrators.
Systems administrators copy the patches securely
-from the software development onto the critical machine.
+from the software assessment repository
+onto the critical machine.
See §3.3.
@@ -929,8 +959,7 @@ by this policy or the Security Manual or other clear
applicable document.
If the Member's authority is not in doubt,
the Member can give that authority.
-
-The Arbitrator's authority must be sought.
+If not, the Arbitrator's authority must be sought.
@@ -947,7 +976,8 @@ policies and practices.
Access to Member's private information is restricted.
Support staff may be authorised by the Board
to access any additional, restricted interfaces.
-Each such special access is managed by the team leader.
+This access is managed by the systems administration
+team leader, see §3.4.1.
8.5. Records and Logs
@@ -968,8 +998,9 @@ Each such special access is managed by the team leader.
9.1.1. Roles and responsibilities
+ - Access Engineer: responsible for controlling access to hardware, and maintaining hardware.
- System administrator: responsible for maintaining core services and integrity.
- - Software Developer: maintain the code base and confirm security ("sign-off") of patches and releases.
+ - Software assessor: maintain the code base and confirm security ("sign-off") of patches and releases.
- Support: human interface with users.
- Team leaders: coordinate with teams, report to board.
- All: respond to Arbitrator's rulings on changes. Respond to critical security issues. Observe.
@@ -979,13 +1010,16 @@ Each such special access is managed by the team leader.
9.1.2. Staffing levels
-Each team should have a minimum of 2 members available at any time.
-Individuals should be active in only one team at any one time,
-but may be observers on any number of teams.
+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.1 for exclusivities.
-One individual in each team is designated leader and reports to Board.
+One individual in each team is designated team leader
+and reports to Board.
9.1.3. Process of new Team Members
@@ -1034,7 +1068,7 @@ The background check should be done on all of:
- systems administrator
- access engineeers
- - software developer
+ - software assessor
- support
- Board
@@ -1052,11 +1086,11 @@ It must include:
- - agreement with appropriate policies, etc
- - contact information
+ - Agreement with appropriate policies, etc.
+ - Contact information. See §10.1.
- 9.1.4.4. Privacy for Hard Roles
+ 9.1.4.4. Privacy for Critical Roles
The following privacy considerations exist:
@@ -1114,6 +1148,16 @@ and may be reversed.
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.3.
+
+
+
+The provisions on Arbitration survive any termination
+by persons fulfilling a critical role.
+That is, even after a person has left a critical role,
+they are still bound by the DRP (COD7),
+and the Arbitrator may reinstate any provision
+of this agreement or bind the person to a ruling.
9.1.8. HR and Training
@@ -1188,7 +1232,13 @@ All external inquiries of security import are filed as disputes and placed befor
-Only the Arbitrator has the authority to deal with external requests and/or create a procedure. Systems administrators, board members and other key roles do not have the authority to answer legal inquiry. The Arbitrator's ruling may instruct individuals, and becomes your authority to act.
+Only the Arbitrator has the authority
+to deal with external requests and/or create a procedure.
+Access Engineers, systems administrators,
+board members and other key roles
+do not have the authority to answer legal inquiry.
+The Arbitrator's ruling may instruct individuals,
+and becomes your authority to act.
9.6. Outsourcing
@@ -1212,7 +1262,7 @@ All arrangements must be:
under Arbitration and DRP,
-
with organisations that are Members of CAcert
- as organisational Members,
+ as organisational Members, and
-
under the spirit of the Principles of CAcert
@@ -1239,7 +1289,7 @@ All incorporated Documents must be documented.
10.3 Related Documents
-Relevant and helpdul Documents should be referenced for convenience.
+Relevant and helpful Documents should be referenced for convenience.