Fig 3 - uploaded by Rajat Kumar Jain
Content may be subject to copyright.
Flow chart explaining how Memory Leak Detector Library participates in the process of serving memory requests.
Source publication
Similar publications
p>A research paper on the performance differences between Rust and C++ and answers which language is better for performance-based applications.</p
Citations
... AOP is being increasingly recognized as an indispensable paradigm in the realm of system application testing [12,13], with Java programs using AspectJ weavers [14] and AspectC++, a C++ based AOP weaver, becoming increasingly utilized for software validation [15]. Jain et al. utilized C++ aspects to detect vulnerabilities caused by memory leakage, improper algorithm implementation, or thread interference [16]. For dynamic software bug reporting, aspects are generated automatically and woven into C++ programs. ...
Cryptographic devices’ complexity necessitates fast security simulation environments against fault attacks. SystemC, a promising candidate in Electronic System Levels (ESLs), can achieve higher simulation speeds while maintaining accuracy and reliability, and its modular and hierarchical design allows for efficient modeling of complex cryptographic algorithms and protocols. However, code modification is required for fault injection and detection. Aspect-Oriented Programming (AOP) can test cryptographic models’ robustness without modifications, potentially replacing real cryptanalysis schemes and reducing the time and effort required for fault injection and detection. Through the utilization of a fault injection/detection environment, this paper presents a novel approach to simulating the security fault attacks of ASCON cryptographic systems at the ESL. The purpose of this methodology is to evaluate the resistance of ASCON SystemC models against fault attacks. The proposed methodology leverages the advantages of AOP to enhance the fault injection and detection process. By applying AOP techniques, we inject faults into the SystemC models without making any changes to the main codebase. This approach not only improves the efficiency of testing cryptographic systems but also ensures that the main functionality remains intact during the fault injection process. The methodology was validated using three scenarios and SystemC ASCON as a case study. The first simulation involved evaluating fault detection capabilities, the second focused on the impact of AOP on executable file size and simulation time, and the third focused on the ESL impact on the ASCON design process. Simulation results show that this methodology can perfectly evaluate the robustness of the ASCON design against fault injection attacks with no significant impact on simulation time and file executable size. Additionally, the simulation results prove that the ASCON development life cycle at the ESL reduces the amount of time devoted to the design procedure by 83.34%, and the ASCON security attack simulations at the ESL decrease the simulation time by 40% compared to the register transfer level (RTL).
