CYBERJA · PRACTICE GUIDE

SOC Detection Engineering & Monitoring Hub

Use synthetic evidence. Enter your own observations, then compare them with the worked direction below.

Open the tool · Open this file in a browser or print it to PDF.

Practice scenario

Repeated failed sign-ins are followed by success.

Record the assessment

Open Connected Workspaces and select SOC & detection. Use the assessment form to work through these prompts.

Log sources, collection and coverage gaps — Identify systems, required events, collection health, timestamps, retention and owners. Missing logs mean unknown visibility.

Exact event value to match — The built-in replay compares the event field exactly. Use login_failure for the supplied dataset; this is not a production SIEM rule.

Grouping field — Select how events are correlated. Different groupings can change both coverage and false positives.

Threshold (event count) — Choose a positive integer. Explain why that threshold is appropriate and what it will miss.

Sliding window (seconds) — Set a window between 1 and 86400 seconds. The replay uses timestamp-ordered events and groups them by the selected field.

Alert triage and escalation runbook — Explain analyst validation, likely false positives, escalation owner, containment authority and supporting queries.

Detection assumptions and limitations — Explain missing sources, bypass possibilities, benign bursts and synthetic dataset limits. A passing replay is not proof of production coverage.

Test result interpretation — After replay, explain whether the observed alerts meet your expectation, why, and what tuning or further tests are needed.

Worked direction

Correlate account, source and timestamps, compare against benign behavior and document escalation criteria.

Review your work

Choose required log sources and assess collection gaps.

Specify a rule with exact fields, window and grouping.

Replay events and inspect the alert evidence.

Document limitations, tuning and escalation.

Evidence and handoff

Capture a mock evidence reference and its limitations. Record the finding, accountable owner and next review. Where a material risk remains, record it in the shared risk register and schedule a follow-up.

Reference: CIS Control 8: Audit Log Management — https://www.cisecurity.org/controls/audit-log-management

Continue with the community

Compare your practice approach with other CyberJA Connect members.

Join CyberJA Connect ↗