Security Policy for CAcert Systems

Creation date: 2009-02-16
Status: work-in-progress

1. Introduction

1.1. Motivation and Scope

This Security Policy sets out required procedures for the secure operation of the CAcert critical computer systems. These systems include:

1. Physical hardware mounting the logical services
2. Webserver + database (core server(s))
3. Signing service (signing server)
4. Support interface
5. Source code (changes and patches)

1.1.1. Effected Personnel

These roles and teams are effected:

• Hardware Controllers (Oophaga)
• Direct Hardware Access Systems Administrators (as listed in Oophaga Appendix B Access List)
• Application Administrators (online access to critical systems at Unix level)
• Support Team (online access via administration interfaces)
• Software Development Team (approval of application code)

1.1.2. Out of Scope

Non-critical systems are not covered by this manual, but may be guided by it, and impacted where they are found within the security context. Architecture is out of scope, see CPS#6.2.

1.2. Principles

Important principles of this Security Policy are:

• dual control -- at least two individuals must control a task
• 4 eyes -- at least two individuals must be present during a task, one to execute and one to observe.
• redundancy -- no single individual is the only one authorized to perform a task.
• escrow -- where critical information (backups, passwords) is kept with other parties
• logging -- where events are recorded in a file
• separation of concerns -- when a core task is split between two people from different areas
• Audit -- where external reviewers do checks on practices and policies

Each task or asset is covered by a variety of protections 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

This Security Policy is part of the configuration-control specification for audit purposes (DRC). 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

This Policy explicitly defers detailed security practices to the Security Manual ("SM"), The SM says how things are done. As practices are things that vary from time to time, including between each event of practice, 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

The Systems Administration team may from time to time explicitly defer single, cohesive components of the security practices into separate procedures documents. Each procedure should be managed in a wiki page under their control, probably at SystemAdministration/Procedures. Each procedure must be referenced explicitly in the Security Manual.

2. Physical Security

Physical assets and security procedures are generally provided and maintained as set forth in the Memorandum of Understanding between CAcert and Stichting Oophaga Foundation of 10 July 2007, and as amended from time to time. Approval of both boards of CAcert and Oophaga is required for changes to the MoU.

The MoU places responsibility for the physical assets (hardware), hosting and for control of access to the hardware with Oophaga.

2.1. Facility

CAcert shall host critical servers in a highly secure facility. There shall be independent verification of the physical and access security.

2.2. Physical Assets

• Big question here is whether Oophaga falls inside SP/SM or not.
• 2nd Big Question is whether Oophaga is in SP or in SM.

2.2.1. Computers

Computers shall be inventoried before being put into service. Inventory list shall be available to all Systems Administrators. Units shall have nickname clearly marked on front and rear of chassis. Machines shall be housed in secured facilities (cages and/or locked racks).

2.2.1.1 Acquisition

Acquisition of new equipment that is subject to a pre-purchase security risk must be done from a vendor that is regularly and commercially in business. Precautions must be taken to prevent equipment being prepared in advance.

Acquisition may be done by CAcert systems administrators but the ownership and control of the hardware transfers to Oophaga the moment the equipment is in use.

2.2.2. Cables

Cabling to all equipment shall be labeled at both ends with identification of end points.

2.2.3. Media

2.2.3.1 Provisioning

Storage media (disk drives, tapes, removable media) are inventoried upon acquisition by Oophaga. CAcert system administrators will report any changes in the use or location of the media to Oophaga and to the routine logging list.

New storage media (whether disk or removable) shall be securely wiped and reformatted before use.

2.2.3.2 Storage

Removable media shall be securely stored at all times, including when not in use. When there is a change to status of media, a report is made to the log specifying the new status (sysadmins present, steps taken, location of storage, etc). Drives that are kept for reuse are wiped securely before storage. Reuse can only be within critical systems.

2.2.3.3 Retirement

Storage media that is exposed to critical data and is to be retired from service shall be destroyed or otherwise secured. The following steps are to be taken:

1. The media is to be securely erased.
2. One of the following, in order of preference:
   1. rendered unreadable via physical means that destroys the platters and electronics, or,
   2. disposed of via a licensed disposal facility, or
   3. sealed and stored securely until the data has expired. The years of retirement and of expiry should be marked by CAcert systems administrator.

Records of secure erasure and method of final disposal shall be tracked in the asset inventory. Where critical data is involved, 2 system administrators must sign-off on each step.

2.3. Physical Access

In accordance with the principle of dual control, at least two persons authorized for access must be on-site at the same time for physical access to be granted.

2.3.1. Access Authorisation

Access to physical equipment must be authorised.

2.3.2. Access Profiles

The Security Manual must present the different access profiles. At least one CAcert systems administrator will be present for logical access to CAcert critical servers. Only the most basic and safest of accesses should be done with one CAcert systems administrator present. Oophaga representatives must not access the data.

2.3.3. Access Logging

All physical accesses are logged and reported to all.

2.3.4. Emergency Access

There is no procedure for emergency access. If emergency access is gained, this must be reported and justified immediately. See DPR.

2.3.5. Physical Security codes & devices

All personel who are in possession of physical security codes and devices (keys) are to be authorised and documented.

End

This is the end of the Security Policy.