TRACKER’S SECURITY - Revision history

Arijus.C at 08:00, 19 February 2026

2026-02-19T08:00:48Z

← Older revision		Revision as of 11:00, 19 February 2026
Line 120:		Line 120:
	Supported versions: 1.1/1.2		Supported versions: 1.1/1.2

	~~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		The preparation is described in the [[Media:FMBXX TLSDTLS encryption configuration v0.3.pdf\|FMBXX TLSDTLS encryption configuration]] for the device you need to activate this.


	[[Category: Usage scenarios]]		[[Category: Usage scenarios]]
	[[Category: Use cases]]		[[Category: Use cases]]

Arnas.Zeb: Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

2023-12-28T13:27:59Z

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

← Older revision		Revision as of 16:27, 28 December 2023
Line 1:		Line 1:
	==Disclaimer==		==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.		[[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.		If you are using Bluetooth® we strongly recommend '''using AES encryption''' for enhanced security.


Line 98:		Line 98:
	====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.

Justinas.strelciunas at 05:27, 14 November 2023

2023-11-14T05:27:37Z

← Older revision		Revision as of 08:27, 14 November 2023
Line 1:		Line 1:
			==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.
Line 114:		Line 121:

	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

	~~==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.~~


	[[Category: Usage scenarios]]		[[Category: Usage scenarios]]
	[[Category: Use cases]]		[[Category: Use cases]]

Justinas.strelciunas: /* Disclaimer */

2023-11-10T07:27:46Z

Disclaimer

← Older revision		Revision as of 10:27, 10 November 2023
Line 117:		Line 117:
	==Disclaimer==		==Disclaimer==

	If you are not using Bluetooth, please consider turning it off or change Bluetooth PIN to remove potential risks.		[[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.		If you are using Bluetooth we strongly recommend '''using AES encryption''' for enhanced security.

	~~Example for formatting:~~

	~~[[File:IMAGE DISCLAIMER.png]]~~


	[[Category: Usage scenarios]]		[[Category: Usage scenarios]]
	[[Category: Use cases]]		[[Category: Use cases]]

Justinas.strelciunas at 13:46, 9 November 2023

2023-11-09T13:46:43Z

← Older revision		Revision as of 16:46, 9 November 2023
Line 114:		Line 114:

	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

			==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]]


	[[Category: Usage scenarios]]		[[Category: Usage scenarios]]
	[[Category: Use cases]]		[[Category: Use cases]]

PavelSafonov at 08:37, 18 February 2022

2022-02-18T08:37:04Z

← Older revision		Revision as of 11:37, 18 February 2022
Line 13:		Line 13:
	[[File:Example Inst.jpg\|thumb\|Instalation\|alt=\|260x260px]]		[[File:Example Inst.jpg\|thumb\|Instalation\|alt=\|260x260px]]
	For gain access to ability change default security state (for device from the factory) you need power up device (10-30V) and connect via USB to the PC. After device will be powered and LED indicators start work you can access to settings.		For gain access to ability change default security state (for device from the factory) you need power up device (10-30V) and connect via USB to the PC. After device will be powered and LED indicators start work you can access to settings.










Line 61:		Line 53:

	This command will emove existing keyword. If device is locked, keyword cannot be changed.		This command will emove existing keyword. If device is locked, keyword cannot be changed.




Line 72:		Line 62:

	Phone numbers have to be written in international standard, using "+" is optional but not necessary (in both cases number will be recognized, but when number is without "+" symbol, IDD Prefix will not be generated, which depends on location of the phone). If no numbers are entered, configuration and sending commands over SMS are allowed from all GSM numbers.		Phone numbers have to be written in international standard, using "+" is optional but not necessary (in both cases number will be recognized, but when number is without "+" symbol, IDD Prefix will not be generated, which depends on location of the phone). If no numbers are entered, configuration and sending commands over SMS are allowed from all GSM numbers.








Line 106:		Line 90:
	* at least 8 characters		* at least 8 characters
	====2.5 BLE STANDARD AES-128====		====2.5 BLE STANDARD AES-128====
	[[File:~~BLE_STANDARD_AES~~-128.gif\|alt=\|thumb\|365x365px]]		[[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.








Line 125:		Line 103:

	==SECURE CONNECTION TO SERVER (TLS)==		==SECURE CONNECTION TO SERVER (TLS)==
	[[File:~~TLS~~.gif\|alt=\|thumb\|365x365px]]		[[File:Tls option.gif\|alt=\|thumb\|365x365px\|TLS]]
	In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.		In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.
	TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.		TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.

PavelSafonov at 08:35, 18 February 2022

2022-02-18T08:35:46Z

← Older revision		Revision as of 11:35, 18 February 2022
Line 66:		Line 66:

	====2.2. SMS security:====		====2.2. SMS security:====
	[[File:~~SMS_Security~~.gif\|alt=\|Set up sms secutiry~~\|thumb\|365x365px~~]]		[[File:Set up SMS security.gif\|alt=\|thumb\|365x365px\|Set up sms secutiry]]
	Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).		Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).

PavelSafonov at 07:53, 14 February 2022

2022-02-14T07:53:57Z

← Older revision		Revision as of 10:53, 14 February 2022
Line 13:		Line 13:
	[[File:Example Inst.jpg\|thumb\|Instalation\|alt=\|260x260px]]		[[File:Example Inst.jpg\|thumb\|Instalation\|alt=\|260x260px]]
	For gain access to ability change default security state (for device from the factory) you need power up device (10-30V) and connect via USB to the PC. After device will be powered and LED indicators start work you can access to settings.		For gain access to ability change default security state (for device from the factory) you need power up device (10-30V) and connect via USB to the PC. After device will be powered and LED indicators start work you can access to settings.










Line 32:		Line 40:

	====2.1. Set up Keyword:====		====2.1. Set up Keyword:====
	[[File:~~Keyword use~~.gif\|thumb\|~~379x379px\|alt=~~\|Set up keyword]]		[[File:Sey up keyword.gif\|alt=\|thumb\|365x365px\|Set up keyword]]


Line 53:		Line 61:

	This command will emove existing keyword. If device is locked, keyword cannot be changed.		This command will emove existing keyword. If device is locked, keyword cannot be changed.




	====2.2. SMS security:====		====2.2. SMS security:====
	[[File:~~Set up SMS security~~.gif\|alt=~~\|thumb\|365x365px~~\|Set up sms secutiry]]		[[File:SMS_Security.gif\|alt=\|Set up sms secutiry\|thumb\|365x365px]]
	Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).		Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).

