# auditability Published articles for auditability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Want to use AI agents safely? Start with design DevFeed: [Want to use AI agents safely? Start with design]() Original publisher: [Read original article]() Author: Colin Eberhardt Published: 2026-08-18T13:12:00Z Content type: opinion Language: en Sources: [Scott Logic]() Topics: [Artificial Intelligence](), [AI Strategy](), [Security](), [Monitoring](), [Architecture & Design](), [Resilience]() Tags: [agentic-ai](), [agents](), [ai](), [artificial-intelligence](), [auditability](), [design](), [end-to-end-process](), [featured](), [governance](), [guardrails](), [monitoring](), [observability](), [operational-resilience](), [quality](), [risk-management](), [security](), [service-design](), [systems](), [trust]() ### AI overview This article argues that organisations adopting AI agents should begin with process and system design rather than controls alone. It explains that design should account for human and machine strengths, establish proportionate guardrails, and define how observability and monitoring evolve as the system matures. ### Source excerpt Concerns about control are one of the biggest barriers to adopting agentic AI, particularly in regulated environments. In this post, we discuss how organisations can harness AI safely by designing processes around the strengths of both humans and machines, then applying the right controls, guardrails and monitoring. ## Content Governance: Keeping Documentation Trustworthy DevFeed: [Content Governance: Keeping Documentation Trustworthy]() Original publisher: [Read original article]() Author: Selvaraaju Murugesan Published: 2026-08-14T13:14:46Z Content type: article Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [Documentation](), [Security](), [audit](), [trust](), [AI Agent](), [Requirements]() Tags: [agent](), [ai](), [audit](), [auditability](), [content](), [documentation](), [governance](), [security](), [technical-writing](), [trust]() ### AI overview This article explains content governance as a structured practice for keeping documentation accurate, secure, compliant, and trustworthy for both human readers and AI agents. It highlights regular audits, quality control, access controls, privacy and compliance checks, and synchronization with software releases. ### Source excerpt Only 21% of business and IT leaders report having a mature governance model ... The post Content Governance: Keeping Documentation Trustworthy appeared first on Document360. ## The rise of agentic platforms: Scaling beyond automation DevFeed: [The rise of agentic platforms: Scaling beyond automation]() Original publisher: [Read original article]() Author: Dima Dababneh Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Automation](), [Artificial Intelligence](), [observability](), [Security](), [Tooling]() Tags: [agentic](), [ai-agents](), [auditability](), [complexity](), [platform-engineering](), [platforms](), [safety](), [security](), [telemetry]() ### AI overview The article explains how platform engineering is evolving from static, rule-based automation toward governed, bounded autonomy. It presents agentic platforms as systems that use goal-driven, context-aware AI agents to reason across infrastructure, policies, telemetry, and workflows while operating within security, cost, and operational guardrails. ### Source excerpt Explore the evolution of platform engineering from static automation to governed, bounded autonomy. Learn how goal-driven, context-aware AI agents reduce cognitive load and scale complex platforms safely within defined constraints ## The foundation: Why Temporal for a data pipeline? DevFeed: [The foundation: Why Temporal for a data pipeline?]() Original publisher: [Read original article]() Author: Houman Kargaran Published: 2026-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [data](), [Orchestration](), [pii](), [Requirements](), [Resilience](), [consistency](), [Availability](), [observability](), [AI search](), [Embeddings]() Tags: [auditability](), [community](), [compliance](), [data](), [data-pipeline](), [embeddings](), [execution](), [foundation](), [requirements](), [resilience](), [search](), [temporal]() ### AI overview This tutorial explains how to justify Temporal as the orchestration layer for a PII-compliant complaint-ingestion pipeline. It covers requirements for resilience, consistency, availability, observability, redaction, internal classification, and semantic search over complaint data. ### Source excerpt How to justify Temporal for a regulated data pipeline: the requirements, the naive approach, and why Durable Execution wins on resilience and auditability. ## Auditable Agentic Orchestration: From Autonomous Systems to Governed Execution DevFeed: [Auditable Agentic Orchestration: From Autonomous Systems to Governed Execution]() Original publisher: [Read original article]() Author: Tom Stavert Published: 2026-07-08T00:00:00Z Content type: article Language: en Sources: [Scott Logic]() Topics: [agent orchestration](), [AI Agent](), [Orchestration](), [workflow automation](), [systems](), [Automation]() Tags: [agentic](), [ai-agents](), [artificial-intelligence](), [auditability](), [automation](), [distributed-systems](), [orchestration](), [workflow]() ### AI overview This article explains how agentic orchestration combines the flexibility of autonomous AI agents with deterministic workflow structures, explicit guardrails, and validation. It discusses workflow engines and agentic subprocesses as mechanisms for improving auditability and control without eliminating adaptive agent behavior. ### Source excerpt Giving AI agents free rein is easy. Trusting their output is hard. This post explores how workflow engines like Fluxnova, and its new Agentic Subprocess, bring auditability and control to agentic orchestration without sacrificing the flexibility that makes agents valuable. ## Prepare for the EU AI Act with Harness AI Security DevFeed: [Prepare for the EU AI Act with Harness AI Security]() Original publisher: [Read original article]() Author: Vikas Gautam Published: 2026-07-02T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Securing AI](), [Security](), [Responsibility & Safety](), [Model Context Protocol]() Tags: [ai](), [ai-security](), [auditability](), [compliance](), [data-governance](), [mcp](), [security](), [shadow-ai](), [vulnerabilities]() ### AI overview Harness describes how its AI Security platform supports EU AI Act compliance through AI asset discovery, risk classification, data-flow visibility, runtime protection, auditability, and continuous monitoring. ### Source excerpt Learn how Harness AI Security helps organizations meet EU AI Act requirements with AI asset discovery, risk classification, runtime protection, auditability, an | Blog ## Your riskiest supplier isn't a vendor. It's a registry. DevFeed: [Your riskiest supplier isn't a vendor. It's a registry.]() Original publisher: [Read original article]() Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Security](), [Open Source](), [npm](), [Maven](), [pip]() Tags: [apra](), [apra-compliance](), [auditability](), [chainguard-libraries](), [cps-230](), [cps-234](), [maven-central](), [npm](), [pypi](), [resilience](), [security](), [supply-chain]() ### AI overview The article argues that public package registries such as npm, PyPI, and Maven Central create an assurance gap for APRA-regulated institutions because organizations may consume artifacts without independently verifying their source or build process. It recommends source-built libraries as a more defensible approach to managing malware risk, operational resilience, and auditability. ### Source excerpt Public registries create supply chain risk. Learn how source-built libraries help APRA-regulated teams improve security, resilience, and auditability. ## Cockroach Labs announces CockroachDB capabilities for AI agents DevFeed: [Cockroach Labs announces CockroachDB capabilities for AI agents]() Original publisher: [Read original article]() Author: Lakshmi Kannan Published: 2026-03-25T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Cockroach Labs](), [MCP Server](), [Databases](), [Model Context Protocol](), [Agent Skills](), [AI research agents](), [Back end](), [Availability](), [Latency]() Tags: [agent-skills](), [agents](), [ai](), [ai-agents](), [auditability](), [backend](), [clusters](), [cockroach-labs](), [cockroachdb](), [database](), [distributed](), [mcp](), [mcp-server](), [operations](), [provisioning](), [scale](), [upgrades]() ### AI overview Cockroach Labs announces capabilities intended to make CockroachDB agent-ready, including a fully managed MCP Server, a redesigned ccloud CLI, and a public library of CockroachDB Agent Skills. The article describes requirements such as structured interfaces, scoped permissions, and auditability for agents operating across the database lifecycle. ### Source excerpt Today Cockroach Labs is announcing new capabilities that make CockroachDB agent-ready, giving AI agents a secure, structured way to work with your database. ## Enhancing Security with User-Specific Access Keys for DigitalOcean Functions DevFeed: [Enhancing Security with User-Specific Access Keys for DigitalOcean Functions]() Original publisher: [Read original article]() Author: Amulya Tomer Published: 2026-03-23T19:30:06Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Security](), [Access Control](), [Authorization](), [Serverless](), [upgrade]() Tags: [access-control](), [auditability](), [automation](), [digitalocean](), [security](), [serverless](), [trust-security](), [update](), [visibility]() ### AI overview DigitalOcean introduces user-specific namespace access keys for DigitalOcean Functions. The update replaces shared namespace credentials with keys tied to individual users, supporting automatic revocation when team members leave, multiple keys per namespace, improved accountability, and optional expiration. ### Source excerpt As teams grow and scale their serverless workloads, managing security postures becomes just as critical as managing code. Our goal at DigitalOcean is to support your growth at every stage. One way we support you is by iterating on our security architecture. Historically, DigitalOcean Functions used a shared credential model within a namespace that is configured in the settings tab of the function view. Same is shared among all users for a functions namespace While simple to start, this model presented challenges for growing teams: if a team member left or changed roles, the shared credentials remained valid. To secure the namespace, admins had to manually revoke and regenerate keys, disrupting workflows for every other developer and production workload using that shared key. Today, we are excited to announce a considerable upgrade to our access model: user-specific namespace access keys. This update shifts access control from the namespace level to the individual identity level, ensuring that access is granted to specific users rather than through a shared key. How user-specific access keys enhance security This transition to user-specific keys solves several critical use cases for teams: Automated access management: When a team member is removed from your DigitalOcean team, their specific access keys are automatically revoked by the platform. This removes the need for manual key rotation and ensures zero disruption to remaining team members. Multiple keys per namespace: A user can create multiple access keys for a namespace, this would allow for easier manual rotation and management of environment-specific keys. Streamlined accountability: Because actions are now associated with unique user-specific keys, you gain better visibility and auditability into resource management. Expiration support: To limit the attack surface further, access keys can optionally have expiration (TTL). The access key will fail to authenticate for any operation(s) after the expirat ## CockroachDB Plans Native X.509 SAN Support for SPIFFE and SPIRE Integration DevFeed: [CockroachDB Plans Native X.509 SAN Support for SPIFFE and SPIRE Integration]() Original publisher: [Read original article]() Author: Sanchit Khanna,Biplav Saraf Published: 2026-03-13T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Databases](), [SPIFFE](), [SPIRE](), [certificates](), [Zero Trust](), [Security](), [Microservice]() Tags: [architectures](), [auditability](), [aws-iam](), [certificates](), [cockroachdb](), [compliance](), [cryptographic](), [database](), [distributed](), [processor](), [regex](), [security](), [soc](), [soc-2](), [spiffe](), [spire](), [standards](), [teams](), [verification](), [zero-trust]() ### AI overview The article previews planned CockroachDB authentication support for Subject Alternative Name fields in X.509 certificates. It explains how SAN support is intended to enable integration with SPIFFE and SPIRE and support regex-based identity mapping for cloud-native workloads. ### Source excerpt In the evolution of cloud-native security, identity has become the new perimeter. ## How to design a resilient payments architecture for SaaS DevFeed: [How to design a resilient payments architecture for SaaS]() Original publisher: [Read original article]() Author: Joshua D'Costa Published: 2026-02-04T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Architecture & Design](), [Transactions](), [Concurrency](), [Availability](), [Scalability](), [observability](), [Security]() Tags: [architecture](), [auditability](), [availability](), [concurrency](), [how-to](), [observability](), [payments](), [saas](), [scalability](), [security](), [transactions]() ### AI overview A practical guide to designing resilient SaaS payment systems. It covers high availability, auditability, scalability, security, compliance, observability, explicit transaction states, retries, idempotency, concurrency control, event replay, and deduplication. ### Source excerpt Design a resilient SaaS payments architecture with idempotency, retries, billing flexibility, compliance controls, and global method support. ## Deploying a Cost-Effective, Scalable PhotoDNA System for CSAM Detection DevFeed: [Deploying a Cost-Effective, Scalable PhotoDNA System for CSAM Detection]() Original publisher: [Read original article]() Author: Anish Kumar Published: 2026-01-20T00:00:00Z Content type: article Language: en Sources: [Scribd Tech]() Topics: [Perceptual hashing](), [observability](), [Machine learning](), [Microsoft]() Tags: [auditability](), [aws](), [content-trust-series](), [cost](), [databricks](), [false-positives](), [featured](), [hashing](), [lambda](), [latency](), [legal](), [microsoft](), [observability](), [privacy](), [reporting](), [scale]() ### AI overview Scribd describes a production system for detecting known Child Sexual Abuse Material using PhotoDNA perceptual hashes. The article covers its integration with NCMEC reporting, ingestion-scale architecture, operational model, cost considerations, and safety-related constraints. ### Source excerpt Child safety is a non-negotiable responsibility for any platform that hosts user-generated content. Over the last year, we designed and deployed a production system that detects known Child Sexual Abuse Material (CSAM) using PhotoDNA perceptual hashes, integrates with the National Center for Missing and Exploted Children's (NCMEC) reporting system, and scales efficiently across our ingestion surfaces. This post explains the problem we set out to solve, how PhotoDNA hashing works, the online child-protection ecosystem (NCMEC, Tech Coalition, Project Lantern), our architecture and operational model, cost considerations, and key learnings. ## Secure AI Agent Infrastructure with Zero-Code MCP DevFeed: [Secure AI Agent Infrastructure with Zero-Code MCP]() Original publisher: [Read original article]() Author: boris.kurktchiev@goteleport.com (Boris Kurktchiev) Published: 2025-12-16T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Security](), [Model Context Protocol](), [AI Agent](), [Authorization](), [MCP Server]() Tags: [ai-agent](), [ai-security](), [auditability](), [authorization](), [least-privilege](), [mcp]() ### AI overview This tutorial explains how Teleport's zero-code MCP integration can secure AI agent infrastructure without writing authorization code or rewriting MCP servers. It describes MCP's role in connecting LLM-based applications to external systems and highlights authorization boundaries, least privilege, just-in-time access, and auditability. ### Source excerpt Secure AI agent workflows without writing authorization code. Teleport delivers least privilege, just-in-time access, and identity auditability for MCP agents. ## Operationalize Redpanda Connect with GitOps DevFeed: [Operationalize Redpanda Connect with GitOps]() Original publisher: [Read original article]() Author: Ben Barkhouse Published: 2025-12-02T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [GitOps](), [Kubernetes](), [CI/CD](), [internal developer portal](), [Command-line interface](), [Git]() Tags: [argo](), [argo-cd](), [auditability](), [cli](), [deployment](), [developer-experience](), [github](), [gitops](), [kubernetes](), [redpanda-connect](), [security](), [yaml]() ### AI overview This tutorial explains how to operationalize Redpanda Connect with GitOps on Kubernetes. It covers declarative management through Git and Argo CD, deployment workflows, and the differences between standalone mode and Streams mode for running pipelines. ### Source excerpt Here's how to operationalize Redpanda Connect with GitOps for less manual ops, predictable deployments, and a standard workflow. ## Orchestrating ambient agents with Temporal DevFeed: [Orchestrating ambient agents with Temporal]() Original publisher: [Read original article]() Author: Kevin Martin Published: 2025-09-18T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Model Context Protocol (MCP)](), [AI Agent](), [Orchestration](), [Artificial Intelligence](), [anthropic](), [OpenAI]() Tags: [agents](), [ai-agent](), [auditability](), [crypto](), [how-to](), [model-context-protocol-mcp](), [orchestration]() ### AI overview An article describes a 24/7 crypto trading platform built with multiple AI agents, using Temporal for durable workflow orchestration and the Model Context Protocol for tool interfaces. It explains how schedules, signals and queries, the Temporal UI, workflow orchestration, and MCP tools support proactive and self-refining agent behavior. ### Source excerpt How Temporal and MCP power a 24/7 crypto trading system of ambient agents: Schedules, Signals and Queries, durable tools, and auditability. ## Using Argo CD's targetRevision Field for Application Promotion DevFeed: [Using Argo CD's targetRevision Field for Application Promotion]() Original publisher: [Read original article]() Author: Kostis Kapelonis Published: 2025-08-01T13:57:26Z Content type: tutorial Language: en Sources: [Codefresh]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Helm charts]() Tags: [argo](), [argo-cd](), [argocd](), [auditability](), [best-practices](), [continuous-deployment](), [gitops](), [helm-charts](), [kubernetes](), [usability]() ### AI overview This guide explains how Argo CD's targetRevision field tracks Git repositories or Helm chart versions and why using it as a promotion mechanism for developer applications can create usability and auditability problems. It recommends using targetRevision: HEAD in ApplicationSets, with specific Helm versions used sparingly for mostly static infrastructure applications. ### Source excerpt In our big guide on how to use ApplicationSets for Argo CD applications, we explained the best practice of having a 3-level structure for all manifests with a clear distinction between Argo CD Application files and Kubernetes resource files. In that article, we also outlined several anti-patterns that we have seen in the wild, meaning [...] The post Abusing the Target Revision Field for Argo CD Promotions appeared first on Codefresh. ## Securing Model Context Protocol (MCP) with Teleport and AWS DevFeed: [Securing Model Context Protocol (MCP) with Teleport and AWS]() Original publisher: [Read original article]() Author: info@goteleport.com (Boris Kurktchiev, Dylan Souvage (AWS), Thierno Diallo (AWS)) Published: 2025-07-11T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Model Context Protocol](), [Amazon Web Services](), [anthropic](), [Amazon Bedrock](), [Strands Agents]() Tags: [agentic-ai](), [ai-agents](), [amazon-bedrock](), [anthropic](), [auditability](), [aws](), [credentials](), [how-to](), [implement](), [least-privilege](), [mcp](), [model-context-protocol](), [security]() ### AI overview This tutorial explains how to secure Anthropic's Model Context Protocol for enterprise AI agents using Teleport and AWS. It discusses least-privilege access, credential management, auditability, and behavioral visibility for MCP-based systems. ### Source excerpt Discover how to implement Anthropic's MCP for AI agents with Teleport and AWS. Eliminate static credentials, enforce least privilege, and ensure AI auditability. ## Your Infrastructure Has a Non-Human Trust Problem DevFeed: [Your Infrastructure Has a Non-Human Trust Problem]() Original publisher: [Read original article]() Author: jack.pitts@goteleport.com (Jack Pitts) Published: 2025-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Security](), [cloud security](), [Zero Trust](), [CI/CD](), [GitHub Actions](), [Kubernetes](), [Amazon Web Services](), [GitLab](), [Jenkins]() Tags: [agent](), [agents](), [auditability](), [aws](), [ci-cd](), [cloud-security](), [credentials](), [github-actions](), [gitlab](), [jenkins](), [kubernetes](), [secrets](), [security](), [token](), [tokens](), [zero-trust]() ### AI overview This article explains how non-human identities, including bots, CI/CD runners, and AI-driven automation, can create cloud security and resiliency risks when they use static credentials and excessive permissions. It presents Teleport Machine & Workload Identity as a way to use short-lived, scoped cryptographic credentials and reviews CI/CD deployment to Kubernetes as an example. ### Source excerpt Non-human identities are a major cloud security risk. Learn how to eliminate static credentials, enforce zero trust, and secure machine-to-machine access. ## Exploring DORA Compliance in Practice: Key Takeaways from Our Recent Webinar DevFeed: [Exploring DORA Compliance in Practice: Key Takeaways from Our Recent Webinar]() Original publisher: [Read original article]() Author: sami@goteleport.com (Sami Ali) Published: 2025-05-07T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [IAM](), [Access Control](), [identity and access management](), [Authorization](), [Security](), [Resilience](), [Monitoring]() Tags: [access-control](), [auditability](), [compliance](), [emea](), [eu](), [financial](), [governance](), [iam](), [identity](), [identity-and-access](), [monitoring](), [security](), [webinar]() ### AI overview This webinar recap explains how the EU's Digital Operational Resilience Act (DORA) affects access control, identity governance, auditability, and third-party risk for financial institutions and service providers. It describes how Teleport can support practical controls such as role-based access and scoped infrastructure access. ### Source excerpt Learn how financial institutions can achieve DORA compliance through practical IAM solutions, with insights from Teleport and Falx on implementing effective controls. ## Mitigating software supply chain risks through faster vulnerability response and verified software images DevFeed: [Mitigating software supply chain risks through faster vulnerability response and verified software images]() Original publisher: [Read original article]() Published: 2024-04-16T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Vulnerabilities](), [open-source-security](), [chainguard images](), [supply chain attacks]() Tags: [auditability](), [chainguard-images](), [cve-2024-3094](), [golang](), [liblzma](), [sbom](), [software-bill-of-materials](), [software-supply-chain](), [supply-chain-attacks](), [supply-chain-integrity](), [supply-chain-security](), [vulnerabilities](), [xz](), [xz-backdoor](), [zero-trust]() ### AI overview The article discusses the xz vulnerability, the risk of future software supply chain attacks, and the importance of rapid patch propagation and software inventory auditability. It presents Chainguard Images as a continuously verified and auditable approach to mitigating these risks. ### Source excerpt Software backdoors are a threat. Learn how to mitigate supply chain security risks by responding faster to vulnerabilities like the xz flaw. ## What do we really mean by microservice configuration? DevFeed: [What do we really mean by microservice configuration?]() Original publisher: [Read original article]() Author: Dominic Black Published: 2022-10-27T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [configuration](), [Microservice](), [API](), [Back end](), [Go Language]() Tags: [api](), [auditability](), [backend](), [configuration](), [go](), [source]() ### AI overview The article explains how Encore designed its configuration API for applications that use different infrastructure resources across local, pull request preview, testing, and production environments. It discusses compile-time safety, clear configuration provenance, descriptive comments, auditability, and storing configuration alongside source code. ### Source excerpt The story of how Encore ended up designing its config API