Skip to content
EternaEdge

APEX — Platform Foundation

One engine. One common operating picture.

APEX is the single engine every EternaEdge product runs on. Every signal — open-source, cyber threat, insider risk, travel, investigations — is normalized into one schema, resolved to one entity, and scored by one risk engine, so the security operations center works from one common operating picture. People make the decisions.

Integrates at
The data and identity level, not the interface level
Human role
People approve every consequential step
It is not
A SIEM, a data lake, or a dashboard
Fig. 01 · Signal flowIllustrative

Five domains in. One operating picture out. The figure runs one illustrative scenario end to end — and stops for a person before the step that matters.

The problem

Five tools, five versions of the truth.

Many security operations centers run one console per discipline. Each keeps its own data model, its own queue, and its own name for the same person. Analysts correlate by hand, duplicate alerts pile up, and teams brief conflicting assessments of the same event.

The operating model

What changes in the security operations center.

The same five disciplines. One foundation underneath them. This is what the floor stops doing, and what it runs on instead.

Security operations today, compared with security operations on APEX
RowAreaTodayOn APEX
01ToolsTodayFragmented tools, each with its own data model.On APEXA unified ecosystem on one canonical schema.
02AlertsTodayDuplicate alerts for the same underlying event.On APEXA single alert stream, resolved to one entity.
03CorrelationTodayManual correlation by analysts across systems.On APEXOne shared risk engine correlating automatically. Analysts assess the result.
04AssessmentsTodayConflicting assessments between teams.On APEXOne common operating picture.
05WorkloadTodayLarge analyst teams stitching tools together.On APEXGoverned automation, with human oversight on consequential steps.
  • Not a SIEM
  • Not a data lake
  • Not a dashboard

APEX is the intelligence fabric under the products. It integrates at the data and identity level, so adding a discipline means one connection to the foundation rather than a connector to every other tool. STRATUM (Cyber Threat) is designed to complement the SIEM a team already runs — it is not a SIEM replacement.

See how it runs as GSOC software for corporate security, or as counterintelligence for defense and intelligence programs.

Illustrative — counts are of what is drawn

The cross-section

A common operating picture, built at the data layer.

A common operating picture is one shared view of what is happening across people, sites, travel, systems, and programs. The foundation is designed to build it before anything reaches a screen — four stages, one signal path. Follow one scenario through all four: three signals arrive in three domains, and each one alone is below threshold.

Illustrative scenario — designed behavior, not a customer result

01 · Normalize

Unified Data Fabric

One language for data

Every signal — a news alert, a badge log, an itinerary, a dark-web mention — is translated into one canonical intelligence schema with shared historical context. Three sources, three formats, one record shape.

When OBSIDIAN (Counterintelligence) asks what we know about a person, the answer includes what LUCID (OSINT Awareness), STRATUM (Cyber Threat), and PATHWAY (Travel Security) know — with no custom integration.

Human role

Analysts work from one record shape instead of translating between tools.

02 · Resolve

Entity Resolution

One memory

Resolution runs continuously across domains. “J. Smith” in travel, “John Smith” in HR, and a username in a cyber log resolve to the same person — and to the program that person works on. One entity, one intelligence picture.

Designed so duplicate alerts collapse into one alert with full context.

Human role

Analysts investigate an entity, not a queue of duplicates.

03 · Score

Shared Risk Engine

One judgment

The shared risk engine scores intent and targeting across every domain at once — open source, cyber, insider risk, travel, and investigations. It weighs signal diversity, role and mission sensitivity, asset criticality, and corroboration between domains.

A minor-looking signal can correctly escalate when it completes a pattern another domain started.

Human role

Analysts review what was correlated — which signals, from which domains — and own the judgment.

04 · Orchestrate

Automated Orchestration

One set of hands

Threshold-driven workflows act on the result: a FORGE (Investigations) case opens, PATHWAY elevates the travel tier to require a pre-travel briefing, and the program protection lead is alerted. Orchestration is threshold-based, with human-in-the-loop controls on consequential steps.

The audit trail shows what automation did and who approved what.

Human role

The program protection lead reviews and approves every consequential next step before it executes.

A point tool sees only its own slice.The engine sees the pattern.

Next · you hold the gate

Governance

The engine proposes. A person decides.

The engine routes, opens, and escalates at threshold. The step that matters is held for a person. Approve or hold it below — the record shows the decision.

Fig. 04 · Approval gateInteractive illustration

Approval queue

You areProgram protection lead

Entity · John SmithRisk · threshold crossed

At threshold · automated and logged

  • Case opened

    FORGE · Entity timeline attached

    Automated · logged

  • Travel tier elevated

    PATHWAY · Pre-travel briefing required

    Automated · logged

  • Program protection lead alerted

    Routed with full entity context

    Automated · logged

Held for a person

Schedule the pre-travel briefing

