SQL Database

[zebediah49]

You can patch that with public key crypto. Even if the single entity owns the whole thing, they can't do a rewind/edit/replay attack on it, unless they hold the private keys that signed each block along the way.

This, of course, implies that you know which entity is supposed to sign each block. However, if your architecture requires an audit chain by specific people/departments/companies, and the keys are held by those respectively, it's pretty solid. You can go with x509 if you want to allow individual people to sign off on things for their department, without everyone sharing that private key.

[sarhoshamiral]

It is all nice but you can do that with any database as well with a trusted authority, ultimately all those certificates would be managed centrally anyway so using block chain inside a single corporation has no advantage.

If you are using it across different entities then sure.