@ -95,7 +95,7 @@ These systems include:
Board may add additional components into the Security Manual.
< / p >
< h4 > < a name = "1.1.1" > 1.1.1.< / a > < / h4 >
< h4 id = "s1.1.1" > 1.1.1. Covered Personnel < / h4 >
< p >
Critical roles are covered.
@ -112,7 +112,7 @@ These roles are defined as:
Software Assessors (including Application Engineers)
< / li > < / ul >
< h4 > < a name = "1.1.2" > 1.1.2.< / a > < / h4 >
< h4 id = "s1.1.2" > 1.1.2. Out of Scope < / h4 >
< p >
Non-critical systems are not covered by this manual,
@ -121,7 +121,7 @@ found within the security context.
Architecture is out of scope, see CPS#6.2.
< / p >
< h3 > < a name = "1.2" > 1.2.< / a > < / h3 >
< h3 id = "s1.2" > 1.2. Principles < / h3 >
< p >
Important principles of this Security Policy are:
< / p >
@ -153,7 +153,7 @@ Each task or asset is covered by a variety of protections
deriving from the above principles.
< / p >
< h3 > < a name = "1.3" > 1.3.< / a > < / h3 >
< h3 id = "s1.3" > 1.3. Definition of Terms< / h3 >
< dl >
< dt > < i > Access Engineer< / i > < / dt >
@ -194,9 +194,9 @@ deriving from the above principles.
< / dl >
< h3 > < a name = "1.4" > 1.4.< / a > < / h3 >
< h3 id = "s1.4" > 1.4. Documents and Version control< / h3 >
< h4 > < a name = "1.4.1" > 1.4.1.< / a > < / h4 >
< h4 id = "s1.4.1" > 1.4.1. The Security Policy Document < / h4 >
< p >
This Security Policy is part of the Configuration-Control Specification
for audit purposes (DRC-A.1).
@ -208,7 +208,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 >
< / p >
< h4 > < a name = "1.4.2" > 1.4.2.< / a > < / h4 >
< h4 id = "s1.4.2" > 1.4.2. The Security Manual (Practices) Document < / h4 >
< p >
This Policy explicitly defers detailed security practices to the
@ -235,7 +235,7 @@ they are expected to be documented in the other.
any section heading in the Policy.
< / p >
< h4 > < a name = "1.4.3" > 1.4.3.< / a > < / h4 >
< h4 id = "s1.4.3" > 1.4.3. The Security Procedures < / h4 >
< p >
The team leaders may from time to time
@ -248,9 +248,9 @@ SystemAdministration/Procedures</a>.
Each procedure must be referenced explicitly in the Security Manual.
< / p >
< h2 > < a name = "2" > 2.< / a > < / h2 >
< h2 id = "s2" > 2. PHYSICAL SECURITY< / h2 >
< h3 > < a name = "2.1" > 2.1.< / a > < / h3 >
< h3 id = "s2.1" > 2.1. Facility < / h3 >
< p >
CAcert shall host critical servers in a highly secure facility.
@ -258,9 +258,9 @@ There shall be independent verification of the physical and
access security.
< / p >
< h3 > < a name = "2.2" > 2.2.< / a > < / h3 >
< h3 id = "s2.2" > 2.2. Physical Assets < / h3 >
< h4 > < a name = "2.2.1" > 2.2.1.< / a > < / h4 >
< h4 id = "s2.2.1" > 2.2.1. Computers < / h4 >
< p >
Computers shall be inventoried before being put into service.
Inventory list shall be available to all
@ -273,7 +273,7 @@ Each unit shall be distinctly and uniquely identified on all visible sides.
Machines shall be housed in secured facilities (cages and/or locked racks).
< / p >
< h4 > < a name = "2.2.1.1" > 2.2.1.1< / a > < / h4 >
< h4 id = "s2.2.1.1" > 2.2.1.1 Acquisition < / h4 >
< p >
Acquisition of new equipment that is subject to a
pre-purchase security risk must be done from a
@ -282,7 +282,7 @@ Precautions must be taken to prevent equipment being
prepared in advance.
< / p >
< h4 > < a name = "2.2.2" > 2.2.2.< / a > < / h4 >
< h4 id = "s2.2.2" > 2.2.2. Service < / h4 >
< p >
Equipment that is subject to a service security risk
@ -290,9 +290,9 @@ must be retired if service is required.
See also § 2.2.3.3.
< / p >
< h4 > < a name = "2.2.3" > 2.2.3.< / a > < / h4 >
< h4 id = "s2.2.3" > 2.2.3. Media < / h4 >
< h4 > < a name = "2.2.3.1" > 2.2.3.1< / a > < / h4 >
< h4 id = "s2.2.3.1" > 2.2.3.1 Provisioning < / h4 >
< p >
Storage media (disk drives, tapes, removable media)
@ -304,7 +304,7 @@ New storage media (whether disk or removable) shall be
securely wiped and reformatted before use.
< / p >
< h4 > < a name = "2.2.3.2" > 2.2.3.2< / a > < / h4 >
< h4 id = "s2.2.3.2" > 2.2.3.2 Storage < / h4 >
< p >
Removable media shall be securely stored at all times,
@ -318,7 +318,7 @@ When there is a change to status of media,
a report is made to the log specifying the new status.
< / p >
< h4 > < a name = "2.2.3.3" > 2.2.3.3< / a > < / h4 >
< h4 id = "s2.2.3.3" > 2.2.3.3 Retirement < / h4 >
< p >
Storage media that is exposed to critical data and is
@ -340,7 +340,7 @@ Where critical data is involved,
two systems administrators must sign-off on each step.
< / p >
< h3 > < a name = "2.3" > 2.3.< / a > < / h3 >
< h3 id = "s2.3" > 2.3. Physical Access < / h3 >
< p >
In accordance with the principle of dual control,
@ -348,13 +348,13 @@ at least two persons authorized for access must
be on-site at the same time for physical access to be granted.
< / p >
< h4 > < a name = "2.3.1" > 2.3.1.< / a > < / h4 >
< h4 id = "s2.3.1" > 2.3.1. Access Authorisation < / h4 >
< p >
Access to physical equipment must be authorised.
< / p >
< h4 > < a name = "2.3.2" > 2.3.2.< / a > < / h4 >
< h4 id = "s2.3.2" > 2.3.2. Access Profiles < / h4 >
< p >
The Security Manual must present the different access profiles.
@ -378,13 +378,13 @@ All are responsible for protecting the data
from access by those not authorised.
< / p >
< h4 > < a name = "2.3.3" > 2.3.3.< / a > < / h4 >
< h4 id = "s2.3.3" > 2.3.3. Access Logging < / h4 >
< p >
All physical accesses are logged and reported to all.
< / p >
< h4 > < a name = "2.3.4" > 2.3.4.< / a > < / h4 >
< h4 id = "s2.3.4" > 2.3.4. Emergency Access < / h4 >
< p >
There must not be a procedure for emergency access.
@ -396,7 +396,7 @@ Arbitrator must be sought as soon as possible.
See DRP.
< / p >
< h4 > < a name = "2.3.5" > 2.3.5.< / a > & devices < / h4 >
< h4 id = "s2.3.5" > 2.3.5. Physical Security codes & devices < / h4 >
< p >
All personel who are in possession of physical security
@ -404,10 +404,10 @@ codes and devices (keys) are to be authorised and documented.
< / p >
< h2 > < a name = "3" > 3.< / a > < / h2 >
< h2 id = "s3" > 3. LOGICAL SECURITY< / h2 >
< h3 > < a name = "3.1" > 3.1.< / a > < / h3 >
< h4 > < a name = "3.1.1" > 3.1.1.< / a > < / h4 >
< h3 id = "s3.1" > 3.1. Network < / h3 >
< h4 id = "s3.1.1" > 3.1.1. Infrastructure < / h4 >
< p >
Current and complete diagrams of the physical and logical
@ -422,7 +422,7 @@ Diagrams should be revision controlled,
and must be updated when any change is made.
< / p >
< h5 > 3.1.1.1. External connectivity < / h5 >
< h5 id = "s3.1.1.1" > 3.1.1.1. External connectivity < / h5 >
< p >
Only such services as are required for normal operation
@ -436,47 +436,47 @@ such access may be granted under the procedures of the SM
and must be reported and logged.
< / p >
< h5 > 3.1.1.2. Internal connectivity < / h5 >
< h5 id = "s3.1.1.2" > 3.1.1.2. Internal connectivity < / h5 >
< p >
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).
< / p >
< h4 > < a name = "3.1.2" > 3.1.2.< / a > < / h4 >
< h4 id = "s3.1.2" > 3.1.2. Operating Configuration < / h4 >
< h5 > 3.1.2.1. Ingress < / h5 >
< h5 id = "s3.1.2.1" > 3.1.2.1. Ingress < / h5 >
< p >
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.
< / p >
< h5 > 3.1.2.2. Egress < / h5 >
< h5 id = "s3.1.2.2" > 3.1.2.2. Egress < / h5 >
< p >
All outbound traffic that is initiated shall be documented; traffic to other destinations must be blocked. Unexpected traffic must be logged as an exception.
< / p >
< h4 > < a name = "3.1.3" > 3.1.3.< / a > < / h4 >
< h4 id = "s3.1.3" > 3.1.3. Intrusion detection < / h4 >
< p >
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.
< / p >
< h3 > < a name = "3.2" > 3.2.< / a > < / h3 >
< h3 id = "s3.2" > 3.2. Operating System < / h3 >
< p >
Any operating system used for critical server machines must be available under an OSI-approved open source software license.
< / p >
< h4 > < a name = "3.2.1" > 3.2.1.< / a > < / h4 >
< h4 id = "s3.2.1" > 3.2.1. Disk Encryption < / h4 >
< p >
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.
< / p >
< h4 > < a name = "3.2.2" > 3.2.2.< / a > < / h4 >
< h4 id = "s3.2.2" > 3.2.2. Operating configuration < / h4 >
< p >
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.
@ -487,13 +487,13 @@ Documentation for installing and configuring servers with the appropriate softwa
< / p >
< h4 > < a name = "3.2.3" > 3.2.3.< / a > < / h4 >
< h4 id = "s3.2.3" > 3.2.3. Patching < / h4 >
< p >
Software used on production servers must be kept current with respect to patches affecting software security. Patch application is governed by CCS and 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).
< / p >
< h5 > < a name = "3.2.3.1" > 3.2.3.1.< / a > < / h5 >
< h5 id = "s3.2.3.1" > 3.2.3.1. “emergency” patching < / h5 >
< p >
Application of a patch is deemed an < i > emergency< / i >
@ -520,7 +520,7 @@ by the team leader to Board
independent of filed disputes.
< / p >
< h3 > < a name = "3.3" > 3.3.< / a > < / h3 >
< h3 id = "s3.3" > 3.3. Application < / h3 >
< p >
Systems administration is to provide a limited environment
@ -528,14 +528,14 @@ to Applications Engineers in order to install and maintain
the application.
< / p >
< h3 > < a name = "3.4" > 3.4.< / a > < / h3 >
< h3 id = "s3.4" > 3.4. Access control < / h3 >
< p >
All access to critical data and services shall be
controlled and logged.
< / p >
< h4 > < a name = "3.4.1" > 3.4.1.< / a > < / h4 >
< h4 id = "s3.4.1" > 3.4.1. Application Access < / h4 >
< p >
General access for Members shall be provided via
@ -545,7 +545,7 @@ Assurance Points and similar methods controlled in
the software system.
< / p >
< h4 > < a name = "3.4.2" > 3.4.2.< / a > < / h4 >
< h4 id = "s3.4.2" > 3.4.2. Special Authorisation < / h4 >
< p >
Additional or special access is granted according to the
@ -597,7 +597,7 @@ All changes of personnel
to the above lists are approved by the Board of CAcert.
< / p >
< h4 > < a name = "3.4.3" > 3.4.3.< / a > < / h4 >
< h4 id = "s3.4.3" > 3.4.3. Authentication < / h4 >
< p >
Strong methods of authentication shall be used
@ -605,7 +605,7 @@ wherever possible.
All authentication schemes must be documented.
< / p >
< h4 > < a name = "3.4.4" > 3.4.4.< / a > < / h4 >
< h4 id = "s3.4.4" > 3.4.4. Removing access < / h4 >
< p >
Follow-up actions to termination must be documented.
@ -615,9 +615,9 @@ See §9.1.7.
< h2 > < a name = "4" > 4.< / a > < / h2 >
< h2 id = "s4" > 4. OPERATIONAL SECURITY < / h2 >
< h3 > < a name = "4.1" > 4.1.< / a > < / h3 >
< h3 id = "s4.1" > 4.1. System administration < / h3 >
< p >
Primary systems administration tasks
@ -628,7 +628,7 @@ account creation and deletion,
and hardware maintenance.
< / p >
< h4 > < a name = "4.1.1" > 4.1.1.< / a > < / h4 >
< h4 id = "s4.1.1" > 4.1.1. Privileged accounts and passphrases < / h4 >
< p >
Access to Accounts
(root and user via SSH or console)
@ -640,7 +640,7 @@ and Application Engineers
in all cases.
< / p >
< h5 > < a name = "4.1.1.1" > 4.1.1.1.< / a > < / h5 >
< h5 id = "s4.1.1.1" > 4.1.1.1. Authorized users < / h5 >
< p >
Only System Administrators
and Application Engineers
@ -649,33 +649,33 @@ in §3.4.2 are authorized to access accounts,
unless specifically directed by the Arbitrator.
< / p >
< h5 > < a name = "4.1.1.2" > 4.1.1.2.< / a > < / h5 >
< h5 id = "s4.1.1.2" > 4.1.1.2. Access to Systems< / h5 >
< p >
All access is secured, logged and monitored.
< / p >
< h5 > < a name = "4.1.1.3" > 4.1.1.3.< / a > < / h5 >
< h5 id = "s4.1.1.3" > 4.1.1.3. Changing < / h5 >
< p >
The procedure for changing passphrases and SSH keys shall be documented.
< / p >
< h4 > < a name = "4.1.2" > 4.1.2.< / a > < / h4 >
< h4 id = "s4.1.2" > 4.1.2. Required staff response time < / h4 >
< p >
Response times should be documented for Disaster Recovery planning. See § 6.
< / p >
< h4 > < a name = "4.1.3" > 4.1.3.< / a > < / h4 >
< h4 id = "s4.1.3" > 4.1.3. Change management procedures < / h4 >
< p >
All changes made to system configuration must be recorded
and reported in regular summaries to the Board of CAcert.
< / p >
< h4 > < a name = "4.1.4" > 4.1.4.< / a > < / h4 >
< h4 id = "s4.1.4" > 4.1.4. Outsourcing < / h4 >
< h3 > < a name = "4.2" > 4.2.< / a > < / h3 >
< h3 id = "s4.2" > 4.2. Logging < / h3 >
< h4 > < a name = "4.2.1" > 4.2.1.< / a > < / h4 >
< h4 id = "s4.2.1" > 4.2.1. Coverage < / h4 >
< p >
All sensitive events should be logged reliably.
@ -683,7 +683,7 @@ Logs should be deleted after an appropriate amount of time
as documented in the Security Manual.
< / p >
< h4 > < a name = "4.2.2" > 4.2.2.< / a > < / h4 >
< h4 id = "s4.2.2" > 4.2.2. Access and Security < / h4 >
< p >
Access to logs must be restricted.
@ -691,7 +691,7 @@ The security of the logs should be documented.
The records retention should be documented.
< / p >
< h4 > < a name = "4.2.3" > 4.2.3.< / a > < / h4 >
< h4 id = "s4.2.3" > 4.2.3. Automated logs < / h4 >
< p >
Logging should be automated,
and use should be made of appropriate system-provided automated tools.
@ -699,7 +699,7 @@ Automated logs should be reviewed periodically;
suspicious events should be flagged and investigated in a timely fashion.
< / p >
< h4 > < a name = "4.2.4" > 4.2.4.< / a > < / h4 >
< h4 id = "s4.2.4" > 4.2.4. Operational (manual) logs < / h4 >
< p >
Configuration changes, no matter how small, must be logged.
< / p >
@ -710,14 +710,14 @@ report provided by the accessor and by
the Access Engineer.
< / p >
< h3 > < a name = "4.3" > 4.3.< / a > < / h3 >
< h3 id = "s4.3" > 4.3. Backup < / h3 >
< p >
The procedure for all backups must be documented,
according to the following sub-headings.
< / p >
< h4 > < a name = "4.3.1" > 4.3.1.< / a > < / h4 >
< h4 id = "s4.3.1" > 4.3.1. Type < / h4 >
< p >
Backups must be taken for operational
and for disaster recovery purposes.
@ -725,26 +725,26 @@ Operational backups may be online and local.
Disaster recovery backups must be offline and remote.
< / p >
< h4 > < a name = "4.3.2" > 4.3.2.< / a > < / h4 >
< h4 id = "s4.3.2" > 4.3.2. Frequency < / h4 >
< h4 > < a name = "4.3.3" > 4.3.3.< / a > < / h4 >
< h4 id = "s4.3.3" > 4.3.3. Storage < / h4 >
< p >
Backups must be protected to the same level as the critical systems themselves.
Disaster recovery backups may be distributed.
< / p >
< h4 > < a name = "4.3.4" > 4.3.4.< / a > < / h4 >
< h4 id = "s4.3.4" > 4.3.4. Retention period and Re-use < / h4 >
< p >
See § 2.2.3.
< / p >
< h4 > < a name = "4.3.5" > 4.3.5.< / a > < / h4 >
< h4 id = "s4.3.5" > 4.3.5. Encryption < / h4 >
< p >
Backups must be encrypted and must only be transmitted via secured channels.
Off-site backups must be dual-encrypted using divergent methods.
< / p >
< h4 > < a name = "4.3.6" > 4.3.6.< / a > < / h4 >
< h4 id = "s4.3.6" > 4.3.6. Verifying Backups < / h4 >
< p >
Two CAcert System Administrators must be
present for verification of a backup.
@ -752,14 +752,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.
< / p >
< h4 > < a name = "4.3.7" > 4.3.7.< / a > < / h4 >
< h4 id = "s4.3.7" > 4.3.7. Key Management < / h4 >
< p >
The encryption keys must be stored securely by the
CAcert systems administrators.
Paper documentation must be stored with manual backups.
< / p >
< h4 > < a name = "4.3.8" > 4.3.8.< / a > < / h4 >
< h4 id = "s4.3.8" > 4.3.8. Reading Backups < / h4 >
< p >
Conditions and procedures for examining the backups
must be documented,
@ -767,21 +767,21 @@ and must be under Arbitrator control for purposes
other than verification and recovery.
< / p >
< h3 > < a name = "4.4" > 4.4.< / a > < / h3 >
< h3 id = "s4.4" > 4.4. Data retention < / h3 >
< h4 > < a name = "4.4.1" > 4.4.1.< / a > < / h4 >
< h4 id = "s4.4.1" > 4.4.1. User data < / h4 >
< p >
Termination of user data is under direction of the Arbitrator.
See CCA.
< / p >
< h4 > < a name = "4.4.2" > 4.4.2.< / a > < / h4 >
< h4 id = "s4.4.2" > 4.4.2. System logs < / h4 >
< p >
See § 4.2.1.
< / p >
< h4 > < a name = "4.4.3" > 4.4.3.< / a > < / h4 >
< h4 id = "s4.4.3" > 4.4.3. Incident reports < / h4 >
< p >
See § 5.6.
< / p >
@ -789,23 +789,23 @@ See §5.6.
< h2 > < a name = "5" > 5.< / a > < / h2 >
< h2 id = "s5" > 5. INCIDENT RESPONSE< / h2 >
< h3 > < a name = "5.1" > 5.1.< / a > < / h3 >
< h3 id = "s5.1" > 5.1. Incidents < / h3 >
< h3 > < a name = "5.2" > 5.2.< / a > < / h3 >
< h3 id = "s5.2" > 5.2. Detection < / h3 >
< p >
The standard of monitoring, alerting and reporting must be documented.
< / p >
< h3 > < a name = "5.3" > 5.3.< / a > < / h3 >
< h4 > < a name = "5.3.1" > 5.3.1.< / a > < / h4 >
< h3 id = "s5.3" > 5.3. Immediate Action < / h3 >
< h4 id = "s5.3.1" > 5.3.1. Severity and Priority < / h4 >
< p >
On discovery of an incident,
an initial assessment of severity and priority must be made.
< / p >
< h4 > < a name = "5.3.2" > 5.3.2.< / a > < / h4 >
< h4 id = "s5.3.2" > 5.3.2. Communications < / h4 >
< p >
An initial report should be circulated.
< / p >
@ -815,7 +815,7 @@ A communications forum should be established for direct
support of high priority or high severity incidents.
< / p >
< h4 > < a name = "5.3.3" > 5.3.3.< / a > < / h4 >
< h4 id = "s5.3.3" > 5.3.3. Escalation < / h4 >
< p >
A process of escalation should be established
for oversight and management purposes,
@ -824,7 +824,7 @@ Oversight starts with four eyes and ends with the Arbitrator.
Management starts with the team leader and ends with the Board.
< / p >
< h3 > < a name = "5.4" > 5.4.< / a > < / h3 >
< h3 id = "s5.4" > 5.4. Investigation < / h3 >
< p >
Incidents must be investigated.
The investigation must be documented.
@ -832,9 +832,9 @@ If the severity is high,
evidence must be secured and escalated to Arbitration.
< / p >
< h3 > < a name = "5.5" > 5.5.< / a > < / h3 >
< h3 id = "s5.5" > 5.5. Response < / h3 >
< h3 > < a name = "5.6" > 5.6.< / a > < / h3 >
< h3 id = "s5.6" > 5.6. Report < / h3 >
< p >
Incident reports shall be be published.
@ -856,32 +856,32 @@ secret, nor the manner and methods be kept confidential.
See § 9.5.
< / p >
< h2 > < a name = "6" > 6.< / a > < / h2 >
< h2 id = "s6" > 6. DISASTER RECOVERY< / h2 >
< p >
Disaster Recovery is the responsibility of the Board of CAcert Inc.
< / p >
< h3 > < a name = "6.1" > 6.1. < / a > < / h3 >
< h3 id = "s6.1" > 6.1. Business Processes < / h3 >
< p >
Board must develop and maintain documentation on Business Processes.
From this list, Core Processes for business continuity / disaster recovery
purposes must be identified.
< / p >
< h3 > < a name = "6.2" > 6.2. < / a > < / h3 >
< h3 id = "s6.2" > 6.2. Recovery Times < / h3 >
< p >
Board should identify standard process times for all processes,
and must designate Maximum Acceptable Outages
and Recovery Time Objectives for the Core Processes.
< / p >
< h3 > < a name = "6.3" > 6.3. < / a > < / h3 >
< h3 id = "s6.3" > 6.3. Plan < / h3 >
< p >
Board must have a basic plan to recover.
< / p >
< h3 > < a name = "6.4" > 6.4. < / a > < / h3 >
< h3 id = "s6.4" > 6.4. Key Persons List < / h3 >
< p >
Board must maintain a key persons List with all the
contact information needed.
@ -892,14 +892,14 @@ infrastructure is not available.
< h2 > < a name = "7" > 7.< / a > < / h2 >
< h2 id = "s7" > 7. SOFTWARE ASSESSMENT< / h2 >
< p >
Software assessment team is responsible
for the security and maintenance of the code.
< / p >
< h3 > < a name = "7.1" > 7.1. < / a > < / h3 >
< h3 id = "s7.1" > 7.1. Authority < / h3 >
< p >
The source code is under CCS.
@ -907,7 +907,7 @@ Additions to the team are approved by Board.
See § 3.4.2.
< / p >
< h3 > < a name = "7.2" > 7.2. < / a > < / h3 >
< h3 id = "s7.2" > 7.2. Tasks < / h3 >
< p >
The primary tasks for Software Assessors are:
< / p >
@ -948,7 +948,7 @@ The primary tasks for Application Engineers are:
< h3 > < a name = "7.3" > 7.3. < / a > < / h3 >
< h3 id = "s7.3" > 7.3. Repository < / h3 >
< p >
The application code and patches are maintained
@ -976,7 +976,7 @@ systems administation team.
Access is made available to the Application Engineers.
< / p >
< h3 > < a name = "7.4" > 7.4. < / a > < / h3 >
< h3 id = "s7.4" > 7.4. Review < / h3 >
< p >
At the minimum,
@ -988,7 +988,7 @@ Author and signers-off must be logged.
The riskier the source is, the more reviews have to be done.
< / p >
< h3 > < a name = "7.5" > 7.5. < / a > < / h3 >
< h3 id = "s7.5" > 7.5. Test and Bugs < / h3 >
< p >
Software assessment team maintains a test system.
@ -1005,7 +1005,7 @@ Bug submission access should be provided to
any Member that requests it.
< / p >
< h3 > < a name = "7.6" > 7.6. < / a > < span class = "strike" > Handover< / span > < span class = "change" > Production< / span > < / h3 >
< h3 id = "s7.6" > 7.6. < span class = "strike" > Handover< / span > < span class = "change" > Production< / span > < / h3 >
< p class = "change" >
The Application Engineer is a role within Software Assessment
@ -1032,10 +1032,10 @@ See §3.3.
< / p >
< h2 > < a name = "8" > 8.< / a > < / h2 >
< h2 id = "s8" > 8. SUPPORT< / h2 >
< h3 > < a name = "8.1" > 8.1. < / a > < / h3 >
< h3 id = "s8.1" > 8.1. Authority < / h3 >
< p >
The software interface gives features to Support Engineer.
Access to the special features is under tight control.
@ -1061,7 +1061,7 @@ Support Engineers are responsible to follow the
policies and practices.
< / p >
< h3 > < a name = "8.2" > 8.2. < / a > < / h3 >
< h3 id = "s8.2" > 8.2. Responsibilities < / h3 >
< p >
Support Engineers have these responsibilities:
@ -1077,7 +1077,7 @@ Support Engineers have these responsibilities:
Tasks and responsibilities as specified in other policies, such as DRP.
< / li > < / ul >
< h3 > < a name = "8.3" > 8.3. < / a > < / h3 >
< h3 id = "s8.3" > 8.3. Channels < / h3 >
< p >
Support may always be contacted by email at
@ -1086,7 +1086,7 @@ Other channels may be made available and documented
in Security Manual.
< / p >
< h3 > < a name = "8.4" > 8.4. < / a > < / h3 >
< h3 id = "s8.4" > 8.4. Records and Logs < / h3 >
< ul >
< li > use of restricted interfaces must be logged. < / li >
@ -1094,7 +1094,7 @@ in Security Manual.
< li > private requests for support should be referred to proper channels and logged there (e.g., by CCs) < / li >
< / ul >
< h3 > < a name = "8.5" > 8.5. < / a > < / h3 >
< h3 id = "s8.5" > 8.5. Arbitration < / h3 >
< p >
Support Engineers refer questions requiring authority
to Arbitration, and may also be called upon to act as
@ -1106,15 +1106,15 @@ these topics, even if not listed as Arbitrators
or Case Managers.
< / p >
< h3 > < a name = "8.6" > 8.6. < / a > < / h3 >
< h3 id = "s8.6" > 8.6. References < / h3 >
< h2 > < a name = "9" > 9.< / a > < / h2 >
< h2 id = "s9" > 9. ADMINISTRATIVE< / h2 >
< h3 > < a name = "9.1" > 9.1. < / a > < / h3 >
< h3 id = "s9.1" > 9.1. Staffing< / h3 >
< h4 > < a name = "9.1.1" > 9.1.1. < / a > < / h4 >
< h4 id = "s9.1.1" > 9.1.1. Roles and responsibilities< / h4 >
< ul >
< li > Access Engineer: responsible for controlling access to hardware, and maintaining hardware. < / li >
@ -1127,7 +1127,7 @@ or Case Managers.
< li > Board: authorise new individuals and accesses. Coordinate overall. < / li >
< / ul >
< h4 > < a name = "9.1.2" > 9.1.2. < / a > < / h4 >
< h4 id = "s9.1.2" > 9.1.2. Staffing levels< / h4 >
< p >
Each team should have a minimum of two members available at any time.
@ -1142,7 +1142,7 @@ One individual in each team is designated team leader
and reports to Board.
< / p >
< h4 > < a name = "9.1.3" > 9.1.3. < / a > < / h4 >
< h4 id = "s9.1.3" > 9.1.3. Process of new Team Members< / h4 >
< p >
New team members need:
@ -1158,7 +1158,7 @@ New team members need:
The team supports the process of adding new team members.
< / p >
< h4 > < a name = "9.1.4" > 9.1.4. < / a > < / h4 >
< h4 id = "s9.1.4" > 9.1.4. Arbitrated Background Check - Procedures< / h4 >
< p >
The Arbitrated Background Check ("ABC")
must be conducted under the direction of the Arbitrator,
@ -1166,7 +1166,7 @@ with a separate Case Manager to provide four eyes.
ABCs are carried out with full seriousness.
< / p >
< h4 > < a name = "9.1.4.1" > 9.1.4.1. < / a > < / h4 >
< h4 id = "s9.1.4.1" > 9.1.4.1. Scope < / h4 >
< p >
An investigation within ABC should include examination of:
< / p >
@ -1180,12 +1180,12 @@ An investigation within ABC should include examination of:
< li > conflicts of interest < / li >
< / ul >
< h4 > < a name = "9.1.4.2" > 9.1.4.2. < / a > < / h4 >
< h4 id = "s9.1.4.2" > 9.1.4.2. Coverage < / h4 >
< p >
ABC is to be done on every individual in a critical role.
< / p >
< h4 > < a name = "9.1.4.3" > 9.1.4.3. < / a > < / h4 >
< h4 id = "s9.1.4.3" > 9.1.4.3. Documentation < / h4 >
< p >
The process of the ABC should be documented as a procedure.
@ -1202,7 +1202,7 @@ It must include:
< li > Contact information. See § 10.1. < / li >
< / ul >
< h4 > < a name = "9.1.4.4" > 9.1.4.4. < / a > < / h4 >
< h4 id = "s9.1.4.4" > 9.1.4.4. Privacy for Critical Roles< / h4 >
< p >
The following privacy considerations exist:
@ -1220,7 +1220,7 @@ The following privacy considerations exist:
CAcert trusted roles give up some privacy for the privacy of others.
< / p >
< h4 > < a name = "9.1.5" > 9.1.5. < / a > < / h4 >
< h4 id = "s9.1.5" > 9.1.5. Authorisation < / h4 >
< p >
Individuals and access (both) must be authorised by the Board.
@ -1237,7 +1237,7 @@ Deliberations and decisions should be documented.
All conflicts of interest should be examined.
< / p >
< h4 > < a name = "9.1.6" > 9.1.6. < / a > < / h4 >
< h4 id = "s9.1.6" > 9.1.6. Security< / h4 >
< p >
It is the responsibility of all individuals to
@ -1251,7 +1251,7 @@ or to ensure that it is reported fully.
See § 9.5.
< / p >
< h4 > < a name = "9.1.7" > 9.1.7. < / a > < / h4 >
< h4 id = "s9.1.7" > 9.1.7. Termination of staff< / h4 >
< p >
Termination of access may be for resignation, Arbitration ruling,
@ -1269,7 +1269,7 @@ and the Arbitrator may reinstate any provision
of this agreement or bind the person to a ruling.
< / p >
< h4 > < a name = "9.1.8" > 9.1.8. < / a > < / h4 >
< h4 id = "s9.1.8" > 9.1.8. HR and Training< / h4 >
< p >
It is the responsibility of the team leaders
@ -1277,9 +1277,9 @@ to coordinate technical testing and training,
especially of new team members.
< / p >
< h3 > < a name = "9.2" > 9.2. < / a > < / h3 >
< h3 id = "s9.2" > 9.2. Root Key Management< / h3 >
< h4 > < a name = "9.2.1" > 9.2.1. < / a > < / h4 >
< h4 id = "s9.2.1" > 9.2.1. Root Key generation< / h4 >
< p >
Root keys are generated only on instruction from the Board.
@ -1297,7 +1297,7 @@ The procedure must include:
< li > Confirmation by each participant over the process and the results. < / li >
< / ul >
< h4 > < a name = "9.2.2" > 9.2.2. < / a > < / h4 >
< h4 id = "s9.2.2" > 9.2.2. Backup and escrow< / h4 >
< p >
Root keys must be kept on reliable removable media used for that purpose only.
@ -1311,24 +1311,24 @@ The top-level root must be escrowed under Board control.
Subroots may be escrowed by either Board or Systems Administration Team.
< / p >
< h4 > < a name = "9.2.3" > 9.2.3. < / a > < / h4 >
< h4 id = "s9.2.3" > 9.2.3. Recovery< / h4 >
< p >
Recovery must only be conducted under Arbitrator authority.
< / p >
< h4 > < a name = "9.2.4" > 9.2.4. < / a > < / h4 >
< h4 id = "s9.2.4" > 9.2.4. Revocation < / h4 >
< h3 > < a name = "9.3" > 9.3. < / a > < / h3 >
< h3 id = "s9.3" > 9.3. Legal< / h3 >
< h4 > < a name = "9.3.1" > 9.3.1. < / a > < / h4 >
< h4 id = "s9.3.1" > 9.3.1. Responsibility< / h4 >
< p >
The Board is responsible to the Community to manage
the CA at the executive level.
< / p >
< h4 > < a name = "9.3.2" > 9.3.2. < / a > < / h4 >
< h4 id = "s9.3.2" > 9.3.2. Response to external (legal) inquiry< / h4 >
< p >
All external inquiries of security import are filed as disputes and placed before the Arbitrator under DRP.
@ -1345,7 +1345,7 @@ The Arbitrator's ruling may instruct individuals,
and becomes your authority to act.
< / p >
< h3 > < a name = "9.4" > 9.4.< / a > < / h3 >
< h3 id = "s9.4" > 9.4. Outsourcing < / h3 >
< p >
Components may be outsourced.
@ -1387,7 +1387,7 @@ Contracts should be written with the above in mind.
< / p >
< h3 > < a name = "9.5" > 9.5< / a > < / h3 >
< h3 id = "s9.5" > 9.5 Confidentiality, Secrecy < / h3 >
< p >
CAcert is an open organisation and adopts a principle
@ -1412,19 +1412,19 @@ All should strive to reduce or remove any such
restriction.
< / p >
< h2 > < a name = "10" > 10.< / a > < / h2 >
< h2 id = "s10" > 10. REFERENCES< / h2 >
< h3 > < a name = "10.1" > 10.1< / a > < / h3 >
< h3 id = "s10.1" > 10.1 Contacts < / h3 >
< p >
Contact information for all key people and teams must be documented.
< / p >
< h3 > < a name = "10.2" > 10.2< / a > < / h3 >
< h3 id = "s10.2" > 10.2 Documents < / h3 >
< p >
All incorporated Documents must be documented.
< / p >
< h3 > < a name = "10.3" > 10.3< / a > < / h3 >
< h3 id = "s10.3" > 10.3 Related Documents < / h3 >
< p >
Relevant and helpful Documents should be referenced for convenience.
< / p >
Ian Grigg
14 years ago