A rapidly growing e-commerce company wants to implement a SIEM solution to improve its security posture and comply with PCI DSS requirements. They need a solution that offers both the necessary technological features and the expertise to manage the system effectively. They also need continuous compliance support and data security assistance. Which SIEM solution is appropriate for this company?
Answer(s): C
A managed SIEM provides both the technology platform and the operational expertise to run it effectively, which aligns with the company's need for features plus ongoing management, compliance support, and security assistance. Rapidly growing organizations often struggle to staff SIEM engineering, content tuning, and 24/7 monitoring internally. Managed SIEM offerings typically include onboarding data sources, maintaining parsers, tuning detections, handling alert triage, producing compliance reports, and advising on remediation--capabilities that directly support PCI DSS requirements and continuous audit readiness. A cloud-based SIEM is a deployment model and can be part of the answer, but it does not guarantee expert management or compliance support unless paired with a managed service. An in-house SIEM requires building and maintaining internal expertise, which conflicts with the stated need for external expertise and continuous support. "Security analytics" is a capability category, not a full SIEM solution model. From a SOC operations standpoint, managed SIEM reduces time-to-value, improves alert quality through professional tuning, and provides consistent reporting and operational coverage without needing the company to immediately build a mature internal SOC function.
A multinational cybersecurity firm wants to enhance its threat intelligence capabilities by integrating real-time threat feeds into Microsoft Sentinel. These feeds include malicious IPs, domains, file hashes, and attack patterns. The firm requires a standardized protocol that allows automated threat intelligence sharing so Sentinel continuously receives updated indicators from external sources in a structured format. Which Microsoft Sentinel data connector should be implemented to integrate threat intelligence feeds using an industry-standard protocol?
TAXII (Trusted Automated eXchange of Indicator Information) is an industry-standard protocol for automated threat intelligence transport, commonly used alongside STIX-formatted threat data. The question explicitly requires a standardized protocol to automate sharing and continuously import structured threat indicators into Sentinel. The TAXII data connector is designed for this purpose: it enables pulling indicator data from TAXII servers so that malicious IPs, domains, and hashes can be ingested and used in detection and enrichment workflows. Syslog is a logging transport protocol for device and system logs, not threat intel sharing. Microsoft Defender for Cloud (Legacy) is unrelated to ingesting external threat feeds via a standardized intel protocol. The "Threat Intelligence Platforms" connector can be used to integrate certain TI sources, but the question specifically calls out using an industry-standard protocol for automated sharing, which is TAXII . From a SOC analyst perspective, using TAXII supports consistent ingestion, reduces manual indicator handling, and improves correlation by allowing Sentinel analytics rules and playbooks to leverage the latest indicators at scale.
Sarah, a financial analyst at a multinational corporation, is suspected of leaking sensitive financial data to an unauthorized external party. The SOC team observed anomalous data transfer patterns originating from her account, flagged by the SIEM, indicating potential data exfiltration. The incident response team must contain the incident swiftly to minimize data loss and protect critical assets. As a SOC analyst, which should be prioritized as the initial containment measure?
Answer(s): A
Initial containment for suspected data exfiltration by a specific user account should prioritize immediately restricting that account's ability to access and transfer data. "Access control" is the broad containment category that includes disabling the account, suspending sessions, revoking tokens, removing access to sensitive shares, and applying conditional access blocks. This is the fastest way to stop ongoing data loss while preserving evidence for investigation. "Change passwords regularly" is a general security hygiene practice, not an initial incident containment action, and it may not stop exfiltration quickly if active sessions or tokens remain valid. "Isolate the storage" can be appropriate if a particular repository is being actively exfiltrated, but it can be disruptive to business operations and may not address the actor's continued access paths across other systems. DCAP is a programmatic capability for monitoring and controlling data access over time; it is valuable, but it is not the immediate first step when the SOC must rapidly stop suspected exfiltration. From a SOC playbook view, the initial action is to reduce attacker/insider access immediately (account restriction), then scope what data was accessed, preserve logs, and coordinate with HR/legal for insider procedures.
A SOC team at a major financial institution detects unauthorized access attempts on its web application. Logs indicate the web application is compromised. To determine the exact attack technique and implement mitigation, forensic investigators assess cookie attributes (such as HttpOnly, Secure, and SameSite) for security weaknesses and track anomalous request patterns that deviate from normal user behavior. Which attack vector is the forensic team investigating?
The focus on cookie attributes (HttpOnly, Secure, SameSite) strongly aligns with session security and session integrity. These attributes are designed to protect session cookies from being stolen or misused: HttpOnly limits JavaScript access to cookies, Secure restricts cookies to HTTPS, and SameSite reduces cross-site request risks. When investigators assess these settings, they are often evaluating whether session tokens could be manipulated, injected, fixed, or abused--behaviors consistent with session poisoning and related session attacks. While XSS can be used to steal cookies, the investigation described is not centered on injected script payloads in application responses; it is centered on cookie security posture and abnormal request patterns tied to sessions. SQL injection is primarily about manipulating database queries and would be investigated through query-related payloads and database error patterns rather than cookie attribute review. MITM attacks can intercept session cookies if transport security is weak, but the question emphasizes cookie attribute weaknesses and anomalous session request patterns--more directly associated with session poisoning/session hijacking analysis. In SOC response, confirming session attack vectors typically leads to rotating session secrets, invalidating active sessions, tightening cookie flags, enforcing TLS, and adding anomaly detection for session token reuse and impossible travel.
David is a SOC analyst responsible for monitoring critical infrastructure. He detects unauthorized applications running on a high-privilege Windows server accessible only by a restricted set of users. The applications were not part of approved deployments, and installations occurred outside business hours. Logs indicate potential system configuration changes around the same timeframe. Which log should he examine to determine when and how these installations occurred?
The Setup event log is the most relevant Windows log for installation activity because it captures events related to software installation, servicing, and setup operations. For unauthorized application installs, the SOC needs timing, installer context, and evidence of package deployment or configuration changes driven by setup processes. The Setup log can contain MSI and update-related events, component installation records, and indications of system changes tied to installation workflows. The Security log is crucial for attribution (logons, privilege use, process creation if enabled), but it is not specifically focused on installer actions and may not capture full installation details unless advanced auditing is configured. The System log focuses on OS-level service and driver events (boot, service start/stop, hardware/driver issues) and may show related changes but is not the primary installation record. The Application log captures events written by applications themselves, which is inconsistent for installer tracing. In SOC practice, analysts often combine Setup log evidence with Security log context (who logged on, elevated rights, process lineage) and endpoint telemetry to identify the actor and technique, but the best single log for "when and how installs occurred" among these options is the Setup event log.
In a large corporation, the HR department receives an urgent email from someone impersonating a high-level executive, requesting immediate transfer of sensitive employee data. The email includes an official-looking document and a phone number for verification. Feeling pressured, the HR manager calls the number and "confirms" the request, then transfers the data. Investigation later confirms the email was fraudulent and the executive had no knowledge of the request. What type of attack did the HR department face?
This is a social engineering attack because the adversary manipulated human trust and urgency to induce an unauthorized action: the transfer of sensitive employee data. The attacker used impersonation, authority pressure (executive pretext), and a controlled "verification" channel (the attacker's phone number) to make the request appear legitimate. These are hallmark social engineering techniques, and in many organizations this is categorized under business email compromise (BEC) or executive impersonation fraud. Credential theft is not the primary outcome described; the attacker did not need passwords if they could convince HR to release data directly. Web-based intrusion and application exploit refer to technical exploitation of systems, which is not indicated. From a SOC response perspective, handling social engineering incidents includes immediate containment (stop further transfers, notify legal/HR, preserve email evidence), scoping who else received similar requests, and implementing process controls: out-of-band verification using known trusted channels, call-back procedures, dual approval for sensitive requests, and training to recognize urgency-based manipulation. Therefore, "Social engineering attack" is the correct classification.
A healthcare organization's SIEM detects unusual HTTP requests targeting its patient portal. The requests originate from a foreign IP address and occur during non-business hours. The methods used are primarily TRACE and OPTIONS, which are rarely seen in normal web traffic. The SIEM correlates these with increased reconnaissance activity on other servers within the same subnet. What is the primary security concern with TRACE and OPTIONS requests?
TRACE and OPTIONS are often associated with reconnaissance because they can reveal how a server is configured and what capabilities it supports. OPTIONS can disclose which HTTP methods are allowed (GET, POST, PUT, DELETE, etc.), helping attackers identify whether risky methods are enabled or misconfigured. TRACE can be abused to reflect request headers back to the client, which may expose sensitive header information in certain misconfigurations and historically has been associated with cross-site tracing risks. In SOC investigations, unusual usage of TRACE/OPTIONS--especially from foreign IPs and outside business hours--often indicates probing to map the attack surface before selecting an exploit path. Uploading payloads is more associated with PUT/POST to vulnerable endpoints, not primarily TRACE/OPTIONS. DDoS facilitation is not a primary characteristic of these methods. Authentication bypass is not an inherent feature of TRACE/OPTIONS; attackers still need a separate vulnerability to bypass auth. Because the question asks for the primary concern, the best answer is that these methods can reveal supported methods and header behavior, increasing attacker knowledge and enabling follow-on exploitation attempts.
A security analyst in a multinational corporation's Threat Intelligence team is tasked with enhancing detection of stealthy malware infections. During an investigation, the analyst observes an unusually high volume of DNS requests directed toward domains that follow patterns commonly associated with Domain Generation Algorithms (DGAs). Recognizing that these automated domain queries could indicate malware attempting to establish communication with command-and-control (C2) infrastructure, the analyst realizes existing detection may be insufficient. The security team needs to define intelligence requirements, including identifying critical data sources, refining detection criteria, and improving monitoring strategies. Which stage of the Cyber Threat Intelligence (CTI) process does this align with?
Answer(s): B
This scenario aligns with requirement analysis because the team is defining what intelligence is needed and how it should be collected and used. The analyst has observed a problem (possible DGA-based malware activity) and recognizes gaps in current detection. The next step in a CTI lifecycle is to translate that concern into actionable intelligence requirements: which telemetry sources are necessary (DNS logs, proxy logs, endpoint telemetry, threat intel on DGA families), what questions must be answered (which hosts, what domains, what patterns, what time windows), and what success criteria look like (detection thresholds, false positive tolerance, enrichment needs). This is the "direction" phase of CTI, where priorities are set and collection needs are specified to ensure intelligence efforts align to threats that matter. "Filtering CTI" would be about reducing noise in collected intelligence or refining feeds after collection. "Intelligence buy-in" is stakeholder alignment and program support, not the analytic definition of requirements. "Automated tool" is not a CTI lifecycle stage. From a SOC perspective, requirement analysis is critical to turn observations into structured detection and hunting objectives that can be measured and improved.
Post your Comments and Discuss EC-Council 312-39v2 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the 312-39v2 content, but please register or login to continue.