Data sharing and synchronization
Select the information exchanged by a connection and interpret source revisions, observation times, and interrupted synchronization.
Connector exchanges the information categories selected in each directional grant. Source products remain authoritative; received records carry source references and observation times so you can judge their scope and freshness.
Information categories
The categories define the content available for exchange:
| Category | Direction for Infra and Guard | Shared content |
|---|---|---|
| Resource inventory | Infra to Guard | Resource IDs, names, selected labels, region, and mappings |
| Operational state | Infra to Guard | Observed resource state and operation references with outcomes |
| Security summaries | Guard to Infra | Severity, finding and incident references, mapped assets, and observed protection state |
| External context | Custom integration to Infra or Guard | Mapped service, deployment, or ticket summaries and source links |
Credentials, volume contents, packet captures, raw endpoint evidence, and employee-sensitive detail are outside these categories. Evidence exports and workload data transfers use their source products' separate authorization and transfer workflows.
Source ownership and freshness
Infra owns infrastructure configuration and operation outcomes. Guard owns security findings, incidents, policies, and response results. Changes to those records use the source product's authorized workflows.
Received information retains the source resource ID, source revision when available, observation time, and receiving time. Receiving time establishes when a copy arrived; observation time establishes when the source reported it. Neither timestamp proves that a disconnected executor still has the same state.
Retries preserve record identity. Receivers use source revisions to prevent an earlier update from replacing a later revision. Delivery order does not establish the order in which product operations completed.
Interrupted synchronization
A failed direction leaves its received information at the last successful synchronization. Connection health and product health are separate: a connected adapter does not establish that every droplet, agent, or protected route is healthy.
Resuming a connection refreshes permitted present state. A refresh does not reconstruct event history that expired under the source product's retention. For an action with an unknown result, the original product operation remains the recovery reference.
Retention and destination copies
Shared records follow the receiving product's retention and hold rules. Pausing, revoking, or deleting a connection stops exchange according to its lifecycle; those actions do not delete records already received.
For data removal, use the destination's authorized deletion process and inspect its retention blockers. For more information about product retention, see Infra data residency and Guard evidence retention.
To change the categories or direction, follow Change the sharing selection.
For a focused selection procedure, use Share an Infra project with Guard or Return Guard security context to Infra. Customer applications can publish external context through the record API under a separately approved grant.