Applied - Cryptography - Report Group5
Applied - Cryptography - Report Group5
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.1 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.2 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Key Security Requirements and Threats . . . . . . . . . . . . . . . . . . . . . . 2
Real-World Impact and Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 State of Art . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1 Lightweight Cryptographic Protocols for RFID Security . . . . . . . . 4
4.2 Post-Quantum Cryptography and Future Directions . . . . . . . . . . . 5
5 Candidate Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6 Selection of Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1 Overall Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Communication Protocol: EPC Gen 2 (ISO 18000-63) . . . . . . . . . . 7
6.3 RFID Reader - Backend-Server Link . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.4 RFID Tag – RFID Reader Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.5 Considerations and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.6 Proposed Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7 Design Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8 Evaluation and Analysis - Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1 Analysis of Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.2 Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.3 Security Comparison-draft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.4 Cost Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
RFID Authentication in Medicine Anti-Forgery Applications 1
1 Introduction
RFID technology is a widely used method for automatic identification and track-
ing of objects through the use of electromagnetic fields. At its core, an RFID
system consists of tags, readers, and a backend database. RFID tags are small
devices that can store information and communicate wirelessly with an RFID
reader via radio waves. There are two main types: passive tags (which do not
have an internal power source and rely on the reader’s signal for energy) and ac-
tive tags (which have their own power supply). These tags can operate at various
frequencies, with low-frequency (125 kHz, offering longer range but slower data
rates with basic protocols) and high-frequency (13.56 MHz, supporting shorter
ranges, faster data transfer, and more robust cryptographic security features).
2 Requirements
should be able to access product data remotely, providing flexibility and en-
hanced monitoring capabilities.
The system should enable deactivation or storage of the RFID tag once the prod-
uct reaches its final destination as it should mantain an organized database of
the product lifecycle. Additionally, RFID should support high-volume operations
by allowing multiple tags to be scanned simultaneously to improve efficiency.
Key Security Requirements and Threats The RFID system has to en-
sure mutual authentication between the tag and the reader in such a way that
unauthorized devices do not get any chance to communicate with the system. It
should also provide cloning attack assurance so that counterfeit products could
not enter because of replicated tags [1]. Another major threat is from replay
attacks, where previously intercepted communication is reused for unauthorized
access.
Other general threats include eavesdropping and Man-in-the-Middle attack-
active attacks, where the attacker tries to capture the communication between
the tags and readers and change it [2]. This implies that ensuring data confiden-
tiality and integrity in sensitive applications unauthorized exposure or tampering
with data could lead to dangerous consequences.
In this respect, both the hardware and also communication protocols have
several vulnerabilities that can be used by a malicious actor to perform most
of the above-mentioned attacks in RFID systems. The likelihood of conducting
such attacks in real-life applications is easier because RFID readers are available
at low costs, which permits an attacker to intercept and change information [3].
The limited computational power of RFID tags further aggravates the risks of
such attacks since strong security measures are harder to implement with low
computational power. Therefore, attacks can be modeled to take advantage of
such weak points where operations of high volumes reduce oversight, and strong
and scalable security solutions are going to be very important in mitigating these
risks.
Lastly, since RFID tags only have restricted computational powers, the se-
curity mechanisms must be lightweight so that their execution can be managed
efficiently without loss of performance. The trade-off between security and effi-
ciency is important for scalability to high-volume supply chain operations.
RFID Authentication in Medicine Anti-Forgery Applications 3
3 Functionality
The following section will aim to describe how the workflow of this system should,
following the description depicted on Figure 1.
Backend
Authentication
Database lookup
Queries RFID tag
Validates RFID tag
Veri es identity
Logs events
Con rms authenticity
Triggers alerts
The RFID Tags must last throughout the entire process, and all stages of
the supply chain. Once the product has arrived at its final destination, the tag is
then deactivated and, or archived. In the background, a record of the products
trail and lifecycle is kept insystem’s database. The logistics and scalability costs
are kept minimal, and the integration costs of RFID authentication system is
kept low, for existing supply chain infrastructures. With Ultra High Frequency
(UHF) RFID technology, the system is designed to handle a large volume of
products by scanning multiple tags simultaneously, keeping track of damaged or
tampered tags.
4 State of Art
The field of RFID security has, in the past years, seen many critical advances
due to increasing demands for efficiency and security, such as those present in
the pharmaceuticals area. Among the main focuses within state-of-the-art RFID
technology, one can find lightweight cryptographic protocols that are supposed
to be run on top of the resource constraints given by a passive RFID tag.
5 Candidate Techniques
The following section presents a selection of candidate techniques from the cur-
rent state of the art for RFID tag technology (Section 4) fulfilling the security
and functionality requirements of the system detailed in previous Sections 2,
3. The following subsections provide an overview of the selected techniques for
RFID tag security.
6 Selection of Design
The following section presents the design proposals based on previous section’s
candidate techniques along with the design selection process. The design selec-
tion process is determined by the overall functional requirements and constraints
listed in previous section 3, with the final implementation following the overall
design depicted on Figure 2.
RFID System
RFID Reader
«controls»
Antenna Reader
«stores/retrieves data»
RFID Tag Backend Server Database
On the other hand, in terms of cost and efficiency, the implementation pro-
posed by Dass et al. (2016) reduces the number communications made to the
RFID tag, as well as the number of overall operations required. The solution
proposed by Dass et al. (2016) is more lightweight than the Flyweight protocol,
and does not solely rely on PRNG, reduces the computational and communi-
cation overhead, whilst retaining similar security features. For a more robust
solution, the overall authentication scheme can be combined with a distance
bounding protocol, can provide a comprehensive level of security that reduces,
whilst remaining attractive to the medical industry and logistics providers. But
in terms of overall comprehensiveness of the security features employed, the so-
lution proposed by Dass et al. (2016) does not provide backward secrecy, i.e.
security against future attacks where once the tag has been compromised, at-
tackers might predict future attacks. But in the case of a tag being compromised,
given the costs related to a tag being cheap to replace, and the overall risks in-
volved in re-using a previously compromised tag, this solution may prove more
applicable in the overall assessment made by the medical industry and logistic
providers.
7 Design Details
Design Assumptions
– a RFID system with only three entities will be considered: a tag, a RFID
reader, and a backend server. If multiple tags go thorugh a scanner / pass by a
reader at the same time, as the reader has no severe energy and computation
limits it will handle the different communications simultaneously in parallel
– the communication channel between reader and backend server is fully secure
(as stated previously)
– the tag is a passive device and communicates with reader through an insecure
wireless channel
– the tag contains two data fields (S, ID): the tag’s secret and the tag’s
pseudonym (index value in the database), where S is 128 bits and ID is
96 bits in length
– as seen later, S is going to be updated in the tag, rewritable memory is
required (EEPROM or FRAM) of 128 bits.
– the backend server maintains a local database with fields ID, h2 (ID), SOld ,
and SNew . Initially, SOld = 0 and SNew = S holds the tag’s secret value
– S is initialized at the tag’s creation and is only known by the tag itself and
the backend server
– the tag and backend system share a dedicated secret pseudorandom function
(in practice a keyed public pseudorandom function h1 with the dedicated
shared secret key S)
– the server’s database is considered secure, with proper access control and
perimeter definition
– random numbers generated are 96 bits in length
– tag memory is insecure and vulnerable to physical attacks
In round-trip systems, signals flow in both directions, and the distance between
two stations is calculated as follows:
c · (tm − td )
d= (1)
2
tm = 2 · tp + td (2)
The aim of this part of the protocol is to infer an upper bound for the distance
between the reader and the tag from the fact that no information can propagate
faster than at the speed of light.
As before mentioned, the RFID device is computationally weak. It can com-
pute the secret pseudorandom function h2 mentioned above, but the time it takes
for this computation (e.g., several milliseconds) is many orders of magnitude
larger than the maximum response-delay variance acceptable for our distance-
bounding application (tens of nanoseconds). We do assume that it is reliably able
to detect large deviations from its nominal clock frequency, in particular any at-
tempt by an attacker to operate the RFID device at at least twice its normal
speed (overclocking attack).
The first phase is not time-critical and calculates (typically in software) a
response R to a challenge NR1 (+ a nonce NT1 ), using a pseudo-random function
h2 and the shared secret key S known to both parties. The 2n bits of R are
not returned directly. Instead, they are split up and loaded into two n-bit shift
registers. A pre-agreed fixed number of clock cycles after the transmission of NR1 ,
the time-critical second phase begins, in which additional single-bit challenges
Ci are transmitted. Each selects one of the two shift registers, which returns its
first bit directly, using fast asynchronous logic that does not wait on any clock
cycle. The first bit in the respective other shift register is discarded at the same
time. This way, only half of all response bits R that were generated for an NR1
are revealed.
Formulating the response RiCi based on the received Ci is a simple single-bit
lookup in a 2-bit memory, which can be implemented in an entirely asynchronous
fashion, requiring only a small number of gate delays, without any clock signals
that the attacker could accelerate to obtain RiCi pre-maturely. As the signal
propagation time tp is very small, it is important that the processing delay td of
the token is short and predictable.
R1C1 = 1
C2 = 1 0011011
1110110
R2C2 = 1
... ...
C
Compare received Ri i
Cn = o 1
with calculated ones 0
Cn
Rn =1
• If they are equal, it is confirmed that the previous session was suc-
cessful and the tag contains SNew as its S value. The server sends
SNew to the reader.
• If V ′ and V are not equal, the server extracts SOld value for the
corresponding matched tag and calculates V ′′ = PRNG(SOld ⊕NR2 ⊕
NT2 ).
It checks if V ′′ and V are equal. If equality holds, then it sets the
variable Flag = 1 and sends SOld to the reader. Here, the server
is confirmed about the unsuccessful previous session, and the tag
contains SOld as its S value.
4. The reader uses the received value (either SNew or SOld ) as a seed to calculate
M = PRNG(S, NR ). It then calculates a random number N = PRNG(M )
and sends N to the tag and M to the server.
5. The tag computes M as well; and uses M as a seed value to calculate N ′
and verifies whether N ′ = N . If they match, the tag confirms the reader is
12 Group 5
legitimate, updates its secret as S = h1 (S||M ′ ), and updates its secret value
as S ⊕ U .
6. The server, after getting M value from the reader, checks the Flag variable.
– If Flag = 0, the secret of the tag has matched with SNew value, and it
calculates U = h1 (SNew || M ). Then, the server updates the secret value
in the database as SOld = SNew and SNew = SNew ⊕ U .
– If Flag = 1, the secret of the tag has matched with SOld value, and it
calculates U = h1 (SOld || M ). Then, the server updates the secret value
in the database as SNew = SOld ⊕ U and SOld remains unchanged.
Generate: NR
NR
Generate: NT ,
Calc V = PRNG(S ⊕ NR ⊕ NT ),
H = h(ID)
V, H, NT
V, H, NT , NR
Flag = 0
Test: Match h(ID) in DB
If match: Check V =
PRNG(SNew ⊕ NR ⊕ NT )
If true: Send SNew
Else if : V = PRNG(SOld ⊕
NR ⊕ NT ),
Set Flag = 1, send SOld
Snew or Sold
M N
With regards to physical tampering a seal or any physical system that proves
that a package containing medical supplies has either been opened or its tag
removed and replaced (with another legit one) would be visible to the quality
assurance inspectors working on field.
secondary operations such as XOR, PRNG, and hashing, where a typical session
requires 1 connection, 1 XOR, 2 hash functions, 1 random number generation
and 3 PRNGs. Communication costs is also the smallest small payload. Three
messages are required - to ensure performance even in bandwidth-constrained
environments. Even though each tag stores 128 bits of secret and 96 bits of
alias, for a total of 224 bits. Avoiding heavy encryption reduces energy costs
which saves the energy of the tag and support longevity in applications such as
supply chain.
Notations:
– TC : Concatenation operation.
– TX : XOR (Exclusive OR) operation.
– TH : Hash function.
– TR : Random number generation.
– TP : Pseudorandom number generation (PRNG).
– TF : Flip operation.
16 Group 5
References
1. M. Burmester and J. Munilla, “Lightweight rfid authentication with forward and
backward security,” ACM Transactions on Information and System Security (TIS-
SEC), vol. 14, no. 1, pp. 1–26, 2011.
2. A. Li, J. Li, Y. Zhang, D. Han, and T. Zhang, “Secure uhf rfid authentication with
smart devices,” IEEE Transactions on Wireless Communications, vol. 22, no. 7,
pp. 4520–4533, 2023.
3. R. Singh, D. Kim, and J. Kim, “Clone tag detection in distributed rfid systems,”
PLOS ONE, vol. 13, no. 3, pp. 1–22, 2018.
4. P. Dass and H. Om, “A secure authentication scheme for rfid systems,” Procedia
Computer Science, vol. 78, pp. 100–106, 2016.
5. G. Hancke and M. Kuhn, “An rfid distance bounding protocol,” in Proceedings of
IEEE/Create-Net SecureComm, pp. 67–73, 2005.
6. H. A. Mohamed and E. Elrabie, “Lightweight cryptographic solutions for rfid sys-
tems using elliptic curve cryptography,” Journal of Network Security, vol. 14,
pp. 47–62, 2019.
7. H. Hong, J. Lee, and S. Kim, “A comprehensive review of hummingbird crypto-
graphic protocols: Applications to rfid systems,” International Journal of Crypto-
graphic Research, vol. 7, pp. 101–118, 2020.
8. F. Amtmann and L. Angarita, EPC® Radio-Frequency Identity Generation-2 UHF
RFID Standard, Release 3.0. GS1 AISBL, 2024.
9. NIST, “Report on post-quantum cryptography,” tech. rep., National Institute of
Standards and Technology, 2024.
10. A. Li, J. Li, Y. Zhang, D. Han, T. Li, and Y. Zhang, “Secure uhf rfid authentication
with smart devices,” IEEE Transactions on Wireless Communications, vol. 22,
no. 7, pp. 4520–4533, 2023.
11. F. Amtmann, L. Angarita, et al., EPC® Radio-Frequency Identity Generation-2
UHF RFID Standard, Release 3.0. GS1 AISBL, January 2024. Specification for
RFID Air Interface Protocol for Communications at 860 MHz – 930 MHz. First
published in 2004, updated with Gen2v2 in 2013 and Gen2v3 in 2024.
12. G. P. Hancke and M. G. Kuhn, “An rfid distance bounding protocol,” Proceedings
of IEEE/Create-Net SecureComm 2005, pp. 67–73, September 2005.
13. National Cyber Security Centre, “Using tls to protect data.”
https://www.ncsc.gov.uk/guidance/using-tls-to-protect-data, 2021. Archived
from the original on July 21, 2021.
14. M. Madhavan, A. Thangaraj, Y. Sankarasubramanian, and K. Viswanathan, “Nlhb:
A non-linear hopper-blum protocol,” pp. 2498 – 2502, 07 2010.
15. H.-Y. Chien, “Sasi: A new ultralightweight rfid authentication protocol providing
strong authentication and strong integrity,” IEEE Transactions on Dependable and
Secure Computing, vol. 4, no. 4, pp. 337–340, 2007.
16. W. Che, F. Saqib, and J. Plusquellic, “Puf-based authentication,” in 2015
IEEE/ACM International Conference on Computer-Aided Design (ICCAD),
pp. 337–344, 2015.
17. A. Alkorji, M. Rohani, and M. Abuali, “Ultra-lightweight mutual authentication
protocol to prevent replay attacks for low-cost rfid tags,” IEEE Access, vol. PP,
pp. 1–1, 01 2024.
18. D. Yum, J. S. Kim, S. Hong, and P. J. Lee, “Distance bounding protocol for mutual
authentication,” IEEE Transactions on Wireless Communications, vol. 10, pp. 592–
601, 02 2011.