LoFP LoFP / t1102

t1102

TitleTags
approved third-party applications that use google drive download urls.
authorized runner deployments by devops/platform teams following change management
false positives may be present if ngrok is an authorized utility. filter as needed.
false positives will be present based on organizations that allow the use of ngrok. filter or monitor as needed.
installation via expected/known configuration management tools (reflected mostly as parent process name)
legitimate applications communicating with the \"api.notion.com\" endpoint that are not already in the exclusion list. the desktop and browser applications do not appear to be using the api by default unless integrations are configured.
legitimate applications communicating with the \"googleapis.com\" endpoints that are not already in the exclusion list. this is environmental dependent and requires further testing and tuning.
legitimate applications communicating with the telegram api e.g. web browsers not in the exclusion list, app with an rss etc.
legitimate github self-hosted runner installations on designated ci/cd infrastructure
legitimate publicly shared files from google drive.
legitimate sub processes started by manage engine servicedesk pro
legitimate usage of cloudflared tunnel.
legitimate usage of cloudflared.
legitimate use of ngrok
legitimate use of telegram bots in the company
legitimate use of the localtonet service.
legitimate use of the ngrok service.
legitimate users may subscribe to sns topics for legitimate purposes. ensure that the subscription is authorized before taking action.
new users or roles may legitimately publish messages to sns topics for authorized purposes. ensure that the action is authorized before taking action.
ninite contacting githubusercontent.com
noise and false positive can be seen if the following instant messaging is allowed to use within corporate network. in this case, a filter is needed.
one might need to exclude other internet browsers found in it's network or other applications like ones mentioned above from microsoft defender.
scheduled runner updates or reconfigurations on existing build agents
self-hosted runners that follow expected/known naming patterns
unknown
user activity (e.g. developer that shared and copied code snippets and used the raw link instead of just copy & paste)
web activity that occurs rarely in small quantities can trigger this alert. possible examples are browsing technical support or vendor urls that are used very sparsely. a user who visits a new and unique web destination may trigger this alert when the activity is sparse. web applications that generate urls unique to a transaction may trigger this when they are used sparsely. web domains can be excluded in cases such as these.