Looking for best practice/used cases for NEO4j to store Facial or similar bio-metrics

[plee]

Hello all! I hope you guys are doing well and staying safe.

I have a quick question regarding storing biometrics in NEO4j. I did research and have not found detailed approach or documents yet.

If you guys could share any knowledge, link, used cases or documents regarding storing biometrics in NEO4j would be greatly appreciated.

1. What is the best practice for storing facial or biometrics into neo4j?
2. Any suggestions or steps needs to be reviewed before the process?
3. What are some limitations I should be aware of? or recommend other tool/db for this case?

Respectfully,

Petra Lee

[dominicvivek06 · Accepted solution]

Hi @plee, I would consider the biometric data as a randomized alphanumeric characters. It depends upon the SDK you are using for example to scan fingers or facial.
in both cases, you can store these information as a file, and call using file handlers (example - AWS S3).
Since you are dealing with sensitive data, I would recommend using methods like Tokenization and encryption.

Link from Mcafee

mcafee.com

What is Tokenization vs Encryption - Benefits Uses Cases Explained | McAfee

en.wikipedia.org

Tokenization (data security)

Tokenization, when applied to data security, is the process of substituting a sensitive data element with a non-sensitive equivalent, referred to as a token, that has no extrinsic or exploitable meaning or value. The token is a reference (i.e. identifier) that maps back to the sensitive data through a tokenization system. The mapping from original data to a token uses methods which render tokens infeasible to reverse in the absence of the tokenization system, for example using tokens created from...