Fragmented identity
Four records, one person
The app, website, branch and API each hold a different view of the customer. A change in one channel doesn't reach the others.
Trust and Identity squad
Cian Gatekeeper — Lead AI Customer Identity Director
AI identity management across every customer channel
Cian Gatekeeper — Lead AI Customer Identity DirectorCian Gatekeeper is an AI agent that keeps one identity record per customer across your app, web, branch and API. He watches for credential stuffing and account takeover signals, recommends when to step up authentication, and tracks what each customer has consented to. Anything risky reaches your team with the evidence attached.
Cian Gatekeeper
Login spike on retail app
IllustrativeFlagged for review
Credential stuffing risk · high
Flag explained
“Many accounts tried from a few networks, high failed-password rate.”
Job description
What Cian Gatekeeper does Job description
Cian Gatekeeper is a Lead AI Customer Identity Director. He sits beside your identity provider and channel systems, links each customer's records into one identity, and watches how that identity is used.
AI AGENT · TRUST AND IDENTITY SQUAD
CIAN GATEKEEPER
Lead AI Customer Identity Director
REPORTS TO
Your CISO or Head of Fraud
WORKS WITH
Your identity provider, mobile and web apps, branch systems and APIs
DEPLOYED
Shadow mode first, then the autonomy you set
KEY RESPONSIBILITIES
01Link each customer's records across app, web, branch and API into one identity record
02Detect credential stuffing, password spraying and account takeover patterns across channels
03Recommend adaptive authentication steps based on the risk of each login and request
04Track consent and its scope for every customer, with a dated record of each change
05Send suspected takeovers and identity conflicts to an analyst with the evidence attached
AUTONOMY MODEL
LOWMEDIUMHIGH
Low risk
Can let routine logins continue, if you allow it
Medium risk
Goes to an analyst by default
High risk
Always goes to an analyst
You set the threshold per rule.
Kill switch: Turn Cian off at any time
Options
How the options compare
| CRITERIA | Separate channel logins | Standard CIAM platform | Cian Gatekeeper |
|---|---|---|---|
| Time to first results | Already in place | Platform migration project | Shadow mode on your live login data |
| Who decides | Fixed rules per channel | Platform policy, then your team | Analyst, inside risk bands you set |
| One view of the customer | No | Yes, once migrated | Linked across the systems you already run |
| Cross-channel attack view | No | Partial | Yes, with patterns grouped into campaigns |
| Why a login was challenged | Rule ID | Policy name | Plain-English reason with the signals behind it |
| Where it's weaker | Attackers work the gaps between channels | A large migration before you see value | Only as good as your source records, and uncertain links need human review |
Works best with
AI agents that work best with Cian Gatekeeper
Cian's identity view gets sharper when other agents add what he can't see on his own.
TRUST AND IDENTITY
Nova Sentinel
Lead AI Zero Trust Security Architect
Scores each session's trust, so Cian's identity view has live context.
Meet NovaTRUST AND IDENTITY
Iris Verma
Senior AI Identity Verification Specialist
Re-verifies documents and liveness when Cian finds an identity conflict.
Meet IrisTRUST AND IDENTITY
Rhea Ledger
Senior AI KYC/AML Compliance Director
Uses the linked identity for screening and customer risk rating.
Meet Rhea
Thoughts that matter
Insights on AI agents, financial crime and compliance
What we're learning about AML, fraud and the evidence examiners ask for.
Best AML Software in 2026: An Honest Comparison for Banks and Fintechs
Read More
goAML Registration and STR Filing in the UAE: A Step-by-Step Guide for Reporting Entities
Read More
Transaction Monitoring Software: UAE Acceptance Checklist
Read More
PEP and Sanctions Screening: What the MLRO Owns
Read More
Session Risk Scoring: Continuous Authentication for Banks
Read More
Impossible Travel Detection in Banking: How It Works
Read More
Questions? We Have Answers
-1.svg)
Frequently Asked Questions
Still have questions?
Talk to the people who build the agents. We'll answer per capability, yes or no.
It keeps one identity record per customer across channels, watches how that identity is used and tracks consent. Cian Gatekeeper links records, detects credential stuffing and takeover patterns, and recommends when to step up authentication. Your team sets the rules and makes the call on anything risky.
No. Cian scores and recommends. Medium-risk activity goes to an analyst by default and high risk always does. Routine logins continue without review only where you allow it. A kill switch turns Cian off without touching your login flows.
No. Cian reads from the identity provider and channel systems you already run and links what they hold. Your authentication stays where it is.
He looks at failed and successful logins across every channel together: many accounts tried from a small set of networks, high failure rates and logins that match leaked credential patterns. He groups those attempts into one campaign for your team.
Cian links records and scores your live logins, but no customer is challenged or locked out. Your current controls keep working, and you compare his findings with your team's. You decide whether, and where, to switch on any autonomy afterwards.
He keeps a dated record of what each customer agreed to, through which channel, and every change since. That record supports access requests and consent reviews under the data protection law that applies to you.
FluxForce runs as SaaS, on-premise or hybrid, built on Microsoft Azure. We agree data residency and which components run inside your environment during deployment design, before any data moves.