Have Smartlinks resolved where Data Residency is pinned

XMLWordPrintable

    • 1

      Problem

      The current implementation of Forge Smart Links and the Rovo Smart Link connector presents challenges for organizations with strict data residency requirements, specifically those mandating that all data, including transient processing and caching, remain within a single geographic region. While persistent copies of data are stored in compliance with data residency settings (e.g., US-pinned storage), transient data processing can occur in multiple regions, including the EU. This cross-region data handling can pose potential compliance risks and conflicts with organizational policies that require data to remain within a specified region. The lack of a mechanism to restrict all aspects of data processing to a single location undermines the ability of organizations to fully control their data's geographic footprint, thereby complicating compliance with internal and external regulations.

       

      Suggestion

      Implement region-aware processing for Smart Link and Rovo connectors that respects data residency settings for both persistent storage AND transient processing/caching operations. Specifically: 1. All processing operations (including temporary caching and data in transit) should be confined to the same region where the customer's data is pinned. 2. Create a configuration option that ensures the entire data lifecycle - from initial processing through temporary caching to permanent storage - remains within the designated region. 3. Maintain the existing encryption and TTL-based deletion practices, but execute them within the pinned region only.

              Assignee:
              Unassigned
              Reporter:
              Kenneth De Coster (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: