No Trust in Legacy Architecture

Databases allow any operator or process with database access to change, delete or insert any data anywhere in the database.

Typically there is no way to tell when or if data has been changed without comparing to a restored backup, a slow and expensive exercise.

While some databases may have implemented change tracking, this can typically be circumvented by an attacker. An attacker can execute SQL statements that can delete or alter entire tables, but these would be quickly detected and remedied by restoring a backup.

Small unauthorised changes can have the greatest negative impact on trust.

Provenance Example

Demand for Trust Platforms to guarantee product and process provenance is building rapidly.

Such a trust application would typically involve:

Some of the certification stages or processes may be expensive.

The value of the certified product is typically greater than an uncertified product.

The platform may certify large shipments of certified product.

Unauthorised change of product data can skip stages or processes,
change weight, quality, value, category etc, undermining trust and integrity.

How can the provider and owner of a Trust Platform guarantee that no unauthorised changes have been made, when conventional databases can be so easily changed?

Decentralised Blockchain

Blockchain has become a buzzword since the launch of Bitcoin, and designers of Provenance Platforms have been working to bring blockchain's immutable properties to databases.

It is important to know that Blockchain is not really the core security of Bitcoin, it is the thousands of servers that vote on the blockchain ledger contents that underpin its immutability. Blockchain itself is simply a hash sequence of values that allow you to determine if any changes happened in the history. The vote on the 'correct' hash sequence is still prone to a well known 51% vote vulnerability.

So in order to access decentralised blockchain immutability engineers require a large number of voting servers. Typically they solve this by using an existing blockchain token and its server network. This solution has a price:

Once such a token network is created it must integrate with your database.

Integration must be performed with every table in the database that requires trust guarantee. It can be argued that all of the tables of a trust platform require integration.

Decentralised Blockchain integration is a significant overhead and expense and exacerbates legacy database problems.

Ultimately certification must be made on the Blockchain as database integration can be tampered with.

Quantum Secure Trust

Blockchains can be secured internally without the need for decentralised networks of mining servers. This can be achieved by securing the start and end of the blockchain.

Portalz Trust implements our Quantum Proof Security technology, creating 'secure blockchain loops' at the core of its DNA Enterprise Foundation.

Conventional

Portalz Trust brings unique-per-record immutability to data contained in Portalz DNA, locking records with Quantum Proof Security and implementing a revolutionary hierarchy of invisible morphed keys.

The resulting security cannot be cracked by any attacker with database access!

That same security infrastructure maintains a Quantum Secured Backup for each record, able to detect unauthorised changes, reporting the breach and automatically restore the authorised record.

This awesome capability is delivered seamlessly and automatically to every data store configured in Portalz DNA.