▶ Watch ↗13:27
Conference affiliation: Fieldguide
Anirudh Veeraragavan is the lead security engineer and first security hire at Fieldguide, which builds software for audit and advisory firms. His work spans shared cryptographic infrastructure at Plaid and controls for financial agents at Fieldguide. In both settings, he explains the engineering beyond a correct result: getting applications onto a shared security service, preserving a reviewer’s signed decision, and recording enough evidence to reconstruct an agent’s work.
Anirudh studied at UCLA from 2016 to 2020. An early project, NXTPitch, combined machine-learning services to give students feedback on pitches and application materials. He developed it with Rahul Sheth. For its 2017 machine-learning extension, Anirudh wrote the Python backend, integrated services from Microsoft Azure, IBM Watson and Eyeris, and built the logic for extracting content from videos and documents.
He subsequently spent five years at Plaid, most recently as a Staff Software Security Engineer. He led product-security initiatives, including a workstream developing agentic penetration-testing systems.
Anirudh also worked on Plaid’s key-management system. In a technical account co-authored with Shuaiwei Cui, he described the team’s decision to centralize cryptography that services had implemented differently. The system retained AWS KMS as its root of trust while moving routine operations into infrastructure tailored to Plaid’s scale and access controls. Envelope encryption let applications encrypt payloads locally and send only their data keys through the central service, reducing traffic and making performance more predictable.
Completing adoption was a substantial part of that work. The team tackled challenging services first, provided tools and documentation for most migrations, then worked directly with owners of the remaining exceptions. Their account explains why building the central service was only part of the task: its security benefits depended on moving applications onto it and continuing to operate it.
At Fieldguide, Anirudh argues that an experienced auditor new to an engagement should be able to follow an agent’s work: understand the test, examine the evidence and reconstruct the conclusion. His writing on defensible agents and financial-agent talk explain why a strong aggregate evaluation score cannot establish whether a particular audit decision was justified.
His approach connects several engineering decisions:
These controls also determine when the agent should stop. Anirudh identifies attempts to change reviewed work, disagreements between runs and evidence that fails the required checks as reasons for human investigation. He favors selective escalation with a clear discrepancy and enough context to examine it. Making a case easy to verify can still leave substantial work before approval; repeatedly asking reviewers to click yes risks turning their signatures into automatic responses.
▶ Watch ↗13:27
Loading more talks and highlights…