Today's lab was more like an exploration than a task. Instead of just following steps, I tried to understand what's actually happening inside the system when processes run.
π§ Step 1 β Setting Things Up
I started by enabling process tracking using Command Prompt since I'm on Windows Home edition.
After running the command, I verified whether logging was working. Then I opened Event Viewer and navigated to Security logs.
β Good sign: I was able to confirm Event ID 4688 (Process Creation)

That meant I could continue the lab.
π Step 2 β Creating Activity
To generate some data, I opened a few applications:
- Notepad
- Command Prompt
- Browser
I also:
- Ran some basic commands
- Opened multiple browser tabs
- Switched between applications
The goal here was simple: create enough activity to observe.
π₯οΈ Step 3 β Observing Processes
Next, I opened Task Manager.
Here, I focused on:
- Process names
- PIDs (Process IDs)
- Number of running processes

At this stage, I wasn't trying to judge anything β just observing.
π€ Step 4 β First Suspicion
One thing immediately stood out:
π The browser had too many processes
At first, it looked suspicious.
But then I thought logically:
- I had opened multiple tabs
- Modern browsers run each tab as a separate process
So this behavior actually made sense.
β Conclusion: Not suspicious β expected behavior
π Step 5 β Checking Logs
Then I moved to Event Viewer.
I searched for:
- Process creation events
I was able to find logs corresponding to the activity I generated earlier.
This helped me connect: π What I did manually π What the system recorded

Even though the logs were limited, they were still useful.
π§ Step 6 β Thinking Like an Analyst
At this point, I asked myself:
- Are these processes expected?
- Do they match my activity?
- Is there anything unusual?
Based on what I observed:
- All processes were related to what I opened
- No unknown or unexpected behavior
β οΈ Limitation Noticed
Since I'm using Windows Home edition:
- I don't have full audit configuration
- Detailed process relationships are not fully visible
So I cannot claim complete visibility.
π More accurate conclusion: No suspicious activity observed within available logs
β Final Takeaway
This lab wasn't just about tracking processes.
It was about learning:
- How to observe before judging
- How to avoid false positives
- How to connect user actions with system behavior