Quote for the day:
"I find that the harder I work, the more luck I seem to have." -- Thomas Jefferson
🎧 Listen to the audio debrief on YouTube
▶ Play Audio DigestDuration: 25 mins • Perfect for listening on the go.
AI agents need more than access control — they need identity at runtime
As companies introduce artificial intelligence programs into their networks
faster than human workers, traditional security systems are struggling to keep
up. Most current access management tools were built for people, relying on
simple passwords and broad job roles. Artificial intelligence programs,
however, require a completely different approach to trust and security.
According to industry experts, these programs need a rigorous onboarding
process similar to what a new employee experiences. Every program needs a
verifiable identity, secure credentials tied directly to hardware, and highly
restricted permissions. Instead of granting general access to an entire
application, organizations must shift to strict action control. This means
giving a program permission to perform only one specific task for a brief,
limited window of time. To maintain security, companies must continuously
verify these identities in real time, inspecting every action before it occurs
and keeping detailed records. Security teams must first discover all the
automated programs already operating within their networks, as many are often
deployed without formal oversight. By establishing clear identities and moving
away from easily shared passwords, organizations can safely integrate these
new automated tools without exposing their core systems to unnecessary risks
or unauthorized actions.5 Ways AI Governance Lowers the AI Hallucination Tax
Deploying AI without proper oversight carries significant risks, a challenge often referred to as the "hallucination tax." This term describes the hidden costs that arise when AI agents deliver incorrect outcomes, forcing human teams to constantly monitor, validate, and correct their work. The danger isn't just that AI makes mistakes—humans do too—but that AI often presents these errors with absolute confidence, creating a false sense of security. Several factors contribute to this tax. First, asking AI to answer questions using unorganized or incorrect data can lead to meaningless results. Second, letting AI agents scan massive amounts of unstructured data without guidelines drives up computing costs and wastes time. Finally, models and data naturally drift or decay over time, meaning an unmonitored AI will eventually stray from its intended behavior. To reduce these risks, experts recommend establishing strong AI governance. This involves building a unified registry of AI use cases, grounding agents in shared terminology, and monitoring systems for drift. Good governance shouldn't just be about creating rules; it should act as a guiding force that provides clear guardrails, ensuring that your AI capabilities remain accurate, cost-effective, and trustworthy as they scale.What Modern Data Architectures Require Today
Modern SAP data integration must go far beyond basic extraction to support
today's cloud, lakehouse architectures, and AI applications. While the core goal
remains extracting operational data for analytics, the methods and requirements
have evolved significantly. Businesses now need highly up-to-date, traceable,
and well-contextualized data that operates seamlessly across diverse platforms
like Microsoft Fabric, Databricks, or Snowflake without locking them into a
single vendor. To achieve this, platforms are moving away from traditional batch
processing toward low-latency, continuous data delivery methods like Table CDC
and CDSFlow, paired with central hubs like Apache Kafka. Crucially, raw data
alone isn't enough; it requires centralized metadata to translate technical
fields into understandable business terms and track its origin, making it usable
for both human teams and AI agents. Organizations must also prioritize open
architectures, such as the Apache Iceberg format, to maintain data sovereignty
and long-term flexibility. Finally, modern data architecture is bidirectional—it
does not just feed external analytics but actively writes insights and triggers
back into operational processes. This dual-flow integration, combined with
adaptable deployment options, forms the foundation for resilient, data-driven
business models that are fully prepared for emerging AI use cases.
The MFA you have isn’t the MFA you think you have
For nearly a decade, multi-factor authentication has been the primary defense
against account takeovers, but simply checking the "MFA enabled" box on
compliance reports is no longer enough to guarantee security. Not all MFA
methods offer equal protection. Older, convenient methods like push
notifications and SMS-based one-time passwords are now routinely bypassed by
attackers. Hackers exploit these through "push fatigue" — bombarding users with
approval prompts until they accidentally accept — or by using reverse-proxy
phishing kits and SIM swapping to intercept codes in real time. Because these
legacy methods fail to verify that the user and the system are communicating
with the genuine destination, organizations must transition to true
phishing-resistant MFA, such as passkeys or hardware keys. These modern
solutions rely on cryptographic origin-binding, meaning the browser
mathematically verifies the website before proceeding, stopping lookalike
phishing domains entirely. Despite the clear security benefits, migrating to
phishing-resistant MFA introduces friction. It requires budget for hardware
keys, disrupts familiar employee workflows, and poses integration challenges
with older systems. To succeed, organizations should avoid forced overnight
rollouts. Instead, they should take a strategic, phased approach, beginning with
high-risk administrator accounts and finance teams before expanding across the
broader workforce to ensure a smooth transition.
How AI Is Disrupting the Monolith vs. Microservices Decision
The arrival of AI and autonomous coding agents is transforming the traditional
debate between monolithic and microservice architectures. In the past, the
choice often depended on team size and domain complexity, progressing from
monoliths to microservices as organizations grew. Today, AI allows a small team
to generate the code for dozens of microservices in a fraction of the time.
However, this ease of creation can trap teams into building distributed systems
they cannot effectively manage or operate, leading to severe architectural
failure. Instead of defaulting to microservices, the author suggests a modular
monolith is often the better foundation for business logic. Yet, AI workloads
present unique challenges—such as probabilistic execution, intensive GPU memory
requirements, and long-running agent workflows—that clash with traditional
CPU-bound applications. This necessitates a new hybrid architecture: keeping
deterministic business operations within a unified core while selectively
extracting specialized AI capabilities into distinct platforms. Furthermore, the
Model Context Protocol (MCP) provides a standardized way for AI agents to
interact with business tools. The key takeaway for architects is that MCP should
function as an interface boundary rather than an excuse to fracture the system
into unnecessary, disparate microservices.
How Financial Services Companies Can Modernize Their Software Supply Chain
Financial services organizations have traditionally tolerated a backlog of
dormant software vulnerabilities because making changes to legacy infrastructure
carries a high risk of operational downtime. For years, prioritizing stability
over immediate patching was a defensible strategy since exploiting these
vulnerabilities required significant time and specialized skills. However, the
emergence of advanced AI models has fundamentally altered this landscape. These
modern systems can swiftly scan code, identify weaknesses, and string together
exploits faster than human teams can patch them. Consequently, vulnerability
exploitation has now surpassed phishing as the primary access method for
breaches in the financial sector. To address this escalating risk, security
leaders are shifting their focus away from massive, multi-year application
overhauls and toward modernizing the software supply chain itself. This approach
involves replacing vulnerable base images and open-source libraries with
hardened, continuously rebuilt components at the foundational level. For older
applications that cannot be readily updated, organizations can use secure,
backported fixes that maintain compatibility. By centrally managing trusted
software artifacts, platform teams can distribute secure building blocks across
their organization. This proactive strategy allows financial institutions to
substantially reduce their attack surface and minimize repetitive triage, all
while keeping their critical systems stable and secure.
Beyond Ownership: Cloud Sovereignty By Design
The European Union is increasingly focused on digital sovereignty, particularly regarding cloud infrastructure. Many businesses mistakenly assume that a cloud provider's corporate ownership, such as being headquartered within the EU, automatically guarantees data protection and complete sovereignty. However, this assumption is a dangerous oversimplification. Corporate structure alone does not shield a company from foreign legal demands. For instance, an EU-owned provider with international operations, offshore support teams, or foreign subcontractors might still be legally compelled to share data with outside governments. Instead of relying strictly on a vendor's corporate origin, organizations should evaluate a provider’s tangible technical and operational safeguards. True digital sovereignty depends on practical realities, including exactly where data is physically stored, who manages the supply chain, and the implementation of strong encryption paired with customer-controlled keys. While corporate structure can reduce legal exposure, only technology can physically eliminate unauthorized access to data. Furthermore, evaluating a cloud supplier is never a single, one-time checklist. Because companies frequently restructure, acquire new investors, or alter operational models, due diligence must remain a continuous process over the life of any contract. Ultimately, prioritizing robust technical controls and ongoing transparency offers a stronger foundation for protecting data than simply checking a vendor's nationality.Microsoft doubles down on Rust
Microsoft has officially elevated Rust to a Tier-1 programming language
internally, giving it the same status as established languages like C# and
TypeScript. This means Rust now benefits from a complete, fully supported
toolchain that integrates seamlessly with Windows and Azure. The core of this
effort is a new code generator designed for the Rust compiler, known as
rustc_codegen_utc. This tool directly links Rust with Microsoft's existing
Visual C++ back end, enabling developers to build low-level Windows services,
drivers, and even kernel components while preserving Rust's renowned memory
safety advantages. By leveraging the proven Visual C++ infrastructure, Microsoft
avoids duplicating decades of compiler optimization and build tooling work while
ensuring full compatibility with existing C and C++ code. Although
rustc_codegen_utc is currently restricted to internal Microsoft teams, it is
already powering over a hundred projects. Based on Microsoft's historical
patterns of rolling out internal tools, it is highly likely that these
capabilities will eventually be integrated into Visual Studio and Visual Studio
Code for external developers. Until then, the broader development community can
use existing Microsoft-supported extensions and crates to familiarize themselves
with building safer, more resilient Windows applications in Rust.
Your customers just gave a bot access to their wallet. Are your controls ready?
As artificial intelligence advances, businesses face a new challenge:
traditional identity verification and fraud controls are built for humans, not
for automated AI agents. While current "Know Your Customer" (KYC) systems check
passports and use selfies to verify identity, AI agents lack physical documents
and biometrics. They are making purchases and conducting transactions on behalf
of users, leaving compliance systems unprepared for customers that aren't
people. The main issue is determining and continuously monitoring delegated
authority. Even if an agent's behavior doesn't trigger traditional fraud alerts,
businesses have no way of knowing if the bot is actually authorized by the user,
what its permissions are, and whether that authority is still valid over time.
This shifts the focus from simply identifying a customer to verifying an agent's
ongoing permissions. For IT channel partners, this presents an opportunity to
guide clients beyond basic bot detection tools toward comprehensive trust
infrastructures. Instead of relying on one-time, event-based checks, companies
need continuous monitoring frameworks that seamlessly handle humans, devices,
and AI agents together. Updating these outdated models is essential for
companies wanting to safely capture the benefits of agent-driven commerce
without exposing themselves to significant compliance risks.
How AI Can Help Defend Against Future Quantum Attacks
Artificial intelligence is fundamentally reshaping the cybersecurity landscape,
compelling organizations to rethink how they evaluate digital trust and
assurance. As malicious actors increasingly leverage AI to uncover hidden
vulnerabilities and exploit years-old security flaws, the traditional reliance
on assumed cryptographic security is no longer adequate. To counter this,
cybersecurity experts are adopting specialized AI tools to accelerate
cryptanalysis—the rigorous process of stress-testing encryption systems. By
automating vulnerability discovery and spotting data patterns faster than ever,
defenders can proactively validate the mathematical algorithms that protect
global infrastructure. This AI-driven evolution in defense aligns perfectly with
the world's ongoing transition to post-quantum cryptography (PQC). With
governments and tech giants aiming for total quantum readiness within the next
decade, deploying these new standards is a massive undertaking. Fortunately, AI
presents a critical opportunity to streamline this shift. AI-assisted validation
allows manufacturers to robustly test emerging PQC algorithms before they scale
in production, ensuring implementations are airtight against both present and
future threats. Ultimately, combining strong cryptographic standards with
continuous, AI-powered testing offers organizations an adaptable and secure path
forward in an increasingly complex post-AI and post-quantum world.
_Dzmitry_Skazau_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale)
/articles/ai-agents-improve-software-architecture/en/smallimage/ai-agents-improve-software-architecture-thumbnail-1790153650841.jpg)
