Logging and Telemetry

3 articles

Agent Security Agentic Permissions AI Agent Security AI Governance Evidence Ai Impact Ai Integration AI Red Teaming AI SDLC & Product Security AI Security AI Security Engineer Career Ai Security Engineering AI Security Foundations AI Security Monitoring AI Security Tools AI Supply Chain AI System Inventory Architecture and Trust Boundaries Ats Systems Attack Career Development Corporate Culture Corporate Culture And Leadership Culture Security Cyber Security cybersecurity Cybersecurity Strategy Data Exposure and Privacy Defend Detection Engineering Distributed Governance Distributed Systems Economic Governance Education Evaluation and Regression Testing Evidence Future of Work governance Governance And Resilience Governance Evidence and Customer Trust Governance, Risk & Compliance Hiring & Talent Hiring Strategy Incident Response & Observability Leadership And Governance LLM Application Security Logging and Telemetry Map MLOps & Platform Security Model and Provider Risk Model Supply Chain Operational Risk Organizational Governance Organizational Resilience Platform Governance Privacy & Data Protection Prompt Injection Psychological Safety psychometrics RAG Authorization RAG Security Recruitment And Talent Red Teaming & Evaluations red-team seceng-workbench Secure Architecture & Design Secure RAG Security Architecture Stochastic Governance Stochastic Resilience Systemic Resilience Talent Acquisition Technical Intelligence Threat Modeling Toolchain Integrity Training & Workshops Vendor Risk & Procurement Workforce Science Workplace Evolution

Defend

Security Monitoring for AI Agents: How to Detect Dangerous Tool Use Before Damage Happens

Security monitoring for AI agents requires tool-call telemetry, action-sequence detection, approval-state tracking, memory monitoring, credential visibility, anomaly detection, and kill-switch response paths. Dangerous tool use should be detected before it becomes data leakage, unauthorized change, financial impact, or customer-facing error.

10 min read

Defend

AI Logging and Telemetry: What to Capture Without Creating a Privacy Disaster

AI systems need logs because you cannot rebuild what happened from vibes. Security teams need to know what prompt was used, what docs were found, what the model said, what tool was called, who approved it, and what happened next.

9 min read

Defend

Vector Database Security: Access Control, Tenant Isolation, Poisoning, and Forensic Logging

Vector database security requires the same seriousness as other production data infrastructure, with additional attention to embeddings, metadata filtering, retrieval authorization, tenant isolation, poisoning resistance, deletion workflows, and forensic logging.

11 min read