+OPS.1.2.2 Archiving
---+OPS.1.2.2.G1. Obsolescence of Archive Systems
---+OPS.1.2.2.G2. Inadequate Indexing Keys for Archives
---+OPS.1.2.2.G3. Unauthorised Archive Access due to Insufficient Logging
---+OPS.1.2.2.G4. Inadequate Transfer of Paper-Based Data to an Electronic Archive
---+OPS.1.2.2.G5. Insufficient Renewal of Cryptographic Procedures During Archiving
---+OPS.1.2.2.G6. Insufficient Archiving Audits
---+OPS.1.2.2.G7. Violation of Legal Framework Conditions Regarding the Use of Archive Systems
---+OPS.1.2.2.A1 Determining Parameters for Electronic Archiving (B)
---+OPS.1.2.2.A2 Drawing up an Archiving Concept (B)
---+OPS.1.2.2.A3 Appropriate Installation of Archive Systems and Storage of Archive Media [IT Operation Department] (B)
---+OPS.1.2.2.A4 Consistent Indexing of Data During Archiving [IT Operation Department, User] (B)
---+OPS.1.2.2.A5 Regular Regeneration of Archived Data [IT Operation Department] (B)
---+OPS.1.2.2.A6 Protection of the Integrity of the Index Database of Archive Systems [IT Operation Department] (B)
---+OPS.1.2.2.A7 Regular Backups of System and Archive Data [IT Operation Department] (B)
---+OPS.1.2.2.A8 Logging Archival Access [IT Operation Department] (B)
---+OPS.1.2.2.A9 Selection of Suitable Data Formats for Archiving Documents [IT Operation Department] (B)
---+OPS.1.2.2.A10 Drawing Up a Policy for Using Archive Systems [IT Operation Department] (S)
---+OPS.1.2.2.A11 Instruction Regarding the Administration and Operation of the Archive System [IT Operation Department, User] (S)
---+OPS.1.2.2.A12 Monitoring of Storage Resources for Archive Media [IT Operation Department] (S)
---+OPS.1.2.2.A13 Regular Auditing of Archiving Processes (S)
---+OPS.1.2.2.A14 Regular Observation of the Market for Archive Systems [IT Operation Department] (S)
---+OPS.1.2.2.A15 Regular Processing of Cryptographically Secured Data During Archiving [IT Operation Department] (S)
---+OPS.1.2.2.A16 Regular Renewal of Technical Archive System Components [IT Operation Department] (S)
---+OPS.1.2.2.A17 Selecting a Suitable Archiving System [IT Operation Department] (S)
---+OPS.1.2.2.A18 Using Appropriate Archive Media [IT Operation Department] (S)
---+OPS.1.2.2.A19 Regular Function and Recovery Tests for Archiving [IT Operation Department] (S)
---+OPS.1.2.2.A20 Appropriate Use of Cryptographic Methods for Archiving [IT Operation Department] (H)
---+OPS.1.2.2.A21 Transfer of Paper-based Data to Electronic Archives (H)

OPS.1.2.2 Archiving

Introduction

Archiving plays a special role in the document management process. On the one hand, digital documents are expected to be available until the end of a specified retention period. On the other, their confidentiality and integrity need to be preserved. In addition, the context must be maintained so that the respective stored sequence can be reconstructed.

For the entire duration of long-term storage, corresponding safeguards for information maintenance and, if required, measures for maintaining evidence must therefore be implemented.

The German IT terms for “electronic archiving” and “electronic long-term storage” are sometimes used synonymously. For better clarity, the terms “archiving” and “digital long-term archive” are used in this module. An IT process for storing electronic documents is referred to as an “archive system”, “digital archive”, or “long-term storage”. The retention period of documents depends on the applicable legal regulations and other requirements, as well as on the purpose of the data involved.

In this module, the term “documents” includes data and digital documents unless these are expressly used with a differing meaning.

From a German legal perspective, the term “archiving” is substantiated and documented by the federal and state archiving laws. "Archiving" in the legally correct sense refers solely to government documents. It refers to how the documents of an authority are to be segregated and preserved by a competent governmental facility (Federal Archive) for an unlimited period of time as soon as they are no longer needed for the purposes of that authority (see Articles 1 and 2 of the German Federal Archives Act (BArchG)). This type of archiving should distinguished from the time-limited retention considered in this module.

Objective

This module describes how digital documents can be securely archived for the long term such that they are reproducible and cannot be changed. To this end, it defines requirements that can be used to securely plan, implement, and operate an archive system.

The storage of paper documents is not considered in this module, but requirements are made as to how these can be digitised and archived.

Scoping and Modelling

Module OPS.1.2.2 Archiving must be applied once to any information domain that involves long-term archiving of electronic documents. Long-term archiving may be necessary due to external or internal requirements, or a system for long-term archiving of electronic documents may already be in operation.

This module does not deal with archiving for an unlimited period of time in the sense of Germany's federal and state archive laws.

It describes security safeguards with which electronic documents can be stored and preserved for the long term within the framework of the applicable retention periods. Safeguards for operative backups are not addressed in this module. Requirements in this regard are covered in CON.3 Backup Concept.

Long-term digital storage consists of individual components, such as a database. Detailed descriptions of how such components can be operated securely are not covered in this module. The requirements of the corresponding modules, such as APP.4.3 Relational Database Systems, SYS.1.1 General Server, and SYS.1.8 Storage Systems should be considered in this regard.

Useful resources

In its publication “Bekanntmachung zur elektronischen Signatur nach dem Signaturgesetz und der Signaturverordnung: Auflistung geeigneter Algorithmen und Parameter” [Announcement on Electronic Signatures Under the Digital Signature Act and the Digital Signature Ordinance: List of Suitable Algorithms and Parameters], the Federal Network Agency for Electricity, Gas, Telecommunications, Post and Railway (BnetzA) lists algorithms and parameters that have been classified as suitable.

The German Institute for Standardisation (DIN) defines criteria for trustworthy digital long-term archives in DIN 31644:2012-04, “Information and Documentation – Criteria for Trustworthy Digital Archives”. DIN 31647:2015-05, “Information and Documentation – Preservation of Evidence in Cryptographically Signed Documents”, defines technical and security requirements for the long-term storage of digitally signed documents while preserving the legal force of digital signatures.

In its technical guideline BSI TR-03138, "RESISCAN: Replacement Scanning”, the BSI has compiled the security-relevant technical and organisational measures that must be taken into account for replacement scanning.

In the technical guideline BSI TR-03125, "TR-ESOR: Preservation of Evidence in Cryptographically Signed Documents” (including its annexes), the BSI provides a guideline that describes how electronically signed data and documents can be stored in a trustworthy manner—that is, in the sense of the legally effective preservation of evidential value—over long periods of time until the end of the respective retention periods.

1. Επισκόπηση

Τίτλος Πρότυπο
OPS.1.2.2.A1 Determining Parameters for Electronic Archiving (B)

Before methods and products for electronic archiving are chosen, the technical, legal and organisational influencing factors MUST be determined and documented. The results MUST be incorporated into the archiving concept in question.

OPS.1.2.2.A2 Drawing up an Archiving Concept (B)

The aims to be achieved through archiving MUST be defined. In particular, this MUST take into consideration the rules to be followed, the employees who will be responsible, and the desired scope of functions and services.

The results MUST be documented in an archiving concept. The Top Management MUST be involved in this process. The archiving concept MUST be adapted to the current circumstances at regular intervals.

OPS.1.2.2.A3 Appropriate Installation of Archive Systems and Storage of Archive Media [IT Operation Department] (B)

The IT components of an archive system MUST be installed in secured rooms. It MUST be ensured that only authorised persons may access the rooms. Archive storage media MUST be stored appropriately.

OPS.1.2.2.A4 Consistent Indexing of Data During Archiving [IT Operation Department, User] (B)

All the data, documents, and records stored in an archive MUST be uniquely indexed. To this end, the desired structure and extent of an archive's index information MUST be defined in the design phase.

OPS.1.2.2.A5 Regular Regeneration of Archived Data [IT Operation Department] (B)

The following MUST be ensured over the entire archiving period in question:

  • the data format used can be processed by the applications used
  • the data stored can be read and reproduced in the future in such a way that semantics and significance can be maintained
  • the file system used on the storage medium can be processed by all the components involved
  • the storage media can be read at any time without technical issues
  • the cryptographic methods used for encryption and the preservation of legal relevance by means of digital signatures, seals, time stamps, or technical evidence records correspond to the state of the art
OPS.1.2.2.A6 Protection of the Integrity of the Index Database of Archive Systems [IT Operation Department] (B)

The integrity of index databases MUST be safeguarded and verifiable. In addition, index databases MUST be backed up regularly. It MUST be possible to restore the backups. Medium-sized and large archives SHOULD have redundant index databases.

OPS.1.2.2.A7 Regular Backups of System and Archive Data [IT Operation Department] (B)

All archive data, the related index databases, and the system data MUST be backed up at regular intervals (see CON.3 Backup Concept).

OPS.1.2.2.A8 Logging Archival Access [IT Operation Department] (B)

All attempts to access electronic archives MUST be logged. To this end, dates, times, users, client systems, the actions performed, and any error messages SHOULD be recorded. The archiving concept in question SHOULD specify how long the log data should be retained.

The log data for archive access SHOULD be evaluated regularly. In so doing, the internal specifications of the organisation at hand SHOULD be taken into account.

The specific staff members to whom specific events (e.g. system errors, timeouts, and the copying of records) should be displayed SHOULD also be defined. Critical events SHOULD be evaluated and, if required, escalated immediately once they are detected.

OPS.1.2.2.A9 Selection of Suitable Data Formats for Archiving Documents [IT Operation Department] (B)

A suitable data format MUST be selected for archiving. It MUST ensure that archived data and selected features of the initial document medium can be reproduced in the long term in a format that is true to the original.

It MUST be possible to unambiguously interpret and electronically process the document structure of the selected data format. The syntax and semantics of the data formats used SHOULD be documented and published by a standardisation organisation. A loss-free image compression method SHOULD be used for evidential and audit-compliant archiving.

OPS.1.2.2.A10 Drawing Up a Policy for Using Archive Systems [IT Operation Department] (S)

It SHOULD be ensured that employees use archive systems as prescribed in the applicable archiving concept. To this end, an administration and user policy SHOULD be drawn up. The administration policy SHOULD cover the following items:

  • assignment of responsibility for operation and administration
  • agreements regarding performance parameters during operation (including service level agreements)
  • terms regarding the assignment of site and data access rights
  • terms regarding the assignment of access rights to the services provided by the archive
  • regulations regarding the handling of archived data and archive media
  • monitoring of the archive system and the related environmental conditions
  • rules on backups
  • rules on logging
  • separation of producers and consumers (OAIS model)
OPS.1.2.2.A11 Instruction Regarding the Administration and Operation of the Archive System [IT Operation Department, User] (S)

Users and the responsible employees in the IT Operation Department SHOULD be trained in their areas of responsibility.

The training of IT Operation Department employees SHOULD cover the following subjects:

  • system architecture and security mechanisms of the archive system used and the underlying operating system
  • installation and operation of the archive system and handling of archive media
  • documentation of administrative activities
  • escalation procedures

The user training SHOULD cover the following subjects:

  • handling the archive system
  • operating the archive system
  • legal framework conditions of archiving

The completion of these training courses and the names of those who attend SHOULD be documented.

OPS.1.2.2.A12 Monitoring of Storage Resources for Archive Media [IT Operation Department] (S)

The capacity available in archive media SHOULD be monitored continuously. Once it has fallen below a defined threshold, a responsible employee MUST be alerted automatically. The alert SHOULD be role-based. A sufficient number of empty archive media MUST be available on short notice at any point in time to prevent storage bottlenecks.

OPS.1.2.2.A13 Regular Auditing of Archiving Processes (S)

Whether archiving processes are still working correctly and properly SHOULD be checked regularly. A checklist SHOULD be drawn up for this that includes questions regarding responsibilities, organisational processes, use of archiving, the redundancy of archived data, administration, and technical assessment of the archive system. The audit results SHOULD be documented transparently and compared against the target condition. Deviations SHOULD be investigated.

OPS.1.2.2.A14 Regular Observation of the Market for Archive Systems [IT Operation Department] (S)

The market for archive systems SHOULD be observed regularly and systematically. Among other aspects, the following criteria SHOULD be taken into account:

  • changes in standards
  • instances in which hardware and software manufacturers move to different technologies
  • published security gaps or vulnerabilities
  • cases in which the security of cryptographic algorithms becomes compromised
OPS.1.2.2.A15 Regular Processing of Cryptographically Secured Data During Archiving [IT Operation Department] (S)

Developments in the field of cryptography should be continuously monitored to assess the ongoing reliability and security of a given algorithm (see also OPS.1.2.2.A20 Appropriate Use of Cryptographic Procedures During Archiving).

Archive data that has been secured using cryptographic procedures that will no longer be suitable for securing in the foreseeable future SHOULD be re-secured in good time using suitable procedures.

OPS.1.2.2.A16 Regular Renewal of Technical Archive System Components [IT Operation Department] (S)

Archive systems SHOULD be kept in line with the current state of the art over long periods of time. New hardware and software SHOULD be tested comprehensively before being installed in a running archive system. When commissioning new components or introducing new file formats, a migration concept SHOULD be drawn up. This concept SHOULD describe all changes, tests, and expected test results. Conversion of the individual data sets SHOULD be documented (using a transfer note).

When converting archive data to new formats, it SHOULD be checked whether the data must also be archived in its initial format as a consequence of legal requirements.

OPS.1.2.2.A17 Selecting a Suitable Archiving System [IT Operation Department] (S)

A new archive system SHOULD always be selected on the basis of the specifications mentioned in the archiving concept in question. It SHOULD meet the requirements formulated in this concept.

OPS.1.2.2.A18 Using Appropriate Archive Media [IT Operation Department] (S)

Appropriate media SHOULD be selected and used for archiving. In doing so, the following aspects should be considered:

  • the data volumes to be archived
  • the average access times
  • the average number of simultaneous users accessing the archive system

The archive media SHOULD also meet the requirements of long-term archiving with regard to audit compliance and useful life.

OPS.1.2.2.A19 Regular Function and Recovery Tests for Archiving [IT Operation Department] (S)

Regular function and recovery tests SHOULD be performed for archiving. The readability and integrity of archived storage media SHOULD be checked at least once a year. Appropriate processes SHOULD be defined for troubleshooting.

Furthermore, the hardware components of archive systems SHOULD be checked for sound functionality at regular intervals. Whether all archiving processes work without any errors SHOULD also be checked regularly.

OPS.1.2.2.A20 Appropriate Use of Cryptographic Methods for Archiving [IT Operation Department] (H)

To cover long retention periods, archive data SHOULD only be secured with cryptographic procedures that are based on current standards.

OPS.1.2.2.A21 Transfer of Paper-based Data to Electronic Archives (H)

If documents on paper are digitised and transferred to an electronic archive, it SHOULD be ensured that the digital copy matches the original document in terms of its images and content.

1.1 Παραπομπές

1.2 Εντοπισμένες απαιτήσεις

1.3 Σχετικοί κανονισμοί

2. Εντοπισμένες απαιτήσεις

Απαιτήσεις
Πηγή Απαίτηση

3. Σχετικοί κανονισμοί

Κανονισμοί
Πηγή Κανονισμός

Συνδεδεμένα ζητήματα