New CAEP event - Risk level change event #205
Open
Conversation
This file contains 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
Risk level change event
FragLegs
requested changes
Sep 24, 2024
|
|
||
| A vendor may deploy mechanisms to gather and analyze various signals associated with subjects such as users, devices, etc. These signals, which can originate from diverse channels and methods beyond the scope of this event description, are processed to derive an abstracted risk level representing the subject's current threat status. | ||
|
|
||
| The Risk Level Change event is employed by the Trasnmitter to communicate any modifications in a subject's assessed risk level at the time indicated by the `event_timestamp` field in the Risk Level Change event. The Transmitter may generate this event to indicate: |
There was a problem hiding this comment.
Suggested change
| The Risk Level Change event is employed by the Trasnmitter to communicate any modifications in a subject's assessed risk level at the time indicated by the `event_timestamp` field in the Risk Level Change event. The Transmitter may generate this event to indicate: | |
| The Risk Level Change event is employed by the Transmitter to communicate any modifications in a subject's assessed risk level at the time indicated by the `event_timestamp` field in the Risk Level Change event. The Transmitter may generate this event to indicate: |
| ### Event Specific Claims {#risk-level-change-event-specific-claims} | ||
| The following optional claims MAY be present in a Session Presented event: | ||
|
|
||
| reason_admin |
There was a problem hiding this comment.
I think it is a mistake to make this optional field required and to use it for passing important info about the event.
|
|
||
| ### Event Specific Claims {#risk-level-change-event-specific-claims} | ||
| The following optional claims MAY be present in a Session Presented event: | ||
|
|
There was a problem hiding this comment.
Could we add a field that describes the type of risk? You mention in your example user risk and device risk. What if we had a field called risk_type whose values were an enum:
- DEVICE
- USER
- ACCOUNT
- OTHER
There may be other values that we should include in this enum as well.
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.
New CAEP event - Risk level change event
Closes #200
Removed
ipsclaim from the event and created #201 to handle it separately for all CAEP events