# DNA-PRESENT: An Improved Security and Low-Latency, Lightweight Cryptographic Solution for IoT
###### Abstract  
The vast interconnection of resource-constrained devices and the immense amount of data exchange in the Internet of Things (IoT) environment resulted in the resurgence of various security threats. This resource-constrained environment of IoT makes data security a very challenging task. Recent trends in integrating lightweight cryptographic algorithms have significantly improved data security in the IoT without affecting performance. The PRESENT block cipher, a standard and lightweight benchmark algorithm, is a widely accepted and implemented algorithm with a simple design, low-cost implementation, and optimum performance. However, this simple design utilizing lightweight linear and non-linear functions led to slow confusion and diffusion properties. The static bits in the permutation layer are the leading cause of slow diffusion, showcasing dependencies between plaintext and ciphertext bits. This research addresses and seeks to overcome this shortcoming of slow confusion and diffusion using the Deoxyribonucleic Acid (DNA) replication process and shift-aided operations, leading to the DNA-PRESENT block cipher. Security, cost, and performance analyses were performed to verify the improvements. The results demonstrated that with only 33.5% additional cost, DNA-PRESENT increased key sensitivity to 73.57%, plaintext sensitivity to 33%, and consistently ensured an average bit error rate (BER) of 50.2%. An evident increase of 176.47 kb/s in throughput and reduced latency to 17 cycles/block kept the good hardware efficiency of 43.41 kbps/KGE, and the reduction in execution time by 0.2333 s led to better performance. Considering the security advances achieved, this cost increase is a trade-off between security and performance. diffusion property; DNA cryptography; Internet of Things (IoT); lightweight cryptography; performance analysis; PRESENT block cipher; security analysis +
Footnote †: journal:  
0000-0001-999-4000-0000-0000-0000-0000-0000-0000-0000-00000-00000-0000-00000-00000-00000-00000-00000-00000-00000-000000-00000-00000-000000-000000-000000-000000-000000-  
However, the algorithm must not exceed the gate limit of 3000 GEs for security implementation [12; 13; 14]. Hence, simple mathematical functions--especially substitution, permutation, shift, and XoR--are prioritized to achieve an optimal balance between low cost, good security, and better performance [12]. The block ciphers in LWC have a Substitution Permutation Network (SPN) structure characterized by alternating layers of substitution box (s-box) and permutation (p-box). This design ensures confusion and diffusion within the algorithm. Confusion obscures the statistical relationship between keys and ciphertext, while diffusion conceals a similar relationship between plaintext and ciphertext [15; 16; 17; 18; 19; 20; 21; 22]. In recent years, numerous lightweight block cipher solutions have been considered for IoT applications, including AES [13]; NOEKEON [23]; ICEBERG [24]; mCrypton [12]; PRESENT [25]; PUFFIN [12; 26]; LED [12; 27]; PRINCE [12]; RECTANGLE [28]; and I-PRESENT [29]. The PRESENT block cipher is an LWC standard in the International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 29192. A simple, yet efficient design of the PRESENT block cipher is still considered a benchmark for the design of new lightweight algorithms, as it ensures an effective balance between cost and performance [30]. The present block cipher has an SPN structure, with wide applicability and acceptance in IoT applications [25; 27; 31; 32; 33]. Despite its wide acceptance and adoption, the algorithm's design needs security improvements [34; 35; 36; 22]. Recent cryptanalysis advancements have led to the exploitation of any specific part of the algorithm instead of attacking the whole algorithm [37; 22]. An in-depth study of PRESENT from the literature establishes two basic weaknesses in PRESENT, which need to be addressed. First, refs.