{"id":156,"date":"2023-02-24T18:09:03","date_gmt":"2023-02-25T00:09:03","guid":{"rendered":"https:\/\/kentprotect.com\/?p=156"},"modified":"2023-03-06T09:55:52","modified_gmt":"2023-03-06T15:55:52","slug":"897-stanford-ph-d-applications-breached","status":"publish","type":"post","link":"https:\/\/kentprotect.com\/index.php\/2023\/02\/24\/897-stanford-ph-d-applications-breached\/","title":{"rendered":"897 Stanford Ph.D. applications breached in 2022-2023"},"content":{"rendered":"
<\/div>\n

(Image source: Stanford University, 2021)<\/p>\n\n\n\n

One-sentence summary: <\/strong><\/p>\n\n\n\n

897 Stanford Ph.D. economic applications were breached for over a month in a December 2022-January 2023 misconfiguration incident. <\/p>\n\n\n\n

Who was involved?<\/strong><\/p>\n\n\n\n

897 Stanford Economics Ph.D. applications, Stanford University, and individual\/s with “two downloads” of the breached data (Stanford University, 2023a, para. 5). <\/p>\n\n\n\n

What was the timeline?<\/strong><\/p>\n\n\n\n

December 5, 2022: Misconfiguration started. Economics Ph.D. applicants’ sensitive application data are publicly available. <\/p>\n\n\n\n

January 24, 2023: Stanford learns of the misconfiguration and immediately remediates it. <\/p>\n\n\n\n

February 17, 2023: Stanford makes a public press release of the incident and begins notifying affected applicants. <\/p>\n\n\n\n

What occurred?<\/strong><\/p>\n\n\n\n

An unknown actor within Stanford modified Stanford’s Ph.D. in economics application folder allowing public read access and exposing the data of over 897 applicants (Stanford University, 2023a, para. 7). The incident took over a month to be identified and resolved (Stanford University, 2023a, paras. 4-5). <\/p>\n\n\n\n

Estimated costs:<\/strong><\/p>\n\n\n\n

Notification costs and IDX M-F phone support (Stanford, 2023b, para. 3). <\/p>\n\n\n\n

IDX “24 months of credit and CyberScan monitoring, a $1,000,000 insurance
reimbursement policy, and fully managed id theft recovery services” (Stanford, 2023b, para. 5). <\/p>\n\n\n\n

Involved laws: <\/strong><\/p>\n\n\n\n

Federal: FERPA.<\/p>\n\n\n\n

State: California: CCPA and Cal. Civ. Code \u00a7 1798.29(a); Massachusetts: 201 CMR 17.00 and M.G.L.A. 93H \u00a7 1. <\/p>\n\n\n\n

Root cause: <\/strong><\/p>\n\n\n\n

“misconfiguration of the folder’s settings” (Stanford, 2023b, para. 2). <\/p>\n\n\n\n

Lessons learned: <\/strong><\/p>\n\n\n\n

Doer\/checker policy. Restricting public read access modification rights to delegated individuals. Continuous vulnerability scanning and assessment. SIEM\/IT alerting for new public read access folders\/files. Automatic rollback configurations (e.g., Lambda & Cloudwatch Event Rule). <\/p>\n\n\n\n

Commentary<\/strong>: <\/p>\n\n\n\n

I applaud Stanford for being transparent about the incident and its root cause. However, this is not their first misconfiguration-related breach of applicant’s data: https:\/\/stanforddaily.com\/2019\/02\/14\/data-breach-allowed-students-to-view-other-students-admission-files-sensitive-personal-data\/. Stanford or Stanford-related entities are also tagged in at least six other data breach incidents: https:\/\/oag.ca.gov\/privacy\/databreach\/list. These will be covered in other breach reports. <\/p>\n\n\n\n

<\/p>\n\n\n\n

Sources: <\/strong><\/p>\n\n\n\n

Stanford University. (2021, April). stanford-university-logo.png<\/em>. logodownload.org. https:\/\/logodownload.org\/wp-content\/uploads\/2021\/04\/stanford-university-logo.png<\/p>\n\n\n\n

Stanford University. (2023a, February 17). Data Security FAQs<\/em>. Stanford Humanities and Sciences. Retrieved February 24, 2023, from https:\/\/humsci.stanford.edu\/data-security-faqs-021723<\/p>\n\n\n\n

Stanford University. (2023b). INFORMATION ABOUT A DATA INCIDENT\/NOTICE OF DATA BREACH. In mass.gov<\/em>. Office of Consumer Affairs and Business Regulation. Retrieved February 24, 2023, from https:\/\/www.mass.gov\/doc\/assigned-data-breach-number-29059-stanford-university\/download<\/p>\n\n\n\n

\n