Security is completely up to you.
iBeacons are safe in the sense that they are very simple devices that do nothing but transmit a three-part identifier (and measure transmitter power). They always advertise unless you go out of their way to stop them.
Anyone can see this identifier, so you better not expect it to be secret! Last week, for example, I went to the Apple store in Washington, DC and used the iBeacon Locate Android app to find out the identifier of the three parts of the iBeacon near the entrance to the Apple store.
With this information, I then set up my own iBeacon to transmit the same part of the tree identifier, theoretically allowing me to push offers to applications configured to respond to the Apple iBeacon.
Is this a security issue? Only if you create a system that incorrectly assumes that the iBeacon identifier is secret.
Interestingly, the Apple iOS APIs prohibit scanning of completely unknown iBeacon identifiers (you should at least know the first of the three part identifiers), offering them to keep this secret. Given that Android and OSX do not offer such a ban, it is best not to expect your iBeacon identifier to remain secret.
source share