Bluetooth Security Considerations: Seminar by Anoop Aravind

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 21

BLUETOOTH SECURITY

CONSIDERATIONS

SEMINAR BY
ANOOP ARAVIND
INTRODUCTION
• Bluetooth is a packet based protocol. IT is an open wireless
technology standard for exchanging data over short
distances.
Bluetooth uses radio technology called frequency hopping
spread spectrum.

Bluetooth provides a secure way to connect and exchange


information between devices such as faxes, mobile phones
and laptops. Bluetooth provides a transmission distance of
range of 10-42mtrs.It integrates security meet in several
layer of protocol.
Bluetooth exactly means a small microchip using a short range
radio line.

Bluetooth can store security related information on services


and device. It also enforces verification and encryption of data
before connection to application.

Many cable wires are replaced by a single Bluetooth device.

Stores security related information on services and devices.


CHARACTERISTIC OF BLUETOOTH
TECHNOLOGY
Transmission distance of range 10 to 42 meters.

Integrates security mechanism in several layers of protocol.


Stores security related information on services and devices.

The encryption key size varies from 8 to 128 bits.

The two devices wanting to establish contact must agree the size of encryption key to use.
 
SECURITY CONSIDERATIONS
Authentication: verifying the identity of communicating devices. User
authentication is not provided natively by Bluetooth.

Confidentiality: preventing information compromise by ensuring that


only authorized devices can access and view data

Authorization: allowing the control of resources by ensuring that a


device is authorized to use a service before permitting it to do so.
Security Features of Bluetooth
Specifications:
Each Bluetooth device must operate in one of the four modes:-

1.Security Mode 1: Is non-secure. Security functionality


(authentication and encryption) is bypassed, leaving the device
and connections susceptible to attackers.
 Bluetooth devices in this mode do not employ any mechanisms
to prevent other Bluetooth-enabled devices from establishing
connections.
 Security Mode 1 is only supported in v2.0 + EDR (and earlier) devices.
Security mode 2:

For this security mode, a security manager (as specified in the


Bluetooth architecture) controls access to specific services and
devices.
The centralized security manager maintains policies for access
control and interfaces with other protocols and device users.
In this mode, the notion of authorization—the process of
deciding if a specific device is allowed to have access to a
specific service—is introduced.
Security mode 3:
The link level-enforced security mode, a Bluetooth device initiates
security procedures before the physical link is fully established.

Bluetooth devices operating in Security Mode 3 mandates


authentication and encryption for all connections to and from the
device.

This mode supports authentication (unidirectional or mutual) and


encryption. The authentication and encryption features are based
on a separate secret link key that is shared by paired devices, once
the pairing has been established.
Security Mode 4: Is a service level enforced security mode in
which security procedures are initiated after link setup.

Security requirements for services protected by Security Mode


4 must be classified as one of the following: authenticated link
key required, unauthenticated link key required, or no security
required.
Bluetooth Security
Recommendations & Precautions
Never use standard commercial Bluetooth headsets.
• Enable Bluetooth functionality only when necessary.
• Require and use only devices with low-power Class 2 or 3
Bluetooth transceivers.
• Keep devices as close together as possible when Bluetooth
links are active.
• Independently monitor devices and links for unauthorized
Bluetooth activity.
• Make devices discoverable (visible to other Bluetooth devices)
only if/when absolutely necessary.
 Make devices connectable (capable of accepting and
completing incoming connection requests) only if/when
absolutely necessary and only until the required
connection is established.

Pair Bluetooth devices in a secure area using long,


randomly generated passkeys. Never enter passkeys
when
unexpectedly prompted for them.

Maintain physical control of devices at all times. Remove


lost or stolen devices from paired device lists.
Use device firewalls, regularly patch Bluetooth devices, and
keep device anti-virus software up to date.

• Comply with all applicable directives, policies, regulations,


and guidance.

• Subject Bluetooth solutions and deployments to


independent security audits by qualified evaluators.
Bluetooth application developers should
consider designing to the following
guidelines:
• Eliminate or disable support for the Headset and Hands-
Free Profiles unless such links are adequately
secured using the techniques described.
• Passkeys should be at least eight digits long. Passkeys
must not be valid indefinitely.
• Use configuration and link activity indicators like LEDs or
desktop icons.
• Require user authorization for all incoming connection
requests, and don’t accept connections, files, or other
objects from unknown, untrusted sources.

• Program each device to initiate Bluetooth authentication


immediately after the initial establishment of the
Bluetooth connection (also known as Security Mode 3, Link
Level security).

• Program each device to initiate 128-bit Bluetooth


encryption immediately after mutual authentication. Layer
FIPS-certified cryptography atop Bluetooth cryptography
for defense in depth.
• Store link keys securely and regularly change link keys
under encryption.
• Remove the user's ability to control Bluetooth settings
that could possibly circumvent security features.
• Enable each Bluetooth service only when needed.
Permanently remove, or disable, all unnecessary Bluetooth
services.
• Digitally sign all Bluetooth firmware, driver, and
application software. Verify that no unauthorized software
applications use Bluetooth application programming
interfaces.
• Prohibit the user from changing or controlling Bluetooth
security features.
Bluetooth Security Mechanisms
Bluetooth links use optional pre-shared key authentication and encryption algorithms that
are widely considered acceptably strong when both implemented and used correctly.
The strength of Bluetooth security relies primarily on the length and randomness of the
passkey used for Bluetooth pairing, during which devices mutually authenticate each
other for the first time and set up a link key for later authentication and encryption.
KEY MANAGEMENT
There are several kinds of keys in the Bluetooth system to
ensure secure transmission. The most important key is the
link key, which is used between two BT devices for
authentication purpose.

Link key:
There are four link keys to cover the different applications
it is used for. They are :

1)Unit key KA, is derived at the installation of the Bluetooth


device from a unit A.

The storage of KA requires little memory space and is often used when device has little
memory or when the device should be accessible to a large
group of users.
2) Combination key, KAB, is derived from two units A and B.
This key is generated for each pair of devices and is used
when more security is needed.

3) The master key, Kmaster, is used when the master device


wants to transmit to several devices at ones. It over rides
the current link key only for one session.

4) The initialization key, Kinit, is used in the initialization


process. This key protects initialization parameters when
they are transmitted.
Encryption key

Encryption key is derived from the current link key.

Each time encryption is needed the encryption key will be


automatically changed .

The purpose of separating the authentication key and encryption key is to facilitate the use of a shorter encryption key without weakening the strength of the authentication procedure .
PIN code
This is a number, which can be fixed or selected by the
user.
The length is usually 4 digits, but it can be anything
between 1 to 16 octets.

You might also like