Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the CrowdStrike edition of October 29, 2026

Academic researchMixedPreprint, not peer reviewedRecent

Beyond the Hype: Evaluating LLM Integration and Practical Limitations in Security Operation Centers

University of Guelph Cyber Science Lab (Rabieinejad, Dehghantanha, Zarrinkalam, Dastgerdy) · Academic research (security operations) · Canada (interview study)

Publisher
arXiv
Original publication
2026-08-17
Source retrieved
2026-10-30
Read original source

What happened

Semi-structured interviews with 20 SOC practitioners found perceived time savings for low-stakes, quickly verifiable tasks such as summarizing logs, but participants framed LLM outputs as preliminary drafts rather than decision-grade conclusions, reported limited trust for high-stakes decisions, and relied on ad-hoc verification and continuous human oversight rather than standardized mitigations. The authors propose a maturity rubric emphasizing auditability.

Why it matters

Indicates where AI assistants such as Charlotte AI are likeliest to help public SOC staff (summaries, drafts) and where oversight remains essential.

Evidence and measured results

Qualitative interviews (n=20); perceived, not measured, benefits; preprint.

Limitations and uncertainty

Small sample; Canadian, mixed-sector participants; not product-specific; not peer reviewed.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
SOC staff are unsure where AI outputs are trustworthy enough to use.
Stakeholders
  • SOC manager
  • Frontline analysts
  • CISO
  • Training lead
Discovery questions
  • Which SOC tasks are low-stakes and quickly verifiable?
  • How are AI outputs checked today?
  • Who approves AI use in investigations?
Value hypothesis
Focusing AI on verifiable drafting tasks may save analyst time with lower risk.
Potential engagement
Use-case triage and verification procedure workshop.
Unsupported claims
  • Quantified time savings
  • Product-specific benefits
  • Readiness for autonomous decisions

Pre-sales engineering

Role takeaway
Fit
Applies to AI assistant features in any SOC platform.
Architecture and integration
Assistant outputs linked to underlying telemetry for verification.
Prerequisites
  • Use-case inventory
  • Citation and traceability features
  • Logging of AI outputs
Constraints
  • Qualitative evidence
  • Small sample
  • Model behavior varies
Security
Hallucinated findings could misdirect response; require links to source evidence.
Proof of value
  • Measure verification time per summary
  • Count errors caught
  • Compare analyst confidence before and after

Delivery

Role takeaway
Work
Verification procedures and training for AI-assisted SOC tasks.
Dependencies
  • AI feature access
  • Analyst participation
  • Management support
Ownership
SOC manager.
Skills and adoption
Analysts learn structured verification of AI drafts.
Governance checkpoints
  • Approved use-case list
  • Quarterly audit of AI-drafted artifacts
  • Incident review of AI errors
Acceptance criteria
  • Verification checklist adopted (proposed)
  • Audit sample reviewed quarterly
  • Use-case list approved by CISO
Risks
  • Ad-hoc verification persists
  • Over-trust over time
  • Analyst skill erosion

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Favours designs that expose reasoning and evidence for verification.

Governance

Who approves, reviews and stays accountable for outcomes?

Calls for standardized verification procedures rather than ad-hoc norms.

Security and privacy

What data, permissions and controls need testing?

Hallucinations and opaque reasoning are operational risks in security decisions.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Cites analyst fatigue and skill shortages as motivations; verification training is needed.

Procurement

What should contracts, pricing and exit terms secure?

Buyers could request traceability and audit features in AI SOC tools.

Operating model

Which teams own the service once it runs?

Continuous human oversight remains part of the SOC model.

Publication history

  1. 2026-10-29CrowdStrike · Issue 0110 resources
Read preserved resource versions (JSON)

Stable resource ID: beyond-the-hype-llm-soc-practitioner-interviews