Content Type
Research Analysis
Within the Content Type facet, Research Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
North America Institutional
Kaiser Permanente made tracking pixels a health-data accountability test
Kaiser Permanente is a risk and accountability case because a healthcare site or app can look like ordinary digital service infrastructure while quietly moving patient-context signals through advertising and analytics systems that were not built for clinical confidentiality.
North America Institutional
Quest Diagnostics made AMCA vendor exposure a medical-data accountability test
Quest Diagnostics is a risk and accountability case because a laboratory can outsource billing and collections work, but patients still experience the resulting data exposure as part of the medical-testing relationship that generated the data.
Global Cloud Services
Facebook made Cambridge Analytica a platform-data accountability test
FACEBOOK is a risk and accountability case because the Cambridge Analytica record showed how a social platform's developer permissions, friend-data access, app review, user notice, enforcement promises, and political-data controls could become civic infrastructure questions…
Global Cloud Services
MongoDB made support metadata boundaries a cloud-database accountability test
MongoDB, Inc. is a risk and accountability case because the accountability issue is that customer metadata can drive targeted abuse even when production database content is not exposed, so the provider has to prove the boundary between account context and data-plane compromise.…
Global Cloud Services
JetBrains made TeamCity rebuild evidence a CI/CD accountability test
JetBrains, s. r. o. is a risk and accountability case because the accountability issue is that a build server is not an ordinary web app; once CI/CD control is in doubt, the evidence must cover secrets, artifacts, plugins, runners, and rebuild trust. The public record matters for…
Global Cloud Services
VMware made ESXi patch debt a hypervisor-continuity accountability test
Vmware International Unlimited Company is a risk and accountability case because the accountability issue is that a hypervisor concentrates many services behind one maintenance decision, so patch debt and recovery proof have to be measured as business-continuity controls. The…
Global Cloud Services
ServiceNow made hosted patch transparency a workflow-data accountability test
ServiceNow, Inc. is a risk and accountability case because the accountability issue is that workflow platforms hold operational records for many teams, so patch transparency has to explain which instances were protected, which customers still had duties, and what data paths…
Global Cloud Services
Discord made support-vendor ID handling a trust-and-safety accountability test
Discord Inc. is a risk and accountability case because the accountability issue is that trust-and-safety support often requires sensitive attachments, so vendor access has to be governed as identity stewardship rather than routine customer service. The public record matters for…
Global Cloud Services
Sophos made firewall hotfix telemetry an appliance-trust accountability test
Sophos Technology GmbH is a risk and accountability case because the accountability issue is that a security appliance is trusted to defend other systems, so emergency hotfixing must be paired with evidence about compromise state, credentials, and customer-visible telemetry. The…
Global Cloud Services
SonicWall made SMA credential rotation a remote-access accountability test
SonicWALL, Inc. is a risk and accountability case because the accountability issue is that remote-access appliances sit at the edge of customer networks, so remediation has to include credential rotation and session evidence rather than only software version state. The public…
Global Cloud Services
Juniper made J-Web exposure isolation a firewall-management accountability test
Juniper Networks, Inc. is a risk and accountability case because the accountability issue is that management interfaces are not merely admin conveniences; when exposed, they become control points over infrastructure devices that many downstream services depend on. The public…
Global Institutional
Samsung made device-account notice scope a customer-data accountability test
Samsung is a risk and accountability case because the accountability issue is that device ecosystems combine accounts, support, commerce, and product relationships, so notice scope has to explain which data fields and user groups were actually involved. The public record matters…
Global National Telecom
Deutsche Telekom made CPE firmware recovery a national broadband accountability test
Deutsche Telekom AG is a risk and accountability case because the accountability issue is that consumer routers are part of national telecom continuity, so firmware recovery has to prove more than a central network fix; it has to reach the customer equipment that keeps households…
Global Cloud Services
SolarWinds made detection delay the missing edge of supply-chain accountability
The SolarWinds record is usually remembered as a signed-update compromise, but its harder accountability lesson is temporal: a trusted software factory was altered, customers were exposed, the public learned of the risk only after a third-party victim found it, and later repair…
Global National Telecom
Rogers made carrier control-plane fragility a public-service accountability problem
Rogers' July 2022 outage began inside a carrier routing change, but its accountability record belongs to everyone who discovered that phone calls, debit payments, emergency access, municipal operations, transport coordination, wholesale service, and small-business continuity…
Global National Telecom
Telstra made emergency-call fallback a third-party trust boundary
Telstra's July 2026 mobile outage showed that a carrier can declare broad restoration while emergency callers, welfare-check teams, transport operators, merchants, carers, and regulators still need a harder form of proof: that the public-service chain depending on the network has…
Global Cloud Services
Google Cloud's Belgium disk loss showed where locality stops being resilience
The 2015 Google Compute Engine Persistent Disk loss in Belgium was tiny by percentage and large by lesson: choosing a local cloud zone can satisfy latency or residency aims while still leaving the customer without an independent, recoverable copy when the physical failure domain…
Global Cloud Services
AWS made US-East-1 notice quality a cloud-dependency accountability record
AWS customers can choose regions, zones, data planes, recovery patterns, and even other providers, but a major US-East-1 control-plane event still forces one immediate question: can the provider tell customers, precisely and in time, whether their continuity plan is failing or…
Global Cloud Services
GitHub made host-key rotation a contract-versus-control accountability test
GitHub's March 2023 RSA SSH host-key replacement was a small cryptographic event with a large governance signal. The company could describe the service as provided under narrow contractual warranties, but developers and businesses still had to treat GitHub's host identity as a…
Global Institutional
23andMe made relatives a common-mode privacy dependency
The 23andMe credential-stuffing incident was not only an account-takeover case. It was a demonstration that a relationship feature can make one compromised account a common-mode exposure path for many people who did not reuse that account's password, did not approve the hostile…