Originating Author: David Floyer
Storage executives have traditionally been responsible for data classification implementations. Data classification is a fundamental building block for effective ILM and archiving initiatives and the potential benefits to the organization go far beyond storage optimization. However out-of-scope organizational requirements can disrupt the initial objectives of data classification projects and managers must be extra careful of scope creep.
In order for IT to implement a full data classification architecture, detailed assessments will be needed with legal, audit, risk management, business lines, architects regarding metadata architecture, application developers and owners to determine metadata automation requirements and operations professionals. In the meantime, storage executives need to limit the scope of any data classification project to what can be achieved in the immediate term.
Action Item: Executives responsible for storage must keep data classification schema simple and limited to data that is system generated (e.g. date of creation and last use). While necessary, expanding the scope of classification efforts should not proceed until data classification schema are defined and automated methods of generation are in place. Relying on any manual entry of classification information will doom data classification projects to failure.