krishicks cbf026366d fix(ocsf): require network activity endpoints (#3355) ...

Previously, Network Activity could be constructed without a source or
destination endpoint, allowing connection, accept, relay, and configuration
events to violate the OCSF 1.8 endpoint constraint.

Now, NetworkActivityBuilder requires a source or destination endpoint at
compile time. Connection failures identify the workload peer or genuine
transparent destination, listener failures identify the listening endpoint,
and mediation-lane failures use Application Lifecycle rather than fabricated
network endpoints. Malformed forward requests use HTTP Activity with a
method-only request, generated 400 response, and workload peer.

Additionally, Unix relay-channel events use Base Event, policy-validation
warnings use Config State Change, and the unused bypass monitor is removed
because the current isolation architecture no longer uses it.

Signed-off-by: Kris Hicks <khicks@nvidia.com>

2026-09-21 17:13:41 +00:00

..

accessing-logs.mdx

feat(sandbox): add canonical main process (#2726)

2026-08-20 22:18:23 +00:00

logging.mdx

fix(ocsf): require network activity endpoints (#3355)

2026-09-21 17:13:41 +00:00

ocsf-json-export.mdx

fix(ocsf): require network activity endpoints (#3355)

2026-09-21 17:13:41 +00:00