Allow manual exclusion of detected APKs or files in the F-Secure app for Android

Debby
Debby Posts: 46 Contributor
edited September 18 in Feature Requests

Hello,

We would like to submit a feature request for the F-Secure app for Android.

Background
When downloading and installing custom APKs or files, the app currently detects them as harmful and only offers the option to remove them. End users cannot manually add exclusions or allowlist entries. This presents a challenge for advanced users or in specific environments where certain APKs or files are trusted but not officially signed.

Interestingly, we have observed that another mobile security app, F-Secure Mobile Security (with different account permissions), appears to offer more flexibility in this situation. However, the standard consumer apps (SAFE/TOTAL Mobile) do not.

Feature Request

Please consider adding manual exclusion/allowlist functionality for APK files on Android, similar to the exclusion functionality for the desktop app.

If full manual exclusion is not possible for security reasons, perhaps a controlled option (e.g., a confirmation warning + account-level permissions) could be introduced.

Also, could you explain the functional differences between the two mobile apps?

Benefits
This will greatly improve usability for advanced users, testers, and environments that require custom apps, while still providing strong default security for average users.

Thank you for your consideration of this request.

2
Up Down
2 votes

Active · Last Updated

Comments

  • Ukko
    Ukko Posts: 3,955 Superuser

    Hello,

    Sorry for the comment. I am also only an F-Secure user. So, just some thoughts based on that.

    When downloading and installing custom APKs or files, the app currently detects them as harmful and only offers the option to remove them. 

    ….

    Please consider adding manual exclusion/allowlist functionality for APK files on Android, similar to the exclusion functionality for the desktop app.

    I think there are differences here. On desktop - most often - if it is not PUA detection (although I haven't refreshed my knowledge on the current design) - it will be automatically processed. For example, deleted or quarantined or access to it was blocked (if none of previous actions is possible). While on Android it’s just a notification, a warning... maybe only when scanning?

    Or do these applications (APKs) also become unusable?

    And it’s also interesting to know - does this really affect absolutely all installed/downloaded custom APKs? I mean F-Secure detects them only based on 'how they are obtained'?

    I also, however, think that the ability to exclude or "hide" some kind of detection would be appropriate.

    And I think you are now using F-Secure SAS (f-secure.com/sas) to get the detection removed? Or it is all about private custom APKs? So, the local exclusion is the only option..

    Or are they really kind of 'harmful' samples or sort of.

    Also, could you explain the functional differences between the two mobile apps?

    Current F-Secure Mobile Security is ex Lookout Life application.

    Normal F-Secure SAFE/TOTAL app is their part of F-Secure TOTAL package.

    So, different subscriptions. Different features (as for now).

    I think that at some point there will be unification in favor of some of them and there will be a single set of features. But, as I think some things are already available in F-Secure Total from the F-Secure Mobile Security 'portfolio'.

    Basically, there is current 'promo' webpage: https://www.f-secure.com/us-en/life-by-f-secure

    And there is story: https://www.f-secure.com/us-en/articles/lookout-s-consumer-business-is-now-lookout-life-by-f-secure

    Thanks!

    Like Awesome

Categories