Data residency
Where each product stores and processes data.
Logs stay on the organization’s own servers
Hosting and data flows should be understandable together. The deployment identifies where records and analysis run, who can access them and which external connections are enabled.
Locations
On-premises servers.
Customer-controlled deployment keeps the SIEM on infrastructure the organization operates. Supported platforms and disconnected operation are defined for the selected configuration.
Beside the SIEM.
Cyberdroid AI Detection, available now to select organizations, runs beside the SIEM on local CPUs and reads its export.
Local inference.
Cyberdroid AI Investigation, in early access, runs its models on the organization’s own hardware. Inference stays local unless an administrator sets an online fallback.
DLP deployment.
ARRTECH DLP runs on premises, as SaaS, hybrid or multi-tenant for service providers.
Verify
Routing metadata.
The routing record identifies the model used for a request. Any external model route is an explicit policy choice.
Outbound actions.
Notifications, ticketing and integrations may send information to other services. Their destinations, permissions and permitted data should be explicit in the configuration.
Limits
Other connections.
SaaS or hybrid components, timestamping, threat intelligence and updates can introduce external connections. Review those flows alongside model hosting and support access.
Page scope.
These summaries explain the product’s role. The proposed deployment identifies the enabled functions, supported configuration and operating responsibilities.
