Symantec Access Management

  • Private Community

  • 1.  Risk Analysis for Jail broken mobile devices

    Broadcom Employee
    Posted Jul 12, 2018 11:18 AM

    There is a requirement from a one of the CA leading customer to Deny all the transactions that are coming from Jail broken mobile devices.

     

    Are we capturing any Mobile Device parameters to determine whether the mobile devices are Jail broken devices or not during Risk Analysis?



  • 2.  Re: Risk Analysis for Jail broken mobile devices

    Posted Jul 12, 2018 12:14 PM

    Yes, we do with the DDNA SDK for iOS and Android devices.

     

    Thanks,

    Lakshmi.



  • 3.  Re: Risk Analysis for Jail broken mobile devices
    Best Answer

    Broadcom Employee
    Posted Jul 13, 2018 01:41 PM

    There is an attribute in DDNA called JAILBROKEN. If this is set to true then risk server will DENY the transaction if the JAILBROKEN custom rule is set to 100

     

    Thanks

    Awijit



  • 4.  Re: Risk Analysis for Jail broken mobile devices

    Broadcom Employee
    Posted Jul 13, 2018 01:46 PM

    Thanks Lakshmi, Awajit!! This helps with DDNA SDK. Is there any parameter available for browser based integration? 



  • 5.  Re: Risk Analysis for Jail broken mobile devices

    Broadcom Employee
    Posted Jul 30, 2018 05:59 PM

    Hi Kiran, in this scenario is the user going to login via mobile phone browser ?

    Is the ask that if the mobile phone browser is used to login then how can risk server verify that device is not rooted ?

     

    Thanks

    Awijit 



  • 6.  Re: Risk Analysis for Jail broken mobile devices

    Broadcom Employee
    Posted Jul 30, 2018 10:56 PM

    Ask is for the applications, accessing from mobile browsers with our standard Javas Script Risk parameter integration.



  • 7.  Re: Risk Analysis for Jail broken mobile devices

    Broadcom Employee
    Posted Jul 31, 2018 10:53 AM

    In the mfp that we collect in browser, I have not seen an attribute that shows whether the device is rooted or not. I think some investigation needs to be done in documentation or code.