You are currently viewing SemiWiki as a guest which gives you limited access to the site. To view blog comments and experience other SemiWiki features you must be a registered member. Registration is fast, simple, and absolutely free so please, join our community today!

Results 1 to 3 of 3

Thread: Survey on Techniques for Improving of Non-volatile memories

  1. #1
    Join Date
    Feb 2015
    Thumbs Up
    Received: 1
    Given: 1

    Survey on Techniques for Improving of Non-volatile memories

    Due to their high density and near-zero leakage power consumption, non-volatile memories (NVMs) are promising candidates for designing future memory systems. However, compared to conventional memories, NVMs also face more-severe security threats, e.g., the limited write endurance of NVMs makes them vulnerable to write-attacks. Also, the non-volatility of NVMs allows the data to persist even after power-off, which can be accessed by a malicious agent. Further, encryption endangers NVM lifetime and performance by reducing the efficacy of redundant-write avoidance techniques.

    The attached paper presents a survey of techniques for improving security of NVM-based memories by addressing the aforementioned challenges. This paper is expected to be useful for researchers and practitioners in the area of memory and hardware/system security.

    It reviews 40+ papers and has been accepted in Journal of Hardware and Systems Security 2018.


    0 Not allowed!

  2. #2
    Top Influencer
    Join Date
    Mar 2012
    Thumbs Up
    Received: 142
    Given: 117
    It is an interesting coverage of the potential vulnerabilities of NVMs to attacks. I think the defense can be both in hardware and software. For hardware, the obvious choice is a DRAM cache, which has no endurance issues and no remanence or retention which could pose security risk. For software, obviously analysis of high-volume upload data patterns can be targeted.

    0 Not allowed!

  3. #3
    Join Date
    Jul 2014
    Thumbs Up
    Received: 10
    Given: 0
    Very nice paper. Lots to think about.

    I think encryption is inevitable and am not sure your suggestions for small blocks are in general feasible, they increase the overheads of managing the media which can add to latency and reduce capacity. If the media does not have enough endurance to be care free (generally, 10M rewrites or better, assuming wear levelling, then the cache has to be quite well planned and reasonably large. Detecting attacks is also good: this should be a widespread plan not just here but other places like CPUs. You can't anticipate every way Specter-style abandoned branching could be weaponized, but you could count how frequently exceptions would be happening under abandoned paths and detect the whole approach before it can gather useful information.

    0 Not allowed!

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts