Security Behaviour Database
All Behaviours > SB175 Does not log in from a rooted mobile device

SB175 Does not log in from a rooted mobile device

Gaining root access ('rooting', also known as 'jailbreaking') on a mobile device is akin to running Windows as an administrator. You have full access to the system directory and can make changes to the way the OS operates. Rooting disables some of the built-in security features of the operating system, and those security features are part of what keeps the operating system safe and your data secure from exposure or corruption. Some malware specifically looks for root access, which allows it to really run amok.

Why is it important?

Using a rooted (or jailbroken) mobile device introduces unnecessary risk. If a device has been rooted, some of the built-in security features have been disabled. These security features are essential to keep data secure from theft or corruption. A rooted device may be running unauthorised (potentially dangerous) apps from outside of the official app stores. If a third-party application was used to root the device, it may have introduced malware while doing so. Rooting a mobile device may void its warranty, leading to financial loss if the device is lost or comes to physical harm.

Priority Tier

Behaviours in SebDB are ranked by their impact on risk. Tier 1 behaviours have the biggest impact, Tier 4 behaviours the least.

Tier 1

Risk Mitigated

Malware Infection

Malware Infection

Malware infections occur when malicious software makes its way on to a device or network.

Account Compromise

Account Compromise

Account compromise happens when unauthorised people access them.

Further reading

SebDB is brought to you byCybSafe| © 2023 CybSafe Ltd