Audit evidence
Records a third party can verify without us.
Signed logs an auditor can verify
Evidence is useful when another person can examine it. Signed exports from a SIEM provide a way to check record integrity independently of the original console.
Records
Signed logs.
ARRTECH SIEM signs every log as it is written and chains each file to the one before. A changed or missing file breaks the chain.
Daily timestamps.
External timestamping can support verification that signature files existed at a particular time. Its connection and operating requirements belong in the deployment plan.
Standalone export.
Any source exports with its signatures, certificate and a standalone verifier, which an auditor runs without the SIEM or ARRTECH.
Integrity reports.
Non-repudiation reports flag any faulty file, by day or by source.
Verify
Audit log.
The console records every login, search and configuration change, so administrators can check who did what.
Detector changes.
Cyberdroid AI Detection, available now to select organizations, records every detector promotion and rollback.
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
What signing proves.
A valid integrity check helps establish that the signed record has not changed. The accuracy of the source and the interpretation of its activity remain part of the review.
Page scope.
These summaries explain the product’s role. The proposed deployment identifies the enabled functions, supported configuration and operating responsibilities.