PATHWAY · Consequential next step

Awaiting approval

Held for approval by the program protection lead.

Audit trail

Append-only
  1. 001APEXThree signals resolved to one entity
  2. 002APEXCombined risk crossed threshold
  3. 003FORGECase opened — entity timeline attached
  4. 004PATHWAYTravel tier elevated — pre-travel briefing required
  5. 005APEXProgram protection lead alerted
  6. 006APEXNext step proposed — held for approval

One step proposed · no decision on the record

Operating picture

Entity
John Smith
Engineer · sensitive program
Signals
3 domains
  • PATHWAYItinerary · high-risk country
  • STRATUMCredential stuffing · program portal
  • LUCIDInfluence campaign · program technology
Risk
Threshold crossed
Case
Opened
Travel tier
Elevated · briefing required
Briefing
Pending approval
Record
6 entries

At threshold the case opens, the travel tier is elevated, and the program protection lead is alerted — automatically, and on the record. The next step that reaches the traveler waits for a person. Approve it or hold it; either way, the record shows who decided.

Automation you can defend

01

Human-in-the-loop controls

Orchestration is threshold-based, with human-in-the-loop controls. Workflows route, open, and escalate at threshold — and people approve the steps that matter before they execute.

02

A complete audit trail

Every automated action is recorded: what ran, what it touched, and who approved it. The record is designed for defensible review, not just operational speed.

03

Governed data access

Assistants and workflows operate on governed, access-controlled data. Authority, oversight, and role-based access controls are part of the architecture.

Compliance statement

“AI assistants operate within APEX, using governed, auditable data. They do not bypass authority, workflows, or oversight.”

AI FORCE — Autonomous Intelligence Assistants, in development — is designed to work inside the same gate: Sentinel is designed to monitor around the clock, Oracle to correlate and brief, Scribe to document the case as it builds.

How EternaEdge secures and governs the platform →

The product system

Every product draws from one engine — and feeds it.

One platform foundation. Five product pillars. One assistant layer. Customers enter through any pillar, and the foundation makes the second product more valuable than the first: everything added lands on the same schema, the same entities, and the same risk picture.

Fig. 05 · The exchangeIllustrative
Product pillars
  • OBSIDIAN — Counterintelligence

    Feeds the engine
    Behavioral baselines, insider risk indicators, and vetting results.
    Draws from the engine
    Cross-domain signals for behavioral correlation, and shared risk scoring.
  • LUCID — OSINT Awareness

    Feeds the engine
    Open-source events, campaign detection, and regional risk.
    Draws from the engine
    Entity correlation targets — the people, assets, facilities, and travel that matter.
  • FORGE — Investigations

    Feeds the engine
    Investigation outcomes and documented resolutions.
    Draws from the engine
    Cases opened at risk thresholds, with enriched entity timelines.
  • STRATUM — Cyber Threat

    Feeds the engine
    Threat actor activity, exposure data, and cyber anomalies.
    Draws from the engine
    Human and mission context for cyber signals.
  • PATHWAY — Travel Security

    Feeds the engine
    Travel plans, in-travel events, and SOS activations.
    Draws from the engine
    Traveler profiles, behavioral indicators, and live intelligence.
Assistant layer
  • AI FORCE — Autonomous Intelligence Assistants

    In development
    Designed to feed the engine
    Monitoring, analysis, documentation, and guidance across every module.
    Designed to draw from it
    Governance, audit trails, and data access controls.

    AI assistants operate within APEX, using governed, auditable data. They do not bypass authority, workflows, or oversight.

One engine

APEX — Platform Foundation

  1. Unified Data FabricOne language for data
  2. Entity ResolutionOne memory
  3. Shared Risk EngineOne judgment
  4. Automated OrchestrationOne set of hands
What two pillars do on one foundation
  • OBSIDIAN and LUCID

    An open-source event can escalate an OBSIDIAN review.

  • OBSIDIAN and FORGE

    OBSIDIAN is designed to open a FORGE case when a pattern crosses threshold.

  • OBSIDIAN and STRATUM

    STRATUM is designed to corroborate OBSIDIAN findings, raising or reducing confidence with each new signal.

  • LUCID and PATHWAY

    A LUCID event near a traveler can trigger a PATHWAY re-briefing.

  • FORGE and PATHWAY

    An emergency SOS in PATHWAY opens a FORGE case automatically.

  • Each pillar added shares one foundation with the rest. Context compounds; people still approve the steps that matter.

    View all products →

Who it changes

One event, read from four seats.

Each role gets the view its decisions need — from the same entity, the same risk picture, and the same record.

Same eventJohn Smith · sensitive program · three signals, three domainsIllustrative

01CSO · CISO

Security leadership

One common operating picture

Today

Five tools brief five assessments of the same event. Leadership reconciles them before it can decide.

On the platform

