Data Tagging: If you don’t tag it how will you know when to delete it, archive it, or secure it?

Migration of unstructured and semi-structured content also involves records and security. Records that should have been declared, archived, or deleted. The same can be applied to potential security exposures. Confidential or data privacy information may have never been removed from unauthorized access nor secured to prevent portability. It is not just simply moving ‘documents’ and ‘spreadsheets’.

Even if retention policies exist, monitoring and enforcement is often haphazard, when considering the amount of content that is spread across diverse repositories and other enterprise systems. The use of auto-classification of content against a taxonomy that is defined to address records and security assists in cleaning up the content, improves compliance, and can protect the organization from security exposures, or worse, a data breach.

Have you used tools that will address this in migration?