- Home
- Armadillo platform

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.

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.

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

One engine, no seams
Sources feed a single engine that correlates, validates and decides. Select a stage to see what it does.
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.
Management plane
Security overview, hosts and health, bundles and rules, reports in PDF and CSV, notifications, users, host enrollment
Response plane
Response actions, cases, archive, agent event audit trail
Prevention plane
IPS block, drop and reject, manual and automatic IP blocks, containment through response actions
Detection plane
Deterministic rules, IDS detection path, alerts, SIEM ingestion and real time correlation
Intelligence plane
Continuous threat intelligence, vulnerability intelligence, correlation context
Visibility plane
Endpoint and host, processes, file integrity, software inventory, ports, sessions, network traffic, monitoring
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.
New threat intelligence
Advisories, exploit information and indicators, or a detailed attack description.

Protection engine
Produces deterministic detection and prevention rules that are validated before release and remain auditable.
Internal method shared under NDAActive 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.
- Intelligence received
- Protection engine
- Bundle deployed
- Protection active
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
- StartDisclosure
- Stage 1Vendor research
- Stage 2Signature authoring
- Stage 3Vendor testing
- Stage 4Update release
- Stage 5Your change window
- EndProtected
Armadillo workflow Maximum observed end to end: 5 seconds, completed reported test set
- StartDisclosure
- Stage 1Armadillo protection engine
- Stage 2Deployed automatically
- EndProtected
Amber stages are time your environment spends exposed. The conventional row shows where protection comes from, not measured durations.
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
- bash PID 4410
- nginx PID 1204
- sshd: svc-deploy@pts/0 PID 4405
File integrity event
- Path
- ~svc-deploy/.ssh/authorized_keys
- Change
- modify
- Before
- 9f2c…a41e
- After
- 07bd…e913
- Severity
- High
- Input
- Flows, source and destination, protocol, volume, packet and flow metadata, internal and external communications
- Process
- Inspect traffic, identify protocols, match IDS and IPS rules, correlate, classify risk, optionally prevent
- Output
- Flow records, detections, alerts, blocked traffic and addresses, protocol breakdown, investigation context
Benign flows pass. A flow matching an active rule stops at the boundary when IPS is enabled.
- Input
- SSH, RDP, FTP and other inbound and outbound sessions with initiator, receiver, service, port, start, end and duration; Open, closed and newly opened ports, internet exposed ports, suspicious services, connection attempts, remote address
- Process
- Reconstruct sessions, classify direction and service, evaluate suspicion, correlate with host and network events; Baseline ports, detect state changes, classify exposure, apply suspicious port logic, correlate
- Output
- Session log with status and confidence, linked alerts and cases; Open, exposed and suspicious counters, port event log, exposure findings, possible alert or block
| Service | Direction | Initiator | Confidence |
|---|---|---|---|
| SSH 22 | Inbound | 10.0.4.21 | High |
| RDP 3389 | Inbound | 198.51.100.7 | Review |
| FTP 21 | Outbound | 10.0.2.9 | Medium |
Port events, last 24 hours
- 8080 newly opened Internet exposed
- 5432 baseline Internal only
- 3389 connection attempts Suspicious
- Input
- Agent events, alerts, rule IDs, severity, status, timestamps, source, destination, host, protocol
- Process
- SIEM ingestion, normalization, real time correlation, deduplication and grouping, severity and status workflow, case logic
- Output
- Alert queue, correlated incidents, cases, archive, dashboards, reports, notifications
- HighPort 3389 newly exposed on ws-fin-117
- HighRDP session from external address
- CriticalSuspicious process spawned by session
Correlated into one case with three linked alerts
- Input
- Installed package and version data plus advisory and CVE data
- Process
- Match packages to advisories, correlate hosts and packages, classify severity, aggregate exposure
- Output
- Exposures by severity, affected packages and hosts, prioritization context
- Inventoryopenssl 3.0.2 on 3 hosts
- Mappingpackage and version resolved
- AdvisoryADV-EXAMPLE-07 matched
- Exposure3 hosts affected
- PriorityCritical
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.

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.