Line 61:		Line 72:

	Phone numbers have to be written in international standard, using "+" is optional but not necessary (in both cases number will be recognized, but when number is without "+" symbol, IDD Prefix will not be generated, which depends on location of the phone). If no numbers are entered, configuration and sending commands over SMS are allowed from all GSM numbers.		Phone numbers have to be written in international standard, using "+" is optional but not necessary (in both cases number will be recognized, but when number is without "+" symbol, IDD Prefix will not be generated, which depends on location of the phone). If no numbers are entered, configuration and sending commands over SMS are allowed from all GSM numbers.











Line 86:		Line 106:
	* at least 8 characters		* at least 8 characters
	====2.5 BLE STANDARD AES-128====		====2.5 BLE STANDARD AES-128====
	[[File:~~BLE Standart AES~~-128.gif\|alt=\|thumb\|365x365px]]		[[File:BLE_STANDARD_AES-128.gif\|alt=\|thumb\|365x365px]]
	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.









Line 98:		Line 125:

	==SECURE CONNECTION TO SERVER (TLS)==		==SECURE CONNECTION TO SERVER (TLS)==
	[[File:~~Tls option~~.gif\|alt=\|thumb\|365x365px]]		[[File:TLS.gif\|alt=\|thumb\|365x365px]]
	In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.		In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.
	TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.		TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.

PavelSafonov at 07:46, 14 February 2022

2022-02-14T07:46:49Z

← Older revision		Revision as of 10:46, 14 February 2022
Line 32:		Line 32:

	====2.1. Set up Keyword:====		====2.1. Set up Keyword:====
	[[File:~~Sey up keyword~~.gif\|alt=~~\|frame~~\|Set up keyword]]		[[File:Keyword use.gif\|thumb\|379x379px\|alt=\|Set up keyword]]


	Configuration security keyword can be set to configurator. Keyword can be saved in configuration file (.cfg), so there is no need to connect the device to the configurator to configure the keyword. Minimum keyword length is 4 symbols and maximum length is 10 symbols. Only uppercase and lowercase letters and numbers are supported. Keyword can be configured to .cfg configuration file when the device is not connected.		Configuration security keyword can be set to configurator. Keyword can be saved in configuration file (.cfg), so there is no need to connect the device to the configurator to configure the keyword. Minimum keyword length is 4 symbols and maximum length is 10 symbols. Only uppercase and lowercase letters and numbers are supported. Keyword can be configured to .cfg configuration file when the device is not connected.

	It can be changed via USB and also via SMS.		It can be changed via USB and also via SMS.

Line 50:		Line 53:

	This command will emove existing keyword. If device is locked, keyword cannot be changed.		This command will emove existing keyword. If device is locked, keyword cannot be changed.

	====2.2. SMS security:====		====2.2. SMS security:====
	[[File:Set up SMS security.gif\|alt=\|thumb\|365x365px\|Set up sms secutiry]]		[[File:Set up SMS security.gif\|alt=\|thumb\|365x365px\|Set up sms secutiry]]
Line 82:		Line 86:
	* at least 8 characters		* at least 8 characters
	====2.5 BLE STANDARD AES-128====		====2.5 BLE STANDARD AES-128====
	[[File:BLE Standart AES-128.gif\|alt=\|thumb\|365x365px~~\|Ble Standard AES-128~~]]		[[File:BLE Standart AES-128.gif\|alt=\|thumb\|365x365px]]
	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.



Line 95:		Line 98:

	==SECURE CONNECTION TO SERVER (TLS)==		==SECURE CONNECTION TO SERVER (TLS)==
	[[File:Tls option.gif\|alt=\|thumb\|365x365px~~\|Secure connection to server~~]]		[[File:Tls option.gif\|alt=\|thumb\|365x365px]]
	In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.		In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.
	TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.		TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.

PavelSafonov at 12:34, 4 February 2022

2022-02-04T12:34:46Z

← Older revision		Revision as of 15:34, 4 February 2022
Line 82:		Line 82:
	* at least 8 characters		* at least 8 characters
	====2.5 BLE STANDARD AES-128====		====2.5 BLE STANDARD AES-128====
	[[File:~~BLE_STANDARD_AES~~-128.gif\|alt=\|thumb\|365x365px]]		[[File:BLE Standart AES-128.gif\|alt=\|thumb\|365x365px\|Ble Standard 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.