One common operating picture across every discipline. Fewer tools, fewer seams, and governance you can defend: what was detected, what was decided, and who approved it.

02Every discipline

Analysts

No swivel‑chair correlation

Today

The same person is a different record in every tool, and the same event is a different alert in each queue.

On the platform

One queue of deduplicated alerts, each with full entity context. The engine correlates; the analyst assesses, escalates, or closes.

03Program protection

Program owners

Threats weighed against the program

Today

A threat seen by another team's tool reaches the program late, or not at all.

On the platform

A threat seen in any domain is evaluated against the program's sensitivity — and the program protection lead reviews and approves the next step.

04Integration

IT and procurement

One foundation, not a mesh

Today

Every tool added means point-to-point connectors to the others, and one more data model to maintain.

On the platform

Integration at the data and identity level, on one foundation, rather than point-to-point connectors between every pair of tools.

Questions

Questions about the platform foundation

What is a common operating picture in security operations?

A common operating picture is a single, shared view of what is happening across an organization's people, sites, travel, systems, and programs, so every team works from the same facts. Many security teams assemble that view by hand from separate tools. APEX — Platform Foundation is designed to build it at the data layer instead: every signal is normalized into one canonical schema, resolved to the entity it concerns, and scored by one shared risk engine. Analysts and security leaders see the same picture, and they make the decisions.

Is APEX a SIEM, a data lake, or a dashboard?

No. APEX is not a SIEM or data lake, and it is a platform product, not a dashboard. A SIEM collects and correlates machine logs for the cyber security operations center. APEX is the intelligence fabric under the EternaEdge products: it integrates at the data and identity level, so signals about people, programs, and assets from different security disciplines resolve to one picture. STRATUM — Cyber Threat covers the cyber domain and is designed to complement the SIEM a team already runs, not replace it.

What is entity resolution, and why does it matter in security operations?

Entity resolution is the work of recognizing that records held in different systems refer to the same real-world person, facility, or program. A traveler listed as J. Smith, an employee record for John Smith, and a username in a cyber log can be one person. APEX is designed to resolve them continuously, so each entity has one intelligence picture and duplicate alerts collapse into a single stream. The aim is that analysts spend less time reconciling records and more time on judgment.

How does a shared risk engine score signals from different security domains?

Point tools typically score risk inside their own slice: travel risk in one console, cyber risk in another. APEX is designed to evaluate intent and targeting across open-source, cyber, insider risk, travel, and investigative signals at once. The shared risk engine weighs signal diversity, role and mission sensitivity, asset criticality, and corroboration between domains, so a minor-looking signal can escalate when it completes a pattern another domain started. Scores feed the thresholds that trigger routing and case creation. People review the result and approve consequential steps.

How is a platform foundation different from integrating tools or putting them on one screen?

Putting several tools on one screen leaves each tool with its own data model, so the analyst still correlates by hand. Point-to-point integrations move alerts between tools, and every added tool brings more connections to maintain. APEX integrates at the data and identity level rather than the interface level: one canonical schema, one resolved entity, one shared risk engine, and one audit trail under every EternaEdge product. The picture is assembled before it reaches a screen, and people decide what happens next.

How does running every signal through one engine change the work of a security operations center?

In many security operations centers, analysts watch several consoles and connect related alerts themselves. With one engine underneath, the work is designed to start from a resolved picture: one alert stream, with each alert tied to the person, site, or program it concerns and context from the other security disciplines already attached. Threshold-based workflows route alerts and open cases in FORGE — Investigations. Analysts, investigators, and security leaders keep the judgment: they review what was correlated, approve consequential steps, and own the decision.

How is automation governed, and who approves actions?

Orchestration in APEX is threshold-based, with human-in-the-loop controls on consequential steps. Workflows are designed to route alerts, open cases, and propose next steps such as briefings; a person approves the steps that matter. The audit trail is designed to show what automation did and who approved what. AI FORCE — Autonomous Intelligence Assistants is in development and is designed to work inside the same controls. AI assistants operate within APEX, using governed, auditable data. They do not bypass authority, workflows, or oversight. People remain responsible for determinations and decisions.

What does converged security mean, and which security domains does APEX bring together?

Converged security means the disciplines that protect an organization work from shared data instead of separate tools. APEX is the foundation under five product pillars: OBSIDIAN — Counterintelligence for insider risk and targeting, LUCID — OSINT Awareness for open-source early warning, FORGE — Investigations for case management, STRATUM — Cyber Threat for cyber threat intelligence, and PATHWAY — Travel Security for traveler protection. Customers enter through any pillar. Each product stands on the same schema, entities, and risk engine, so its signals are designed to add context to the others. People in each discipline keep their own authority.

See a scenario traced through one engine.

Customers enter through any pillar. Every product stands on the same data, the same entities, and the same risk picture — and a person approves the steps that matter.

View all products →