Skip to main content

Capabilities

How AlphaSOC collects, enriches, detects, and stores your telemetry.

This page covers AlphaSOC's threat detection capabilities stage by stage: how Collect & Normalize maps your telemetry to OCSF, how Enrich & Detect analyzes each event and runs detections against it, and how Index & Store keeps the results searchable in the Security Data Lake. For how the Analytics Engine and the Security Data Lake fit together, see Architecture.

Collect & Normalize​

AlphaSOC accepts telemetry in any format and maps every event to the Open Cybersecurity Schema Framework (OCSF) as it arrives. Every later stage, from detection to the data lake, works on the same normalized events.

Data Sources​

You send logs to a supported transport, and AlphaSOC collects them from there: cloud storage (Amazon S3, Azure Blob Storage, Google Cloud Storage), a stream (Azure Event Hubs, Kafka), Cribl Stream, or a direct upload over HTTPS or SFTP. Application sources such as GitHub, Okta, and Slack work the same way: you export their logs to one of these transports.

Architecture gives example sources for each category, Collecting Data covers every transport, and Data Origins lists every supported source with its ID.

OCSF Normalization​

Collectors detect each log's format and map its events to OCSF, so there are no parsers for you to write and no data model to maintain. Because OCSF is an open schema, the same events are readable by your SIEM, your data lake tools, and AI agents without translation. The OCSF pages show how AlphaSOC maps each event class.

Enrich & Detect​

AlphaSOC enriches every event as it arrives and analyzes it on six dimensions. Detection then runs managed detections and your Sigma rules against the enriched events, and everything this stage produces is written to the Security Data Lake.

Six Dimensions of Analysis​

Each indicator in an event, such as a domain or an IP address, is enriched on arrival with its prevalence, domain age, and infrastructure flags, then analyzed on six dimensions, shown in the graphic on Architecture. The dimensions add context; detection then decides what becomes a finding.

DimensionWhat it analyzes
Active fingerprintingScans destinations through an anonymizing proxy layer to identify command-and-control (C2) infrastructure
Reputation scoringChecks each destination's live reputation with third-party APIs
Prevalence analysisCompares destinations across all AlphaSOC customers, so traffic to rare destinations stands out
Time series modelingBaselines normal activity and flags spikes, beaconing, and other anomalies
Feature classificationPicks out lookalike domains and patterns such as DNS tunneling
Intelligence correlationMatches destinations against AlphaSOC's threat intelligence to flag known bad infrastructure

Intelligence correlation draws on AlphaSOC's own threat intelligence: 70+ sources, holding 1M+ live, curated indicators. It's part of the platform, so there are no feeds or API keys for you to license.

Managed Detections​

AlphaSOC writes and maintains a library of hundreds of detections, each mapped to MITRE ATT&CK. They cover cloud platforms (Amazon Web Services, Google Cloud, and Microsoft Azure), application logs, and DNS and IP traffic, and find threats such as command and control, data exfiltration, account compromise, and insecure configuration. AlphaSOC updates them as threats change, so there's nothing for you to write or deploy. Each match produces an OCSF detection finding, stored in the Security Data Lake.

The Detections page lists every managed detection, and MITRE ATT&CK Coverage maps them to tactics and techniques.

Custom Sigma Rules​

Detect Anything™ with Sigma. Write detections specific to your environment in Sigma, the open detection standard, or use thousands of community rules for Windows, macOS, Linux, cloud platforms, and applications. You manage them as Detection as Code (DaC): rules deploy from Git through your CI/CD pipeline, with no translation to a vendor query language. Sigma rules run against raw or normalized data, so a rule doesn't need OCSF fields, and they produce the same OCSF detection findings as managed detections.

Sigma Rules shows how to write and deploy your own.

Index & Store​

The Security Data Lake indexes everything the Analytics Engine produces and keeps the normalized OCSF data (findings, evidence, and activity) hot for 18 months by default. Raw events are kept for a shorter period, and retention is configurable.

Data Layers​

The lake holds four aligned layers, findings, evidence, activity, and events, each suited to a different question, from what AlphaSOC detected to exactly what a device or user did.

The Security Data Lake's four layers: Findings (what did AlphaSOC detect?), Evidence (has this indicator ever been seen?), Activity (who looked something up, and from where?), and Events (what exactly happened, raw log included?).

Optimized for Security Data​

The lake is built for OCSF security data, so queries run against OCSF field indexes and Bloom filters instead of raw records. A Bloom filter tells AlphaSOC at once whether an indicator appears in the data, so you get an instant yes or no on any indicator across the whole retention window. AI agents can also run KQL queries over the lake through the MCP server. For the other ways to query the lake from your tools, see Integrations on Architecture.

What's Next​

Questions? Contact support@alphasoc.com.