You're talking to someone who deploys AI tools to serve a mission: processing benefits claims, triaging cases, routing taxpayer documents, accelerating declassification reviews. They don't think of themselves as an identity buyer. They're right. Identity infrastructure is not their job.
But the AI tool they own creates identity governance obligations whether they budgeted for them or not. Open with access management terminology, and this conversation ends immediately. The frame that works is the one they already operate in: OMB M-25-21, the High-Impact AI classification, and the accountability structures their agency has already committed to.
The compliance landscape is concrete. M-25-21 consolidates prior categories into a single "high-impact AI" designation for any AI application whose outputs could materially affect "rights, opportunities, access to services, or safety." The VA requires AI Impact Assessments for high-impact use cases in operation. GAO found the IRS running 126 active AI use cases as of mid-2025, up from 10 three years earlier, with some tools not appearing in the required inventory at all.
M-25-21's mandatory risk management practices for high-impact AI carried a compliance deadline of April 15, 2026. Program Officers deploying AI tools that touch citizen data are likely already inside the accountability boundary.
The identity question sits inside that compliance gap. An AI tool accessing benefits data or making routing decisions on taxpayer documents operates with machine credentials connecting to mission-critical systems. Someone approved that access. Whether anyone governs it on an ongoing basis is a separate and usually unanswered question.
1. "Has your AI tool been classified under your agency's M-25-21 high-impact framework, and does the AI Impact Assessment cover who approved the tool's access to your mission systems?"
Why this works now: The compliance deadline has passed. Program Officers deploying AI tools that touch citizen data are likely inside the high-impact boundary. The AI Impact Assessment is a document they already know about. The access-approval question extends it naturally.
What the answer tells you: "Yes, we've been classified and assessed" opens the door to ask what the assessment covers. "We're still working through classification" means the tool may be operating without required governance, six weeks past the deadline. "That's IT's responsibility" tells you the accountability chain has a gap between mission ownership and infrastructure control.
2. "If your AI tool accesses case data or benefits records autonomously, who is the named human owner of that access, and is that ownership documented in your agency's AI use case inventory?"
Why this works now: GAO found over 25% of IRS AI use cases lacked basic quality information in the inventory, and some tools weren't inventoried at all. The Program Officer may own a tool that is technically unaccounted for in the governance framework their agency committed to.
What the answer tells you: A named owner and an inventory entry is a real answer. "The vendor manages that" is a deflection: M-25-21 accountability sits with the agency regardless of who built the tool. An unowned agent accessing benefits data is an audit finding waiting to happen.
3. "If your agency's CAIO asked you tomorrow to demonstrate continuous monitoring of what your AI tool can reach and do inside your mission systems, could you produce that record?"
Why this works now: M-25-21 requires ongoing monitoring for high-impact AI, and the Chief AI Officer role carries explicit approval authority. This connects the Program Officer's tool to an accountability chain they recognize without pulling them into infrastructure vocabulary.
What the answer tells you: Confidence means the Program Officer has visibility into what the tool accesses and how that access is reviewed. Hesitation means the monitoring infrastructure doesn't exist yet, and the compliance requirement does. (Okta's non-human identity governance and continuous access certification capabilities connect here, positioned as the compliance layer the Program Officer needs to satisfy the CAIO's requirements.)