Product security
The controls built into each product.
Scoped access and recorded activity
Each key and role has its own scope, so an administrator can show who could reach what.
Controls
Signed agents.
Every agent is code-signed, and the console manages the certificates. The SIEM agent encrypts logs in transit and holds them if the server is unreachable.
Separate keys.
Individual agent credentials make access attributable and allow one agent’s permissions to be changed or revoked independently.
One vault.
A credential vault manages the accounts used by integrations. Connection checks and controlled access help the team maintain those links.
Scoped roles.
Each tenant has its own users and sources, and roles decide who reads each source and uses each feature. Sign-in is local or through Active Directory and LDAP.
Protected agents.
Administrative and tamper-protection controls help prevent unauthorized changes to endpoint agents. The supported controls are reviewed for the selected platform and configuration.
Verify
Signed logs.
ARRTECH SIEM signs and chains every log. Any source exports with a standalone verifier, so an auditor can check it without ARRTECH.
Audit log.
The console records every login, search and configuration change, so administrators can check who did what.
Recorded requests.
AI Investigation retains the request, outcome and reason, including work that needed approval or could not proceed. That record helps the team examine how the system used its permissions.
Limits
Page scope.
These summaries explain the product’s role. The proposed deployment identifies the enabled functions, supported configuration and operating responsibilities.
