Chapter 4 · Reading 12 of 12
Investigating fileless activity
Security+ SY0-801 · Objectives 2.5, 4.4, 4.8
At the end of the shift the advising office can account for every executable in its approved image. An endpoint record nevertheless shows unusual activity under a document viewer. That apparent contradiction is a good test of what you have learned about malware classification.
Evidence can survive without a payload file
Fileless activity relies substantially on memory or existing system facilities during execution. It may still leave artifacts in event logs, configuration stores, scheduled activity, caches or network telemetry. Living off the land refers to abuse of legitimate tools already available in an environment. The concepts overlap. Legitimate administration can produce many of the same process names.
Start with a behavioral question. Did the expected account start this process from an expected parent on a device it manages during an approved window? Link process creation, endpoint detections, authentication and network records. Normalize time and check sensor coverage. A file inventory answers what was present at collection time. It cannot reconstruct every action that occurred between inventories.
Preserve volatile context and business continuity
An analyst sees an unfamiliar child process under a document viewer on an admissions workstation. Check the approved support calendar and ask whether a case or maintenance job accounts for the activity. If the endpoint is actively exposing records, isolation can limit harm while preserving live state. Power loss can destroy volatile evidence. Have an authorized responder decide what to acquire given immediate risk, privacy and available expertise.
Preserve original records and record clock offsets, collection method and any gaps. Restrict administrative tools by role and monitor their behavior in context. Validate defenses with an approved benign workflow and confirm normal support work still succeeds. Report the observed process chain and independent corroboration rather than claiming an attack solely because a legitimate interpreter ran.
Document what a sensor could see
Campus IT added process logging on Tuesday, and the unusual connection was observed on Monday evening. Tuesday’s clean process report gives little evidence about Monday. Preserve the collection start time and look for an independent record that covers the earlier interval. If none exists, report that limitation and decide what can be done safely with the remaining evidence. Improving visibility for the next incident is a worthwhile outcome even when the current investigation cannot reconstruct every step.
Tell the story across three clocks
The mail system timestamps delivery of an advising form. The endpoint timestamps a child process. The network sensor timestamps a connection. Before drawing a line between them, verify the device, user session, time zone and clock offsets. Ask whether an approved accessibility or support integration normally produces the same behavior. Preserve the sequence with the collector names and the observations each can support.
When briefing the advising office, start with the affected function and confirmed action. Explain what evidence is still missing, who will seek it and what would change the current containment decision. The response is useful even when the software family remains unknown. That same habit will guide vulnerability assessment, where a tool's finding also needs independent interpretation.
Inspect the three records, then use the evidence to answer the question.
1. Disk inventory
Scheduled file scan reports no new executable.
2. Process tree
Endpoint records show an unusual process under a document viewer.
3. Network record
Network sensor attributes an external connection to the same host and time.
Apply the reading
Why can a clean file scan coexist with suspicious execution evidence?
Compare your reasoning
A scan inventories files at a particular time. Memory and process activity may leave different evidence.