9 posts tagged with #agentic-ai
Part 1 of the series "Building a Partner Sales Agent on Amazon Bedrock AgentCore", built around one real project: a conversational agent that connects HubSpot CRM and AWS Partner Central for an AWS Partner's sales team.
We knew shadow IT. Now comes shadow code: production code that AI agents write past IT, security, and compliance. 79 percent of organisations have no overview of the agents running in their environment. Four risks that get bought along unnoticed, and an audit in three steps.
Around 95 percent of enterprise GenAI pilots show no measurable impact. Why the step from pilot to production is the hardest one of all — and what the few exceptions do differently. From my own experience building a product with AI agents over five months.
A field report from one of AWS’ newest AI-driven security services - from setup to findings to verdict.
AWS launched Amazon Bedrock AgentCore Payments with Coinbase and Stripe. This is not just a feature update. It is the moment agents move from planners to actors with financial impact. What that means for architects and CISOs.
67 percent of security leaders do not know which AI models and agents are running in their organisation. That is the core finding of the Pentera 2026 Report. And while Gartner projects that 40 percent of all enterprise apps will have AI agents built in by end of 2026, both curves are moving in the wrong direction.
79 percent of organisations are deploying or testing Agentic AI. Only 21 percent have a mature governance model for it. That is not a surprise - it is the consequence of governance always lagging behind technology. Three core questions every CISO team needs to answer now.
393 test files, all green. Then a colleague sat down with me. What he showed was systematic: AI-generated tests fail in predictable patterns. The seven anti-patterns I documented in my codebase - and how a Kiro Skill fixes them.
Vibe coding may work for prototypes. For enterprise code with security requirements, it is an architectural dead end. How AWS Kiro charts a radically different path with spec-driven development - and what 175,000 lines of code in 19 days says about that path.
