IBM 4765 cryptographic coprocessor

Arnold, Todd; Buscaglia, C.; Chan, Fransiskus Axel Peter; Condorelli, V.; Dayka, J.; Santiago-Fernandez, W.; Hadzic, N.; Hocker, M. D.; Jordan, M.; Morris, Trevor; Klaus, Werner

doi:10.1147/jrd.2011.2178736

Cited by 20 publications

(14 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…TrustedDB TrustedDB is an SQL database processing engine that makes use of IBM 4764/5 cryptographic coprocessors [10] to run custom queries securely [12]. Coprocessors offer several cryptographic schemes such as the Advanced Encryption Standard (AES), the Triple Data Encryption Standard (3DES), RSA, pseu-dorandom number generation and cryptographic hash functions.…”

Section: Secure Trusted Hardwarementioning

confidence: 99%

Enforcing Privacy in Cloud Databases

Moghadam

Darmont

Gavin

2017

Big Data Analytics and Knowledge Discovery

View full text Add to dashboard Cite

Abstract. Outsourcing databases, i.e., resorting to Database-as-a-Service (DBaaS), is nowadays a popular choice due to the elasticity, availability, scalability and pay-as-you-go features of cloud computing. However, most data are sensitive to some extent, and data privacy remains one of the top concerns to DBaaS users, for obvious legal and competitive reasons. In this paper, we survey the mechanisms that aim at making databases secure in a cloud environment, and discuss current pitfalls and related research challenges.

show abstract

Section: Secure Trusted Hardwarementioning

confidence: 99%

Enforcing Privacy in Cloud Databases

Moghadam

Darmont

Gavin

2017

Big Data Analytics and Knowledge Discovery

View full text Add to dashboard Cite

show abstract

“…The authors propose the use of a fully trusted party (a trusted hardware module [1], [2] in their case) to make a cryptographically secure SSE scheme efficient and sketch a construction for relational databases.…”

Section: Introductionmentioning

confidence: 99%

Distributed Searchable Symmetric Encryption

Bösch

Andreas

Leenders

et al. 2014

2014 Twelfth Annual International Conference on Privacy, Security and Trust

View full text Add to dashboard Cite

Abstract-Searchable Symmetric Encryption (SSE) allows a client to store encrypted data on a storage provider in such a way, that the client is able to search and retrieve the data selectively without the storage provider learning the contents of the data or the words being searched for. Practical SSE schemes usually leak (sensitive) information during or after a query (e.g., the search pattern). Secure schemes on the other hand are not practical, namely they are neither efficient in the computational search complexity, nor scalable with large data sets. To achieve efficiency and security at the same time, we introduce the concept of distributed SSE (DSSE), which uses a query proxy in addition to the storage provider.We give a construction that combines an inverted index approach (for efficiency) with scrambling functions used in private information retrieval (PIR) (for security). The proposed scheme, which is entirely based on XOR operations and pseudorandom functions, is efficient and does not leak the search pattern. For instance, a secure search in an index over one million documents and 500 keywords is executed in less than 1 second.

show abstract

“…The IBM 4765 [1] cryptographic coprocessor resembles a general-purpose computer, encased in a tamper-proof housing and packed onto a PCIe card. Its security policies require that most access to the persistent storage be brokered through the built-in bootloader, and in particular its subsystem called the Persistent Memory Manager (PMM).…”

Section: Introductionmentioning

confidence: 99%

“…Figure 1 shows its call graph. The complexity of implementation, and thus also reasoning, caused by the non-determinism of (2) is then further aggravated by (1), since longer implementations induce new restart points.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Verification of a Transactional Memory Manager under Hardware Failures and Restarts

Marić

Sprenger

2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. We present our formal verification of the persistent memory manager in IBM's 4765 secure coprocessor. Its task is to achieve a transactional semantics of memory updates in the face of restarts and hardware failures and to provide resilience against the latter. The inclusion of hardware failures is novel in this area and incurs a significant jump in system complexity. We tackle the resulting verification challenge by a combination of a monad-based model, an abstraction that reduces the system's non-determinism, and stepwise refinement. We propose novel proof rules for handling repeated restarts and nested metadata transactions. Our entire development is formalized in Isabelle/HOL.

show abstract

IBM 4765 cryptographic coprocessor

Cited by 20 publications

References 1 publication

Enforcing Privacy in Cloud Databases

Enforcing Privacy in Cloud Databases

Distributed Searchable Symmetric Encryption

Verification of a Transactional Memory Manager under Hardware Failures and Restarts

Contact Info

Product

Resources

About