nerdexam
CompTIA

CAS-003 · Question #804

A security analyst is trying to identify the source of a recent data loss incident. The analyst has reviewed all the for the time surrounding the identified all the assets on the network at the time…

The correct answer is D. Static code analysis. When an analyst suspects application code contains obfuscated clues to a data loss incident, static code analysis is the appropriate next tool to examine the code without executing it.

Enterprise Security Operations

Question

A security analyst is trying to identify the source of a recent data loss incident. The analyst has reviewed all the for the time surrounding the identified all the assets on the network at the time of the data loss. The analyst suspects the key to finding the source was obfuscated in an application. Which of the following tools should the analyst use NEXT?

Options

  • ASoftware Decomplier
  • BNetwork enurrerator
  • CLog reduction and analysis tool
  • DStatic code analysis

How the community answered

(45 responses)
  • A
    16% (7)
  • B
    11% (5)
  • C
    2% (1)
  • D
    71% (32)

Why each option

When an analyst suspects application code contains obfuscated clues to a data loss incident, static code analysis is the appropriate next tool to examine the code without executing it.

ASoftware Decomplier

A software decompiler converts compiled binaries back into readable source code but does not analyze that code for obfuscated patterns or malicious logic - it is a preparatory step, not an analysis tool.

BNetwork enurrerator

A network enumerator discovers active hosts, open ports, and services on a network and has no capability to inspect or analyze the internal logic of an application.

CLog reduction and analysis tool

Log reduction and analysis tools process event logs for patterns and anomalies, but the analyst has already reviewed the logs and suspects the key is embedded inside the application itself, not in log data.

DStatic code analysisCorrect

Static code analysis examines application source code or compiled code without executing it, making it ideal for uncovering obfuscated logic, hidden strings, and disguised functions that may have facilitated data exfiltration. Unlike runtime analysis, it can reveal all code paths including those intentionally obscured by a threat actor. This directly addresses the analyst's suspicion that the source of the incident was concealed within application code.

Concept tested: Static code analysis for identifying obfuscated application logic

Source: https://owasp.org/www-community/controls/Static_Code_Analysis

Topics

#data loss investigation#static code analysis#application forensics#incident response

Community Discussion

No community discussion yet for this question.

Full CAS-003 Practice