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

Threat detection order #78

Closed
reyesmfabian opened this issue Jul 3, 2023 · 1 comment
Closed

Threat detection order #78

reyesmfabian opened this issue Jul 3, 2023 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request FAQ Useful information for the community

Comments

@reyesmfabian
Copy link

Hi,

Is there a way to set the order of threat detection?

We will set certain unique actions for each type of threat according to its severity. For example for "emulators" we will show a warning message, for others like "hooks" we will close the app.

We would like to know if there is a possibility to tell the SDK which threats to analyze first to avoid possible problems in UX, for example that the SDK detects the emulator and tries to show the message and then closes abruptly when it finds the hook.

@reyesmfabian reyesmfabian added the enhancement New feature or request label Jul 3, 2023
@msikyna
Copy link
Member

msikyna commented Jul 4, 2023

Hello @reyesmfabian,

currently, there is no way of setting the order of threat detection for freeRASP. The checks are performed asynchronously on Android, synchronously for iOS. If a check fails, the corresponding callback is executed.

However, in the BusinessRASP+, there is a way how to accomplish this. To see other differences between the freeRASP and businessRASP: https://github.com/orgs/talsec/discussions/5.

If you would like to follow up on the topic, just pick a time slot in Calendly.

Kind regards,
Talsec team

NB: If you are killing an application based on callbacks, make sure that it is done appropriately (e.g. see the https://stackoverflow.com/questions/45109557/flutter-how-to-programmatically-exit-the-app)

@msikyna msikyna added the documentation Improvements or additions to documentation label Jul 19, 2023
@msikyna msikyna closed this as completed Sep 27, 2023
@tompsota tompsota added the FAQ Useful information for the community label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request FAQ Useful information for the community
Projects
None yet
Development

No branches or pull requests

4 participants