Signify Insights
DiscoverSignify PlaygroundSignify FieldworkSignify LabsSignify KidsSpotlightsAboutSignify SolutionSignify HiveSignify Impact
Signify Playground
A publishing & interactive-learning property · Philadelphia · est. 2019
Signify PlaygroundDrillCyber · Cloud & SaaS exposure7 minLevel 3
DrillCloud & SaaS · Cyber

Who Can See This

Twelve configurations, and one question each: who can actually reach it? The trap is the label — “only people with the link” and “AuthenticatedUsers” both mean something much wider than they read.

~7 min · Scored · Per-item recap · No sign-up

1. An object-store bucket with account-level public access blocking turned off, and a bucket policy granting read on objects to Principal "*".

2. A document shared with "anyone with the link can view". Not indexed. The link is in an email thread that has since been forwarded to a supplier.

3. An internal wiki space with permissions set to "all logged-in users", holding the production runbook and the location of its credentials.

4. A managed database with a private endpoint, no public address, a security group permitting only the application subnet, and identity-based authentication.

5. A container ACL granting access to "AuthenticatedUsers", which in this provider means any authenticated account in the PROVIDER, not any account in your tenant.

6. A dashboard published through a feature the tool labels "publish to web — only people with the link can view".

7. A document shared with three named accounts, link sharing disabled, and an access expiry set.

8. A collaboration channel set so that anyone in the organisation can join, carrying the notes from an active incident bridge.

9. A Kubernetes service of type LoadBalancer exposing the cluster admin dashboard, with no ingress restriction and unchanged default credentials.

10. A default sharing setting of "everyone in the company", applied automatically to a newly created folder now holding HR case files.

11. A calendar shared through a secret address the provider describes as private, pasted into a support ticket eighteen months ago.

12. A bucket with public access blocked at the account level, a policy granting a single named role, and access logging enabled.

0%

Provider wording differs and changes; the examples are written to be recognisable across the major platforms rather than exact for any one. Educational — verify against your own provider's current documentation, because the meaning of a principal name is the thing most likely to have moved.