You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the improvement you would like to see
Log authentication attempts when a user tries to authenticate towards Flotilla (also when the authentication fails)
How will this change existing functionality?
No functional change for the user. Operations team will get better overview of usage.
How will this improvement affect the current Threat Model?
Increases overview of the usage of the application, the operations team can see if there has been a lot of authentication attempts.
The text was updated successfully, but these errors were encountered:
We log authentication attempts in the respective managed identities(linked to app registration) in Azure AD. There should be some setting to bundle this logging with the AI, I propose we investigate this pattern.
We log authentication attempts in the respective managed identities(linked to app registration) in Azure AD. There should be some setting to bundle this logging with the AI, I propose we investigate this pattern.
Great, I was not aware. This seems sufficient for now. I dont think we need or want to also log this in Application Insights, so I will close this issue.
What we may want in the future is some automatic report / notification if there is a lot of unknown / unsuccessful authentication attempts in a short period of time
Describe the improvement you would like to see
Log authentication attempts when a user tries to authenticate towards Flotilla (also when the authentication fails)
How will this change existing functionality?
No functional change for the user. Operations team will get better overview of usage.
How will this improvement affect the current Threat Model?
Increases overview of the usage of the application, the operations team can see if there has been a lot of authentication attempts.
The text was updated successfully, but these errors were encountered: