LoFP LoFP / t1528

t1528

TitleTags
false positives may occur if users are granting consents as part of legitimate application integrations or setups. it is crucial to review the application and the permissions it requests to ensure they align with organizational policies and security best practices.
in most organizations, device code authentication will be used to access common microsoft service but it may be legitimate for others. filter as needed.
it's recommended that you rotate your access keys periodically to help keep your storage account secure. normal key rotation can be exempted from the rule. an abnormal time frame and/or a key rotation from unfamiliar users, hosts, or locations should be investigated.
microsofts algorithm to identify risky applications is unknown and may flag legitimate applications.
oauth applications that require file permissions may be legitimate, investigate and filter as needed.
oauth applications that require mail permissions may be legitimate, investigate and filter as needed.
this detection is low-volume and is seen infrequently in most organizations. when this detection appears it's high risk, and users should be remediated.
unlikely
update_known_false_positives
users may deny consent for legitimate applications by mistake, filter as needed.
verify whether the user identity, user agent, and/or hostname should be using getsecretstring api for the specified secretid. if known behavior is causing false positives, it can be exempted from the rule.
we recommend investigating the sessions flagged by this detection in the context of other sign-ins from the user.
when and administrator is making legitimate uri configuration changes to an application. this should be a planned event.
when the permission is legitimately needed for the app