01 / DECISION
Define the operational decision
A file can keep the expected name while its contents change. Integrity evidence helps administrators detect a mismatch before a rate file reaches tills or downstream store systems.
Compare the released file with its approved source using version, size, date and cryptographic hash evidence.
02 / PROCEDURE
Run the control sequence
- 01
Assign a release identifier to the approved artifact.
- 02
Calculate and store a cryptographic hash outside the protected file.
- 03
Compare size, modified time and hash before publication.
- 04
Recheck the deployed export or import artifact where practical.
- 05
Escalate any mismatch instead of overwriting the evidence.
03 / EVIDENCE
Keep a usable release record
Record the master path, accountable owner, working-copy identifier, proposed change, reviewer, approval time, release version, cryptographic hash, backup location, restore result, temporary-access expiry and publication outcome. Keep this evidence outside the protected artifact so it remains available when the file cannot be opened.
Use a consistent release identifier across the approval, published artifact and recovery copy. Never place credentials, customer data or unnecessary commercial detail in the evidence record. Retain prior approved versions according to policy, and verify that the artifact accepted by the downstream POS matches the one that was reviewed.
04 / BOUNDARY
Keep adjacent controls separate
A matching hash proves file identity against the recorded reference; it does not prove prices are correct or authorized.
Test restrictions with representative roles and a nonproduction file before applying them to the only master. Preserve an independently restorable backup, keep price authorization separate from technical administration, and confirm that automated import services still have the access their documented task requires. After an update, compare the released version and hash, review the POS import result and close any temporary exception. Recheck the workflow after Windows, product, account, folder, storage or POS changes because earlier evidence may no longer describe the current environment.
05 / QUESTIONS
Common questions
Does a protected file prove its prices are approved?
No. Approval evidence, pricing logic and file restrictions solve different problems.
Can the protected master replace a backup?
No. Keep and test a separately controlled recovery copy.
Should administrators remove every restriction during an urgent update?
No. Diagnose the exact required action and grant the smallest approved, time-limited exception.
06 / SOURCES
Primary references
References support specific control concepts and do not imply endorsement.