4,689
edits
Changes
mLine 1:
Line 1: + + + + + + + Line 91:
Line 98: − + Line 114:
Line 121: − − ==Disclaimer== − − If you are not using Bluetooth, please consider turning it off or change Bluetooth PIN to remove potential risks. − − If you are using Bluetooth we strongly recommend using AES encryption for enhanced security. − − Example for formatting: − − [[File:IMAGE DISCLAIMER.png]]
Text replacement - "Bluetooth(?!®)" to "Bluetooth®"
==Disclaimer==
[[File:Alert.png|left|link=]] <br> If you are not using Bluetooth®, '''please consider turning it off''' or '''change Bluetooth® PIN''' to remove potential risks.
If you are using Bluetooth® we strongly recommend '''using AES encryption''' for enhanced security.
==Solution description==
==Solution description==
GPS trackers provide valuable data for business efficiency and secure vehicles against thefts. At the same time, the tracking devices can be stolen with a purpose to sell them, sabotaged by reconfiguring with fault parameters, or hacked to steal sensitive data. To prevent unauthorized access to the trackers, it is necessary to have additional security measures for logging in through all possible devices. When a login fails, the user is denied access and trackers remain safe.
GPS trackers provide valuable data for business efficiency and secure vehicles against thefts. At the same time, the tracking devices can be stolen with a purpose to sell them, sabotaged by reconfiguring with fault parameters, or hacked to steal sensitive data. To prevent unauthorized access to the trackers, it is necessary to have additional security measures for logging in through all possible devices. When a login fails, the user is denied access and trackers remain safe.
====2.5 BLE STANDARD AES-128====
====2.5 BLE STANDARD AES-128====
[[File:BLE Standart AES-128.gif|alt=|thumb|365x365px|BLE standart AES-128]]
[[File:BLE Standart AES-128.gif|alt=|thumb|365x365px|BLE standart AES-128]]
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded. AES128 key field settings showed below.
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth® 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded. AES128 key field settings showed below.
If a key is present the outgoing data will be ciphered by the configured key and incoming data will be deciphered. The '''AES128 key''' must be in '''HEX format with a length of 16 bytes'''. As an example 11223344556677889900AABBCCDDEEFF is used.
If a key is present the outgoing data will be ciphered by the configured key and incoming data will be deciphered. The '''AES128 key''' must be in '''HEX format with a length of 16 bytes'''. As an example 11223344556677889900AABBCCDDEEFF is used.
All preparation describe in the [https://wiki.teltonika-gps.com/wikibase/images/4/4e/FMBXX_TLSDTLS_encryption_configuration_v0.3.pdf TLS/DTLS prepare guide] in the device you need activate this
All preparation describe in the [https://wiki.teltonika-gps.com/wikibase/images/4/4e/FMBXX_TLSDTLS_encryption_configuration_v0.3.pdf TLS/DTLS prepare guide] in the device you need activate this
[[Category: Usage scenarios]]
[[Category: Usage scenarios]]
[[Category: Use cases]]
[[Category: Use cases]]
