Research Security Beyond Compliance: Five Takeaways from Safeguarding America’s Research

On October 14–15, the Southeast Defense Innovation Center (SEDIC) brought federal counterintelligence and research security officials, congressional staff, university leaders and industry partners to Kannapolis, North Carolina, for its Safeguarding America’s Research workshop. Finch AI was proud to serve as the event’s Gold sponsor.

The organizers framed the day around a single charge: move the protection of federally funded research beyond compliance and toward proactive security programs. The timing could not be more relevant. In June, an executive order directed the FBI to expand its Quantum Information Science and Technology Counterintelligence Protection Team. Shortly after in August, the Department of War gave 30 universities roughly two weeks to audit their ties to institutions on the Section 1286 list with future research funding at stake. And in September, two universities were placed under federal investigation over foreign-funding disclosures and given 30 days to produce records. The research security landscape remains dynamic, compounding with ever changing rules and regulations.

From the Institute for Defense Analyses’ quantum case study to a closing panel that included university leaders from MIT, the University of Tennessee Knoxville, UNC Charlotte and the University of Toronto, five takeaways from the workshop stood out for research security officers (RSOs) heading back to campus:

  • Compliance is the floor, not the finish line. Program certifications, training and disclosure requirements establish a necessary baseline. But audits and investigations test something different: whether an institution actually knows who its researchers are working with and can prove it. A program that can certify but can’t document its answer to a sponsor’s question, and suspected follow ups, about a specific collaborator isn’t yet a mature research security program.
  • Audit-readiness is now measured in days, not semesters. A two-week audit window or a 30-day records demand leaves no time to build a capability from scratch. The institutions positioned to respond have already done the foundational work: resolving researcher identities, mapping affiliations and collaboration networks, screening against current federal lists and documenting the logic behind every determination. And because those lists change, like the 1286 list update in July, screening must be repeatable, not a one-time spreadsheet exercise.
  • Counterintelligence insight must translate into campus-ready decisions. The day’s panels paired current and former counterintelligence professionals from the FBI, NCIS, CIA, Army counterintelligence and Canada’s CSIS with the people making research security decisions on campus. Threat awareness alone doesn’t tell an RSO whether to approve a visiting scholar or an international partnership. A risk-based, evidence-backed process does and it MUST apply consistent criteria, protect legitimate collaboration and treat every researcher fairly.
  • The threat doesn’t scale down with institution size. The academic institutions in attendance at the workshop varied in size, ranging from MIT and Johns Hopkins to The Citadel and Trident Technical College. Adversaries don’t confine their interest to institutions above NSPM-33’s $50 million threshold, yet smaller institutions rarely have the staff, data or tools of a large R1. Peer networks like the one SEDIC convened, shared frameworks and the right technology partners help close that gap.
  • Protecting quantum requires precision about who is working on what. The afternoon’s focus on quantum underscored how squarely the field sits in adversaries’ sights. Yet quantum research spans across many domains–physics, engineering, materials science and computer science–and it moves quickly from campus labs to startups. As we’ve noted before, there is still no widely adopted crosswalk between U.S. Critical and Emerging Technology areas and the taxonomies used to classify research. Without one, “protect quantum” remains a policy goal rather than an operational capability.

The workshop ended on the question every RSO eventually faces: what do we do on Monday morning? Our answer starts with visibility: know who your researchers are, who they collaborate with and who funds them; know which of those relationships touch federally designated entities or critical technologies; and keep the evidence behind every determination. That foundation is what lets a program withstand an audit and, more importantly, get “left of theft.”

That is the challenge we are focused on at FinchAI. We help research security teams apply AI and open-source data to reach defensible, risk-based determinations at the pace of today’s audits and investigations demand while protecting legitimate collaboration and helping secure the innovation enterprise.

If we connected in Kannapolis, thank you for the conversation. If we didn’t, we would welcome one. To learn more about how Finch AI can help, please get in touch at researchsecurity@finchai.com.

Discover More