A Microsoft Teams member was made owner of multiple teams
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
Goal
Detect when a user is made owner of multiple Microsoft Teams. This could indicate an adversary or insider threat attempting to escalate the privileges of the assigned user with regard to various teams chats, as most users tend to own few teams curated to specific topics.
Strategy
Monitor Microsoft Teams audit logs to look for events with an @evt.name
value of MemberRoleChanged
and a @Members.Role
value of 2
indicating the change to an Owner role. Generally, most users will own a few teams related to specific topics that correlate with that job role. However, if this activity is observed from an external user or a user whose job function does not correlate with the assigned team, this might be an indicator of malicious activity.
Triage and response
- Determine if the user
{{@usr.email}}
intended to make the assigned user {{@Member.UPN}}
the owner of the teams within the{{TeamName}}
attribute. - If the
{{@usr.email}}
didn’t intend to assign the owner privileges to {{@Member.UPN}}
:- Investigate other activities performed by the user
{{@usr.email}}
using the Cloud SIEM - User Investigation dashboard. - Investigate other activities performed by the source IP
{{@network.client.ip}}
using the Cloud SIEM - IP Investigation dashboard. - Investigate the activities that might have been performed by the subject user
{{@Member.UPN}}
after they were assigned the owner privileges. - Begin your organization’s incident response process and investigate.