| C1.1 Repository functions on well supported operating systems and other core infrastructural software. |
| C1.2 Repository ensures that it has adequate hardware and software support for backup functionality sufficient for the repository’s services and for the data held, e.g., metadata associated with access controls, repository main content. |
| C1.3 Repository manages the number and location of copies of all digital objects. |
| C1.4 Repository has mechanisms in place to ensure any/multiple copies of digital objects are synchronized. |
| C1.5 Repository has effective mechanisms to detect bit corruption or loss. |
| C1.6 Repository reports to its administration all incidents of data corruption or loss, and steps taken to repair/replace corrupt or lost data. |
| C1.7 Repository has defined processes for storage media and/or hardware change (e.g., refreshing, migration). |
| C1.8 Repository has a documented change management process that identifies changes to critical processes that potentially affect the repository’s ability to comply with its mandatory responsibilities. |
| C1.9 Repository has a process for testing the effect of critical changes to the system. |
| C1.10 Repository has a process to react to the availability of new software security updates based on a risk-benefit assessment. |
| C2.1 Repository has hardware technologies appropriate to the services it provides to its designated communities and has procedures in place to receive and monitor notifications, and evaluate when hardware technology changes are needed. |
| C2.2 Repository has software technologies appropriate to the services it provides to its designated community(ies) and has procedures in place to receive and monitor notifications, and evaluate when software technology changes are needed. |
| C3.1 Repository maintains a systematic analysis of such factors as data, systems, personnel, physical plant, and security needs. |
| C3.2 Repository has implemented controls to adequately address each of the defined security needs. |
| C3.3 Repository staff have delineated roles, responsibilities, and authorizations related to implementing changes within the system. |
| C3.4 Repository has suitable written disaster preparedness and recovery plan(s), including at least one off-site backup of all preserved information together with an offsite copy of the recovery plan(s). |