Building and Maintaining a Data Inventory

ISACA CDPSE · Data Lifecycle Governance · Bởi Super Admin

A complete and current data inventory of structured and unstructured personal information, maintained through change management, documentation, and periodic review, is essential to identifying and protecting sensitive data.

A well-worn but still relevant principle in data security holds that you cannot protect what you don't know you have. This underscores the need for effective asset management at all levels, since only specifically identified data can be managed and protected. For a privacy program to be effective, organizations must have a complete and accurate inventory of all personal information. While an inventory of structured information residing in application database management systems tends to remain fairly static, the transient nature of unstructured data creates additional challenges. Organizations must find ways to identify all structured and unstructured data, particularly when it contains personal information within the scope of relevant privacy laws, and proactive data discovery can be implemented to provide visibility into the existence, creation, and use of unstructured data. In practice, few IT departments track their data until regulation forces them to, after which they employ data discovery tools to identify datasets they should have been tracking all along.

Keeping the Inventory Current

For an organization's data inventory to remain current, three activities need to become part of business-as-usual processes. First, change management processes must call out an update to the data inventory whenever an addition or change to an information system affects it. Second, business processes that interact with personal information must be documented. Third, periodic reviews of the data inventory should be performed to confirm its accuracy.

The Inventory as a Gap Analysis

Periodic data inventory reviews should not only catalog existing instances of sensitive and personal information but also determine, for each instance, whether the data should exist where it is found. By understanding the business processes that handle personal information, organizations can better identify where it is collected, processed, and stored. A data inventory should therefore be thought of less as a census and more as a gap analysis: every instance of sensitive information should be examined through the lens of the business processes and data management policy to determine whether it should exist and whether current protective controls are adequate. Organizations with lower process maturity are more likely to use unstructured methods to perform procedures and complete tasks, often resulting in greater use of email for process workflows and unstructured data stores for data storage. Email, file servers, and cloud storage services represent the majority of unstructured data in many organizations.

Elements of a Catalog Entry

When inventorying data, each catalog entry should include a unique identifier; the name of the file(s) or directory/directories; the physical location, which is critical for identifying data sovereignty issues; a description of the contents, including personally identifiable information (PII) data fields; provenance; purpose; date of last update, which aids in the removal of old data; access permissions; the data owner/custodian; and the retention period. This information is useful for developing data flow diagrams. Automation in larger organizations will ease the burden of manual, time-consuming processes for identifying datasets and keeping data inventories up to date.

Key takeaways

  • Organizations cannot protect personal information they have not identified, making a complete data inventory foundational to privacy programs.
  • Unstructured data is more challenging to track than structured data, requiring proactive data discovery tools.
  • A current inventory depends on change management triggers, documentation of business processes, and periodic accuracy reviews.
  • Inventory reviews function as a gap analysis, evaluating whether each data instance should exist and whether controls are adequate, and each catalog entry should capture identifiers, location, contents, provenance, purpose, update date, access permissions, owner, and retention period.
0.0 (0 đánh giá)

Thảo luận / Bình luận (0)

Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!

Vui lòng Đăng nhập để tham gia thảo luận.