search

talsec / Free-RASP-ReactNative

React Native plugin for improving app security and threat monitoring on Android and iOS mobile devices.
https://github.com/talsec/Free-RASP-Community
MIT License
84 stars 10 forks source link

Issue on IOS event detection #50

Closed Kiran0791 closed 3 weeks ago

Kiran0791 commented 7 months ago

After the app is installed for the first time the event are triggered. But if the close and restarted the app its not detecting the threat.

Can i get some help on this or is there any config am missing

msikyna commented 7 months ago

Hello @Kiran0791 , could you please explain what exact threat are you referring to? Or is it all threats?

Kind regards, Talsec team

Kiran0791 commented 7 months ago

Hi, Its on all threat looks like. on fresh install i am able to see secureHardwareNotAvailable but if i close the app and open again its not detecting

tompsota commented 7 months ago

Hi @Kiran0791 ,

First, thanks for opening the issue.

Couple of questions, so we can determine where the problem is:

You can also check our implementation in the demo app in example folder.

Kind regards, Tomas

Kiran0791 commented 7 months ago

I have followed the similar implementation as in demo app

tompsota commented 7 months ago

I tested the most recent version of freerasp but can't reproduce the problem. Do you use the useFreeRasp hook?

Kiran0791 commented 7 months ago

Yes useFreeRasp is used. also A common component created and its loaded from App.js

Below is the code file.txt

tompsota commented 7 months ago

Hi, the integration seems fine. I used your component with slight modifications, which you can check here. Then loaded this component in the App.tsx. However I receive the callbacks even after closing and reopening the app.

Are you testing dev or release build? If you are on simulator and use the out-of-the-box simulator without any modifications with dev build, then you will receive just secureHardwareNotAvailable check (some checks are ignored in the dev build by freerasp automatically, see docs here). However this check is later ignored in the code snippet provided. There should be only log visible, but UI won't change. In the production build, however, you should always receive all the callbacks except passcode and deviceID, which are ignored again in the code snippet.

Kiran0791 commented 7 months ago

It happened on release build. Wat is advisable. To show a screen or to crash app when threat is detected. Previously i was crashing the app and once the user relauched the app these events were not getting triggered

tompsota commented 7 months ago

You can read more about threats and recommended actions in our wiki here.

Anyway, the bug you describe is concerning. Can you explain step-by-step how to reproduce the bug?

You can also reach out to us at info@talsec.app if that option suits you better.

github-actions[bot] commented 3 months ago

Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.

github-actions[bot] commented 1 month ago

Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.

github-actions[bot] commented 3 weeks ago

Hello! This issue has been closed. If you believe this issue is still relevant and requires attention, please reopen the issue.