LoFP LoFP / t1566

t1566

TitleTags
all kind of software downloads
all kinds of software downloads
business workflows that occur very occasionally, and involve a business relationship with an organization in a country that does not routinely appear in network events, can trigger this alert. a new business workflow with an organization in a country with which no workflows previously existed may trigger this alert - although the model will learn that the new destination country is no longer anomalous as the activity becomes ongoing. business travelers who roam to many countries for brief periods may trigger this alert.
cases in which a user mounts an image file for legitimate reasons
developers testing new applications or oauth flows in non-production tenants may generate alerts during development cycles.
file located in the appdata folder with trusted signature
google workspace users typically share drive resources with a shareable link where parameters are edited to indicate when it is viewable or editable by the intended recipient. it is uncommon for a user in an organization to manually copy a drive object from an external drive to their corporate drive. this may happen where users find a useful spreadsheet in a public drive, for example, and replicate it to their drive. it is uncommon for the copied object to execute a container-bound script either unless the user was intentionally aware, suggesting the object uses container-bound scripts to accomplish a legitimate task.
initial sso configuration issues or first-time federation setup errors for legitimate users may trigger this detection. temporary federation service outages affecting multiple users simultaneously.
legitimate automation, sdks, or custom applications that obtain tokens through the microsoft authentication broker against graph, azure ad, or device registration service may use non-browser user agents. baseline approved service principals, managed identities, and developer tooling before tuning exclusions for known automation patterns.
legitimate cases in which archives contain iso or img files and the user opens the archive and the image via clicking and not extraction
legitimate device registrations using microsoft authentication broker may occur during corporate enrollment scenarios or bulk provisioning, but it is uncommon for multiple source ips to register the same identity across microsoft graph, device registration service (drs), and azure active directory (aad) in a short time span.
legitimate files reported by the users
legitimate macro files downloaded from the internet
legitimate macro files sent as attachments via emails
legitimate node.js or undici-based automation, health checks, or internal services that use the microsoft authentication broker or the same first-party application ids against graph or exchange may match. developers using axios or undici with delegated flows can also resemble this pattern.
legitimate usage of hdiutil by administrators and users.
legitimate use of device code flow where a user authenticates via browser for a cli tool or headless application. common legitimate scenarios include azure cli, azure powershell, or vs code remote development. review the user agent combinations - browser + known cli tool from the same user may be expected behavior.
legitimate used of encrypted zip files
legitimate users may have to use ssm to perform actions against machines in the cloud to update or maintain them
new legitimate applications or integrations recently deployed in the environment may trigger this detection during initial setup or rollout phases.
opening of headers or footers in email signatures that include svg images or legitimate svg attachments
organizations that use azure monitor alert rules with financial or billing related naming conventions for legitimate infrastructure monitoring may trigger this rule. review the email subject and recipient to determine if the alert originates from a known internal azure subscription.
potential fp by sysadmin opening a zip file containing a legitimate iso file
rare legitimate interactive device code flows that use the microsoft authentication broker against exchange, graph, or yammer may match, for example during troubleshooting or specialized kiosk setups. document approved scenarios and exclude known principals or networks.
security researchers, sandbox detonations, or red team engagements that intentionally run the kali365 client against a monitored tenant may generate this user agent. document approved research activity and exclude the associated principals, source ips, or tenants if expected.
signals are generated by microsoft defender for office 365. false-positives may occur if legitimate user activity is misclassified as a threat.
software installation iso files
there are legitimate uses of ssm to send commands to ec2 instances
third-party saas applications with sharepoint integration may appear as new app ids when users first authorize access.
this will alert on legitimate macro usage as well, additional tuning is required
unknown
unlikely
users authenticating from multiple devices and using the devicecode protocol or the visual studio code client.
users enrolling or joining devices while on corporate vpns, consumer vpns, or cloud egress that map to the listed asns may match. legitimate mobile device management or bulk provisioning that uses the broker against device registration service from the same networks can also trigger alerts. baseline `source.as.organization.name` and successful broker-to-drs sign-ins before tuning exclusions for approved asns or user groups.
users on vpns, carrier nat, or cloud egress that map to flagged asns may match. legitimate bulk enrollment or scripted onboarding that uses the same oauth client can also produce the sequence. baseline `source.as.organization.name` and successful registration sources before adding exclusions.
very common in environments that rely heavily on macro documents
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.