Connected system
An agent gateway, application, workflow service or telemetry source you control.
Security
Bring every connected system into view.
Arkna brings their activity into one record, while keeping every source clear.
Check a sample record →
Gateway
Policy
Approval
CRM
Identity
ITSM
Telemetry
Provider
Arkna record
Observed activity
Data path
How connected activity becomes a record.
Capture method
Proxy, SDK or existing telemetry, selected for the workflow and its review question.
Arkna record
Observed events organised with source references, timing, controls and review context.
Reviewer output
A readable view or export prepared for the person responsible for checking the workflow.
Coverage depends on connected sources and the activity they make available.
Two separate questions
Integrity is not completeness.
Integrity asks whether included data changed. Coverage asks what was included at all.
Did included data change?
Hash-chain checks can show whether the events included in an export still match the record produced by Arkna.
What was included at all?
The capture statement identifies connected sources, observed activity and known gaps. It does not turn an unseen event into a seen one.
Current public position
What can be checked now.
| Area | Status | Public position |
|---|---|---|
| Browser verification | Available | You can check the sample pack in your browser. Its contents never return to Arkna. |
| Hash-chain integrity | Available | You can recompute the included sample events and compare them with the export. |
| Capture coverage | Scoped | Coverage depends on the connection path and what each source emits. Arkna documents the boundary for each workflow. |
| Data residency | Scoped | We confirm deployment and residency requirements against your environment before implementation. |
| Retention and deletion | Scoped | We agree retention, access and deletion behaviour with you before deployment. |
| External time authority | Not claimed | Arkna does not offer an external timestamp service yet. We will name the operator and its trust model first. |
Security review
Questions we expect.
DataWhich fields does Arkna capture, minimise, exclude or redact for this workflow?
AccessWho can view, export or administer the record, and how is that access governed?
FailureWhat happens when a source, connection or downstream component is unavailable?
LifecycleWhere does the record live, how long do you keep it, and who deletes it?
Bring your architect
Bring the systems that matter into view.
We will map one workflow, its connected sources and the review question the record should answer.