In most systems, data security relies solely on the administrator password. If an attacker gains direct access to the database, they can change prices, falsify payments, or delete transaction history. At RK-CMS, we approach this issue differently.
We operate on a simple principle: even if an attacker gains access to the database, they won't be able to undetected change information or steal money.
To achieve this, we use two levels of protection: digital signatures and an unbroken transaction chain.
Data Signatures: Like a Seal on a Document
Imagine that each record in our database is an official document. For a document to be considered authentic, it must bear a wet seal.
In RK-CMS, this seal is represented by a signature (a unique digital code, a hash). The system automatically calculates this code for each record based on its contents.
How it works in practice:
Let's say there's a row in the database: "User Vasya, balance: 100 rubles."
The system takes this row, runs it through a special algorithm, and produces a code, for example: A1B2C3. This code, A1B2C3, is stored next to the data.
Now, if a hacker tries to silently replace the data in the database and writes "Balance: 1,000,000 rubles," the signature won't match. The algorithm will return a different code for the new amount, for example, X9Y8Z7.
Result: RK-CMS constantly checks the data against its signatures. If an attacker has changed a number in the database but is unable to recalculate the signature (which they can't do because they don't know the secret key), the system immediately detects the substitution. Such corrupted data is blocked and not allowed to be displayed on the website. The user won't see the fake balance, and the administrator will receive an alarm.
Transaction Integrity: An Unbreakable Chain
Balances and transaction history are the sweet spot for hackers. They can simply delete a debit or insert a fake deposit. To prevent this, we protect transactions not individually, but as a single chain.
In RK-CMS, all transactions aren't simply stored in a table; they're summarized and linked to each other.
What happens if a hacker tries to delete one of the transactions?
Let's say they delete Transaction #2 (a deposit) to reduce the user's balance or to cover their tracks.
The chain is immediately broken. The hash doesn't match, and the final checksum of the entire transaction ledger doesn't match the master.
Result: It's impossible to simply delete or insert a transaction into the middle of the history. The system immediately detects a hole in the archive and blocks access to the damaged section until the circumstances are clarified. You won't lose money because someone purged database records.
RK-CMS protects data not with a perimeter (a huge fence), but from the inside. We ensure that the data itself cannot be used for malicious purposes.
Switched a payment amount? The site will refuse to display it.
Deleted a transaction? The system will detect the gap and restore the history from a backup or block the attempt.
This ensures that the information on the site is always honest and complete, based on the database, and not the result of malicious activity.
