Re: [Architecture] Security Analytics

Great stuff Seshika and the team.. This will definitely make a difference in the IS product and our effort to focus more on Identity Governance.. As discussed, for the first phase lets focus on login analytics and user/role/.. lifecycle tracking... Thanks & regards, -Prabath On Tue, Feb 2, 2016

Re: [Architecture] Security Analytics

Would there be a way we can integrate Security Analytics with lets say API Analytics, lets say if there is a fraud detected due to several API Calls can we find out out from which API calls and calling which backend service? On Tue, Feb 2, 2016 at 11:30 AM, Seshika Fernando

Re: [Architecture] Security Analytics

Hi Iranga, Valid point. There is a certain amount of overlap between security anlaytics and api invocation related analytics (because they use similar security mechanism). As we progress, we are hoping to figure out how we can employ the relevant security analytics for APIM. And this will not

Re: [Architecture] Security Analytics

Hi Seshika, Thinking about this, I think we should replace the line chart with a Heatmap that has time (as days) as X axis and user, role, service provider, ip ( user can pick any) y axis because heatmap is much better on drill down and exploration. [image: Inline image 2] Then user can click

Re: [Architecture] Security Analytics

@Lahiru: +1. I'm hoping to analyze the data that we can get from IS so that we can design some more, relevant analytics from it. I'll add more authorization specific analytics as you have mentioned. @Srinath: +1. I'll change the line graphs to this. On Tue, Feb 2, 2016 at 9:33 AM, Srinath Perera

Re: [Architecture] Security Analytics

Hi Seshi, I think we can consider Authorization stats also. Since WSO2 IS has a good implementation of XACML spec, we can collect stats on, the requests allowed, denied, with which granularity, etc. Thanks. On Mon, Feb 1, 2016 at 1:59 PM, Seshika Fernando wrote: > Hi all, >