Folder Lock for Provenance Records

Match the product to one bounded job

Folder Lock may fit a selected encrypted archive workflow after current-version testing. It is not a collections-management platform, recipient-authorization service, guaranteed backup or guaranteed password-recovery mechanism.

Test the complete workflow

1. 01Obtain the current installer, documentation, license and supported Windows requirements from official sources.
2. 02Create a fictional provenance record export and a separate fictional access credential.
3. 03Test archive creation, import, lock, reopen and file-manifest comparison.
4. 04Inspect temporary folders, recent-file lists and source locations for plaintext residue.
5. 05Restore a separately stored copy and document password-loss consequences.

Inspect each step in context

Keep provenance controls separate

The product does not establish donor or seller consent, title validation, ownership and cultural-property duties, collections-system roles, recipient authorization, provenance-record accuracy, provider permissions, guaranteed backup, password recovery or enterprise identity management. It cannot automatically remove plaintext copies created before or after decryption. Treat the provenance record, the recipient system account, the recipient acknowledgement and the recovery material as separate record classes. Confirm who is permitted to retain each one, whether the recipient is authorized, and whether provider or engagement rules restrict local copies. A successful locker test does not confirm that a recipient accepted the extract or that the correct manager released it. Keep the authorized recipient acknowledgement outside the encrypted provenance archive so it can be consulted during an access problem. Before the acquisition review begins, document a fallback path that does not require sharing a recipient account password or opening confidential material. After the acquisition review, review temporary folders, email downloads, browser downloads and sync locations under the authority of the relevant owner. Never promise secure deletion, anonymity or guaranteed recovery on the basis of a product screen alone. Document the current tested release, operating environment and recovery result before adoption. Run the pilot with fabricated accession and ownership records, then obtain written approval from the registrar, information-security owner and records authority before introducing live provenance material. Recheck the workflow after product updates, operating-system changes or storage migrations, because a previously successful test is not permanent evidence of compatibility. Maintain a separate verified recovery copy and a current decision record.

Primary references

• NewSoftwares: Folder Lock features
• NewSoftwares: Folder Lock
• NIST SP 800-111: Storage Encryption

Supplied visuals may depict legacy releases. References support specific boundaries and do not imply endorsement.