Skip to content
Aurora

The Sharing Playbook

What evidence should you check before sharing confidential files?

Check provider evidence before sharing confidential files. Record requirements, sample results and unanswered questions with a free approval worksheet.

Access And Responsibility · Aurora Datarooms

Archive Date Published
A professional checks paperwork beside his laptop in a home office with a sofa and window.

Get The Free Worksheet

Before you put confidential files into a new sharing service, write down what the review needs, find evidence for each need and name the person who can say yes. Read what the provider commits to, then test the setup yourself with harmless sample files. If a requirement has no answer yet, leave it open until someone with the authority to close it does.

The moment this matters is usually a client email: "Can we put these documents here?" A feature list won't answer that. A short record will: one that shows why you said yes, what conditions came with it and what you are still waiting to hear.

Start with the job you need to approve

Describe the use in one sentence. For example: a small engineering practice wants two outside advisors to review project documents for four weeks. One advisor needs the commercial pack. The other needs the technical pack. The practice's negotiation notes stay internal.

Then note anything that could change which service you choose:

  • What happens if someone sees the wrong file, a file goes missing or the service is down for a day?
  • Does a client agreement call for a specific certification, storage location or approved supplier?
  • Who looks after access, including when that person is on holiday?
  • What does the firm need to keep once the review ends?

Your answers decide how deep the check goes. The UK's National Cyber Security Center recommends its full cloud security principles for sensitive work, including commercially sensitive information, and keeps its lighter approach for simpler cases. Very sensitive work may also need a security or privacy specialist. NCSC guidance on choosing a cloud provider.

Turn each requirement into a question with evidence

Keep a short evidence register. Each line needs four things: the requirement, where the answer came from, what the answer doesn't cover and who decides. Write down the exact plan and settings you are assessing. A feature on a provider's top plan may not exist on the plan you're about to buy.

What you're decidingQuestion to askEvidence to keep
Who gets inHow does the service confirm the invited person, and what happens if an invitation is forwarded?Current invitation guidance and the result of your own sample test
Where access stopsWho can change access, and which of your own administrators can read the source files?Role descriptions, the settings you chose and which sample files opened or were refused
How the provider handles dataWho runs the service, where is information handled, and what can their support staff or suppliers see?A dated reply from the provider and the terms or processing information that apply
Certifications you needDoes the report or certificate cover this service, this setup and this period?The scope and date of the report, plus any gaps
Recovery and leavingWhat can be recovered or exported, and what happens to stored copies after you close the account?The written procedure, its limits and timing, and a sample export if you can run one
Looking into problemsWhich actions are recorded, for how long, and how do you report a suspected incident?An example activity record, the retention period and the support route

Note the exact page or reply you relied on and the date you checked it. If a provider just says "yes", ask what the yes covers. Keep this register in your internal records.

For certificates and audit reports, check what was assessed and when. NCSC advises checking that the evidence is recent and covers the way you will actually use the service. Ask about the application and the hosting company underneath it separately. NCSC guidance on independent validation.

Label what kind of evidence you have

Evidence comes in different strengths. A provider statement tells you what the provider says it does. A contract tells you what it has agreed to do. Your own test tells you what happened in one setup on one day. An independent audit adds a fourth view, with its own scope and date.

Put those labels in the register. "The provider says deleted files are removed within a set period" and "the sample file no longer appears on screen" answer different questions. The second one tells you nothing about storage or backups.

Invitations need the same care. Microsoft describes several kinds of sharing link, including links that work for anyone who has them and links that only work for named people. Those options are specific to Microsoft, but they show why you should ask any service exactly what it means by "link". Microsoft's sharing and permissions guidance.

Test access with sample files

Make one harmless sample file for each audience and one internal-only sample. Use test accounts you control, set up with the roles real participants would have. Don't upload real confidential files just to see whether the setup works.

  1. Open the expected file as each invited recipient.
  2. Check that the same recipient can't find or open the other audience's sample or the internal sample, including through a saved direct link.
  3. Check viewing and downloading separately against the settings you agreed.
  4. Try the invitation from a different email address you control. Write down what actually happened and whether it matches the provider's description.
  5. Remove the test recipient's access and try again. Note any delay, any session that stays open and any copy that remains available.

For each step, record who you were signed in as, what you did, when and what happened. If something doesn't match, fix the setup and test again. Stay inside your own accounts and samples. The test is about your setup, so leave other customers and the provider's infrastructure alone.

