The Visibility Gap: Turning Observability into DevSecOps Signals (sponsored by Datadog)Security teams and dev teams share the same production environment but operate from different signals. Without runtime context, security monitoring has blind spots with misconfigured infrastructure and threats in flight. This session draws on Fone Dynamics' ISO 27001 journey to show how runtime telemetry, cloud audit logs, and code scanning give DevSecOps and SecOps teams shared context.
What this session is about
Playbook
Editorial commentary · what to actually do about this on Monday
The concept
SecOps and DevOps see the same systems through different lenses. Runtime telemetry becomes the shared substrate that makes them speak the same language.
Why it matters
Vulnerability scans tell you what *could* be wrong. Runtime telemetry tells you what *is* wrong, right now. ISO 27001 (and most modern audits) want evidence of controls *operating*, not just existing.
The hard parts
Mapping abstract control language ("access is restricted to authorised users") to concrete log events ("user X read object Y from bucket Z") is laborious. Most orgs duck it.
Playbook moves
(1) Build a control-to-signal map: one row per control, one column per evidence source. (2) Anything without a signal source is a paper control — burn those down. (3) Tag existing logs with control IDs at ingestion, not at audit time.
The surprise
The fastest path to ISO 27001 evidence isn't more controls — it's tagging existing logs to existing control IDs. Most enterprises already have 70%+ of evidence; they just can't find it on demand.
---
Independent editorial perspective — not an official AWS or speaker statement. Designed for executives evaluating what to brief their teams on next.
Live updates related to this session LIVE
Sourced via Parallel AI Monitor — continuous web watch on 21 topical streams. Updated .
- ovaledge.com Decision lineage & audit trails for agents
Governed context observability for AI agents explained
Google Cloud’s Gemini Enterprise Agent Platform observability documentation describes using OpenTelemetry telemetry to monitor agents and MCP servers through metrics, traces, and logs. It covers execution paths, multi-agent system visibility, and monitoring policy interceptions i
- docs.cloud.google.com Decision lineage & audit trails for agents
Observability overview | Gemini Enterprise Agent Platform | Google Cloud Documentation
Google Cloud’s Gemini Enterprise Agent Platform observability documentation describes using OpenTelemetry telemetry to monitor agents and MCP servers through metrics, traces, and logs. It covers execution paths, multi-agent system visibility, and monitoring policy interceptions i
- thenewstack.io Decision lineage & audit trails for agents
The agent didn't break your controls. It went around them.
VentureBeat reported that AI agents create a security and accountability gap when they can read data and modify systems without sufficient observability. Traditional security logging may not capture the agent’s contextual reasoning, tool calls, or the chain of actions needed to r
- instagram.com high confidence Decision lineage & audit trails for agents
AI agents are moving beyond experimentation and into ...
Camunda announced real-time AI-agent observability in Camunda 8.10. Its Operate interface shows each agent’s current state, active tool calls, model and token usage, guardrail limits, full conversation history, and the reasoning behind tool choices. The same process-instance reco
- venturebeat.com Decision lineage & audit trails for agents
AI agents are exposing a security gap between the data ...
VentureBeat reported that AI agents create a security and accountability gap when they can read data and modify systems without sufficient observability. Traditional security logging may not capture the agent’s contextual reasoning, tool calls, or the chain of actions needed to r
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.