t1110 | LoFP

t1110

Title	Tags
a legitimate application that has been deleted from the tenant while a client continues to authenticate against its former client id via ropc can generate error code 700016. a misconfigured legacy client submitting an incorrect client id is also possible. in both cases the client id is typically stable and low-volume, unlike the many distinct or randomized identifiers seen in spoofing. verify the application identifier, the source infrastructure, and whether the same principal is targeted by many different unresolved client ids.	t1087 t1110 azure elastic
a misconfigured service account can trigger this alert. a password change on an account used by an email client can trigger this alert. security test cycles that include brute force or password spraying activities may trigger this alert.	t1110 ml elastic
a user experiencing legitimate login issues (forgotten password, typos) may trigger credential attack alerts before successfully authenticating.	t1078 t1110 okta elastic
a user experiencing login issues may generate multiple device tokens through repeated legitimate attempts.	t1110 okta elastic
account fallback reasons (after failed login with specific account)	t1110 t1110.001 windows sigma
an okta admnistrator may be logged into multiple accounts from the same host for legitimate reasons.	t1078 t1110 okta elastic
automated monitoring or penetration testing tools scanning from multiple ips.	t1110 okta elastic
automated password reset flows where a user fails multiple times then succeeds after resetting their password.	t1078 t1110 okta elastic
automated processes or misconfigured applications retrying authentication may trigger this rule.	t1110 okta elastic
automated processes that attempt to authenticate using expired credentials or have misconfigured authentication settings may lead to false positives.	t1110 _deprecated azure elastic
automated testing or monitoring tools that do not persist cookies may trigger this rule.	t1110 okta elastic
based on the high-frequency threshold, it would be unlikely for a legitimate user to exceed the threshold for failed totp code attempts in a short time-span over multiple sessions.	t1110 azure elastic
build servers and ci systems can sometimes trigger this alert. security test cycles that include brute force or password spraying activities may trigger this alert.	t1078 t1110 ml elastic
corporate proxy or vpn exit nodes may aggregate traffic from multiple legitimate users.	t1110 okta elastic
expected red team assessments or penetration tests may utilize teamfiltration to evaluate the security posture of azure or microsoft 365 environments. if this is expected behavior, consider adjusting the rule or adding exceptions for specific ip addresses, registered applications, jwt tokens, prts or user	t1069 t1082 t1087 t1110 t1201 t1526 t1580 T1673 azure elastic
known legacy accounts	t1078 t1078.004 t1110 azure sigma
large enterprises with many users experiencing simultaneous password issues during credential rotation events.	t1110 okta elastic
legitimate administrative or security assessment activities may use these user-agents, especially in environments where teamfiltration is employed for authorized audits. if this is expected behavior, consider adjusting the rule or adding exceptions for specific user-agents or ip addresses.	t1069 t1082 t1087 t1110 t1201 t1526 t1580 T1673 azure elastic
legitimate failed login attempts by authorized users. investigate the source of repeated failed login attempts.	t1110 aws sigma
legitimate or intentional inbound connections from public ip addresses on the rdp port.	t1078 t1110 t1133 windows sigma
legitimate user wrong password attempts.	t1021 t1021.004 t1078 t1078.004 t1110 bitbucket sigma
misconfigured phones, expired credentials, or provisioning errors can generate repeated register failures from a single device. validate the client, affected extensions, and registration state before escalating.	t1110 network elastic
misconfigured systems	t1078 t1078.004 t1110 azure sigma
security audits may trigger this alert. conditions that generate bursts of failed logins, such as misconfigured applications or account lockouts could trigger this alert.	t1110 ml elastic
service account misconfigured	t1078 t1078.004 t1110 azure sigma
shared egress addresses, managed service providers, help desks, identity-provider outages, password rotation, or several legitimate users entering incorrect credentials before another user successfully authenticates may trigger this rule. add exceptions only for confirmed shared-service sources and scope them to the relevant appliance.	t1078 t1110 t1133 network elastic
shared service accounts accessed from multiple legitimate infrastructure ips.	t1110 okta elastic
shared systems such as kiosks and conference room computers may be used by multiple users.	t1078 t1110 okta elastic
shared systems such as kiosks or conference room computers may have multiple users authenticating.	t1110 okta elastic
software that uses the caret encased keywords pass and user in its command line	t1110 t1110.001 windows sigma
systems with names equal to the spoofed ones used by the brute force tools	t1110 windows sigma
this event could stem from users changing an account's password that's used to authenticate via a job or an automated process. investigate the source of such events and mitigate them	t1110 windows sigma
tools that use similar command line flags and values	t1110 t1110.002 windows sigma
unknown	t1003 t1003.001 t1003.002 t1003.003 t1003.004 t1003.006 t1005 t1008 t1010 t1012 t1018 t1020 t1021 t1021.001 t1021.002 t1021.003 t1021.005 t1021.006 t1027 t1027.001 t1027.003 t1027.004 t1027.005 t1027.009 t1027.010 t1033 t1036 t1036.003 t1036.005 t1036.007 t1040 t1046 t1047 t1048 t1048.003 t1049 t1053 t1053.002 t1053.005 t1055 t1055.001 t1055.003 t1055.009 t1055.011 t1055.012 t1056 t1056.001 t1057 t1059 t1059.001 t1059.002 t1059.003 t1059.004 t1059.005 t1059.006 t1059.007 t1068 t1069 t1069.001 t1069.002 t1069.003 t1070 t1070.003 t1070.004 t1070.005 t1070.006 t1071 t1071.001 t1071.004 t1072 t1074 t1074.001 t1078 t1078.001 t1078.002 t1078.003 t1078.004 t1082 t1083 t1087 t1087.001 t1087.002 t1087.004 t1090 t1090.001 t1090.003 t1095 t1098 t1102 t1102.001 t1102.003 t1105 t1106 t1110 t1110.001 t1112 t1113 t1114 t1114.001 t1115 t1119 t1123 t1127 t1127.001 t1133 t1134 t1134.001 t1134.002 t1134.003 t1135 t1136 t1136.001 t1136.002 t1137 t1137.002 t1137.006 t1140 t1176 t1176.001 t1185 t1187 t1190 t1195 t1195.001 t1197 t1199 t1200 t1201 t1202 t1203 t1204 t1204.001 t1204.002 t1204.004 t1207 t1210 t1211 t1212 t1216 t1216.001 t1217 t1218 t1218.001 t1218.002 t1218.003 t1218.005 t1218.007 t1218.009 t1218.010 t1218.011 t1218.013 t1219 t1219.002 t1220 t1222 t1222.001 t1482 t1484 t1485 t1486 t1489 t1490 t1491 t1491.001 t1497 t1497.001 t1498 t1499 t1499.004 t1505 t1505.003 t1505.004 t1518 t1518.001 t1526 t1528 t1529 t1531 t1537 t1539 t1543 t1543.001 t1543.003 t1543.004 t1546 t1546.001 t1546.002 t1546.003 t1546.007 t1546.008 t1546.009 t1546.010 t1546.011 t1546.012 t1546.015 t1547 t1547.001 t1547.003 t1547.004 t1547.005 t1547.006 t1547.008 t1547.009 t1547.010 t1548 t1548.002 t1552 t1552.001 t1552.002 t1552.004 t1552.006 t1553 t1553.004 t1554 t1555 t1555.003 t1555.004 t1555.005 t1556 t1556.002 t1557 t1557.001 t1557.003 t1558 t1558.003 t1559 t1559.001 t1559.002 t1560 t1560.001 t1563 t1563.002 t1564 t1564.001 t1564.002 t1564.003 t1564.004 t1565 t1566 t1566.001 t1566.002 t1567 t1567.002 t1569 t1569.002 t1571 t1572 t1573 t1574 t1574.001 t1574.005 t1574.006 t1574.008 t1574.011 t1584 t1587 t1587.001 t1588 t1588.001 t1588.002 t1593 t1593.003 t1595 t1608 t1609 t1611 t1614 t1614.001 t1615 t1620 t1621 t1649 t1685 t1685.001 t1685.005 t1686 t1686.003 rpc_firewall kubernetes onelogin okta cisco zeek linux azure m365 gcp aws windows macos sigma
unlikely. except due to misconfigurations	t1078 t1110 t1557 cisco huawei juniper sigma
user has been put in acception group so they can use legacy authentication	t1078 t1078.004 t1110 azure sigma
users accessing their accounts from anonymized ip addresses, such as vpns or tor, may trigger this rule. if this is expected behavior in your environment, consider adjusting the rule or adding exceptions for specific users or ip ranges.	t1071 t1078 t1110 t1556 azure elastic
users actually login but miss-click into the deny button when mfa prompt.	t1078 t1078.004 t1110 t1621 azure sigma
users may share an endpoint related to work or personal use in which separate okta accounts are used.	t1078 t1110 okta elastic
users who frequently travel or access their accounts from different geographic locations may trigger this rule due to the unlikely travel detection mechanism. if this is expected behavior, consider adjusting the rule or adding exceptions for specific users.	t1071 t1078 t1110 t1556 azure elastic
users who have recently changed their passwords may trigger this rule due to the password spray detection mechanism. if this is expected behavior, consider adjusting the rule or adding exceptions for specific users.	t1071 t1078 t1110 t1556 azure elastic
users with legitimate multi-location access (mobile + home + office) experiencing concurrent login issues.	t1110 okta elastic
vulnerability scanners	t1078 t1078.004 t1110 t1190 t1505 t1505.001 azure sigma
we recommend investigating the sessions flagged by this detection in the context of other sign-ins from the user.	t1078 t1090 t1098 t1110 t1528 t1606 azure sigma