Crypto Secure Data Management with In-Database Blockchain
summary
Claim: Oracle adds a blockchain table keyword to enforce immutable rows via chained cryptographic digests, preventing updates even by DBAs and detecting disk‑level tampering when verification fails. Implementation details: digests chain row+previous, optional per‑row user signatures, an open source verifier lets outsiders recompute checks, and digests can be published for third‑party audit. Result: SQL‑level integration needs no app rewrite, supports analytics and the JSON‑relational duality, and runs at regular database speeds.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:49Why in-database blockchain matters
- 3:15Oracle blockchain tables
- 5:45Cryptographic chaining
- 8:12Tamper detection below DB layer
- 10:43Open-source verification
- 11:47Preventing data cover-ups
- 14:16Cryptographic signing
- 15:42Converged database features
- 18:58Smartphone analogy
- 20:22JSON relational duality
- 21:47Summary
related talks
22mBlockchain for the enterprise: Crypto-secure data management
34mWhat's new with in-database blockchain and crypto-security?
12mLeveraging Blockchain for Test Data Integrity
24mOracle's vision for simplifying data-driven apps and analytics
19mMission-critical databases made simple
14mEncrypted Databases Made Secure Yet Maintainable
15mBest Practices for Securing Oracle Database
24mRethinking Database Architecture to Embrace Modern App Dev
