Safeguard Docs
Security Operations Center

SecOps (SIEM, alerts and cases)

OCSF-normalized security event ingestion, continuous detection with Sigma rules and IOC matching, and deduplicated alerts.

SecOps (SIEM)

SecOps turns the security signals already flowing through Safeguard, plus your cloud and identity logs, into a normalized event stream with continuous detection on top: event ingestion, OCSF normalization, detection with IOC matching, and deduplicated alerts.

Event ingestion

Collectors feed a normalized event pipeline:

  • Internal - AppSec findings and API traffic, adapted from the tenant-scoped streams already inside the platform.
  • Cloud - AWS CloudTrail, Azure Activity, and GCP audit logs, pulled incrementally with a persisted per-account cursor.
  • Push - a syslog/CEF listener and a generic webhook endpoint.

Ingestion protects itself under load: if events arrive faster than they can be processed, excess is shed with a recorded metric rather than blocking your systems or silently losing data - any loss is always surfaced, never hidden.

Normalization (OCSF)

Every raw log is mapped to an OCSF-aligned event: a class (authentication, process, network, file, api, config, dns, …), the extracted actor / target / source and destination IPs, and ATT&CK technique tags where the source event implies a technique. The full raw record is preserved at the hot tier so hunts can reach unmapped fields. Adding a new source is typically a configuration change, not custom development.

The event store is retention-tiered: a hot tier (full fidelity, days), a warm tier (downsampled), and a cold archive, moved automatically by lifecycle policy. Every read and write is tenant/org/descendant-scoped.

Continuous detection and IOC matching

Detection runs continuously over the event stream:

  • Detection rules + Sigma are executed against new events per tenant; each match produces an Alert carrying the rule, contributing event IDs, severity, and ATT&CK tags.
  • Real-time IOC matching checks every event's IPs, hashes, and domains against the threat-intel store; a hit raises an alert.
  • Deduplication collapses identical alerts within a sliding window so a noisy condition produces one alert, not thousands.

Alerts you get

Alerts are the built output surface. Each alert records the firing rule or IOC, the events that contributed to it, a severity, and ATT&CK technique tags. Example detections include Sigma "impossible travel" on authentication events and known-bad IOC matches on network events.

Configuration

The SecOps engine is gated by a server-enforced feature flag (ff.siem), fail-safe off. Internal collectors activate with the platform.

Events and alerts are tenant/org/descendant-scoped, access-controlled, and audit-logged, with per-tenant retention and residency.

On this page