Evaluating the cost to cipher the NoC communication

Oliveira, Bruno; Reusch, Rafael Schild; Medina, Henrique; Moraes, Fernando

doi:10.1109/lascas.2018.8399914

Cited by 10 publications

(8 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…If the NIs are assumed trusted (in-house design), the countermeasure(s) can be integrated within the NI units. Many researchers have integrated their security solutions in the NI units, e.g., bulky modules for symmetric and asymmetric cryptography [40], [49], [50]. Also, most countermeasures that guarantee secure memory access are implemented in the NI.…”

Section: Wired Nocs Countermeasuresmentioning

confidence: 99%

See 1 more Smart Citation

A Survey on the Security of Wired, Wireless, and 3D Network-on-Chips

et al. 2021

View full text Add to dashboard Cite

Network-on-Chips (NoCs) have been widely used as a scalable communication solution in the design of multiprocessor system-on-chips (MPSoCs). NoCs manage communications between on-chip Intellectual Property (IP) cores and allow processing cores to achieve higher performance by outsourcing their communication tasks. NoC paradigm is based on the idea of resource sharing where hardware resources, including buffers, communication links, routers, etc., are shared between all IPs of the MPSoC. In fact, the data being routed by each NoC router might not be related to the router's local core. Such a utilization-centric design approach can raise security issues in MPSoCs-based designs, e.g., integrity and confidentiality of the data being routed in an NoC might be compromised by unauthorized accesses/modifications of intermediate routers. Many papers in the literature have discovered and addressed security holes of NoCs, aiming at improving the security of the NoC paradigm. However, to the best of our knowledge, there is no solid survey study on the security vulnerabilities and countermeasures for NoCs. This paper will review security threats and countermeasures proposed so far for wired NoCs, wireless NoCs, and 3D NoCs. The paper aims at giving the readers an insight into the attacks and weaknesses/strengths of countermeasures.

show abstract

Section: Wired Nocs Countermeasuresmentioning

confidence: 99%

“…Oliveira et al [49] aimed at measuring the latency overhead of AES encryption when used between the NI and the router. The proposed architecture consists of a manager element that generates unique random keys for each communication session.…”

Section: A Data Confidentiality Countermeasuresmentioning

confidence: 99%

A Survey on the Security of Wired, Wireless, and 3D Network-on-Chips

et al. 2021

View full text Add to dashboard Cite

show abstract

“…Oliveira et al [33] propose an architecture that includes a firewall capable of filtering incoming and outgoing NoC traffic, an AES cipher block to encrypt the NoC flow and, an auxiliary NoC that use a Hamiltonian path to configure the firewall rules and distribute the keys. Figure 7 presents the interfaces connected to the firewall.…”

Section: (Vi) Cryptographymentioning

confidence: 99%

“…Santana et al [48] extend the aforementioned work [33], by adopting four security countermeasures: spatial isolation of applications, a dedicated network to send sensitive data, filters to block malicious traffic, lightweight cryptography. This proposal is decoupled from the M CSoC architecture, protecting the system from attacks, such as Denial of Service and man-in-the-middle, ensuring confidentiality and in-tegrity to applications.…”

Section: (Vi) Cryptographymentioning

confidence: 99%

A Survey on Security Mechanisms for NoC-based Many-Core SoCs

Caimi

Faccenda

Moraes

2021

JICS

View full text Add to dashboard Cite

The adoption of many-cores systems introduces the concern for data protection as a critical design requirement due to the resource sharing and the simultaneous executions of several applications on the platform. A secure application that processes sensitive data may have its security harmed by a malicious process. The literature contains several proposals to protect many-cores against attacks, focusing on the protection of the application execution or the access to shared memories. However, there is a gap to be fulfilled: a solution covering the entire application lifetime, including its admission, execution, and peripheral's access. This survey discusses three security-related issues: the secure admission of applications, the prevention of resource sharing during their execution, and the safe access to external devices. This survey concludes with an evaluation of the studied methods, pointing out directions and research opportunities.

show abstract

“…Table 1 presents a broad overview of works covering security for applications executing in MCSoCs. The Table shows the adoption of different methods, including Physical Unclonable Function (PUF) and Message Authentication Code (MAC) [10], firewalls [11]- [13], encryption [12,13], temporal communication partition [14], packet validation [15], routing schemes [16], and Secure Zones (SZ).…”

Section: Introductionmentioning

confidence: 99%

SDN-Based Secure Application Admission and Execution for Many-Cores

2020

View full text Add to dashboard Cite

General-purpose many-core system-on-chip (MCSoC) requires support to the execution of dynamic workloads, i.e., admission of new applications at runtime. Some applications may require QoS and security from the MCSoC, not tolerating that malicious tasks or hardware Trojans steal or corrupts their data. A robust method to provide security is to isolate the communication and computation. Most current works employ such isolation in continuous regions named secure zones (SZ). Motivated by the recent study of the Software-Defined Networking (SDN) paradigm for MCSoCs, this work proposes to use SDN-based management to implement the communication isolation at runtime. The computation isolation occurs by mapping only tasks of the same application at each core. The communication isolation is supported by the SDN paradigm, which establishes dedicating paths for secure applications. Results show that the SDN-based approach presents a negligible latency to admit and execute a secure application, with a reduced hardware cost and higher computational resources utilization compared to SZs.

show abstract

Evaluating the cost to cipher the NoC communication

Cited by 10 publications

References 9 publications

A Survey on the Security of Wired, Wireless, and 3D Network-on-Chips

A Survey on the Security of Wired, Wireless, and 3D Network-on-Chips

A Survey on Security Mechanisms for NoC-based Many-Core SoCs

SDN-Based Secure Application Admission and Execution for Many-Cores

Contact Info

Product

Resources

About