Prepare Smarter for the PPAN01 Exam

Attack Index is intended to quantify user-centric risk by combining the severity of threats a user is exposed to and the diversity of those threats over time (D). This aligns with how IR prioritizes investigations: a user repeatedly targeted by multiple high-severity threat types (credential phishing + impostor/BEC + malware delivery) represents a higher likelihood of compromise and greater operational risk than a user receiving large volumes of low-risk spam. In Proofpoint SOC workflows, Attack Index helps drive proactive actions—focus investigations on “most attacked” users, increase monitoring, enforce stronger controls (MFA, conditional access), and deliver targeted training interventions for users with risky behavior. VIP status can be used for business-impact prioritization, but it is not the defining calculation factor for “threat burden.” Active Directory group membership may be used for segmentation and reporting but is not the core metric component. The concept is to score what the user is facing in terms of threat intensity and breadth, enabling triage on the People page and supporting escalation decisions when high Attack Index correlates with clicks or delivered accessible threats.

A high-quality incident report captures what the adversary did in a way that enables prevention and detection improvements. Including adversary tactics and techniques (C) is essential because it translates raw artifacts (emails, URLs, headers, click events) into actionable security engineering outcomes: which initial access method was used (credential phishing vs BEC), which impersonation technique (display name, lookalike domain, supplier compromise), what persistence was attempted (mailbox rules/forwarding, OAuth consent), and what objectives were pursued (invoice fraud, data theft, lateral phishing). In Proofpoint-centered IR, mapping tactics and techniques supports targeted control tuning: URL Defense policy, attachment sandboxing, impostor rules, DMARC enforcement, and TRAP automation; it also improves analyst playbooks (what pivots to run next time, what indicators to hunt). The incident response plan (B) is a reference document, not an incident-specific report item. Network diagrams (A) may be helpful in some incidents but are not always relevant for email-led events. Threat landscape reporting (D) is contextual intel, but the report must focus on what occurred in this incident and what to change to reduce recurrence, which is best captured via tactics/techniques.

Attack Index is a user-level risk/burden metric intended to help SOC teams prioritize which people to investigate first based on the amount and severity/diversity of threat activity directed at them (and often their exposure/interaction, depending on module). The report that directly supports that workflow is “Very Attacked People,” which is designed to surface users with the highest Attack Index and concentration of targeted threats. Operationally, this aligns with IR queue management: instead of treating all alerts equally, analysts use user-centric risk ranking to focus on likely compromise candidates (e.g., frequent recipients of credential phishing, repeated exposure to the same campaign, or elevated threat severity). “Top 10 Recipients” is volume-oriented and may include benign bulk mail; “Top 10 Clickers” is behavior-oriented but does not necessarily reflect overall threat burden; and “VIP Activity” is scoped to a subset (VIPs) rather than the complete organization’s risk ranking. In Proofpoint-led IR best practice, this report is commonly used to drive daily standups, assign investigations, and justify proactive account checks (MFA posture, suspicious logins, mailbox rules) for the highest-risk users.

This is a lookalike-domain tactic (C), where the attacker registers a visually similar domain to impersonate a legitimate brand. The deception relies on human pattern recognition: inserting hyphens, swapping characters, or using similar-looking TLDs so recipients perceive the domain as legitimate. In Proofpoint investigations, analysts validate lookalike domains by checking domain age (newly registered), WHOIS/registrar patterns where available, sending infrastructure (new IP ranges, mismatched rDNS), and authentication misalignment (SPF/DKIM/DMARC failures or lack of alignment). Lookalike domains are common in BEC and credential phishing: they enable “near-perfect” spoofing without compromising the real domain. This differs from domain hijacking (compromising a legitimate domain), display-name spoofing (only the visible name is faked), and subdomain takeover (taking control of an orphaned DNS record). For response, analysts often add the lookalike domain to blocklists, tune impostor detection policies, alert targeted recipients, and strengthen DMARC enforcement and brand monitoring to reduce future impersonation success.

This is a lookalike-domain tactic (C), where the attacker registers a visually similar domain to impersonate a legitimate brand. The deception relies on human pattern recognition: inserting hyphens, swapping characters, or using similar-looking TLDs so recipients perceive the domain as legitimate. In Proofpoint investigations, analysts validate lookalike domains by checking domain age (newly registered), WHOIS/registrar patterns where available, sending infrastructure (new IP ranges, mismatched rDNS), and authentication misalignment (SPF/DKIM/DMARC failures or lack of alignment). Lookalike domains are common in BEC and credential phishing: they enable “near-perfect” spoofing without compromising the real domain. This differs from domain hijacking (compromising a legitimate domain), display-name spoofing (only the visible name is faked), and subdomain takeover (taking control of an orphaned DNS record). For response, analysts often add the lookalike domain to blocklists, tune impostor detection policies, alert targeted recipients, and strengthen DMARC enforcement and brand monitoring to reduce future impersonation success.