Standard access review checks who holds permissions inside the system. Public link control checks whether the data itself has become externally reachable through a shareable URL. Both matter, but public link control is broader because it covers access paths that do not rely on an active internal session.
How Public Link Control Differs from Access Review
Public link control is about whether a file, folder, or record has an externally reachable sharing path, while access review is about whether named users still need the permissions they already have. That distinction matters because a public link can create exposure even when the internal permission list looks clean, so the two checks answer different questions.
In practice, access review is a governance control over entitlements. It asks who has access, whether that access is still justified, and whether it should be reduced or removed. Public link control is a sharing control. It asks whether the object can be opened by anyone who obtains the URL, whether that link is intended, and whether the link should expire, be revoked, or be made less discoverable.
The two controls also operate at different layers of the access problem. A user can pass access review and still leave sensitive content exposed through a public share link, especially if the link was created outside the usual entitlement workflow. That is why teams treat link-based exposure as a separate control path, not just another item inside periodic certification.
What Each Control Actually Verifies
Access review is strongest when the goal is entitlement hygiene: role drift, stale permissions, excessive access, and approvals that need recertification. It is usually tied to identity records, ownership, and business justification. The question it answers is whether the right people still hold the right access inside the system.
Public link control verifies a different condition: whether the object can be reached without being in the normal permission set. If a link is public, broadly shared, or capable of being forwarded beyond the intended audience, the exposure can exist even if no user appears over-privileged in the review queue. That makes link governance a data exposure control as much as an access control.
For that reason, organisations often need both. Access Reviews and Certification Guide is useful when you are deciding who should keep access, while link governance is the better lens when you need to confirm whether the content itself has become shareable outside the intended boundary.
Where access reviews focus on entitlement state, public link control focuses on reachability state. That includes anonymous access, overly broad sharing settings, inherited links, long-lived links, and links created by users who do not realise the platform has turned a private object into a publicly discoverable one.
Why Link Exposure Can Slip Past Review Programs
Review programs are often built around identities, roles, and approvals, so they can miss content that is reachable through a mechanism outside the entitlement list. A reviewer may confirm that no external user has direct access, yet a shareable URL still allows access. In that case, the data exposure exists independently of the permission record.
This is why link control needs separate operational ownership. One team may run periodic certification, but another may need to monitor public sharing settings, tokenised links, external collaboration defaults, and link expiry. If those controls are not connected, the organisation can certify the wrong thing and keep the real exposure in place.
The broader governance problem is that access review is retrospective and public link control is often preventative and continuous. Review tells you what should have been removed; link control tells you what can still be reached now. Both are useful, but they catch different failure modes.
Practitioners should also recognise that public links can break the usual assumption that access is mediated by identity. Once a URL is sufficient for access, the control objective shifts from “who is authorised” to “how widely can the object be reached and rediscovered.” That is a materially different threat model.
Risk and Threat Considerations
Public links create exposure even when internal entitlements look well managed, because forwarding, indexing, logging leaks, or misconfiguration can make the resource reachable outside the intended audience. Access review reduces entitlement drift, but it does not reliably detect a data object that has become externally reachable through a shareable URL.
Failure mechanism: The organisation certifies user permissions while a public or broadly shared link remains active, so the object stays accessible through an alternate path that bypasses the reviewed entitlement set.
Impact: Sensitive data can be disclosed, copied, or forwarded without a corresponding permission grant in the system of record, which makes detection, containment, and accountability harder.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Access review and entitlement recertification are core account governance concerns. |
| AC-3 — Access Enforcement | Public link control depends on enforcing who can reach data and through which paths. | |
| Recommendation — Review account and entitlement assignments regularly and remove unnecessary access. Enforce access decisions so only approved paths can reach the data. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The question contrasts two access control mechanisms for data reachability and entitlement governance. |
| Recommendation — Define and apply access control rules for both user permissions and shared links. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | The topic is about managing access paths, review cadence, and revocation of overbroad access. |
| Recommendation — Centralize access control and ensure link-sharing revocation is covered in governance. | ||
| OWASP ASVS | V8 — Authorization | The distinction turns on whether access is controlled by identity permissions or by an externalised share path. |
| Recommendation — Verify that authorization checks cover both direct access and alternate sharing paths. | ||
Practitioner Guidance
What to verify: Confirm whether your control evidence covers both identity-based access and link-based reachability. A clean access review report is not enough if the platform allows anonymous, external, or time-unbounded links.
Implementation sequence: First inventory public sharing modes and link expiry behaviour, then define who can create externally reachable links, and only then fold those checks into the recurring access review process. That sequence prevents teams from treating link exposure as a downstream exception.
Practitioner takeaway: Treat access review as a permission hygiene control and public link control as an exposure control, because the strongest programmes measure both who may enter and whether the data can still escape through another path.
Related resources from NHI Mgmt Group
- How should security teams reduce user access review fatigue without weakening control?
- What should IAM teams review when SAML attributes drive access control?
- Why does the minimum necessary standard matter for access control teams?
- What is the difference between access review and real compliance control?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org