Back to catalog
Static reviewDevelopment

Skill dossier

correlating-security-events-in-qradar

Source declaration

Correlates security events in IBM QRadar SIEM using AQL (Ariel Query Language), custom rules, building blocks, and offense management to detect multi-stage attacks across network, endpoint, and application log sources. Use when SOC analysts need to investigate QRadar offenses, build correlation rules, or tune detection logic for reducing false positives.

The author's original description, preserved in English. It describes intent, not verified performance.

Correlates security events in IBM QRadar SIEM using AQL (Ariel Query Language), custom rules, building blocks, and offense management to detect multi-stage attacks across network, endpoint, and application log sources. Use when SOC analysts need to investigate QRadar offenses, build correlation rules, or tune detection logic for reducing false positives.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Correlates security events in IBM QRadar SIEM using AQL (Ariel Query Language), custom rules, building blocks, and offense management to detect multi-stage attacks across network, endpoint, and application log sources. Use when SOC analysts need to investigate QRadar offenses, build correlation rules, or tune detection logic for reducing false positives. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L55]
  • Step 1: Investigate an Offense with AQL [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L57]
  • Step 2: Build a Custom Correlation Rule [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L87]
  • Step 3: Use AQL for Cross-Source Correlation [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L115]
  • Step 4: Configure Reference Sets for Context Enrichment [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L164]
  • Step 5: Tune Offense Generation [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L193]
  • Step 6: Build Custom Dashboard for Correlation Monitoring [Source statement; provisional, not tested. Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L220]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
29.7 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/correlating-security-events-in-qradar/LICENSEOther11 KB
skills/correlating-security-events-in-qradar/references/api-reference.mdReference2.2 KB
skills/correlating-security-events-in-qradar/scripts/agent.pyScript6.5 KB
skills/correlating-security-events-in-qradar/SKILL.mdInstruction10 KB

SKILL.md frontmatter

{
  "name": "correlating-security-events-in-qradar",
  "description": "Correlates security events in IBM QRadar SIEM using AQL (Ariel Query Language), custom rules, building blocks, and offense management to detect multi-stage attacks across network, endpoint, and application log sources. Use when SOC analysts need to investigate QRadar offenses, build correlation rules, or tune detection logic for reducing false positives.\n",
  "domain": "cybersecurity",
  "subdomain": "soc-operations",
  "tags": [
    "soc",
    "qradar",
    "siem",
    "aql",
    "correlation",
    "offense-management",
    "ibm"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "RS.MA-01",
    "DE.AE-06"
  ],
  "mitre_attack": [
    "T1078",
    "T1110.003",
    "T1021",
    "T1071.001",
    "T1041"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Investigate an Offense with AQL

    Source-described action candidate under “Step 1: Investigate an Offense with AQL”; not verified execution.

  4. 04
    Action

    Step 2: Build a Custom Correlation Rule

    Source-described action candidate under “Step 2: Build a Custom Correlation Rule”; not verified execution.

  5. 05
    Action

    Create a multi-condition rule detecting brute force followed by successful login:

    Source-described action candidate under “Step 2: Build a Custom Correlation Rule”; not verified execution.

  6. 06
    Input

    Step 3: Use AQL for Cross-Source Correlation

    Source-described input candidate under “Step 3: Use AQL for Cross-Source Correlation”; not verified execution.

Inspect all extracted workflow candidates (20 candidate steps)
  1. 07
    Action

    Step 4: Configure Reference Sets for Context Enrichment

    Source-described action candidate under “Step 4: Configure Reference Sets for Context Enrichment”; not verified execution.

  2. 08
    Action

    Create reference sets for dynamic whitelists and watchlists:

    Source-described action candidate under “Step 4: Configure Reference Sets for Context Enrichment”; not verified execution.

  3. 09
    Action

    Use reference sets in rule conditions to exclude known benign activity:

    Source-described action candidate under “Step 4: Configure Reference Sets for Context Enrichment”; not verified execution.

  4. 10
    Action

    Step 5: Tune Offense Generation

    Source-described action candidate under “Step 5: Tune Offense Generation”; not verified execution.

  5. 11
    Action

    Apply tuning:

    Source-described action candidate under “Step 5: Tune Offense Generation”; not verified execution.

  6. 12
    Action

    Add high-frequency false positive sources to reference set exclusions

    Source-described action candidate under “Step 5: Tune Offense Generation”; not verified execution.

  7. 13
    Action

    Increase event thresholds on noisy rules (e.g., 10 failed logins -> 25 for service accounts)

    Source-described action candidate under “Step 5: Tune Offense Generation”; not verified execution.

  8. 14
    Action

    Set offense coalescing to group related events under a single offense

    Source-described action candidate under “Step 5: Tune Offense Generation”; not verified execution.

  9. 15
    Action

    Step 6: Build Custom Dashboard for Correlation Monitoring

    Source-described action candidate under “Step 6: Build Custom Dashboard for Correlation Monitoring”; not verified execution.

  10. 16
    Action

    Create a QRadar Pulse dashboard with key correlation metrics:

    Source-described action candidate under “Step 6: Build Custom Dashboard for Correlation Monitoring”; not verified execution.

  11. 17
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  12. 18
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  13. 19
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  14. 20
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

40 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

16 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 16 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

23 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 23 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/correlating-security-events-in-qradar/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/correlating-security-events-in-qradar/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/correlating-security-events-in-qradar
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.