Every protective command, traced to its result.
Command Map follows each instruction from the platform to every agent and shows whether it was delivered, executed and applied. A live topology places each server by security state, from critical and uncontained to fully protected.
- Command flow from request to applied result
- Live topology by security state
- Failed and expired commands surfaced
- Incident response view
- Live updates, no refresh needed
OutcomeProof that every protective action actually reached its target.

Network behavior that signatures miss.
NDR analyzes the connections your servers make and flags behavior that does not fit: hidden communication with attacker infrastructure, a server suddenly reaching many destinations, rare destinations and unusual volumes of data leaving the network.
- Beaconing detection
- Fan out detection
- Rare destination detection
- Outbound volume anomalies
- Findings mapped to MITRE ATT&CK
- Destination and network asset views
OutcomeBehavior based detection that complements signatures and catches what they cannot.

Protect the identities attackers target first.
ITDR brings accounts into the security picture. It resolves identities across servers, keeps privileged accounts under watch, tracks failed logins and sessions, and scores the risk of every identity so stolen or misused credentials do not go unnoticed.
- Identity resolution across servers
- Privileged account tracking
- Failed login and session monitoring
- Risk score for every identity
- Identity findings and investigation
- Connectors and response history
OutcomeAccount takeover and misuse become visible before they become a breach.

Automate response, without losing control.
SOAR turns response procedures into playbooks of typed steps, with approval gates where they matter and verification that every action actually took effect. Agents accept actions only from a closed, typed library, never an arbitrary command.
- Playbooks with approvals, delays and branches
- Closed library of typed actions
- Reversible actions where possible
- Verification that each action worked
- Approval queue and execution timeline
- Failure and recovery tracking
OutcomeConsistent, auditable response at machine speed, with people in charge.

Guardrails for the AI agents on your servers.
As AI assistants and agents gain access to servers and tools, the AI Execution Firewall decides what they may run and enforces that decision inside the Armadillo agent on the host. Destructive or unknown tools are denied by default.
- Policies for each AI tool
- Deny by default for destructive and unknown tools
- Approval workflow for held actions
- Inventory of AI agents and MCP servers
- Tool activity and alerts
- Enforcement coverage per agent
OutcomeAdopt AI on your infrastructure without handing it the keys.

Know where sensitive data lives, and when it moves.
Data Security classifies sensitive files with rules your team writes and can test against any path, then flags access to classified files that is followed by an outbound transfer. No model guesses at your data: every label has a rule behind it.
- Restricted, confidential, internal and public labels
- Test any path against your rules
- Sensitive asset discovery
- Data movement and file operations
- Exfiltration findings
- Destination risk, prevention policy and audit
OutcomeSensitive data stays visible, governed and accounted for.

Global threat intelligence, at work on every server.
IOC Intelligence brings threat feeds into Armadillo, delivers the indicators to every agent and matches them against server activity, both live and looking back in time with retro hunts across stored telemetry.
- Feed management with reliability and expiry
- Indicators delivered to every agent
- Matching across server telemetry
- Retro hunts over historical data
- Feed health monitoring
- Suppressions and incident links
OutcomeKnown threats are recognized the moment they touch your environment.

From a hunch to a closed case.
Analysts hunt across collected telemetry by selecting observed values, with no query language to learn. Related evidence is grouped into incidents, and cases track every investigation through to closure.
- Point and click threat hunting
- Saved searches and export
- Incidents built from correlated evidence
- Case management with linked alerts
- Alert archive with restore
- Email notifications
OutcomeInvestigations move faster, and nothing gets lost along the way.
- Firewalls
- Cloud audit logs
- Identity providers
- Other security tools

