• haneul 13 hours ago

    Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.

    If anyone is more familiar with Temporal, is there a way clients could have had internal defense in depth that guards against tenant leakage at the provider (Temporal) level?

    • jiggunjer 9 hours ago

      Don't use namespaces. Wire up multi-tenant at the RBAC level. Need stronger isolation? Run another cluster.

      • bdj108 12 hours ago

        Things like this are inevitable, especially these days.

        • UltraSane 8 hours ago

          Encrypting tenant data with per tenant keys is a good defense against this kind of thing.