AI Cyber Defense / Identity, phishing and deepfake resistance
AI Cyber Defense: Make authenticator enrollment a privileged event
Require recent strong reauthentication for enrollment and send change notifications through an existing independent channel. Investigate unexpected additions immediately.
Environment and inputs: Enterprise identity providers, privileged access, service desks and business approval workflows; controls depend on application support.
Scenario and goal
An attacker with a temporary session may add an authenticator that outlives the original compromise.
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
Correlate authenticator additions with recent recovery, sign-in risk, administrator roles and changes to notification destinations.
Validate with an authorized exercise
Add a test authenticator through the approved path and verify notification; replay a synthetic risky-enrollment event and confirm that the case includes the prior recovery context.
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.