Jackson & Co., a mid-sized law firm, is concerned about web-based cyber threats. The IT team implements a solution that serves as an intermediary for all HTTP and HTTPS requests. This allows the SOC to inspect, filter, and control web traffic to detect and block malicious websites, phishing attempts, and other online threats before they reach users. Which containment method is the organization using to gain visibility and control over web traffic?
Answer(s): D
A proxy server acts as an intermediary between users and the internet, routing HTTP/HTTPS requests through a controlled inspection point. This provides visibility (who accessed what, when, from which device) and enables enforcement (block categories, block malicious destinations, inspect headers, apply SSL/TLS inspection where permitted, and enforce acceptable-use policies). While web content filtering is often a feature implemented through proxies or secure web gateways, the question explicitly describes an "intermediary for all HTTP and HTTPS requests," which is the defining characteristic of a proxy. Whitelisting and blacklisting are policy methods (allow/deny lists) that can be applied within a proxy or firewall, but they are not the architectural containment method described. From a SOC containment standpoint, proxying enables rapid response actions: block newly observed malicious domains/URLs, monitor for beaconing, and prevent users from reaching phishing infrastructure. It also supports investigations by providing centralized web activity logs for correlation with endpoint and identity telemetry. Therefore, the correct option is proxy servers.
A financial services company implements a SIEM solution to enhance cybersecurity. Despite deployment, it fails to detect known attacks or suspicious activities. Although reports are generated, the team struggles to interpret them. Investigation shows that critical logs from firewalls, IDS, and endpoint devices are not reaching the SIEM. What is the reason the SIEM is not functioning as expected?
Answer(s): A
If critical logs are not reaching the SIEM, the most direct root cause is an architectural or configuration failure in the SIEM deployment. A SIEM's detection capability depends on ingesting the right telemetry from key control points (network, endpoint, identity, cloud). Missing firewall, IDS, and endpoint logs creates blind spots that will prevent detections from firing, even for well-known attacks, because the SIEM simply lacks the required evidence. This commonly happens due to misconfigured collectors/agents, incorrect forwarding rules, blocked network paths, wrong ports/protocols, parsing failures, certificate/auth issues, or incomplete onboarding of data sources. While lack of SIEM knowledge can affect tuning and interpretation, it does not explain missing log delivery. Volume-handling issues typically show up as ingestion throttling, dropped events, or delayed indexing after logs are onboarded--not as a complete absence of critical sources. Performance delays can degrade detection timeliness, but again the scenario states the logs are not reaching the SIEM at all. From a SOC engineering standpoint, the first troubleshooting steps are data pipeline validation (connectivity, agent health, message counts), ingestion dashboards, and source- side forwarding verification. Therefore, improper configuration or deployment architecture is the correct reason.
During a routine security audit, analysts discover several web servers still use a vulnerable third- party library flagged for a zero-day exploit. The vulnerability was identified previously and patches were deployed, but the application team rolled back patches due to instability and compatibility issues. The vulnerability remains unaddressed, and no alternative mitigations are in place. How should the security team classify this risk in the context of web application security?
Answer(s): C
This is best classified as "Vulnerable and outdated components" because the organization is knowingly running a third-party library with a known exploitable vulnerability and has rolled back the available fix. In web application security, third-party dependencies are a major risk driver because attackers routinely target widely used frameworks and libraries, especially when exploit code becomes available or active exploitation is observed. Even if the rollback was motivated by stability, leaving the vulnerable component in production without compensating controls (WAF rules,disabling vulnerable functionality, strict input validation, segmentation) maintains high risk. Software and data integrity failures would focus on unauthorized changes or untrusted code deployment; the issue here is the presence of a known vulnerable dependency. Security logging/monitoring failures refer to insufficient visibility, not the root exposure. Insecure design refers to architectural weaknesses built into the application; while dependency management can be part of secure design, the immediate classification is the vulnerable component itself. From a SOC perspective, this classification drives remediation: prioritize patch-compatible fixes, upgrade dependency versions, implement compensating controls until patching is possible, and improve change management to prevent security rollback without risk acceptance and mitigation.
At 10:30 AM, during routine monitoring, Tier 1 SOC analyst Jennifer detects unusual network traffic and confirms an active LockBit ransomware infection targeting systems in the finance department. She escalates to the SOC lead, Sarah, who activates the Incident Response Team (IRT) and instructs the network team to isolate the finance department's VLAN to prevent further spread across the network. Which phase of the Incident Response process is currently being implemented?
Isolating the finance department's VLAN is a classic containment action. Containment focuses on limiting spread, stopping additional damage, and preventing further compromise while the team stabilizes the environment. In ransomware incidents, rapid segmentation and isolation can prevent lateral movement, reduce the number of encrypted systems, and preserve critical services. The scenario shows escalation to leadership, activation of the IRT, and immediate network isolation--all consistent with containment. Eradication would come next and involves removing ransomware artifacts, closing exploited vulnerabilities, eliminating persistence mechanisms, and ensuring the threat cannot return. Evidence gathering and forensic analysis may occur in parallel after containment, especially to preserve volatile evidence, but the central action described is isolation to stop spread. Notification involves informing stakeholders (legal, leadership, regulators) and is not the primary activity described. From a SOC playbook standpoint, containment is often the first priority once ransomware is confirmed because time is critical: every minute of uncontrolled spread increases operational and financial impact. Therefore, the current phase is containment.
You are a SOC analyst at a leading financial institution tasked with developing a comprehensive threat model to safeguard critical assets: sensitive customer data, online banking applications, and real-time payment processing systems. The organization has observed increased targeted attacks on financial entities, including credential theft, account takeovers, and sophisticated phishing. Senior management is concerned about long-term financial and reputational damage. You need intelligence providing insights into high-level risks, geopolitical threats, and emerging cybercriminal strategies with long-term implications for security posture. Which type of threat intelligence are you seeking?
Strategic threat intelligence is aimed at executive and program-level decision-making. It focuses on high-level risk trends, geopolitical drivers, adversary motivations, target selection, and emerging threat landscapes that influence long-term security posture and investment priorities. The question emphasizes senior management concerns, long-term implications, and broad risks affecting financial institutions--hallmarks of strategic intelligence. Technical intelligence is focused on specific indicators (IPs, domains, hashes) and technical artifacts for immediate detection. Tactical intelligence focuses on adversary tactics, techniques, and procedures (TTPs) that help defenders improve detections and controls. Operational intelligence is more immediate, relating to current campaigns, adversary capabilities, and near-term targeting information used for active defense and incident response. While tactical and operational intelligence are valuable for SOC detections and playbooks, the requirement here is "high-level risks and long-term implications," which maps most directly to strategic threat intelligence.
A security team is configuring a newly deployed SIEM system. With limited resources, they must prioritize monitoring scenarios that provide the greatest security benefit. The team understands an effective SIEM relies on well-defined use cases tailored to the organization's environment. Which factor should guide their selection of use cases?
Use cases should be selected based on the availability and quality of data because detections cannot work without reliable telemetry. In SOC engineering, the first constraint is data: what sources exist, how complete they are, how quickly they arrive, and whether fields are parsable and consistent. Choosing use cases that your environment can actually support produces faster time-to-value, fewer false positives, and fewer blind spots. Prioritizing "zero-day" use cases is too vague and often unrealistic, because zero-days vary widely and require strong behavioral telemetry and baselines. Implementing as many use cases as possible spreads resources thin and increases noise, creating alert fatigue. Compliance-driven use cases are important, but if the underlying data is missing or poor quality, compliance rules will still fail operationally and can create a false sense of security. A mature approach is: start with high-value, high-feasibility detections that match available data (identity compromise, suspicious admin actions, endpoint malware, critical network anomalies), then expand as data coverage improves. Therefore, data availability and quality should guide initial use case selection.
The SOC team at GlobalTech has finished patching a critical vulnerability exploited during a ransomware attack. The team is now restoring 2.3 TB of encrypted data from their Veeam backup system, rebuilding 23 compromised workstations identified through SIEM logs, and re-enabling network access for the finance department after validating systems are clean. Which Incident Response phase is this?
This activity is Recovery because it focuses on restoring systems and business operations to a normal, trusted state after the threat has been contained and eradicated. Restoring encrypted data from backups, rebuilding compromised workstations, and re-enabling network access are all recovery tasks. The key objective in recovery is to return services safely while ensuring the environment is clean and stable--hence validation steps before reconnecting systems to production networks. Containment would have occurred earlier and would include isolating affected VLANs/hosts and stopping spread. Eradication would include removing ransomware artifacts, closing persistence, patching vulnerabilities (which the scenario says has already been done), and ensuring the attacker cannot regain access. Post-incident activities occur after recovery and include lessons learned, reporting, process improvements, and control updates. From a SOC operational standpoint, recovery is often the most resource-intensive phase because it requires coordination between security, IT operations, application owners, and business units to restore systems, verify integrity, and monitor for reinfection. Because the scenario is explicitly about restore/rebuild and safe return-to-service, the correct phase is recovery.
A large financial organization has experienced an increase in sophisticated cyber threats, including zero-day attacks and APTs. Traditional detection relies heavily on signatures and manual intervention, causing delays. The CISO is exploring AI-driven solutions that can automatically analyze large datasets, detect anomalies, and adapt to evolving threats in real time--identifying suspicious activity without predefined signatures and with minimal human oversight. Which key AI technology should the organization focus on?
Answer(s): B
Machine learning is the key AI technology for detecting suspicious activity without predefined signatures by learning patterns from data and identifying anomalies, outliers, and high-risk behaviors. In SOC contexts, ML can model normal baselines for users, hosts, and applications, then flag deviations such as unusual authentication patterns, unexpected data transfers, or rare process behaviors--capabilities that are particularly useful against zero-days and APTs that evade signature- based tools. NLP is valuable for processing human-language text (tickets, email content, narrative logs), but it is not the primary engine for behavioral anomaly detection across telemetry. Static IP blocking is a manual control that can be bypassed and does not "learn" or adapt. Heuristic-based signatures still rely on predefined patterns, even if they are generalized, and are not the same as adaptive learning. From a SOC perspective, ML can improve detection coverage when combined with strong telemetry and tuning, but it also requires governance: monitoring model drift, validating outputs, and ensuring explainability for analysts. Because the scenario prioritizes signatureless detection and real-time adaptation, machine learning is the best fit.
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.