For lab 7, we have to look at the logs where folders/files are accessed. In order to centralize these logs to Kibana, we must enable something in local policy. While my first attempt at this did not work, my second one did for some reason but, here is the general process.

Untitled

The above screenshot shows us where files were accessed. There is some configuration needed to make sure these logs show up, which is to make sure the folder or file that you want to access is audited and is creating logs for when someone accesses it.

Untitled

You can check it by looking at the folder’s properties and going to the advanced section and seeing whether or not the folder/file is being audited. You can also double check if it is working by looking at the local system event logs:

Untitled

In order to get these logs, you need to make sure they are enabled on the local security program:

Untitled

For some reason my Kibana would not show the events where the files I wanted to audit were. For example I would have my event viewer show me this:

Untitled

But for some reason it would not be forwarded to Kibana as well, even though I know that there are logs with this event ID being forwarded. So this is something I will look at later. I redid the process but I enforced rules on Windows Server 2016 through my run and, then it worked? Not really sure but, as long as the logs appear I think it is fine to use them as evidence, just it won’t be centralized as much.