A passing test covers only the steps you ran. It can't prove the whole service is secure, show how backups are handled or confirm that a client's requirements are met. A file someone has downloaded can stay on their device after their online access ends. The download-permissions guide helps you decide what recipients should be able to keep.

Write down what the decision allows

Here is how the engineering practice's approval record might look. The rows show possible outcomes to illustrate the reasoning. No real service was tested to produce them.

RequirementWhere it standsNext step
Each advisor sees only their agreed filesThe sample test behaved as expectedRecord the tested setup and who maintains it
One client requires a specific audit reportThe report hasn't been suppliedHold that client's files until the requirement is settled
A final record of the review must be keptThe export steps are written down, but no sample export has been runName someone to test it before approving that part

Keep the outcomes plain: ready for this use, waiting on evidence, or needs a different setup. Note who decided, what the decision covers and what would trigger another look. Avoid an overall score. A score lets several nice features hide one requirement you can't meet.

For activity records, find out which actions are recorded, who can see the records and how long they are kept. NCSC treats audit coverage and retention as questions to answer in any cloud assessment. NCSC audit information guidance.

Try the same test in Aurora

In Aurora, your files live once in a library. Each room shows one audience only the files you pick for it. Access groups and individual permissions narrow things further inside a room. Invitations are tied to the invited email address. Organization owners and administrators can see the whole library, so include them when you decide who has access.

A good first trial is the test above. Create one library with harmless commercial, technical and internal samples. Set up two rooms with different selections and check each one with recipients you control. The 30-day trial includes one organization, unlimited libraries, two rooms, three internal users and 25 external users, with no card required. Try a sample sharing setup.

Aurora does not currently have a SOC 2 report or ISO 27001 certification. If your review needs one, keep that requirement open and use an approved service for those files. A passing sample test is evidence about the setup you tested, and only that setup.

Use the free evidence worksheet below to name your next open question and the person who will answer it. Once the service is approved, the disclosure checklist helps you decide what each audience should receive.

Confidential sharing evidence register

Free to use and adapt. Keep your completed worksheet in your own project files.

Download Worksheet (.md)

Use this free worksheet for one decision: one sharing service, one use. Keep completed copies internal. It is a working record. It is not a security audit, and it is not an approval from Aurora.

Describe the use

FieldYour record
Review or project
Provider, service and plan
Who will see the files, and for how long
Files you plan to share
Files that must stay internal
What happens if files leak, go missing or the service is down
Client or company requirements you must meet
Person who can approve this use
Person who maintains the setup, and their backup

Keep one row per requirement

Copy this row for each requirement. Add where the evidence came from and the date. Label the evidence as provider statement, contract, your own test or independent audit. Note what it covers and what it doesn't.

Requirement and scopeEvidence type, source and dateStill unansweredWho decides, and next step
Example: an invited advisor can open only the agreed sample filesOwn test; test record dated [date]; plan and role tested [details]The wider service is checked separately[Name] checks the final selection before real invitations go out

Think about who gets in, access settings, what your administrators and the provider's support staff can see, suppliers, certifications you need, where data is stored, recovery, export, closing the account, copies people keep and incident support. Mark the requirements you can't do without. A missing one stays visible in the final decision.

Record a sample test

Use harmless files and accounts you control. Write down what actually happened, including anything that didn't match. Never put passwords, tokens or live invitation links in this worksheet.

CheckExpected resultWhat happened, and whenFix and retest
Invited recipient opens their agreed sampleOpens
Recipient tries the other audience's sample by browsing and by saved linkRefused
Recipient tries the internal-only sampleRefused
Recipient views or downloadsMatches the agreed settings
A different email address you control uses the invitationMatches the provider's description
Removed recipient tries to get back inMatches the provider's description

Note the account roles, plan and settings you tested. A sample test only shows what happened in that setup. How the wider service runs, how storage is handled and any audit questions need their own evidence. Files someone already downloaded can stay on their device.

Make the decision, and know when to revisit it

FieldYour record
DecisionReady for this use / Waiting on evidence / Needs a different setup
Files and audiences approved
Conditions and required settings
Open requirements and next steps
Who decided, and when
Next review date or trigger

Look at the record again when the files become more sensitive, the audience or administrators change, the provider's terms or evidence change, or a test fails. If a requirement needs a specialist, it stays with that specialist. One completed worksheet does not approve every future project.

Keep going

The guide to checking evidence before sharing confidential files has the worked example and the sources. For copies recipients keep after downloading, use the download-permissions guide.

Sources