Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Interviews in SOC analyst

        Work in the tool while you explain your decisions.

        Choose a role and level. Each interview has a new task, follow-up questions and a report that checks your work and your explanation.

        Speak or type. Sign in to save your results across devices.

        Timed assessment

        • 12 practical questions
        • 45 minutes
        • Mid level

        Questions are drawn from a bank of 36. Your report includes a skill breakdown and lessons to practice next.

        Practice interviews

        Junior tasks cover the fundamentals. Mid and senior tasks add debugging, changing requirements and review decisions.

        10 interviews

        • SOC analyst
        • Junior
        • 30 min

        Unique failed login events

        For failed authentication login actions, count distinct event IDs as attempts, grouped by src. Authentication exports can contain a duplicate of the same event. Count distinct event IDs when the task asks for attempts, and group by the source address. A failed logout must not become a login attempt. The boundary matters because an inflated count can make a benign source cross a detection threshold. Search the fictional records for the behavior described below. Return the fields or aggregate named in the task. If neither is specified, return every matching record with every field.

        Start interview
        Skills and rubricUnique failed login events
        • Authentication exports can contain a duplicate of the same event. Count distinct event IDs when the task asks for attempts, and group by the source address. A failed logout must not become a login attempt. The boundary matters because an inflated count can make a benign source cross a detection threshold.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Junior
        • 30 min

        Attachment to child process

        Return endpoint events where winword.exe starts powershell.exe. A parent process helps explain how a child started. An office document spawning an encoded script deserves different handling from an approved inventory script. Search for the parent and child together, then inspect the surrounding delivery and download events. The lineage supports an execution hypothesis; it does not identify an attacker or prove every action on the host. For the analyst handoff, return only id, time, source, action and outcome, in that column order.

        Start interview
        Skills and rubricAttachment to child process
        • A parent process helps explain how a child started. An office document spawning an encoded script deserves different handling from an approved inventory script. Search for the parent and child together, then inspect the surrounding delivery and download events. The lineage supports an execution hypothesis; it does not identify an attacker or prove every action on the host.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Junior
        • 30 min

        Outbound volume and exclusions

        Return unapproved proxy upload events larger than 500000 bytes. A large approved backup is not equivalent to an unexplained upload. Combine action, approval and byte conditions before comparing outbound volume. Bytes describe observed transfer size, not the sensitivity of the content. Preserve the destination and ask for content classification rather than claiming confirmed data theft from size alone. Return the distinct matching event count in one column named matches. A duplicated export row is one event.

        Start interview
        Skills and rubricOutbound volume and exclusions
        • A large approved backup is not equivalent to an unexplained upload. Combine action, approval and byte conditions before comparing outbound volume. Bytes describe observed transfer size, not the sensitivity of the content. Preserve the destination and ask for content classification rather than claiming confirmed data theft from size alone.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Mid
        • 30 min

        ATT&CK behavior mapping

        ATT&CK names observed adversary behaviors. Use a technique only when the evidence supports its behavior, and keep the observation separate from actor attribution. A delivered attachment can support a spearphishing attachment hypothesis; a failed login alone cannot prove stolen credentials. A mapping is a navigation aid for analysis, not a verdict or a guarantee of complete coverage. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricATT&CK behavior mapping
        • ATT&CK names observed adversary behaviors. Use a technique only when the evidence supports its behavior, and keep the observation separate from actor attribution. A delivered attachment can support a spearphishing attachment hypothesis; a failed login alone cannot prove stolen credentials. A mapping is a navigation aid for analysis, not a verdict or a guarantee of complete coverage.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Mid
        • 30 min

        Precision-preserving rule tuning

        Rule tuning needs a positive and a negative test. Keep the suspicious office child process while excluding the documented management script. A blanket shell exclusion would reduce alerts and erase the behavior you wanted to detect. Record the exception boundary so the next analyst can test it after the approved tool changes. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricPrecision-preserving rule tuning
        • Rule tuning needs a positive and a negative test. Keep the suspicious office child process while excluding the documented management script. A blanket shell exclusion would reduce alerts and erase the behavior you wanted to detect. Record the exception boundary so the next analyst can test it after the approved tool changes.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Mid
        • 30 min

        Containment authority and scope

        Containment changes business operations and can destroy useful context. The scenario authorizes isolating the affected workstation while preserving telemetry and escalating the cloud role change. Choose that bounded action rather than shutting down the whole organization or doing nothing. An analyst must keep the approval, scope and reason visible for the incident lead. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricContainment authority and scope
        • Containment changes business operations and can destroy useful context. The scenario authorizes isolating the affected workstation while preserving telemetry and escalating the cloud role change. Choose that bounded action rather than shutting down the whole organization or doing nothing. An analyst must keep the approval, scope and reason visible for the incident lead.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Mid
        • 30 min

        Evidence-led incident reports

        A responder needs observed facts, affected scope, current actions and unanswered questions. Separate confirmed execution evidence from suspected data exposure. Cite the endpoint and outbound records, state that content sensitivity is unverified, and assign the next validation. Avoid naming an attacker or declaring data theft from an upload size alone. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricEvidence-led incident reports
        • A responder needs observed facts, affected scope, current actions and unanswered questions. Separate confirmed execution evidence from suspected data exposure. Cite the endpoint and outbound records, state that content sensitivity is unverified, and assign the next validation. Avoid naming an attacker or declaring data theft from an upload size alone.
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • SOC analyst
        • Senior
        • 30 min

        Incident event chronology

        A timeline is a claim about sequence. Sort by the event timestamp in UTC and preserve the original time field. Ingestion delay can make later activity arrive first. Distinguish a delivered attachment, a script start, a task creation and an outbound upload. Sequence can support a hypothesis without proving that each event caused the next. Select the four incident events for delivery, script execution, persistence and upload. Put their IDs in event-time order, earliest first.

        Start interview
        Skills and rubricIncident event chronology
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • Defend the scope, authority and recovery checks before another engineer relies on the result.
        • SOC analyst
        • Senior
        • 30 min

        Risk ownership and exceptions

        An analyst documents exposure and proposes controls. A designated business risk owner accepts residual risk under the stated policy. A score reduction or missing alert does not grant that authority. Preserve the exposed known-exploited finding and require a bounded exception with a review date rather than silently closing it. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricRisk ownership and exceptions
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • Defend the scope, authority and recovery checks before another engineer relies on the result.
        • SOC analyst
        • Senior
        • 30 min

        Telemetry gaps and detection coverage

        No matching events can mean no observed activity, a wrong search or a missing source. Check collection health before treating silence as safety. The cloud audit-disabled record is a reason to verify telemetry availability and preserve existing evidence. It does not prove that every unseen action was malicious or that the tenant was fully monitored. Choose the defensible decision and cite all event IDs needed to support it. Exclude unrelated evidence.

        Start interview
        Skills and rubricTelemetry gaps and detection coverage
        • I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
        • I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.
        • Defend the scope, authority and recovery checks before another engineer relies on the result.

        Interview Hub access

        The Interview Hub is included in All Access. Choose a plan or sign in to your account to continue.

        View plansSign in or join

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Change your plan

        Checking the price

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.