Lesson 2 of 10 · About 5 minutes

Searching security events

Learn the concept.

A security information and event management system, or SIEM, brings events together for searching and investigation. A useful search has a clear purpose and a bounded scope.

Choose fields

Identify the account, device, action, result, and timestamp fields available in the data. Field names differ between tools.

Start narrow, then expand

Begin with the alert entity and relevant time range. Broaden deliberately if nearby activity could explain the event.

Keep the search reproducible

Record the filters, time zone, and source so another analyst can repeat the search. No result may mean missing data rather than no activity.

Field example02 / A

Put it in context

Search the fictional sign-in dataset for account jlee between 09:00 and 09:20 UTC, then compare successes and failures. Record the window with your findings.

SEE THE IDEA

Make a search repeatable

An example search plan, not syntax for a particular SIEM.

  1. Question
    What happened around this sign-in?

    Keep the investigation purpose explicit.

  2. Account
    jlee

    Use the account field from the chosen source.

  3. Window
    09:00–09:20 UTC

    Record both bounds and the time zone.

  4. Source
    Sign-in events

    Compare failures and successes; check collection coverage.

Expand the scope deliberately and record each change.
Read the visualNo events were returned. What should you check first?

Check the source, filters, time interpretation, and collection coverage before concluding that nothing happened.

Make a decision.

Use what you just learned. A correct answer lets you save this lesson to your progress.

Take this with you.

A search should answer a specific question and be repeatable.

YOUR LEARNING SPACE