Google managed to finish all the upgrades involving security for Android Oreo. This brand new operating system is already on few cell phones, like Pixel and Nexus. It is said that it requires 0.5% of the dynamism of Android gadgets.
Is booting really making my phone vulnerable?
It is a sure thing that Marshmallow and Nougat had done a great job in upgrading security features on telephones. But when it comes to Oreo, we might rethink the whole Verified Boot thing that it’s supposed to stop devices from booting up with modified programming. This feature, Android Verified Boot 2.0 works with Project Treble and together enables security updates to take place, updates consisting in certain arrangements, like footer and rollback insurance, which lets the device boot if it’s minimized enough to reach a seasoned OS variant, which could mean vulnerability.
Is it really safe to have Android Oreo on my phone?
Next to the Verified Boot it comes the new OEM Lock Hardware Abstractions Layer or HAL that allows the producers of the devices to see how it is unlockable, opened or bolted. Also, it has a bolster in the safe equipment and the improvement of the chip that can prevent possible assaults when it comes to Pixel 2 devices. Next on the list is the Control Flow Integration (CFI), which Google has authorized to deny certain changes in order to prevent aggressors to get to you easily. Then, we’re to talk about Android Oreo that does not allow access to direct equipment from the media system. It also has seccomp separating, PAN (Privileged Access Never) copying, KASLR(Kernel Address Space Layout Randomisation). Besides that, Google has limited WebView by enabling a different procedure to prevent outside attacks from happening, by developing it in a disconnected sandbox.
