A is what makes sense here. The main use of lookup tables in Cortex XDR is to bring in extra info from outside sources (like threat intel or asset lists) and match it up with your internal logs. Not really for running playbooks or making reports directly. Pretty sure that's correct, unless Palo's changed something lately.
I see why B looks good if you're thinking automation, but XDR remediation suggestions are usually vendor-agnostic patching steps, so A fits. Haven't seen auto-delete get recommended like that. Anyone else getting a different vibe?
B for sure. Starring is just a way to visually mark an alert as important so analysts remember to look at it later. It doesn't auto-resolve, recalc severity, or merge anything. Unless they've added some new automation, I'm pretty confident it's still just a flag for importance-correct me if I'm missing something.
Kinda nitpicky but if you had a playbook that auto-stars certain alerts, doesn't it still just mean it's marked important for the analyst? So B is right as long as starring doesn't trigger other automations tied to the alert itself. Pretty sure that's the current behavior but open to correction.
I’m wondering, if the question used the term “remediation” instead of “forensic investigation”, would C or D make sense? Feels like changing firewall rules or incident scores is more remediation than forensics. What do others think?
Tricky wording! Forensic investigation usually means evidence analysis, so A and B make sense. If the question asked about containment or response, then maybe C or D could be considered, but that's not the case here. Pretty sure it's A/B unless Palo Alto changes their definition of forensic in documentation. Disagree?
Actually, I'd say C. The Query Library should help with scheduling reports, right? I remember reading something about automating that process in practice questions. Not totally certain but C feels like a decent pick here.
A and B. Query Library's main perks are saving and sharing queries, not automating reports or making incidents. C is tempting but that's handled elsewhere in XDR, not the Library itself. If anyone's seen scheduling as a direct library feature let me know, but pretty sure that's a common trap here.