Android 10 and Apple iOS 14 devices use randomized MAC addresses when connecting to wireless networks to provide privacy for users.
Within most vendors NAC (Network Access Control) products and many network components, the MAC address is considered to be the unique identifier for a given endpoint.
Due to the MAC address randomization, this one-to-one mapping is no longer true and a single endpoint could end up generating multiple endpoint entries within the mentioned NAC solutions.

The next sections show how MAC address randomization is implemented on mobile endpoints:
Google Android 10
* Randomization is enabled by default.
* When a user upgrades from a previous version of Android to Android 10, the saved Service Set Identifiers (SSIDs) will stay configured without randomization.
* Randomization can be set up per network profile (SSID).
* Once a random MAC address is used for a given network profile, the mobile device will continue to use the same random MAC address even after the user deletes the network profile and recreates the SSID/network profile.
* For more information on Android MAC randomization, see Privacy: MAC Randomization.

Apple iOS 14, iPad OS 14, watchOS 7
* Randomization is enabled by default.
* When a user upgrades from a previous version of iOS to iOS 14, the randomization will be enabled for all of the existing SSIDs.
* Randomization can be set up per network profile (SSID).
* Once a random MAC address is used for a given network profile, the mobile device will continue to use the same random MAC address even after the user deletes the network profile and recreates the SSID/network profile.
* For more information on iOS MAC randomization, see Use private Wi-Fi addresses in iOS 14, iPadOS 14, and watchOS 7.

Please make the WIFI MAC randomization feature configurable for each network profile (SSID).

The policy for email signatures is very static. Wildcards are not possible. % USERNAME% works, but looks bad.
Result:
"Best regards
Firstname.Lastname"

Desired is:
"Best regards
Firstname Lastname"

One policy would have to be created for each user. Has been confirmed by Sophos support. There is no possibility to use placeholders. e.g. Firstname Lastname from the user directory. This is imperative. On the other hand, the operation of the self service portal is very complex and there is a policy jungle.

Die Policy für Email Signaturen ist sehr statisch. Platzhalter sind nicht möglich. %USERNAME% würde gehen, sieht aber schlecht aus.
Resultat:
"Freundliche Grüsse
vorname.nachname"

Gewünscht ist
"Freundliche Grüsse
Vorname Nachname"

Es müsste pro User eine Richtlinie erstellt werden. Wurde vom Sophos Support bestätigt. Es fehlt die Möglichkeit Placeholders zu nutzen. zB. Vorname Nachname aus dem Benutzerverzeichnis. Dies ist zwingend notwendig. andererseits ist der Betrieb vom Self Service Portal sehr aufwändig und es gibt einen policie jungle.

I'm using Google Authenticator separately for some of my online accounts which Intercept X's authenticator component does not seem to work. Initially, that app did not have a backup/restore function (which would be a pain to end-users when changing to a new phone if they rely on Google Authenticator).

However, I just noticed after a recent update that Google decided to add that missing part, and they made it more convenient than what Intercept X has to offer: hit Transfer account and an option for QR code pops up. So all you need to do is scan it on the device where you want to migrate the tokens and it's done.

I think having this on Intercept X could improve user experience. Currently, you export your configuration to a file, transfer it to the destination by some medium (email, MMC, etc.) then import the file to restore the configuration. It's actually okay, but if there's a better way of doing it, then why not?

I hope Intercept X gets a QR code configuration transfer option in the future. Just the authenticator configuration transfer will actually do, but it would be way better if it's that plus the entire app's settings.

Apparently, the signature settings in the email secure app have been changed since the new update. Android users cannot store their own signature. This must be configured by the administrator and then applies equally to all Android users.

iOS users can store their own email signature in the Sophos Email Secure app!

According to Sophos Support, this is what is wanted and to change it again, we should suggest it as an idea.

It would make a lot of sense that every Android email secure app user can store their own email signature.
(As it was before)

Scheinbar wurde seit dem neuen Update die Signatur Einstellungen in der E-Mail Secure App geändert. Android Nutzer können keine eigene Signatur für sich hinterlegen. Dies muss vom Administrator konfiguriert werden und gilt dann für alle Android Nutzer gleich.

iOS Nutzer können eine eigene E-Mail Signatur in der Sophos E-Mail Secure App hinterlegen!

Laut dem Sophos Support ist dies so gewollt und um es wieder zu ändern, soll wir es als Idee vorschlagen.

Es würde sehr sinnvoll sein, dass jeder Android E-Mail Secure App Nutzer seine eigene E-Mail Signatur hinterlegen kann. (So wie es vorher auch war)