AI Defence / Product tour
Inspect the evidence behind a decision.
Follow a fictional configuration finding across six views. The tour explains the intended operator experience and its evidence boundaries. These are illustrative interfaces, not screenshots of a deployed AI Defence application.
Illustrative product tour — synthetic data
Select a view to explore the workflow. The controls only change this demonstration. No endpoint is contacted, no command is issued and no incident is submitted.
Start with what was observed.
Review the coverage of this fictional assessment before interpreting any result.
The figures represent this synthetic case only. Unavailable checks do not count as passed checks.
- Linux host assessment
- Observed
- Selected configuration checks
- Observed
- Independent network validation
- Unavailable
- Windows validation
- Unavailable
View 1 of 6 · Scope
What each view helps you understand
Scope shows which synthetic checks have an observation and which remain unavailable. Host context identifies the fictional asset and distinguishes recent communication from a security verdict. The finding view connects the observed condition to a recommendation.
The authority view separates a proposal from an action. The evidence view compares a local result with missing independent coverage. The review view retains uncertainty instead of presenting an incomplete case as a verified repair. All six explanations remain available below the interactive surface.
| View | Reviewer task | Meaning and boundary |
|---|---|---|
| Scope | Identify what was examined. | Synthetic inventory and coverage; no live fleet management. |
| Host | Read context and freshness. | A heartbeat means communication, not security approval. |
| Finding | Understand the observation. | A configuration difference warrants review; it is not proof of intrusion. |
| Authority | Examine the proposed response. | No approval or execution occurs in the tour. |
| Evidence | Compare required observations. | A local pass cannot supply missing independent evidence. |
| Review | Record the outstanding decision. | Illustrates intended case handling; no deployed case-management UI is claimed. |
Request a demonstration of the current implementation
A live demonstration should identify the exact components running, show their inputs and results, and distinguish working integration from a simulated view. Ask to see a representative Linux report, collector configuration and handling of an unavailable check.
For a proposed deployment, include telemetry delivery, administrative access and any requested action or recovery path in the acceptance evidence. The contact route opens an email to Altari so you can describe the environment and the functions you want to evaluate.
Talk directly to Altari
Bring the environment.
Start with the right questions.
Discuss a demonstration, current capabilities and a bounded evaluation with Altari Systems.