Legal Services Offshore blog
Build a trade secret vault access log that records each authorized viewer
An access log that ties each viewer, approval, vault location, and review date to a source while counsel keeps the confidentiality analysis.

Key takeaways
A trade secret vault holds material that derives value from being kept confidential, so every access should have a documented purpose and an approver. The log records the vault, the material, the viewer, the approval, the access time, and the review date. It also records the source of the approval. A shared login is not an access record.
Access is not a single permission but a series of events. A person may be approved for a folder, open one file, download it, and later lose the approval. The log should capture the grant, the access, and the revocation separately. A list of current users cannot show who viewed what.
The vault record and the legal confidentiality analysis are separate. The log records who was allowed in and what happened, while counsel decides whether the information is protected and whether a disclosure was permitted. An access event is not a legal conclusion. A log entry should not carry a conclusion that the material is or is not a trade secret.
Counsel decides the protection strategy, the disclosure rules, and any response to a suspected loss. The support lane maintains the access log, the approval trail, and the review schedule. That division keeps a security log from becoming a privilege opinion. Every exception should name the lawyer who will resolve it.
Identify the vault and the protected material
Record the vault name, the system or repository, the owner, and the access model. Note whether access is granted by group, by individual, or by link. A public link bypasses the approval trail and should be recorded as an exception. The reviewer should be able to find the vault from the log.
Record each protected item or collection by a stable identifier, such as a document name, a folder, or a data set. Note the date the item was placed in the vault and the person who placed it. A file that was never registered in the log is outside the control. The inventory should match the vault contents.
Record the confidentiality basis by reference to the agreement, the court order, or the internal policy. Do not summarize the legal reasoning in the access row. Note the source and the date. The lawyer decides how the basis applies to a specific viewer.
Record the retention and destruction rule for each item, if one applies. Note the rule source and the next review date. A vault item that should have been destroyed is a risk the log should show. The lawyer confirms the retention decision.
Record each access grant and its basis
Create one row for each approved viewer and record the name, the role, the matter, and the approval date. Note the approver and the scope of the grant. A grant to a whole team is broader than a grant to one person. The log should show the exact scope.
Record the business reason for the access, such as reviewing a claim, preparing a filing, or responding to a diligence request. A reason such as needs access is not enough to audit. Note the source of the request and the person who confirmed it. The reviewer should understand why the viewer needed the material.
Record any confidentiality agreement, ethical wall, or client consent that supports the grant. Note the date and the source document. A grant without the required consent may be improper even if the person is trusted. The lawyer decides whether the consent is sufficient.
Record the expiration date or the review date for each grant. A grant without an end date tends to become permanent. Note the person who will review it and the action required. The log should show when the access must be reconsidered.
Track each access event and review
Record each access event with the viewer, the item, the time, and the action taken, such as view, download, print, or share. Use the system log where available and do not rely on self-reporting. A download is a higher-risk event than a view. The log should preserve the system timestamp.
Record any access that falls outside the approved scope and route it to the approver. Note the date it was detected and the person who reviewed it. Do not delete the event because it was accidental. The record should show the exception and the response.
Record the periodic review of access grants and the reviewer who performed it. Note the grants that were continued, narrowed, or removed. A review that only confirms the current list cannot show whether access is still needed. The log should show the decision for each grant.
Record any revocation and the date it took effect. Confirm that the system access actually ended rather than only that a request was sent. Note the person who verified the change. A revocation that exists only in an email is not a control.
Separate access records from confidentiality advice
Keep viewer names, approvals, timestamps, and system events in the log. Keep the analysis of trade secret status, reasonable measures, and misappropriation in counsel work product. A support note should not state that the material is protected. That question belongs to the lawyer advising the client.
Record a client instruction about access or disclosure, but do not draft the legal basis for it. Note the instruction date and the lawyer who approved it. Keep the communication with the matter record. The log should show who decided and when.
Record any suspected unauthorized access by reference to the incident record, not by conclusion. Note the source and the question for counsel. A suspicion is not a finding, and the log should label it carefully. The lawyer decides what response is required.
Record privileged or confidential investigation material by reference and keep it out of the general access folder. Note the access list and the approval date. An access log is not a safe place for a legal opinion. The entry should point to the protected file.
Handle a revocation or an unexpected access
When access is revoked, record the reason in neutral terms, the effective date, and the person who approved the change. Confirm that every system and shared link was updated. Note the verification date. A revocation that leaves a copy or a link open is incomplete.
When an unexpected access appears, record the event, the viewer, the item, and the time. Preserve the system evidence before any cleanup. Route the event to counsel and the security owner the same day. Do not confront the viewer without an approved plan.
When a viewer changes role, record the new role, the date, and the access that should change with it. A promotion or a transfer can leave old access in place. Note the review and the person who completed it. The log should show the access decision after the change.
When a link is shared outside the approved group, record the link, the recipient, the date, and the action taken. Note whether the link was disabled and when. A link that cannot be traced is a control gap. The lawyer decides what notice or remedy is required.
Review the log before a disclosure event
Run a review before a production, a diligence request, or a hearing and confirm that every viewer is still approved. Check the grants against the current matter team. Record the reviewer and the date. A late review leaves no time to remove stale access.
Confirm that every access exception has a named owner and a resolution date. An exception without an owner tends to be rediscovered after a loss. Record the assignment and the follow-up. The log is complete only when every exception has a path.
Sample a few access events and trace each one to the system record and the approval. A missing approval or a wrong timestamp is easy to catch before a disclosure. Record the sample result and any correction. The sample is a control check, not a performance score.
Record the review result and the next review date in the log. Keep the reviewed version with the matter record so the next disclosure starts from the same source. A recurring review prevents access from drifting. The next request should need fewer corrections.
A supervised support lane can keep the access grants, the system events, and the review schedule current while the lawyer decides what protection the information requires. Explore case file management support.