<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.0 20120330//EN" "http://jats.nlm.nih.gov/publishing/1.0/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" article-type="research-article" xml:lang="en">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">IR</journal-id>
<journal-title-group>
<journal-title>Information Research</journal-title>
</journal-title-group>
<issn pub-type="epub">1368-1613</issn>
<publisher>
<publisher-name>University of Bor&#x00E5;s</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">ir30iConf47287</article-id>
<article-id pub-id-type="doi">10.47989/ir30iConf47287</article-id>
<article-categories>
<subj-group xml:lang="en">
<subject>Research article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Investigating privacy risks in open government data: an exploratory case study</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>Carter</surname><given-names>Daniel</given-names></name>
<xref ref-type="aff" rid="aff0001"/></contrib>
<contrib contrib-type="author"><name><surname>Stratton</surname><given-names>Caroline</given-names></name>
<xref ref-type="aff" rid="aff0002"/></contrib>
<aff id="aff0001"><bold>Daniel Carter</bold> is an Associate Professor in the school of journalism and mass communication at Texas State University. They can be contacted at <email xlink:href="dcarter@txstate.edu">dcarter@txstate.edu</email>.</aff>
<aff id="aff0002"><bold>Caroline Stratton</bold> is a social scientist who studies technology, society, and policy topics.</aff>
</contrib-group>
<pub-date pub-type="epub"><day>06</day><month>05</month><year>2025</year></pub-date>
<pub-date pub-type="collection"><year>2025</year></pub-date>
<volume>30</volume>
<issue>i</issue>
<fpage>523</fpage>
<lpage>532</lpage>
<permissions>
<copyright-year>2025</copyright-year>
<copyright-holder>&#x00A9; 2025 The Author(s).</copyright-holder>
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc/4.0/">
<license-p>This is an Open Access article distributed under the terms of the Creative Commons Attribution-NonCommercial 4.0 International License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by-nc/4.0/">http://creativecommons.org/licenses/by-nc/4.0/</ext-link>), permitting all non-commercial use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<abstract xml:lang="en">
<title>Abstract</title>
<p><bold>Introduction.</bold> As governments increasingly release large datasets to the public, concerns have arisen regarding the potential risks associated with the inadvertent disclosure of personal information. However, there are few empirical case studies of this phenomena.</p>
<p><bold>Method.</bold> Taking a red teaming approach, we collected public, nonprofit reporting documents from the IRS, as well as a list of professional athletes. Using standard data processing techniques, we attempt to identify and evaluate the personal information that can be attached to these notable individuals in order to propose a framework describing how features of information, people and processes influence the potential release of personal information.</p>
<p><bold>Findings.</bold> We find that name commonness plays a large role in determining the feasibility of matching records. We also find that personal information, including addresses and business relationships, are accessible in the dataset.</p>
<p><bold>Conclusion.</bold> Our exploratory case study suggests several features of information, people and processes that influence the release of private information held in open government data. While limited, it suggests the value of further work in the area. </p>
</abstract>
</article-meta>
</front>
<body>
<sec id="sec1">
<title>Introduction</title>
<p>In recent years, the open government data (OGD) movement has gained significant traction, promoting transparency, accountability, participation and trust (<xref rid="R5" ref-type="bibr">Janssen et al., 2012</xref>). However, as governments increasingly release large datasets to the public, concerns have arisen regarding the potential risks associated with the inadvertent disclosure of personal information(<xref rid="R6" ref-type="bibr">Graham et al., 2016</xref>). This paper extends the literature on open government data by presenting an exploratory study that evaluates the risk related to a specific case of government data and proposes an initial framework that can guide future work.</p>
<p>Specifically, we focus here on the risk that personal information might be inadvertently released in nonprofit reporting documents such as the IRS form 990. The risk scenario that we attempt to better understand is one in which a dataset collected from such a source might be used to identify personal information such as addresses and contact information for notable individuals such as celebrities (in this case, NBA players) or a list of less notable people that might be relevant in a specific context (e.g., journalists, activists or teachers). While such contact information is available through other public sources, such as property records, we choose to work with nonprofit reporting documents because they have a national scope and, for risk scenarios that rely on targeting individuals with wealth, likely represent a higher density of targets.</p>
<p>The generalized information context that we attempt to understand, then, is a large dataset that is not valuable as a whole but is rather assumed to contain some valuable information that must be located and extracted. In conducting a case study to better understand this phenomenon, we assume that an adversary would approach this as an information retrieval task and model our work accordingly.</p>
<p>Based on our findings, we propose an initial framework that identifies key attributes of information, people, and processes that may impact the likelihood of harmful data release as a result of OGD initiatives. By examining these factors, we aim to contribute to the ongoing dialogue about balancing the benefits of open government data with the need to protect individual privacy and prevent potential misuse of personal information.</p>
</sec>
<sec id="sec2">
<title>Literature review</title>
<p>The literature on OGD has raised the possibility that privacy is a salient concern for governments and may be in tension with the aim of transparency (<xref rid="R6" ref-type="bibr">Graham et al., 2016</xref>; <xref rid="R6" ref-type="bibr">Janssen &#x0026; van den Hoven, 2015</xref>). In general, while OGD conforms to the conditions that (<xref rid="R5" ref-type="bibr">Janssen et al. 2012</xref>, p. 258) stipulate as <italic>&#x2018;non-privacy-restricted and non-confidential data which is produced with public money and is made available without any restrictions on its usage or distribution,&#x2019;</italic> the removal of all personally identifiable information (PII) from OGD, both that of residents who interact with governments and that of government workers, is far from uniform. In some cases, the value of an open dataset lies in its identification of people and their associated characteristics. The three most popular datasets on New York City&#x2019;s open data portal as of September 2024, for example, list individuals&#x2019; names and their vehicle identification numbers (For Hire Vehicles dataset), individuals&#x2019; names and scores for a civil service exam (Civil Service List dataset), and individuals&#x2019; names and addresses associated with building permits (DOB Job Application Filings dataset) (<xref rid="R2" ref-type="bibr">City of New York, n.d.</xref>).</p>
<p>While scholars have speculated about the relationship between privacy and OGD, we find little identification or exploration of specific cases in the literature. For most OGD research, the concept of individual privacy is left at the hypothetical level.</p>
<p>In the years since OGD has grown in popularity, other phenomena that jeopardize individual privacy, such as the growth of data broker companies (<xref rid="R3" ref-type="bibr">Crain, 2018</xref>) and the prevalence of large- scale corporate data breaches (e.g., <xref rid="R9" ref-type="bibr">Newman, 2024</xref>; <xref rid="R11" ref-type="bibr">Srinivasan, 2017</xref>), have perhaps overshadowed interest in risk and OGD. While the impacts of selling and stealing data are certainly grave, the risk posed by PII in OGD is one of hiding in plain sight, with potentially valuable personal information available to anyone capable of finding it. An older example illustrating potential harms of PII in OGD comes from Eightmaps, a visualization that showed donors to a 2008 California ballot measure to stop single-sex couples from marrying (<xref rid="R12" ref-type="bibr">Stone, 2009</xref>). De-identifying individual data is among the strategies that governments might take to reduce individual risk to privacy. Techniques for re-identification, though, may be powerful enough to nullify such efforts. <xref rid="R7" ref-type="bibr">Liu et al. (2021)</xref>, for example, raised the possibility of re-identification for a dataset of car trips from highway toll-collecting, with license plate numbers removed. Because the dataset also contained information about location of departure, destination, and travel times, the authors argued that re-identification might be possible for some entries.</p>
<p>The potential for exploitation of PII found in OGD would seem to be against the ethos of the OGD movement, which has emphasized the transparency benefits and potential gains in efficiency for government and other stakeholders; however, one of the most important proclamations regarding OGD, Barack <xref rid="R10" ref-type="bibr">Obama&#x2019;s 2013</xref> Executive Order (2013), declares that these data can and should lead to economic benefit, because enterprising people can <italic>&#x2018;develop a vast range of useful new products and businesses using these public information resources.&#x2019;</italic> A tension emerges here, then, between the commercial value of OGD and the potential for that value to be derived through the exploitation of PII found in government information. In this short paper, we explore risk around PII in OGD through a specific information retrieval task, building toward future work by asking:</p>
<p>What are the salient features of public information, people and processes that put personal information at risk?</p>
</sec>
<sec id="sec3">
<title>Methods</title>
<p>To explore our research question, we adopted a red teaming approach (<xref rid="R8" ref-type="bibr">Mansfield-Devine, 2018</xref>) designed to understand how the release of personal information might be perpetrated by someone with a financial or personal incentive. We began with a dataset composed of Form 990-N submissions made publicly available from the IRS. Form 990-N is an abbreviated version of the standard form 990 which is used by nonprofit organizations with gross receipts of less than $50,000 to make annual reports. The abbreviated form 990-N data is made available in a single, delimited text file, as opposed to the full form 990 data, which would require more sophisticated search and join procedures. While we assume that there are differences in these datasets related to the information made available as well as other features such as the prevalence of professional document preparers, we chose the abbreviated set in order to facilitate an initial, exploratory study and because the ease of acquiring and working with the data might more closely align with the workflows of adversaries.</p>
<p>Our <italic>form 990-N dataset</italic> consists of 1.39 million records, representing annual reports from 2007 through 2023. The relevant information included in the data includes the principal officer&#x2019;s name and address as well as the address listed for the organization. We note that the full form 990 includes additional information that might be relevant to the topic, such as information related to revenue and board member compensation.</p>
<p>In order to explore the presence of information related to notable individuals in the dataset, we use a list of NBA player names obtained from basketball-reference.com, which includes all players who have ever played in the league. The dataset, which we refer to here as the <italic>target dataset</italic>, includes 5,738 players. Because the name of the nonprofit&#x2019;s principal officer is the only feature that can be matched, we do not include other features, such as date of birth, in our <italic>target dataset</italic>.</p>
<p>In order to explore the extent to which notable individuals can be identified in our <italic>form 990-N dataset</italic>, we first reduce the dataset to include only records that match a name in the <italic>target dataset</italic>. The resulting <italic>matched dataset</italic> includes 5,769 form 990-N records that might correspond to a notable individual. However, some of these records will obviously represent false positives, or organizations with a principal officer who shares a name with a notable individual.</p>
<p>Because we are interested in features of the information as well as of the processes used to identify relevant personal information within it, we employ an evaluation process that balances thoroughness with feasibility, as follows:
<list list-type="order">
<list-item><p><bold>Ranking by Commonness:</bold> We first ranked all the names in our dataset based on their commonness, from least common to most common using Hadley Wickham&#x2019;s babynames dataset (2022), which includes all first names used at least five times in the US, as provided by the Social Security Administration. This ranking allowed us to prioritize the evaluation of names that were more likely to correspond to notable individuals.</p></list-item>
<list-item><p><bold>Cutoff Determination:</bold> The information contained in the public forms collected is insufficient to automatically verify if information is relevant (i.e., it corresponds to a notable individual); therefore, a more time-consuming, manual process must be employed. Because we assume that the value of information about players is randomly distributed (i.e., there is as much likelihood of value in the information regarding a notable individual that is easy to identify as one that is difficult to identify), we also assume that an efficient search strategy, such as would be adopted by an adversary, would focus efforts on data that is easier to verify and has a greater chance of corresponding to a notable individual. We discuss findings related to determining such a search cutoff below.</p></list-item>
<list-item><p><bold>Analysis:</bold> For each record we evaluated, we determined the following:
<list list-type="order">
<list-item><p>Relevance: Using information available online, are we able to determine if the named principal officer is a notable individual from our <italic>target dataset</italic>? We use a conservative approach and only record a match if we are able to locate explicit confirming information.</p></list-item>
<list-item><p>Personal information: We evaluate if the information from the form 990-N record contains personal details such as a non-commercial address.</p></list-item>
<list-item><p>Evidence of professional preparation: We evaluate if there is evidence that a professional entity such as a law firm or business manager prepared the form.</p></list-item>
<list-item><p>Additional notes: We make note of any aspects of the form information that does not correspond to our analysis plan or warrants further attention.</p></list-item>
</list></p></list-item>
</list></p>
</sec>
<sec id="sec4">
<title>Findings</title>
<p>We observe that both the <italic>target dataset</italic> and the <italic>form 990-N dataset</italic> exhibit an exponential distribution of name commonness (<xref ref-type="fig" rid="F1">figures 1</xref> and <xref ref-type="fig" rid="F2">2</xref>). We also observe that the <italic>merged dataset</italic> exhibits a markedly different distribution, with a greater proportion of results found to have higher name commonness (<xref ref-type="fig" rid="F3">figure 3</xref>). Calculating the ratio of the proportion of values from the <italic>merged dataset</italic> to the <italic>form 990-N dataset</italic>, we find a roughly linear increasing relationship (<xref ref-type="fig" rid="F4">figure 4</xref>), suggesting that the number of results that do not correspond to an individual in the <italic>target dataset</italic> will increase with name commonness. While this is not a surprising result, it has notable consequences for the general search problem described, as it suggests that an adversary would likely focus efforts on less common names. </p>
<fig id="F1">
<label>Figure 1.</label>
<caption><p>Distribution of name commonness in the Form 990-N dataset.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images\c43-fig1.jpg"><alt-text>none</alt-text></graphic>
</fig>
<fig id="F2">
<label>Figure 2.</label>
<caption><p>Distribution of name commonness in the target dataset.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images\c43-fig2.jpg"><alt-text>none</alt-text></graphic>
</fig>
<fig id="F3">
<label>Figure 3.</label>
<caption><p>Distribution of name commonness in the matched dataset.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images\c43-fig3.jpg"><alt-text>none</alt-text></graphic>
</fig>
<fig id="F4">
<label>Figure 4.</label>
<caption><p>Ratio of the proportion of records, by name commonness, in the merged dataset and the Form 990-N dataset.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images\c43-fig4.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>Because the purpose of this study is not to locate as much personal information as possible but to identify features of the information, people and processes involved that influence the risk of personal information release, we do not attempt to determine a precise cutoff (based, for example, in the ratio presented in <xref ref-type="fig" rid="F4">figure 4</xref>) &#x2014; indeed, given the highly contextual nature of the search task, determining such a limit is not realistic in this context. Instead, we evaluated records until we reached a point at which more than 100 consecutive records could not be matched to an individual from the <italic>target dataset,</italic> resulting in the inspection of 384 records. <xref ref-type="fig" rid="F5">Figure 5</xref> depicts the observed decrease in the rate of matches.</p>
<p>Of the evaluated records, we found that 13% matched an individual in the <italic>target dataset</italic>, with the rate of matches decreasing, as expected, as names became more common. Notably, we find that this rate decreases sharply, with just over 5% of records evaluated before matches became quite rare.</p>
<fig id="F5">
<label>Figure 5.</label>
<caption><p>Percent of verified matched by name commonness</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="images\c43-fig5.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>Of the verified matches, 52% included a non-commercial address, which we assume is likely the individual&#x2019;s residence. Notably, this information can be linked to other personal information, such as the value of an individual&#x2019;s home, which, while public, can be difficult to locate because property records are held at the county level.</p>
<p>36% of the matched records show evidence of the use of a professional service to submit the information. Observed professional services included both law firms and agencies that represent athletes. In all such cases, a commercial address was present instead of a residential address.</p>
</sec>
<sec id="sec5">
<title>Discussion</title>
<p>Based on the results of our exploratory case study, we propose the following framework, which highlights features of the documents, people and processes involved in open government data.</p>
<sec id="sec5_1">
<title>Information characteristics</title>
<p>At a basic level, we observe that the fields included in the released public data play a role in determining the risk of personal information disclosure. While it&#x2019;s obvious that the inclusion of details such as social security numbers or health information would increase the risk related to disclosure, we also note that the absence of information that is commonly used to link records (e.g., date of birth) plays a marked role in reducing risk and makes the verification process more laborious.</p>
</sec>
<sec id="sec5_2">
<title>Individual characteristics</title>
<p>We observe two features of individuals that likely impact the release of personal information through OGD processes: information literacy and name commonness.</p>
<p>Regarding information literacy, we observed several records in which fields were filled with information other than what was requested. This was most frequent with the form&#x2019;s Website field, which was sometimes used by individuals to enter an email address. In these cases, a lack of information literacy results in the release of personal information and provides another opportunity to link the record to additional information. The inclusion of personal addresses might be considered another example of a lack of information literacy. As we noted, professional preparation services, such as law firms, always use a commercial address, likely signaling that these entities believe there is an advantage to obscuring personal information. The inclusion of such information, then, signals an individual&#x2019;s lack of information literacy and understanding of how submitted information is, or is not, made public.</p>
<p>We also observe that less common names have a notable effect on the difficulty of verifying information in the specific search context described. This is especially obvious in our <italic>target dataset</italic> of NBA players, as a substantial number of foreign players come to the United States for this reason. As we discuss above, higher name commonality quickly makes verifying information impractical without automatic processing, making individuals with less common or foreign names much more vulnerable.</p>
</sec>
<sec id="sec5_3">
<title>Process characteristics</title>
<p>Related to the process through which information is submitted, we observe that individuals who use a business intermediary such as an agent or lawyer appear much less likely to include personal information such as a home address. Instead, the address of the business appears in the public information; while this masks some of the individual&#x2019;s information, it can reveal other information such as business relationships that might be valuable in themselves.</p>
</sec>
</sec>
<sec id="sec6">
<title>Conclusion</title>
<p>This paper presents a needed empirical study of the risks associated with OGD. Taking a red teaming approach, we sought to better understand the features of information, people and processes that influence the risk of personal information disclosure. While we note challenges to the information retrieval task described above, notably in relation to name commonness and linking data, we also note that, with fairly little effort and using only public data, we were able to obtain the residential addresses of 50 NBA players, as well as other, non-public information such as the agency they contract with. The value of this information is highly context-dependent, but our study does suggest that a process similar to ours could be profitable to an adversary in some contexts.</p>
<p>Because this is an exploratory study, it has considerable limitations.</p>
<p>At a very broad level, we are constrained by the general difficulty of studying behavior (the exploitation of public information) that would likely be considered unethical and therefore difficult to access through conventional qualitative methods (see, for example, <xref rid="R1" ref-type="bibr">Carter et al., 2021</xref>). Our approach here, red teaming, is adopted from computer science contexts in which the goal is not to describe a process occurring in the world but to imagine and circumvent such a process. While it is beyond the scope of this short case study to further explore the methodological and epistemological implications of adopting red teaming in the context of social science research, we believe that it has potential value, especially in the early, exploratory stages of research when there is a need for the creation of initial frameworks that can be validated and modified by further work. While we believe that the data and processes, we adopt have features that likely generalize to other contexts, a small, single case is necessarily limited. Studies that, for example, survey public datasets and classify the kinds of personal information found in them could help guide such work. Additional case studies that purposefully address a wide range of contexts could validate and extend the framework presented above.</p>
</sec>
</body>
<back>
<ref-list>
<title>References</title>
<ref id="R1"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Carter</surname><given-names>D.</given-names></name><name><surname>Acker</surname><given-names>A.</given-names></name><name><surname>Sholler</surname><given-names>D.</given-names></name></person-group><year>2021</year><article-title>Investigative approaches to researching information technology companies</article-title><source>Journal of the Association for Information Science and Technology</source><volume>72</volume><issue>6</issue><fpage>655</fpage><lpage>666</lpage><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/asi.24446">https://doi.org/10.1002/asi.24446</ext-link></element-citation></ref>
<ref id="R2"><element-citation publication-type="other"><person-group person-group-type="author"><collab>City of New York</collab></person-group><comment>n.d.</comment><article-title>NYC Open Data</article-title><source>NYC Open Data</source><comment>Retrieved September 13</comment><year>2024</year><ext-link ext-link-type="uri" xlink:href="http://nycod-wpengine.com/">http://nycod-wpengine.com/</ext-link></element-citation></ref>
<ref id="R3"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Crain</surname><given-names>M.</given-names></name></person-group><year>2018</year><article-title>The limits of transparency: Data brokers and commodification</article-title><source>New Media &#x0026; Society</source><volume>20</volume><issue>1</issue><fpage>88</fpage><lpage>104</lpage><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/1461444816657096">https://doi.org/10.1177/1461444816657096</ext-link></element-citation></ref>
<ref id="R4"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Graham</surname><given-names>F. S.</given-names></name><name><surname>Gooden</surname><given-names>S. T.</given-names></name><name><surname>Martin</surname><given-names>K. J.</given-names></name></person-group><year>2016</year><article-title>Navigating the Transparency&#x2013;Privacy Paradox in Public Sector Data Sharing</article-title><source>The American Review of Public Administration</source><volume>46</volume><issue>5</issue><fpage>569</fpage><lpage>591</lpage><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/0275074014561116">https://doi.org/10.1177/0275074014561116</ext-link></element-citation></ref>
<ref id="R5"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Janssen</surname><given-names>M.</given-names></name><name><surname>Charalabidis</surname><given-names>Y.</given-names></name><name><surname>Zuiderwijk</surname><given-names>A.</given-names></name></person-group><year>2012</year><article-title>Benefits, Adoption Barriers and Myths of Open Data and Open Government</article-title><source>Information Systems Management</source><volume>29</volume><issue>4</issue><fpage>258</fpage><lpage>268</lpage><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1080/10580530.2012.716740">https://doi.org/10.1080/10580530.2012.716740</ext-link></element-citation></ref>
<ref id="R6"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Janssen</surname><given-names>M.</given-names></name><name><surname>van den Hoven</surname><given-names>J.</given-names></name></person-group><year>2015</year><source>Big and Open Linked Data (BOLD) in government: A challenge to transparency and privacy? Government Information Quarterly</source><volume>32</volume><issue>4</issue><fpage>363</fpage><lpage>368</lpage><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.giq.2015.11.007">https://doi.org/10.1016/j.giq.2015.11.007</ext-link></element-citation></ref>
<ref id="R7"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Liu</surname><given-names>C.-Y.</given-names></name><name><surname>Li</surname><given-names>W.-P.</given-names></name><name><surname>Tu</surname><given-names>Y.-P.</given-names></name></person-group><year>2021</year><article-title>Privacy Perils of Open Data and Data Sharing: A Case Study of Taiwan&#x2019;s Open Data Policy and Practices</article-title><source>Washington International Law Journal</source><volume>30</volume><issue>3</issue><ext-link ext-link-type="uri" xlink:href="https://digitalcommons.law.uw.edu/wilj/vol30/iss3/8">https://digitalcommons.law.uw.edu/wilj/vol30/iss3/8</ext-link></element-citation></ref>
<ref id="R8"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mansfield-Devine</surname><given-names>S.</given-names></name></person-group><year>2018</year><article-title>The best form of defence&#x2013;the benefits of red teaming</article-title><source>Computer Fraud &#x0026; Security</source><volume>2018</volume><issue>10</issue><fpage>8</fpage><lpage>12</lpage></element-citation></ref>
<ref id="R9"><element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Newman</surname><given-names>L. H.</given-names></name></person-group><year>2024</year><comment>August 16</comment><article-title>The Slow-Burn Nightmare of the National Public Data Breach</article-title><source>Wired</source><ext-link ext-link-type="uri" xlink:href="https://www.wired.com/story/national-public-data-breach-leak/">https://www.wired.com/story/national-public-data-breach-leak/</ext-link></element-citation></ref>
<ref id="R10"><element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Obama</surname><given-names>B.</given-names></name></person-group><year>2013</year><comment>May 9</comment><article-title>Executive Order&#x2014;Making Open and Machine Readable the New Default for Government Information</article-title><source>The White House, Office of the Press Secretary</source></element-citation></ref>
<ref id="R11"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Srinivasan</surname><given-names>S.</given-names></name></person-group><year>2017</year><comment>October</comment><source>Data Breach at Equifax</source><publisher-name>Harvard Business School</publisher-name><ext-link ext-link-type="uri" xlink:href="https://www.hbs.edu/faculty/Pages/item.aspx?num=53509">https://www.hbs.edu/faculty/Pages/item.aspx?num=53509</ext-link></element-citation></ref>
<ref id="R12"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Stone</surname><given-names>B.</given-names></name></person-group><year>2009</year><comment>February 7</comment><source>Prop 8 Donor Web Site Shows Disclosure Law Is 2-Edged Sword</source><publisher-name>The New York Times</publisher-name><ext-link ext-link-type="uri" xlink:href="https://www.nytimes.com/2009/02/08/business/08stream.html">https://www.nytimes.com/2009/02/08/business/08stream.html</ext-link></element-citation></ref>
<ref id="R13"><element-citation publication-type="other"><person-group person-group-type="author"><name><surname>Wickham</surname><given-names>H.</given-names></name></person-group><year>2022</year><article-title>Package &#x2018;babynames&#x2019; [Computer software]</article-title><ext-link ext-link-type="uri" xlink:href="https://cran.r-project.org/web/packages/babynames/babynames.pdf">https://cran.r-project.org/web/packages/babynames/babynames.pdf</ext-link></element-citation></ref>
</ref-list>
</back>
</article>