Exposing the secret Office 365 detailed activity logs and forensics tool
1–10 of 42 posts
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#2[deleted]
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#3Did not know, wow.
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#4This is similar to Azure activity logs - in that they do not provide you log access to "read" actions.. only write/delete ones. However, Azure actually DOES keep those read ops logged. Though I guess, it's not similar in that: Azure still doesn't have an API to fetch them.. not even an undocumented one.
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#5So is there a secret tool? Or is this just an undocumented API call that people are only now finding out about?
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#6This makes me wonder how many other APIs rely solely on obscurity to protect major features.
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#7I looked at the API calls on the CrowdStrike blog post and I have been using parts of these API's for calls in PowerShell for at least the past year for tracking down issues we have had in Office 365. I can understand how frustrating it can be if your competitors seem to have "secret knowledge". However that knowledge may have been gotten by calling up the very helpful people at MS support, laying out the problem and they send you a Powershell script in return.
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#8I looked at the API calls on the CrowdStrike blog post and I have been using parts of these API's for calls in PowerShell for at least the past year for tracking down issues we have had in Office 365. I can understand how frustrating it can be if your competitors seem to have "secret knowledge". However that knowledge may have been gotten by calling up the very helpful people at MS support, laying out the problem and…
I couldn't agree more. Why is the API not public? Is it because some sort of top secret corporate conspiracy? Or is it that management just decided to avoid the burden of publishing and maintaining an immature or lesser used API? After reading your comment that whole article seemed a little sensationalist
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#9So is there a secret tool? Or is this just an undocumented API call that people are only now finding out about?
It's a secret tool that uses undocumented APIs :)
Re: Exposing the secret Office 365 detailed activity logs and forensics tool
#10gee this is a fucking surprise