AI Cyber Defense / Identity, phishing and deepfake resistance
AI Cyber Defense: Prevent support chatbots from authorizing identity changes
Keep identity proofing and reset authorization in the identity service. Limit the chatbot to request collection until the verified workflow issues a scoped action approval.
Environment and inputs: Enterprise identity providers, privileged access, service desks and business approval workflows; controls depend on application support.
Scenario and goal
An attacker may persuade an AI support assistant to turn a plausible conversation into a reset instruction.
Why it matters
For this scenario, assume the request can use correct names, fluent language and convincing media. The durable boundary is the verified identity and transaction authorization, including enrollment, recovery and exceptions. Distinguish proof of the person from permission for the requested action. A strong authentication method does not by itself authorize a payment, application grant or administrator role change.
Evidence to collect
Capture the authenticated user, proposed action, downstream authorization decision and tool invocation receipt.
Validate with an authorized exercise
Submit a fictional persuasive reset request to a test assistant; verify no reset occurs without the identity service's approval and that the denied action is recorded.
Rollout and checks
Before enforcement, inventory application support, fallback methods and the emergency-access path. Roll out to a test group and inspect the evaluated policy at the resource as well as the identity provider. Record session lifetime and revocation behavior separately for each application; do not assume existing access ends immediately when a password or policy changes.
Scope and limits
This guide proposes a defensive test; it is not a tested production design. Check platform support and local requirements. References explain the mechanisms but do not certify the design. Behavior alone does not prove AI involvement.