red, orange, and gray for critical, high, and medium, respectively, supporting immediate visual prioritization.
The Worm. OrbitKill finding represents the most urgent item, showing lateral propagation characteristics across
the 10.0.0.0/8 subnet. The security report summary panel permits the analyst to commit this assessment as a
hash-chain entry per Eq. (3). The results validate that φ(q) resolves the domain-specific threat nomenclature
correctly and that ψ consistently selects tabular rendering for structured multi-attribute event sets. The output
for the query “Show me failed login attempts for SpaceAgency-X systems.” The intent classifier φ(q) routes this
to the authentication failure class C₂, with ψ selecting V = bar_chart for comparing aggregated failure counts
across discrete system categories (Fig. 5). The resulting chart, titled “Failed Login Attempts by System”, presents
four system segments: Mission Control, which records approximately 23 failures; Satellite Comm 14; Data
Centre 12; and Ground Station 7. The AI narrative above the chart describes the retrieval approach: querying
Windows Event ID 4625 records from Winlogbeat agents alongside SSH and web authentication failure rules
from the wazuh-alerts-* index. The raw event entries shown below include repeated admin credential failures
on SX-CTRL-SRV-01 originating from 192.168.1.45 and a root login rejection on SX-GND-BLR-04 from
10.50.22.118. The clustering of 23 mission control failures from a single-source address over a narrow
timeframe is characteristic of an automated credential-stuffing or brute-force campaign targeting the
infrastructure’s most privileged tier. This output demonstrates CyRA’s capacity to distil raw log streams into a
prioritized, immediately actionable summary that conventional Kibana-based workflows would require
multiple expert queries to replicate.
The output of a network anomaly trend query is shown in Fig. 6. φ(q) assigns the input to the network anomaly
class C₃, and ψ selects V = line_chart is selected as the time-ordered format suited to the trend data. The chart,
entitled “Network Anomaly Trends (Last 24 Hours)” plots, shows the hourly aggregate anomaly counts across
the full day. Background activity is maintained at approximately 8–12 events per hour before it increases to
approximately 89 events at 16:00 and then decreases to 21 by the end of the day. The AI commentary isolates
two key findings from Suricata and Wazuh streams. The 16:00 surge is attributed to a spike in “ET SCAN
Potential SSH Scan” alerts directed at the Bengaluru Ground Station subnet, which is consistent with MITRE
ATT&CK T1071 (application layer protocol) reconnaissance activity.
[20]
Second, persistent low-level “GPL
ATTACK_RESPONSE” signature matches throughout the day suggest that ongoing outbound data exfiltration
attempts are blocked by the perimeter firewall. The system recommends investigating source IPs associated
with the 16:00 spike to determine whether they originate from authorized research partner address ranges or
external malicious actors. These results demonstrate CyRA’s ability to not only render a temporal visualization
but also provide structured threat-intelligence commentary correlated with known adversary techniques,
substantially reducing the analyst’s time to hypothesis formation. X systems?” Because this query lacks a single
narrow data focus, φ(q) resolves it to the general assessment class C₄, prompting ψ to select V = text as the
primary modality, augmented by a severity distribution chart. The AI narrative synthesizes intelligence
spanning all monitored threat dimensions: it enumerates active malware detections across satellite and ground-
segment agents, quantifies authentication anomalies in the recent monitoring window, and elevates the 16:00
network anomaly spike as the highest-priority open investigation item. The severity distribution chart offers a
proportional breakdown of open alerts across the critical, high, medium, and low bands, providing an immediate
grasp of risk concentration without additional category queries. This hybrid text-and-chart format is exclusive
to the general intent class, illustrating how ψ scales response richness to match query breadth. CyRA thus
demonstrates the capacity to address both tactical event-level and strategic posture-level analytical
requirements within a single conversational interface, a combination absent from all baseline systems in Table
3. Fig. 7. depicts CyRA’s handling of the broad posture query “What is the current security status of SpaceAgency-
X.”
5.3 Blockchain integrity verification
Hash-chain integrity was assessed by generating a controlled set of security reports and verifying that the chain
remained consistent with the formulation in Eq. (3). Deliberate modification of any stored field, index,
timestamp, payload, or predecessor hash produced an immediate and detectable SHA-256 mismatch,
confirming the tamper-evident character of the logging mechanism. Across 50 independently generated test
reports, every entry produced a unique, deterministically reproducible hash certificate.
5.4 Blockchain performance analysis
As noted, the logging subsystem is a single-node hash-chain rather than a fully distributed consensus
blockchain. Overhead profiling was conducted on a commodity development workstation (Intel Core i7, 16 GB
RAM). Per-block SHA-256 computation required 8.2 ms ± 0.6 ms on average, with each block occupying
approximately 512 bytes of storage. This overhead is negligible relative to the 1.3-second end-to-end query