Add Fraudulent Login Evaluation Enhancement Proposal#45
Open
JoseSzycho wants to merge 2 commits into
Open
Conversation
…t login enhancement template
…tion CRD and process documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Title
docs: add enhancement proposal for fraudulent login evaluationPR Description
Summary
This pull request adds the enhancement proposal (KEP) for shifting the responsibility of evaluating suspicious user logins and alerting users of anomalous access from the identity provider (
zitadel-provider) to the central fraud detection system (fraud-operator).Key Concepts & Proposal Details
fraud.miloapis.com/v1alpha1that represents a transient login event.userRef(referencing the user resource),loginEmail(capturing the email address used for the specific login attempt, crucial for multi-provider OIDC login contexts), andloginContext(IP address, User-Agent, device fingerprint, and creation timestamp).isFraudulentand three key conditions:Ready: Signifies if the evaluation completed and notification was processed.UserRefValid: Indicates if the referenced user is valid and exists in the system.NotificationSent: Indicates if the alert notification has been successfully created.SessionAPI) to verify context safety.