Settings' security about ios-fleet-management-sdk HOT 11 CLOSED

I don't think that you should be encouraged to hide the beacons, because based on our field tests, they need to placed exactly where the contextual information is needed.

from ios-fleet-management-sdk.

I think it depend of the usage, for advertising and thing like that, you will shouldn't have to use the immediate proximity I think.

This feature is more useful for payment system for example. And I'm not really sure it's smart to let this kind of device accessible by the user, it's too simple to be stolen and retail company can't easily fix an alarm system on it…

And by the way, it can be placed exactly where your need but inside a decorative paper work or under the table (depending of the table radio wave absorption property).

from ios-fleet-management-sdk.

On Wed, Nov 20, 2013 at 9:17 AM, Yoann Gini [email protected]:

This feature is more useful for payment system for example. And I'm not
really sure it's smart to let this kind of device accessible by the user,
it's too simple to be stolen and retail company can't easily fix an alarm
system on it…

Isn't a beacon just a signal for software to initiate a session and that
session would have security protocols? It's not clear why beacons need
security?

from ios-fleet-management-sdk.

Of course beacon are only for session initiation. And the immediate proximity status is needed to be sure we are looking for the good informations.

Here we are talking about security for settings update (UUID, major and minor number).

from ios-fleet-management-sdk.

In a museum you probably won't be able to hide it anywhere.

from ios-fleet-management-sdk.

Museum is maybe the more easiest deployment to secure. Stick the beacon next to the exposed art piece and let the museum security do they work. They are used to avoid people touching exposed things.

from ios-fleet-management-sdk.

Not every museum wants to avoid user interaction...
I'm working on one that is designed so the visitors can touch everything.

from ios-fleet-management-sdk.

Wow! People allowed to touch art? Really interesting!

To be honest, I've no idea here. Just use the same tool for beacon security than your art security. By the way, how do you avoid degradation in this condition?

But even in this situation, I think a toggle button under the beacon will be more secure in most situation than OTA password protected settings update.

from ios-fleet-management-sdk.

Not every museum contains art :)
It's a natural science museum.

I think a toggle button under the beacon will be more secure in most situation than OTA password

I agree, in most situations. I'm supposing they're trying to find a way that can work on every situation.

from ios-fleet-management-sdk.

Since we may use it for sensible topic like payment or thing like that, what's the best ? Good security on most situations or average security on every situations ?

Experience in security show that OTA and remote access can't really be secured. It's a continus process with password modification, time mitigation, communication encryption, peer authentication and things like that to keep restricted access secure…

from ios-fleet-management-sdk.

This is very wide subject and we are definitely going to introduce some security solutions soon. For now I'm going to close that issue as it is not exactly the SDK issue. If you want to start discussion on that subject feel more then welcome to use our community portal http://community.estimote.com

from ios-fleet-management-sdk.