The browser informs on itself in the GET message, and it does indeed identify itself as (at least) chrome-based, and goes on to provide the version which does correspond to the version displayed in the SafeZone Browser "About" information 17.0.963.81 (Developer Build 127271 Windows)
GET /webhp?sourceid=chrome-instant&ix=seb&ie=UTF-8&ion=1 HTTP/1.1
Host:
www.google.comConnection: keep-alive
X-Purpose: instant
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.81 Safari/535.11
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: PREF=ID=70e9666e6d444a4f:U=1d19aefb35cc2790:FF=0:LD=en:TM=1346892717:LM=1368819930:S=r-h5v7eDsunauFgf; NID=67=Ihm6W-sI-5LAkE0YhmrX21u31vSg3QaPzEeaVPQp0BO_hiy_KKM6IZy23S5VRWM-4ZUU3VXGdXgGheLvBYyqfBOmUwXleEf1W55NV8itDKo6gsqJrGoAzzAhmQn6EIOJTufhKdS505oh19SDgT8
In addition to the quoted security bulletin, I would add that the point of a SafeZone Browser for sensitive transactions will be of limited functionality when the browser is unsupported.
In my case it is QuickBooks Online.
They support two major versions back, only. Anything older and they throw an error telling you to upgrade. This is to alleviate support calls they cannot control.
So beyond security, I would submit that there is also a use/business case for updating the browser more aggressively.
Thanks