-
Type:
Task
-
Resolution: Unresolved
-
Priority:
High
-
Affects Version/s: None
-
FLW Mobile App
-
All
What this is
Handle a lost or stolen FLW phone so that its data cannot be misused and uploads from it are stopped.
Steps
- An admin can revoke the device's key for the FLW app.
- After revocation, uploads from that device are rejected by the central server (AMM-2533).
- The breach process starts when a device is reported lost or stolen.
- [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]
- Where does the admin revoke a key (Admin-UI or another place)? There is no Admin-UI screen for this in 3.14.
- Who owns the breach process and what is the steps list?
- 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).