Security/Privacy – new category

[JJ-Foust]

A written description must be included on your Team’s DevPost, on how the app/application/solution should be secured. Be specific to your application’s security needs – describe how the different parts/functions of the solution should be secured for both data security and privacy. Do not provide generic security guidance. Limit the solution security plan to 300 words. (Failure to post a description will result in a 0 score for this category!)

[ZhienWang]

Note: this is for Production implementation. So we can describe a lot of things we don't really need to implement as of now.

Here are some standard security implementations we can have.

1. 2 factor authentication on Sign up and logins
2. In case of lost passwords, verify with Email address and OAuth with Google/Facebook.
3. For back-end, we would have admin accounts only accessible by Dept of Agriculture. This is a web page integrated into their existing web portal and should be IP-bound.
4. All database entries should be tracked by the person's username and date of entry. A backup of the table transaction entries should be stored in a separate table for future verifications and audit.

[JJ-Foust]

Do we even need to have logins for pet owners?

Would it be simpler just to have them input data with out a login?

Unless you can think of a reason we need to create a login?

[JJ-Foust]

Entry tracking. Also not sure we need this feature since everything is tracked by hard copy signatures.