Difference between revisions 657271872 and 657271983 on enwiki

== Introduction ==
What a content management system does, and how it interacts with storage, and how the objective of defining a trusted storage subsystem is related to the concept of a trusted ECM system. In fact, this should be the first thing stated.

a)	ECM control head writes the ESI
b)	At least 2 copies are written directly by the control head, with at least 1 copy written to Trusted WORM as described/defined in this doc.
c)	Policies, and the procedures to ensure complete and accurate ESI capture and retention until policy-defined disposal/destruction point.
d)	Virtualization
e)	Minimum and expansion

Introduction should start with a statement about ECM and trusted systems.  The concept and criteria of a trusted system applies to ECM systems because of their role in managing business records. Then concept of a trusted system covers all aspects of the system and the management practices applied to the system. Storage is one critical area.  This standard will address storage, etc.⏎
⏎
== Scope ==
This International Standard specifies functional and technical requirements associated with storage sub-systems storing/managing organizational records, in a protected/secured fashion, during the lifecycle of the information.   This standard provides sufficient detail enabling organizations, including product suppliers, to identify/specify functionality of all aspects of the information storage environment considered to be non-alterable storage environments (or Trusted WORM), preventing modifica(contracted; show full)

The Trusted Storage standard (ISO 18759) for trusted storage environments addresses both these criteria and will therefore provide guidance to organizations seeking to meet diverse legal requirements and mandates as regards the production and management of their electronic records.