- Alerts linked to hosts
- Ticketing and chat
- Another SIEM
Bring your other security tools into one picture.
Armadillo takes in events from firewalls, cloud audit logs and identity providers, turns them into alerts with detection rules that are tested before activation, and links every external alert to the affected server.
- Firewall, cloud audit and sign in events
- Typed detection rules, tested before activation
- External alerts linked to affected servers
- Findings shared with ticketing, chat or another SIEM
OutcomeOne place to see and act on security events from across your environment.
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
| Module | What it does | What it produces |
|---|---|---|
| Hosts | Tracks enrollment and health; classifies healthy, degraded or offline | Host inventory, health, agent actions |
| Processes | Process snapshot and history; evaluates suspicious indicators | Process events and investigation evidence |
| File integrity | Compares watched file state; classifies create, modify, delete, rename, permission and ownership changes | Change stream with path, severity, before and after hashes |
| Software inventory | Full snapshot, then deltas; tracks additions, removals and versions | Per host package inventory and history |
| Traffic | Aggregates and classifies flows; protocol analysis; top flows | Flow volume, protocol breakdown, top flows |
| Sessions | Builds session records; inbound or outbound; status and confidence | Active, resolved and high confidence sessions |
| Ports | Maintains a baseline; detects changes; marks exposure and suspicious services | Open, exposed, suspicious, opened and closed in 24 hours |
| Monitoring | Time series of CPU, disk and network per host and fleet | Monitoring charts and averages |
| Command Map | Traces every command from the platform to each agent; places servers on a topology by security state | Delivered, executed and applied status; live security topology |
Intelligence
| Module | What it does | What it produces |
|---|---|---|
| Continuous intelligence | Ingests threat knowledge for the protection engine | Updated detection content without a separate release cycle |
| Vulnerability exposures | Server side package to advisory correlation; severity by host and package | Exposure counts, affected hosts and packages |
| IOC Intelligence | Manages threat feeds, delivers indicators to every agent, matches live and historical telemetry | Indicator matches, retro hunts, feed health |
| External sources | Ingests firewall, cloud audit and identity sign in events; typed rules tested before activation | External alerts linked to affected hosts |
Detection
| Module | What it does | What it produces |
|---|---|---|
| Protection engine | Turns new intelligence into deterministic rules, validated before release | Validated detection and prevention rules |
| IDS detection path | Rule evaluation, detection decision, severity, SIEM correlation | Alert with rule ID, source, destination, protocol, host |
| Alerts | Correlation and classification; severity and status workflow | Alert queue; archive, investigate, acknowledge |
| Explainable alerts | Explains each detection: rule, CVE, host, attacker, confidence, known and unknown, benign explanations | Investigation ready alert with next steps |
| NDR | Behavioral analytics on flows: beaconing, fan out, rare destinations, outbound volume | Behavioral findings mapped to MITRE ATT&CK |
| ITDR | Resolves identities, tracks privileged accounts, failed logins and sessions | Identity risk scores and findings |
Prevention
| Module | What it does | What it produces |
|---|---|---|
| IPS prevention path | Enforcement decision; block, drop, reject or firewall action | Threat prevented, block and audit event |
| IP blocks | Policy check, queued firewall block, enforcement, expiry and failure handling | Active, enforced, failed and expired blocks |
| Rules and bundles | Rule lifecycle and bundle management; distribution to agents | Active bundle state at enrolled hosts |
| AI Execution Firewall | Policy for the tools AI agents may run, enforced inside the Armadillo agent; deny by default for destructive and unknown tools | Allowed, held and denied decisions with approvals |
| Data Security | Classifies sensitive files with tested rules; flags classified access followed by outbound transfer | Exfiltration findings, destination risk, audit |
Response
| Module | What it does | What it produces |
|---|---|---|
| Response actions | Authorization, dispatch, agent execution, result and audit capture | Kill process, diagnostics, restart or disable service, quarantine file, isolate host |
| Cases | Groups related activity into an investigation workflow | Ownership, status, history, resolution trail |
| Agent events | Audits control plane actions and execution state | Applied, failed and pending actions with timestamps |
| Archive | Preserves records after triage; restore to active workflow | Searchable archive and audit evidence |
| SOAR | Playbooks of typed steps with approval gates, delays and branches; closed action library | Verified, auditable automated response |
| Threat hunting and incidents | Point and click hunting across telemetry; incidents built from correlated evidence | Saved hunts, incidents and linked cases |
Management
| Module | What it does | What it produces |
|---|---|---|
| Security overview | Summarizes platform wide operational and security state | Central posture dashboard |
| Reports | Queries retained data and formats report sections | PDF and CSV security reports |
| Notifications | Routes alerts to configured destinations | Security alert emails |
| Health | Agent, service and engine health checks | Posture status and warnings |
| Users and account security | Access control and account management | Authorized platform access |
| Host enrollment | Install, register, associate to workspace, begin telemetry | Enrolled host in inventory |
03.4Processing flows
Ten end to end processing flows
How each kind of event moves through Armadillo.
A. Normal traffic
- Capture
- extract protocol
- flow and session
- evaluate IDS rules
- correlate
- decide
OutputBenign traffic passes; telemetry stored; no prevention action
B. Known malicious traffic
- Rule match
- classify severity
- alert
- enforce block or drop when IPS is enabled
- log
- correlate into a case
OutputAlert with rule ID, prevention, audit trail, case update
C. New threat intelligence
- Ingest
- Armadillo protection engine
- deploy to the rule base
OutputNew bundle distributed; matching traffic detected and, with IPS enabled, prevented
D. Vulnerable software
- Package to advisory correlation
- severity
- host and package aggregation
OutputExposure view with affected hosts and packages
E. Sensitive file change
- Compare state and hash
- classify the change
- assign severity
- correlate with process
- user and host
OutputFile integrity event with before and after hashes
F. Suspicious process
- Evaluate against rules and context
- flag
- correlate with host
- network and file activity
OutputProcess evidence; analyst can kill the process, quarantine a file, isolate the host or collect diagnostics
G. Remote access session
- Reconstruct the session
- classify direction and service
- correlate with confidence
OutputSession record, possible alert or case
H. Port exposure change
- Update baseline
- classify exposure and service
- correlate
- alert when risk logic matches
OutputPort event, exposure status, optional block
I. Analyst response
- Authorization
- queue command
- agent check in
- execute
- return status
- audit
OutputApplied, failed or pending action
J. Reporting
- Query
- aggregate
- format
- export
OutputPDF or CSV report for audit and management
03.5Telemetry
Telemetry Armadillo captures
The data elements the platform collects and correlates, by domain.

