FLW app: lost or stolen device handling (key revoke and rejected uploads)

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: High
    • 3.0
    • Affects Version/s: None

      What this is
      Handle a lost or stolen FLW phone so that its data cannot be misused and uploads from it are stopped.

      Steps

      1. An admin can revoke the device's key for the FLW app.
      2. After revocation, uploads from that device are rejected by the central server (AMM-2533).
      3. The breach process starts when a device is reported lost or stolen.
      4. [TBD/CLARIFICATION REQUIRED] Whether the FLW app should also be able to wipe or lock local data on the next login after revocation.

      Done when

      • An admin can revoke a device key.
      • Uploads from a revoked device are rejected.
      • The FLW user sees a clear message when their device has been revoked.

      Dependencies: FLW-1273 (device encryption), AMM-2533, AMM-2536. Mirrors the lost-laptop rule in AMM-2536.

      Open questions: [TBD/CLARIFICATION REQUIRED]

      1. Where does the admin revoke a key (Admin-UI or another place)? There is no Admin-UI screen for this in 3.14.
      2. Who owns the breach process and what is the steps list?
      3. How does a replacement phone get a new key and its unsynced data (if any)?

      Source: DPDPA Compliance Proposal v14, sections 5 (Rules), 8 (M12).

              Assignee:
              Saurav Mishra
              Reporter:
              Shivani Garg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: