Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Move contact number into a new database table #593

Open
prestonlimlianjie opened this issue Dec 20, 2022 · 0 comments
Open

[Feature] Move contact number into a new database table #593

prestonlimlianjie opened this issue Dec 20, 2022 · 0 comments

Comments

@prestonlimlianjie
Copy link
Contributor

Challenge

Contact numbers of our CMS users are deemed as sensitive personal identifiable information (PII). At present, the contact number of each user is stored in the Users table. This means that Isomer engineers could easily accidentally retrieve the contact number data and use it in places where it is unnecessary.

Suggested solution

As suggested by @dcshzj here, we could put all PII into a new database table such that Isomer engineers need to explicitly attempt to retrieve the PII; this reduces the risk of accidentally retrieving PII data where unnecessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant