1. Home
  2. Armadillo platform

Armadillo

A unified security system

What goes into Armadillo, what it does with it, and what it produces. Every section here is condensed from the Armadillo Technical Due Diligence dossier.

Conceptual Armadillo console panels

01Overview01 / 06

01.1Platform overview

Get to know Armadillo

A six minute walkthrough of the platform: deployment on a test server, a live attack detected and explained, and every module of the console.

ArmadilloPlatform overview
05:52

01.2Architecture

Architecture

Sources feed one engine; the engine correlates, validates and decides; outcomes surface in one console. Select any stage.

Armadillo data flow

Select any stage for detail

Sources
ArmadilloEngine
Outcomes

One engine, no seams

Sources feed a single engine that correlates, validates and decides. Select a stage to see what it does.

Data flow as described in the Armadillo technical due diligence dossier.Engineers walk through the detailed architecture during evaluation.

01.3Security planes

One platform. Multiple security planes.

Every plane reads from and writes to the same data model, so context never crosses an integration seam.

Detection plane

Deterministic rules, IDS detection path, alerts, SIEM ingestion and real time correlation

02Protection engine02 / 06

02.1The protection engine

From new threat to active protection

New threat intelligence, or a sufficiently detailed attack description, goes in. Validated protection comes out, deployed and enforced in your environment automatically. No vendor release cycle, no manual rule writing.

Earth at night seen from orbit, city lights across a continent
Input

New threat intelligence

Advisories, exploit information and indicators, or a detailed attack description.

Armadillo

Protection engine

Produces deterministic detection and prevention rules that are validated before release and remain auditable.

Internal method shared under NDA
Output

Active protection

A new versioned rule bundle, deployed to enrolled agents and engines and enforced where policy allows.

  • Automaticfrom intelligence to enforcement
  • Deterministicexplicit logic, not an opaque decision
  • Validatedbefore any rule is released
  • Auditableevery rule versioned and traceable

02.2Time to protection

Time to protection, measured end to end

≤5seconds

Maximum observed end to end time to protection across the completed reported Armadillo test set.

  • Start Fresh threat intelligence or attack description received.
  • End Protection active at the customer side.
  • Scope The completed, reported Armadillo test set documented in the technical due diligence dossier.
  • Reading This is the maximum observed value in that set. It does not predict the result for every threat or environment.
  1. Intelligence received
  2. Protection engine
  3. Bundle deployed
  4. Protection active
00.0 s≤ 05.0 s

Replay of a documented benchmark. Stage positions show order, not individual durations.

02.3Zero day protection

Where zero day protection comes from

In a conventional stack protection is a vendor deliverable. In Armadillo the rule is derived from the intelligence itself.

Conventional signature model Protection waits on an external release cycle

  1. StartDisclosure
  2. Stage 1Vendor research
  3. Stage 2Signature authoring
  4. Stage 3Vendor testing
  5. Stage 4Update release
  6. Stage 5Your change window
  7. EndProtected

Armadillo workflow Maximum observed end to end: 5 seconds, completed reported test set

  1. StartDisclosure
  2. Stage 1Armadillo protection engine
  3. Stage 2Deployed automatically
  4. EndProtected

Amber stages are time your environment spends exposed. The conventional row shows where protection comes from, not measured durations.

Review the benchmark method

03Modules03 / 06

03.1Inputs and outputs

What goes in, what Armadillo does, what comes out

Endpoint, network, session, port, event and vulnerability telemetry in one engine. Views below use synthetic example data.

Input
Agent identity, host state and health, engine and bundle version, CPU, disk and network metrics, installed software, processes, file changes
Process
Collect, normalize, track host state, analyze processes, files and software, correlate with detections and vulnerability context
Output
Host inventory and health, process events, file integrity events, software inventory, exposure findings, endpoint alerts, response targets

Process lineage, host app-prod-04

  • systemd PID 1
    • sshd: svc-deploy@pts/0 PID 4405
      • bash PID 4410
        • python3 /tmp/.x/upd.py PID 4471Suspicious
    • nginx PID 1204

File integrity event

Path
~svc-deploy/.ssh/authorized_keys
Change
modify
Before
9f2c…a41e
After
07bd…e913
Severity
High

03.2Advanced modules

Beyond the endpoint. Ten advanced modules, one console.

Network behavior, identities, automated response, AI agents, sensitive data and global threat intelligence now sit beside endpoint detection, on the same data model and in the same console. Every screen below is the real product.

Armadillo consoleExplainable alerts
Armadillo alert detail for an Oracle PeopleSoft exploit attempt, CVE-2023-22047, with summary, response and why it triggered

Every alert explains itself.

Open any alert and Armadillo shows why it fired: the rule that matched, the vulnerability it targets, the affected host, the attacker and the confidence. It also states what is known, what is not, possible benign explanations and the next steps to take.

  • Threats named by vulnerability (CVE)
  • Attacker and target on every alert
  • What is known and what is not
  • Possible benign explanations
  • Recommended next steps
  • Network context and evidence

OutcomeAnalysts understand every alert at a glance, without digging through logs.

Screens from the Armadillo console, test environment. See them on your own servers

03.3Module reference

Every module, input to output

Grouped by security plane.

Visibility

Visibility modules
ModuleWhat it doesWhat it produces
HostsTracks enrollment and health; classifies healthy, degraded or offlineHost inventory, health, agent actions
ProcessesProcess snapshot and history; evaluates suspicious indicatorsProcess events and investigation evidence
File integrityCompares watched file state; classifies create, modify, delete, rename, permission and ownership changesChange stream with path, severity, before and after hashes
Software inventoryFull snapshot, then deltas; tracks additions, removals and versionsPer host package inventory and history
TrafficAggregates and classifies flows; protocol analysis; top flowsFlow volume, protocol breakdown, top flows
SessionsBuilds session records; inbound or outbound; status and confidenceActive, resolved and high confidence sessions
PortsMaintains a baseline; detects changes; marks exposure and suspicious servicesOpen, exposed, suspicious, opened and closed in 24 hours
MonitoringTime series of CPU, disk and network per host and fleetMonitoring charts and averages
Command MapTraces every command from the platform to each agent; places servers on a topology by security stateDelivered, executed and applied status; live security topology

Intelligence

Intelligence modules
ModuleWhat it doesWhat it produces
Continuous intelligenceIngests threat knowledge for the protection engineUpdated detection content without a separate release cycle
Vulnerability exposuresServer side package to advisory correlation; severity by host and packageExposure counts, affected hosts and packages
IOC IntelligenceManages threat feeds, delivers indicators to every agent, matches live and historical telemetryIndicator matches, retro hunts, feed health
External sourcesIngests firewall, cloud audit and identity sign in events; typed rules tested before activationExternal alerts linked to affected hosts

Detection

Detection modules
ModuleWhat it doesWhat it produces
Protection engineTurns new intelligence into deterministic rules, validated before releaseValidated detection and prevention rules
IDS detection pathRule evaluation, detection decision, severity, SIEM correlationAlert with rule ID, source, destination, protocol, host
AlertsCorrelation and classification; severity and status workflowAlert queue; archive, investigate, acknowledge
Explainable alertsExplains each detection: rule, CVE, host, attacker, confidence, known and unknown, benign explanationsInvestigation ready alert with next steps
NDRBehavioral analytics on flows: beaconing, fan out, rare destinations, outbound volumeBehavioral findings mapped to MITRE ATT&CK
ITDRResolves identities, tracks privileged accounts, failed logins and sessionsIdentity risk scores and findings

Prevention

Prevention modules
ModuleWhat it doesWhat it produces
IPS prevention pathEnforcement decision; block, drop, reject or firewall actionThreat prevented, block and audit event
IP blocksPolicy check, queued firewall block, enforcement, expiry and failure handlingActive, enforced, failed and expired blocks
Rules and bundlesRule lifecycle and bundle management; distribution to agentsActive bundle state at enrolled hosts
AI Execution FirewallPolicy for the tools AI agents may run, enforced inside the Armadillo agent; deny by default for destructive and unknown toolsAllowed, held and denied decisions with approvals
Data SecurityClassifies sensitive files with tested rules; flags classified access followed by outbound transferExfiltration findings, destination risk, audit

Response

Response modules
ModuleWhat it doesWhat it produces
Response actionsAuthorization, dispatch, agent execution, result and audit captureKill process, diagnostics, restart or disable service, quarantine file, isolate host
CasesGroups related activity into an investigation workflowOwnership, status, history, resolution trail
Agent eventsAudits control plane actions and execution stateApplied, failed and pending actions with timestamps
ArchivePreserves records after triage; restore to active workflowSearchable archive and audit evidence
SOARPlaybooks of typed steps with approval gates, delays and branches; closed action libraryVerified, auditable automated response
Threat hunting and incidentsPoint and click hunting across telemetry; incidents built from correlated evidenceSaved hunts, incidents and linked cases

Management

Management modules
ModuleWhat it doesWhat it produces
Security overviewSummarizes platform wide operational and security stateCentral posture dashboard
ReportsQueries retained data and formats report sectionsPDF and CSV security reports
NotificationsRoutes alerts to configured destinationsSecurity alert emails
HealthAgent, service and engine health checksPosture status and warnings
Users and account securityAccess control and account managementAuthorized platform access
Host enrollmentInstall, register, associate to workspace, begin telemetryEnrolled host in inventory

03.4Processing flows

Ten end to end processing flows

How each kind of event moves through Armadillo.

A. Normal traffic

  1. Capture
  2. extract protocol
  3. flow and session
  4. evaluate IDS rules
  5. correlate
  6. decide

OutputBenign traffic passes; telemetry stored; no prevention action

03.5Telemetry

Telemetry Armadillo captures

The data elements the platform collects and correlates, by domain.

Data streaming through layered protection rings
Host and agent
Agent name, hostname, status, engine version, bundle version, last seen, health state
Alert
Detection title, rule ID, source IP, destination IP, protocol, severity, status, host, detected time, action
Traffic flow
Protocol, source, destination, bytes, flow count, time window, protocol totals
Session
Principal, initiator, receiver, service and port, protocol, start, end, duration, status, confidence, direction
Port event
Time, host, event type (baseline, opened, closed, attempt), protocol, port, service, confidence, risk, remote IP
Block event
Time, source IP, state, manual or automatic, detection, severity, port, duration, expiry, reason
Process
Name, PID, user, lineage, last observed, state, suspicious flag, host
File integrity
Time, severity, change type, path, user or UID, size, before and after hash, host
Software inventory
Host, snapshot type, OS and kernel context, package, version, source, timestamp
Vulnerability exposure
Advisory count, severity, affected host and package, mapping, last evaluated
Response event
Time, agent, kind, type, target, status, actor, resolved time, reason or incident reference
Monitoring
CPU, disk, network in, network out, host and fleet averages over time

04Response04 / 06

04.1Response

From detection to action

Armadillo does not stop at the alert. Prevention runs automatically where policy allows. Deeper actions are analyst initiated, authorized and audited. Select an action to follow its command path.

A digital shield of hexagonal cells fed by circuit traces, with an orange chevron

Automatic under policy

  • Block, drop or rejectWhen the IPS policy is enabled, confirmed malicious traffic is prevented and logged
  • Automatic IP blockingWhen auto blocking is enabled, detections queue a firewall block at the agent
  • Protection updatesNew rule bundles are deployed to active environments automatically

Analyst initiated

Command lifecycle

Kill process python3, PID 4471 on app-prod-04 synthetic example

  1. Authorization
  2. Dispatch
  3. Agent check in
  4. Execution
  5. Status returned
  6. Audit

04.2One scenario, end to end

The whole loop, in one scenario

A conceptual product walkthrough from new intelligence to audited response.

Conceptual walkthrough, not a customer incident

  1. 01

    IntelligenceINGEST

    New threat intelligence arrives

    An advisory describing a new exploit technique reaches Armadillo.

  2. 02

    DetectionRULE VALIDATED

    Armadillo produces validated protection

    The protection engine turns it into a deterministic rule, validated before release.

  3. 03

    ManagementBUNDLE CURRENT

    The protection bundle updates

    The rule joins a new bundle version and deploys to enrolled agents automatically.

  4. 04

    VisibilityTELEMETRY

    Suspicious activity appears

    Traffic matching the new rule reaches the network boundary.

  5. 05

    DetectionALERT

    IDS detects it

    Rule evaluation produces an alert with rule ID, source and host.

  6. 06

    PreventionIPS ACTIVE

    IPS enforces prevention

    With the IPS policy enabled, the flow is dropped and a block is recorded.

  7. 07

    DetectionCORRELATED

    Context is correlated

    Process, file and session telemetry on the host are linked to the alert.

  8. 08

    ResponseCASE OPEN

    A case opens

    The incident appears in the investigation workflow with all evidence.

  9. 09

    ResponseACTION READY

    Response is available

    An analyst can isolate the host, kill the process or quarantine a file.

  10. 10

    ManagementAUDIT

    The audit trail records it

    Every rule, block and action is recorded with actor, target and time.

05Deployment and outputs05 / 06

05.1In country processing

Security analysis that stays in country

Armadillo is designed for deployment models where telemetry, logs and traffic are analyzed on site or on in country infrastructure, with rules that remain visible and auditable.

The deployment model is agreed with each customer. It supports data residency requirements; it does not by itself establish compliance with a specific regulation.

Doha skyline at night

05.2What each team gets

What each team gets

SOC analyst
Prioritized alerts, correlated events, cases, process, file, network and session evidence, response actions, archive
Security administrator
Host health, agents, IPS policy, rules and bundles, blocks, notifications, account security, audit trail
Network and infrastructure
Traffic flows, protocol usage, open and exposed ports, connection attempts, sessions, blocked addresses, resource monitoring
Vulnerability and risk
Software inventory, advisory correlation, affected hosts and packages, severity distribution
Management
Security reports, incident and response audit trail, local processing posture, operational metrics

Built to keep the queue to real findings

Because Armadillo derives detections from defined threat conditions, every alert traces back to a condition an analyst can read. The design goal is a queue that reflects actual threat activity, with far less noise than probabilistic scoring produces.

05.3The console

One console, every module

Overview, hosts, alerts, traffic, sessions, ports, blocks, cases, processes, file integrity, software, vulnerabilities, reports, rules and bundles.

Conceptual Armadillo console panels: activity chart, alert queue and an escalated alert
ArmadilloConsole
Conceptual view, synthetic data
Hosts4846 healthy
Open alerts72 high
Active blocks12IPS on
Bundlev.nextcurrent

06Due diligence06 / 06

For security architects

Armadillo Technical Due Diligence

The technical dossier behind this page, for evaluators who need the system model rather than the summary.

Encrypted data streaming through layered protection rings
  1. Input, process, output modelSystem level and module by module
  2. Telemetry fieldsEvery data element Armadillo captures
  3. Processing flowsTen end to end flows, from normal traffic to reporting
  4. Rule automationMethod and validation, under NDA
  5. Time to protectionBenchmark definition and result

See Armadillo against your environment

A technical session with our engineers covering your stack, your threat model and how Armadillo would be deployed.