Skip to content

5.1.1.7 Risk management policy or plan for failures affecting copies of contents

The repository shall have a risk management policy or plan addressing whether technical or operational failures can affect copies of contents in a way that can lead to loss.

Supporting Text

This is necessary in order to ensure that the same (or similar) event does not result in the loss of other secured copies of the archive content.

Examples for Meeting the Requirement

Documented testing procedures; documentation of results from prior tests on the other secured copies, documentation of change management process; assessment of risk associated with a process change; analysis of the expected impact of a process change.

Discussion

There are examples of hardware failures that strike several copies of the archive contents at the same time, human operational errors that are carried out for several copies of archive contents, major media migrations performed at several copies at the same time, media (disks/tapes) supply shortage when a tsunami hit the area where a large percentage of the media were produced.

The repository cannot foresee all possible cases, but can contribute with documentation of independent components for the copies of archive holding (hardware, media, operating system, programs, operational procedures, etc.) as well as coordination efforts to prevent, for example, simultaneous bigger upgrades.

Evidence Provided

This requirement was added in the most recent version of ISO 16363. The APTrust Certification Working Group is working on updating this page.