Chuck Borges: From SSA Whistleblower to Maryland State Senate Candidate
Chuck Borges’ 2023 career trajectory was defined by a clash between federal data governance responsibilities and controversial executive overreach, culminating in his resignation from the Social Security Administration (SSA) as chief data officer (CDO) and a subsequent pivot to Maryland state senate politics. As CDO, Borges was tasked with safeguarding SSA’s sensitive databases—containing Social Security numbers, citizenship records, and personal benefits data for nearly every American—only to face mounting friction with Elon Musk’s “Department of Government Efficiency” (DOGE). After alleging DOGE mishandled data in an unsecure cloud environment, Borges blew the whistle and resigned, now seeking to channel his experience into state-level public service.
Interview: Chuck Borges on Data Governance, Whistleblowing, and Public Service
Q: Why did you decide to run for office? And how did working under DOGE influence your decision to run?
A: I resigned from SSA in late August, and the following month was particularly challenging, both personally and professionally, involving congressional engagements, media outreach, and documentation review. During this period, I emphasized to local groups the critical importance of data privacy—a nonpartisan issue affecting all Americans. In early October, the local Democratic Party approached me about running for office. My motivation stems from witnessing systemic government dysfunction during my tenure at SSA, where key responsibilities were undermined by unclear oversight structures and operational missteps. DOGE did not directly influence my decision, but the broader institutional failures I experienced reinforced my commitment to serve the public more effectively.
Q: When you first heard about DOGE involving itself at SSA, what did you expect would happen?
A: Initially, the structure and purpose of DOGE’s involvement were unclear. No formal framework was communicated regarding their operational scope or intended use cases. I was told they would execute discrete projects and conduct system reviews, yet for the first several months, there was minimal interaction between my team and DOGE personnel.
Q: When did you start growing concerned about how SSA leadership and DOGE was handling data at the agency?
A: My first concern arose with media reports of changes to the Death Master File, specifically the classification of 6,000 living immigrants as deceased. As CDO, I would have expected consultation on such critical datasets, as they involve personal identifiers and operational risks. This lack of engagement signaled a breakdown in data governance processes.
Q: How did you approach the work when you had limited insight into what was happening?
A: I attempted to engage with SSA leadership through established channels but faced barriers, including denial of permission to convene data governance councils—bodies critical to standardizing data protocols. My role as CDO requires transparency and control over sensitive information, yet administrative hurdles and lack of oversight paralyzed these efforts.
Q: As an expert in government data, what do you believe was the purpose behind DOGE’s decision to move SSA data to a separate, unsecure cloud environment?
A: No legitimate use case for such large-scale data migration to an unsecure cloud was communicated or justified during my tenure. The Numident database, containing birth records and personal identifiers, was among the datasets in question—a repository of highly sensitive, actionable information.
Q: What’s the worst-case scenario of uploading sensitive SSA data to an unsecure cloud?
A: Unsecured personal data, including Numident details (e.g., date of birth, mother’s maiden name), poses severe risks of exposure to bad actors. Even accidental breaches via human error could compromise individuals’ privacy and identity, which are irreversibly damaged by such exposure.
Q: When did you first raise concerns about DOGE’s access to SSA data? What made you realize those concerns weren’t going to be addressed internally?
A: I first raised concerns internally, but within a week, employees were instructed not to engage with my inquiries. This dismissal confirmed that systemic issues would not be resolved through internal channels.
Q: Why did you decide to become a whistleblower?
A: As CDO, I had a statutory duty to ensure data security. When I could not verify the safety of SSA’s data under DOGE’s purview, and my role became unenforceable, I had an ethical obligation to report these risks to oversight authorities.
Q: Was there a moment when you realized the cost of raising these concerns would end your career?
A: Yes. Observing colleagues facing dismissal for speaking up made me aware of the potential consequences. However, as a leader, I believed the duty to protect public data superseded personal career risks.
Q: What advice would you give to federal employees in similar positions?
A: For leaders: (1) Adhere strictly to legal compliance; (2) Avoid placing subordinates in ethically compromising positions; (3) Cultivate a culture of inquiry to ensure concerns are heard. For rank-and-file employees: Document work rigorously to preserve accountability and enable audits.
Q: Elon Musk stated DOGE is still operational and cutting costs in federal agencies. What risks does this pose?
A: Government inefficiency is legitimate, but DOGE’s approach risks prioritizing speed over data security and compliance. Sensitive information and taxpayer resources demand intentional governance—speed without safeguards endangers public trust.
Q: What are your goals as a Maryland state senator candidate?
A: Southern Maryland’s unique blend of biodiversity, agricultural expertise, and proximity to Washington, D.C. (with military installations) positions it to lead in sustainable growth. My experience in executive data governance and public policy will help bridge technical innovation with regional needs, fostering a model for East Coast prosperity.
Interview edited for clarity and length.