• A Peek Behind How BlackBerry Secures Android


    It's a pretty difficult concept to think about. How do you take an insecure operating system and make it secure using enterprise software?

    It's something that gets done everyday by BlackBerry. We know about AtHoc and BES12 and the eventual Good acquisition but how did they do it for Android?

    The BlackBerry Blog let us in on the secret and the truth? Well, it's no secret. BlackBerry is really, really good at security.

    BlackBerry’s Hardware Root of Trust, a unique manufacturing process that injects cryptographic keys into the device hardware, providing a secure foundation for the entire platform.
    Verified Boot and Secure Bootchain, which uses the embedded keys to verify every layer of the device from hardware to OS to applications in order to make sure they haven’t been tampered with.
    A hardened Linux kernel with numerous patches and configuration changes to improve security.
    FIPS 140-2 compliant full disk encryption on by default to protect your privacy.
    The BlackBerry Infrastructure, a secure distributed global network that transmits petabytes of encrypted data to and from the world’s most powerful leaders and professionals.
    BES12, the leading Enterprise Mobility Management platform used by the world’s most powerful governments and corporations.
    And as we learned from the recent webinar, Android for Work is there to separate play and work on the same device.

    BlackBerry's own DTEK software monitors device security as well.




    PRIV comes pre-loaded with the brand new BlackBerry DTEK application, designed to help you manage and protect your privacy. DTEK tells you which apps access your personal data and shows the overall security of your device based on factors such as the strength of your password, your encryption settings and the apps you have installed. DTEK even makes recommendations on how you can improve your overall security rating.
    Read the entire explanation of what BlackBerry offer Android for security at the BlackBerry Blog.


    comments powered by Disqus