- 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.

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
- Authorization
- Dispatch
- Agent check in
- Execution
- Status returned
- 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
- 01
New threat intelligence arrives
An advisory describing a new exploit technique reaches Armadillo.
- 02
Armadillo produces validated protection
The protection engine turns it into a deterministic rule, validated before release.
- 03
The protection bundle updates
The rule joins a new bundle version and deploys to enrolled agents automatically.
- 04
Suspicious activity appears
Traffic matching the new rule reaches the network boundary.
- 05
IDS detects it
Rule evaluation produces an alert with rule ID, source and host.
- 06
IPS enforces prevention
With the IPS policy enabled, the flow is dropped and a block is recorded.
- 07
Context is correlated
Process, file and session telemetry on the host are linked to the alert.
- 08
A case opens
The incident appears in the investigation workflow with all evidence.
- 09
Response is available
An analyst can isolate the host, kill the process or quarantine a file.
- 10
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.
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.

| Severity | Detection | Rule ID | Action |
|---|---|---|---|
| Critical | Exploit attempt, web service | AR-EXAMPLE-0142 | Blocked |
| High | Lateral movement pattern | AR-EXAMPLE-0088 | Case opened |
| Medium | Unexpected outbound volume | AR-EXAMPLE-0031 | Investigating |
| Service | Direction | Initiator | Confidence |
|---|---|---|---|
| SSH 22 | Inbound | 10.0.4.21 | High |
| RDP 3389 | Inbound | 198.51.100.7 | Review |
| FTP 21 | Outbound | 10.0.2.9 | Medium |
Port events, last 24 hours
- 8080 newly opened Internet exposed
- 5432 baseline Internal only
- 3389 connection attempts Suspicious
| Change | Path | Host | Severity |
|---|---|---|---|
| modify | /home/svc-deploy/.ssh/authorized_keys | app-prod-04 | High |
| create | /tmp/.x/upd.py | app-prod-04 | Medium |
| create | C:\Users\Public\Libraries\svc.dll | ws-fin-117 | High |
- Inventoryopenssl 3.0.2 on 3 hosts
- Mappingpackage and version resolved
- AdvisoryADV-EXAMPLE-07 matched
- Exposure3 hosts affected
- PriorityCritical
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.

- Input, process, output modelSystem level and module by module
- Telemetry fieldsEvery data element Armadillo captures
- Processing flowsTen end to end flows, from normal traffic to reporting
- Rule automationMethod and validation, under NDA
- 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.
