You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Options to capture social engineering MFA prompt exhaustion:
Action.social.variety.MFA bombing
Action.social.variety.Brute force (consistently pestering the individual until they take an action, such as Prompt bombing)
-Action.social.variety.Prompt bombing [https://arcticwolf.com/resources/blog/prompt-bomb-uber-hack/]
phil_note: if we use the same term for this as hacking.brute forcing and malware brute force, they'll get aggregated together, even tho they are conceptually different from a protection stand point)
2,3,7 Phishing site + malware password dumper are probably fine to capture using existing social varieties and malware. From a defensive perspective, it makes sense to group these together since they are defended in the same way.
SMS Hijacking (MFA Intercept)
action.hacking.variety.MFA intercept (capturing the secondary factor while in transit such as SMS hijacking)
Intercept may be a good but not interactive (confidentiality loss)
Hijack (Attacker gains the ability to act as the victim and denies it to the victim)
Add:
SIM asset (media? physical?)
hijack action (which categories - hacking)
Social brute force
Multiple Authentication Factor data variety (any credential or other authentication factor in addition to the first)
Coding_style:
intercept actions should be coded as a confidentiality loss of a MFA data variety
transfer an accounts active sim to an attacker controlled device so they can receive the 2nd factor: asset: SIM, data.variety MFA, action hijacking. Likely preceded by a social action.
spamming MFA requests: social.brute force. No data.variety.MFA, but integrity.change behavior.
Currently there isn't a good way of capturing MFA bypass, in which there is a secondary action that is leveraged to bypass MFA.
Here are the types of attacks that are known:
Potentially out of scope
The text was updated successfully, but these errors were encountered: