Case 06 · External collaboration and security
Blocking the risky tool would have been easy. Solving the real problem was harder.
Engineers needed to send large files to customers, suppliers and project partners. Blocking the consumer tool would not remove that business need.
OutcomeThe restriction became sustainable because a practical, governed route already existed.
Dramatised with a synthetic consultant. Based on anonymised Blue Hybrid delivery records. No client, customer or employee is depicted.
Evidence ledger
What the record supports.
Every figure is labelled by what it represents.
Structural
Approved firsta usable route existed before restriction
A structural control outcome, not a numeric claim.
Qualitative
Visibleownership and external access
The design made sharing relationships and activity easier to govern.
Qualitative
Repeatableexternal collaboration model
A qualitative operating outcome with no invented saving.
The visible risk
Consumer file-transfer services were quick, which is why people used them.
They were also difficult for the business to govern: ownership was unclear, auditability was limited, retention was inconsistent and external access became hard to see once a file left.
The real problem
Blocking the tool would not remove the need.
Engineers would still have large files to send. Without an approved route, the behaviour would move somewhere less visible. The control had to solve the work as well as the risk.
The design
We built the approved route before enforcing the restriction.
Blue Hybrid designed a controlled external file-transfer service using Microsoft 365. It sat inside a wider collaboration model using SharePoint, Entra B2B, Conditional Access, Defender and documented risk decisions.
- Where files were stored
- How external users authenticated
- Who owned the sharing relationship
- What was logged
- How long access remained available
- How exceptions were handled
The business decision
A false choice became a practical question.
Leadership no longer had to choose between unmanaged file sharing and stopping engineers from delivering work. It could decide whether the controlled route was sufficient and which exceptions were genuinely necessary.
The strongest security control was the one that made the unsafe behaviour unnecessary.
The qualitative impact
The restriction became sustainable.
- Less dependence on anonymous transfer services
- Clearer ownership of shared files
- Better visibility of external access
- A repeatable sharing model
- Fewer one-off technical exceptions
- Lower risk of sensitive engineering data leaving through unmanaged channels
Film transcript
Read the documentary narration.
Make the unsafe behaviour unnecessary
Blue Hybrid case study narration: Blocking consumer transfer tools would have removed the shortcut, not the need. We built the approved Microsoft 365 route first, making unsafe behaviour unnecessary.
Dramatised with a synthetic consultant. Based on anonymised Blue Hybrid delivery records. No client, customer or employee is depicted.
Your situation will be different
Bring us the visible request. We will investigate the decision underneath it.
What happens next
- Share the problem, timing and intended outcome
- We review mutual fit and delivery capacity
- If aligned, we invite the next conversation