Listen on Spotify

Why does this link say Anyone with the link?

Cold open

The file was shared for convenience. "Just send them the link." Ten minutes later, someone notices the permission setting and freezes in a posture last seen in people reading legal disclaimers after the mistake, not before it.

The document was not leaked to the public internet in a cinematic way. It was simply made available through the most common security phrase in modern office work: "It should be fine."

HR-Z0 case note: convenience links age into security debt.

The horror

Open sharing defaults create a soft, persistent risk:

Symptoms

The symptoms are always recognizable:

  • sensitive files are shared more broadly than intended
  • vendors and guests keep access longer than expected
  • teams lose track of who can open what
  • data distribution exceeds actual business need
  • security reviews become archaeology instead of policy

The danger is not always an immediate incident. Often it is the slow buildup of exposure surface no one is actively managing.

Cost

The cost is not abstract.

  • Time: senior staff lose days to access cleanup, lockouts, and incident retros that should have been prevented by baseline controls.
  • Money: emergency response, audit remediation, and avoidable downtime are the most expensive way to run security.
  • Trust: once access looks random, leadership assumes every control is optional, including the important ones.

The root cause

The lockout or over-permission event is the symptom. Exception culture is the disease.

1

Sharing defaults favor speed over control

If "anyone with the link" is easy and common, people will use it. Repeatedly. Especially under deadline pressure.

2

Access review is weak or absent

Businesses tend to review large incidents, not routine oversharing. Unfortunately, routine oversharing is how access sprawl becomes normal.

3

Collaboration rules are unclear

When teams do not know when to use direct access, domain-only sharing, guest access, or public links, the path of least resistance wins.

4

Exceptions became policy through operational inertia

When teams do not know when to use direct access, domain-only sharing, guest access, or public links, the path of least resistance wins.

The fix

The fix is not a security memo. The fix is enforced baseline behavior that survives turnover.

1

NorthStar identifies where sharing risk lives

NorthStar maps the practical patterns of document sharing, guest collaboration, and external access across the business.

2

Oort establishes safer defaults

Oort improves security hygiene with:

  • safer sharing defaults
  • clearer rules for external access
  • periodic access reviews
  • baseline identity controls such as MFA

Where collaboration structure contributes to the mess, Orion helps clean up the workspace model and ownership patterns that drive chaotic sharing behavior.

3

Oort turns baseline controls into continuous operations

We automate access reviews, exception expiry, backup/restore verification, and sharing enforcement so security does not depend on heroic memory.

If "anyone with the link" feels normal, the risk has already become cultural.

HR-Z0
HR-Z0
Comms Officer

Comms Officer HR-Z0 (a.k.a. “H.R. Zero”) is Galaxie’s deadpan broadcast voice for the Office Horror Stories series — part dispatcher, part incident historian, part morale damage control.
Built from equal parts helpdesk transcripts, post-mortems, and calendar trauma, HR-Z0 doesn’t “tell stories.” It files reports from the front lines of messy operations — where ownership evaporates, folders time-travel, and a “quick change” becomes a six-month saga.

Give us a call

Available from 9am to 8pm, Monday to Friday.

Send us a message

Send your message any time you want.

Our usual reply time: 1 Business day