Risk Register (TikTok Inc. v. Garland)¶
Risk register for data collection, algorithmic control, divestiture, and speech-governance risks.
Purpose¶
This document converts TikTok Inc. v. Garland into a practical security, legal, and governance artifact. It is grounded in the Supreme Court's narrow First Amendment holding and the opinion's discussion of data collection, recommendation algorithms, source code, foreign-adversary control, and qualified divestiture.
Hallucinated writing examples¶
Scenario: (2025) (Security/legal lead) (executive, regulator, customer, or assessor audience) (Security Director maintains a risk register for leadership review.)
Subject: Risk Register for TikTok platform-control risk governance
Context: The Supreme Court affirmed the D.C. Circuit in a case involving a foreign-adversary controlled application statute, TikTok's U.S. user scale, sensitive data collection, recommendation algorithms, and ByteDance control. The opinion emphasized that the holding is narrow, but it treats data collection and platform control as concrete national-security issues when a foreign adversary can influence access, code, or operations.
Decision or ask: Approve a cross-functional workstream focused on tracking residual risks in platform-control governance. The work should be led jointly by Security, Product Engineering, Privacy, Legal, Government Affairs, GRC, and Communications so technical facts, legal positions, and external statements remain consistent.
Implementation: Register risks for sensitive data exposure, algorithm control, cross-border access, code provenance, divestiture readiness, policy-speech conflict, and evidence gaps. Phase one inventories sensitive data, user-scale exposure, privileged access, source-code custody, and recommendation-system dependencies. Phase two validates whether controls are technically enforceable through logging, segmentation, change approval, and independent evidence. Phase three converts the evidence into board reporting, customer explanations, and regulator-ready documentation.
Measurement: Track data-inventory coverage, percentage of privileged access reviewed, cross-border transfer exceptions, recommendation-system changes with complete approval records, source-code dependency findings, unresolved high-risk issues, and evidence accepted without rework during review.
Expected output: A risk register with owners, likelihood, impact, mitigation, and review cadence. Success means leadership can explain who controls the platform, what data is exposed, how algorithmic and code changes are governed, what residual foreign-control risks remain, and which evidence proves the controls are operating.