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

Store data safely #6

Open
TeamSahamati opened this issue Jan 4, 2022 · 0 comments
Open

Store data safely #6

TeamSahamati opened this issue Jan 4, 2022 · 0 comments

Comments

@TeamSahamati
Copy link

Input from Christian Damour, security expert, FIME

I would recommend using whitebox cryptography and a unique storage key per device.

Potential security mechanisms to implement include:
• Anti-Tampering
• Anti-Rooting
• Anti-Instrumentation
• Anti-Emulation
• Anti-Debugging
• Device-Binding
• Obfuscation
• White-box Cryptography
Many of these are available from specialist software technology providers. They allow
developers to adopt solutions which have already passed the complex security evaluation.
For instance for obfuscation, Proguard (freeware) is not sufficient and Dexguard offers appropriate level security (commercial solution).

"For obfuscating any string resources or an asset file, use a library like StringCare."
I have never heard about StringCare in the context of payment. I think it is Open Source and provides weak obfuscation feature.

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