RPMB Memory Controller with Authentication for Replay Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices lack effective mechanisms to protect against replay attacks on sensitive data and ensure secure, authenticated access to replay protected memory blocks (RPMBs), which compromises data integrity and security.
Innovation Solution
Incorporating a replay protected memory block (RPMB) with an RPMB engine that uses authentication keys and hash algorithms to control access, ensuring secure storage and retrieval of sensitive data through authenticated operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If authentication mechanisms are implemented for RPMB access, then data security is improved, but device complexity increases
Solution Approach 1:
The storage device is segmented into multiple memory blocks, with specific blocks designated as RPMBs that require authentication. The controller separately manages authenticated access to RPMBs versus unauthenticated access to other memory blocks, isolating security requirements to specific segments rather than applying complexity across the entire device.
Solution Approach 2:
An authentication mechanism acts as an intermediary between the host and the RPMB. The controller mediates access requests by verifying authentication information before allowing writes to or reads from RPMBs, thereby enforcing security without requiring the host to directly implement complex security protocols.
2Reliability
If authentication operations are performed for every write request to RPMB, then data integrity is improved, but operating speed deteriorates
Solution Approach 1:
Authentication information is prepared and verified in advance before data writing to the RPMB. The controller performs authentication checks on write requests before committing data, ensuring that only authenticated data is stored in the protected memory block, thereby maintaining integrity while streamlining the write process.
3Reliability
If separate authenticated read commands are required for RPMB, then security is improved, but ease of operation deteriorates
Solution Approach 1:
The controller provides a unified interface for both authenticated and unauthenticated memory access. While separate authenticated commands are used for RPMB operations, the controller manages the complexity internally, presenting a consistent interface to the host that handles both types of access without requiring the host to implement different protocols for different memory regions.
Data Source
AI summary
Provided herein may be a storage device and a method of operating the same. The method of operating a storage device including a replay protected memory block (RPMB) may include receiving a write request for the RPMB from an external host, selectively storing data in the RPMB based on an authentication operation, receiving a read request from the external host, and providing result data to the external host in response to the read request, wherein the read request includes a message indicating that a read command to be subsequently received from the external host is a command related to the result data.


