16.7.12. There are several known vulnerabilities in SMS which may make it unsuitable and unsafe for authentication purposes. Vulnerabilities include:
Hackers have been able to mislead and persuade carriers and service providers into porting a phone number to a new device through a SIM
swap. This can often be achieved with minimal personal information such as your phone number, date of birth, full name, the last four digits of
your bank card access number, bank account number, mobile device number, Social Security number or similar information. Users often store
bank cards with their mobile device so if the device is stolen or simply accessed temporarily, this data can also be accessed. Once the phone
number has been redirected, physical access to your device is no longer required. Any SMS codes are then subject to compromise.
If text messages are synched with or duplicated on a laptop, tablet or other personal device, then SMS are vulnerable if the device used by
another person or if the device is stolen.
There are vulnerabilities in mobile telecommunication infrastructure in what's described as a SS7 (Signalling System 7) attack. An SS7 attack is
an exploit that takes advantage of a weakness in the design of SS7 which can enable data theft, eavesdropping, text interception and location
tracking. SS7 is a protocol dating from the mid-1970’s and almost all telecommunication service providers have now implemented security
measures to counter SS7 exploits. Social engineering remains a risk.
Key Benefits
16.7.13. The principal benefits of MFA include:
Strengthened security and credential protection;
Streamlined user access;
Reduced administrative overhead;
Increased security visibility; and
Improved compliance.
Adaptive Authentication
16.7.14. Adaptive Authentication varies the level or degree of authentication required where an unusual authentication request occurs. For example, out of
normal hours, from an unusual geolocation, from an unrecognised device, from an unrecognised IP address and so on. When an unusual authentication
request is received, Adaptive Authentication may request additional credentials such as a one-time code provided to a known mobile phone number.
Some risk factors that may trigger Adaptive Authentication include:
The location of the access request such as such as a café, airport or home;
The time of the access request such as like late at night, over weekends or during normal working hours;
The type of device, such as a smartphone, tablet, laptop or unrecognised device;
The type of connection, for example, a public network such as the internet, or a VPN or some other private network; and
A request for access to privileged accounts.
16.7.15. Adaptive authentication includes what is sometimes described as transaction identification where known characteristics are compared to the
transaction or access request. For example a known location or common access request. If known characteristics do not match then additional
authentication steps may be indicated or required.
Client-Side Authentication
16.7.16. Client-side authentication originates from the user’s device such as laptop, mobile phone, tablet or home computer. These devices may provide a
variety of authentication methods including:
Inherence factor/Biometric:
Fingerprint scans;
Facial recognition;
Voice command/recognition;
Iris scans;
Keystroke dynamics;
Knowledge factor:
PIN codes;
Pattern codes;
Possession factor:
Geofencing;
Bluetooth device proximity/Near field communication (NFC).
16.7.17. It is important to note that some biometric and other measures, for example fingerprints, are susceptible to attacks such as spoofing. To combat these
biometric attacks secondary measures are also required, for example pulse-sensing in addition to fingerprint detection in order to ensure the fingerprint
presentation is a live person. Clearly not all secondary measures are fully effective in themselves and multiple secondary measures may be required
for high risk/high value authorisation requests.
Single-User and Multi-User Authorisation
16.7.18. Single-User authorisationinvolves prompting the account holder to authorise an action being taken on his behalf. For example, single-user
authorisation can even prevent fraud as it occurs in a user-friendly manner. Instead of calling the customer to verify the legitimacy of a purchase,
credit card companies could request customer authentication for an on-line purchase by sending an authorisation request to the customer through an
alternate channel such as a mobile phone.
16.7.19. Multi-User authorisation usually requires multiple and separate authentications (usually people) in order to authorise a transaction or event, such as
establishing an account. This system supports the “separation of duties” concept common in accounting transactions or other high risk activities.
Another example is a password change for a privileged account. Multiuser authorisation may also assess risk indicators and context (e.g. time,
location) to select the authentication components and requirements.
227
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents