I remember practicing a question similar to this, and I think IP addresses from the header are definitely included. They help trace the origin of the email.
I feel pretty confident about the first three options - URLs/domains, who reported it, and IP addresses from the header. The other ones seem a bit more ambiguous.
Okay, let's see... URLs, domains, and IP addresses in the body seem like a safe bet. And the person who reported the phishing attempt would definitely be important to track.
Hmm, this looks like a tricky one. I'll need to think carefully about the types of observables that could be stored in the Security Phishing Email record.
Hmm, I'm not sure about F. Wouldn't that just be internal information for the security team? I'd focus on the external indicators that could help identify the phishing source.
Ha! I bet the security team would also want to know the 'state of the phishing email' - you know, like if it was opened, clicked, or forwarded. That's a good one, C!
A, D, and E for sure. I mean, that's the basic info you'd want to capture, right? The URLs, IPs, and file hashes could be clues to the source of the phishing attack.
Kallie
3 months agoVirgilio
4 months agoBronwyn
4 months agoBok
4 months agoClorinda
4 months agoDenae
5 months agoDorsey
5 months agoElmira
5 months agoHannah
5 months agoXuan
5 months agoHelaine
5 months agoLyndia
5 months agoAdelle
5 months agoHerminia
5 months agoArt
1 year agoLorrine
1 year agoYolande
1 year agoAmber
1 year agoCarissa
1 year agoLucia
1 year agoDevora
1 year agoJamika
1 year agoBrittney
1 year agoErick
1 year agoWilda
1 year agoLatanya
1 year agoAnastacia
2 years agoSolange
1 year agoLigia
1 year agoLeontine
1 year ago