SQL Server ledger verification depends on independently stored digests
SQL Server ledger tables record changes in a verifiable structure, but their tamper evidence only holds if verification is run and the expected digests are kept outside the database. Microsoft's guidance calls for periodic digest generation and storage in tamper-proof locations such as immutable cloud containers or WORM devices, since a copy beside the database could be altered along with it. Operators must define which ledger is covered, where digests live and who can modify them, how often digests are generated, and who reviews failed checks. Verification is resource-intensive and should be scheduled against production workloads, and restores should be tested together with verification because a restored database can carry a different ledger history. Any mismatch should be treated as an incident, with evidence preserved before recovery.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in