Back to portfolioPROJECT CASE STUDY / 01
FLAGSHIP · SECURITY OPERATIONS PLATFORM

ENGINEERING PROJECT / 01

AegisSOC.

CASE STUDY
2026

A local-first security operations platform for collecting telemetry, investigating alerts, enriching indicators and governing response actions.

PROJECTAegisSOC
TYPEFLAGSHIP
TECHNOLOGIES8 core tools
PythonFastAPIPostgreSQLDocker ComposeAlembicWazuhMISPOpenCTI

01 / CONTEXT

THE WHY

The challenge

Security investigations often require analysts to move between disconnected tools, normalize inconsistent events and preserve a trustworthy record of decisions. AegisSOC explores how those workflows can be brought together in a controlled, self-hosted environment.

02 / SYSTEM DESIGN

THE STRUCTURE

How the pieces fit together

A high-level view of the documented workflow and component boundaries.

01

Telemetry sources

Wazuh alerts and authenticated event producers submit source-aware security events.

02

FastAPI application

Normalizes ingestion, serves analyst workflows and enforces workspace-aware access.

03

PostgreSQL

Stores events, investigations, cases, integration state and audit history with row-level security.

04

Background workers

Run scheduled detections, retention, provider synchronization and approved response delivery.

05

External intelligence & receiver

MISP and OpenCTI enrich indicators; a configured receiver handles approved response requests.

03 / ENGINEERING LOG

THE BUILD SEQUENCE

How the work took shape

A transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.

  1. 01
    01 · SCOPEDocumented

    Define the operating boundaries

    Established a local-first SOC workflow with explicit limits for detection content, scanner imports and receiver-based response.

  2. 02
    02 · PLATFORMImplemented

    Build the application foundation

    Structured the platform around FastAPI, PostgreSQL, Alembic and Docker Compose, with separate workers for scheduled and integration tasks.

  3. 03
    03 · SECURITYImplemented

    Enforce workspace and response controls

    Added workspace membership checks, PostgreSQL row-level security, a restricted runtime database role, approval gates, signed webhook delivery and audit history.

  4. 04
    04 · INTEGRATIONSImplemented

    Connect telemetry and intelligence

    Built source-aware event ingestion, replay protection, MISP and OpenCTI enrichment, plus imports for external vulnerability-scan findings.

  5. 05
    05 · EVIDENCENext

    Refresh current interface evidence

    The existing gallery is from an earlier lab build. Capture fresh screenshots from the current local build before presenting them as current release evidence.

04 / DESIGN JUDGMENT

TRADE-OFFS & REASONS

Decisions behind the design

The engineering choices that shape the system—and the reason each boundary exists.

01

Keep the platform local-first

A self-hosted lab makes the data flow and service boundaries easier to inspect while avoiding a premature claim of production readiness.

02

Separate authorization from UI visibility

Workspace membership checks and PostgreSQL row-level security provide layered enforcement; hiding a control in the interface is not an access-control boundary.

03

Require approval before response delivery

Signed, idempotent receiver-based webhooks create an auditable hand-off without giving the platform arbitrary endpoint command execution.

04

Treat scanner data as imported evidence

Normalizing Nessus, Tenable and Qualys exports keeps the integration honest: AegisSOC consumes findings but does not launch scans.

05 / NEXT INVESTIGATION

THE NEXT USEFUL TEST

What I would test next

Capture a fresh dashboard set from the current local build, then add integration contract tests for event ingestion, intelligence-provider failures and signed response delivery. Publish the exact test command and output alongside the refreshed evidence.

06 / IMPLEMENTATION

THE HOW

Engineering approach

The work is broken into practical building blocks, from initial design through to validation.

  1. 01

    Ingests and normalizes security events with replay protection and source-aware handling.

  2. 02

    Provides investigation and search workflows backed by PostgreSQL and workspace-level access controls.

  3. 03

    Uses deterministic detection rules and a documented, bounded Sigma subset.

  4. 04

    Enriches investigations with IOC intelligence through MISP and OpenCTI integrations.

  5. 05

    Imports asset-risk findings from Nessus, Tenable and Qualys exports.

  6. 06

    Routes response requests through approvals, signed webhook delivery, idempotency and audit history.

07 / VERIFICATION

THE CHECKS

Validation & evidence

Specific checks documented for this project. Results are scoped to the recorded lab or test run.

Access controlLayered

Workspace membership checks are combined with PostgreSQL row-level security and a restricted runtime database role.

Event ingestionReplay-aware

Canonical event ingestion includes source-aware normalization and replay protection.

Response governanceApproval-gated

Requests are approved, delivered through signed webhooks and tracked with idempotency and audit history.

08 / RESULTS

THE VALUE

What this project demonstrates

01

A modular FastAPI and PostgreSQL application with dedicated workers for scheduled jobs, retention, integrations and response.

02

Security boundaries that include workspace membership checks, PostgreSQL row-level security and a non-owner runtime database role.

03

An auditable response workflow that makes approval and delivery state explicit.

09 / EVIDENCE

THE BUILD

Project in practice

Original project captures and walkthrough media. Each item is labelled to explain what it demonstrates.

These seven genuine dashboard captures are from an earlier lab build. The AegisSOC screenshot gallery states that they do not represent the latest dashboard fixes; fresh captures from the current local build are still required before treating them as release evidence.

10 / ENGINEERING NOTES

TRANSPARENCY

Scope, assumptions & limitations

Clear boundaries matter. These notes describe what the current project does—and what it does not claim to do.

  • This is an actively developed engineering project and lab deployment, not a certified production SIEM.
  • Scanner integrations normalize exported findings; they do not launch vulnerability scans.
  • Sigma support is intentionally limited to a documented subset.
  • Response delivery is receiver-based; it does not perform endpoint isolation or arbitrary command execution.
  • Provider compatibility and deployment security must be validated for each environment.