Daily Tech Digest by Kannan Subbiah: microsegmentation

Showing posts with label microsegmentation. Show all posts

Daily Tech Digest - July 07, 2026

Quote for the day:

“Cybersecurity is not about avoiding risk; it’s about managing it.” -- Admiral Mike Rogers

🎧 Listen to this digest on YouTube Music

Duration: 23 mins • Perfect for listening on the go.

Why developers are over the cloud

While cloud computing remains massive, software developers are fundamentally shifting their initial focus away from choosing a specific cloud provider and instead prioritizing tools that offer the fastest development workflow. In the past, the "first mile" of building an application usually started with selecting foundational infrastructure from major vendors like AWS or Azure. Today, developers increasingly start their projects in AI-assisted coding environments and utilize streamlined platforms like Vercel, Cloudflare, or Supabase. These modern developer experience platforms effectively abstract away complex backend infrastructure, allowing engineering teams to focus entirely on their core application logic rather than managing servers, databases, or networking components. However, traditional cloud providers still dominate the "second mile" of software development—the crucial transition from a working prototype to enterprise-grade production. This stage requires robust security, compliance, cost management, and identity controls. To maintain their relevance, major cloud infrastructure providers must adapt by integrating directly into modern coding workflows rather than expecting users to navigate complex cloud consoles. Ultimately, developers are flocking toward platforms that deliver immediate application outcomes, challenging legacy cloud giants to make the leap to production feel like a natural, seamless upgrade rather than a difficult administrative burden.

The token economy: The state of AI mid-2026

By mid-2026, the artificial intelligence industry has firmly moved past its experimental phase and matured into a tangible, large-scale economy. The primary focus has shifted from software laboratories to expansive physical infrastructure. Companies are now constructing gigawatt-scale computing facilities to meet intense processing demands. These sprawling centers require unprecedented amounts of electricity, making power generation just as critical to the industry as the technology itself. The underlying currency of this working economy is the token. Inference platforms are processing tens of trillions of tokens daily, driven largely by independent software programs that perform complex tasks like coding and internet research without human oversight. As software increasingly interacts directly with other software, the main competitive battleground is no longer just about creating smarter models, but about systematically lowering the processing cost for each token. This technological shift is also altering global priorities. Recognizing the strategic importance of these computing systems, nations are heavily funding independent AI initiatives. Governments are securing local infrastructure and building proprietary knowledge bases to ensure they retain direct control over their hardware, data, and economic resources rather than depending on foreign tech providers.

The problem with AI model routing

As organizations move away from simply maximizing artificial intelligence usage, many are adopting a new strategy called model routing. The idea is quite straightforward: send complex questions to advanced, expensive models and route simpler, everyday requests to cheaper alternatives. While this approach seems like a highly practical way to manage rising costs, it carries significant technical flaws. The fundamental problem is that modern language models rely heavily on keeping recent data in a ready memory state—such as remembering recent conversation history and caching details—to operate efficiently. When organizations route requests across different models from various providers, they throw away these essential, built-in efficiencies. Every switch causes a system cold start, forcing the platform to reprocess the entire context completely from scratch. This wasted effort ultimately raises the overall cost for everyone involved, effectively negating the expected financial savings. Consequently, rather than relying on third-party routing systems that create disjointed workflows, the industry will likely shift toward built-in routing managed directly by the major providers. By handling the routing internally, these providers can preserve system efficiency and lower costs, which will ultimately lead to deeper reliance on a single ecosystem.

Delegated authentication: A security essential plus strategic data asset

The rapid shift from physical cards to mobile transactions has introduced significant security and compliance challenges, often resulting in clunky customer experiences. Older verification methods required shoppers to use static passwords during checkout, which frequently caused them to abandon their carts out of frustration. To solve this problem, delegated authentication allows merchants to verify a customer’s identity—often through familiar methods like fingerprint or facial recognition—and seamlessly pass that proof directly to the card issuer. This smoother process reduces purchase friction while still meeting strict security regulations. Modern payment systems now treat this authentication data as a practical tool rather than a simple compliance checklist. By sharing clear transaction context, banks can safely reduce false card declines and approve more legitimate purchases. Furthermore, as automated commerce expands and digital assistants begin making purchases on behalf of users, these systems adapt by establishing pre-approved spending boundaries. By combining secure data handling with clear customer permissions, financial institutions can accurately verify both human shoppers and their automated representatives. Ultimately, this collaborative approach aligns business operations with firm security standards, ensuring that everyday payments remain safe and dependably convenient.

Single points of failure fail. The SaaS layer is not an exception

Higher education institutions have heavily consolidated their core operations into a small number of massive software platforms, turning these systems into critical single points of failure. Recent major disruptions, including severe ransomware attacks and extended platform outages during crucial times like finals week, have highlighted the danger of this dependency. When these platforms go dark, entire academic operations halt, leaving students and faculty stranded without access to coursework, rosters, or grades. The risk is compounded by the fact that the education sector has a history of paying ransoms, which actively incentivizes further attacks. To address this vulnerability, information technology leaders must stop treating external software as an exception to standard disaster recovery practices. Service level agreements and compliance checklists are not sufficient to keep classes running during a crisis. Instead, institutions need an independent contingency plan. Building a secure, independent data repository that regularly synchronizes information from primary systems ensures that schools maintain access to vital records during an outage. Just as modern infrastructure requires redundant network connections and backup power, securing academic operations demands building reliable workarounds for when primary platforms inevitably fail.

Operational Resilience Starts with Risk-Intelligent Microsegmentation

In a highly connected world, protecting critical infrastructure like manufacturing plants and water treatment facilities has become more challenging. If operational technology systems fail, the entire business halts. Recognizing this threat, ColorTokens has partnered with Claroty to improve security for these vital environments. The collaboration combines Claroty’s ability to deeply monitor and catalog physical and digital assets with ColorTokens’ expertise in controlling how those systems communicate. Because modern cyber threats can spread rapidly, simply detecting an intrusion is no longer enough. Organizations must prevent attackers from moving freely across their networks. This approach uses risk-aware network separation to block harmful activity without interrupting essential business functions. By integrating with existing monitoring and defense tools, the joint solution allows security teams to identify vulnerabilities and apply protective rules without installing complex software on older machinery. Ultimately, it is impossible to prevent every attack. However, by understanding which systems carry the most risk and limiting their exposure, companies can ensure that a minor breach does not become a major crisis. This strategy focuses on practical readiness, giving organizations the reliable control they need to maintain continuous operations and safeguard both production and human safety.

Zebra CIO warns of 'AI bloat' risk in enterprise adoption push

As companies rush to adopt artificial intelligence, they risk creating "AI bloat" by deploying tools without a solid strategy, warns Matt Ausman, Chief Information Officer at Zebra Technologies. Much like the software subscription bloat of the past, disorganized AI integration leads to over-engineering, clutter, and inefficiency. The core issue is that corporate ambition is currently outpacing workforce readiness. Deep, effective AI adoption is a multi-year effort where change management and employee training often lag far behind the initial technology rollout. To prevent this scattered approach, Ausman outlines a structured five-step blueprint for success. Organizations should establish cross-functional governance, appoint a dedicated executive to lead the transformation, clearly define their strategy, heavily invest in training for all staff, and launch a comprehensive change management program with steady feedback loops. Zebra itself is modeling this disciplined approach by focusing on standard, widely deployed tools rather than chasing every new release. The company actively uses AI to assist frontline workers, automating routine tasks like pallet scanning while keeping a close eye on employee well-being to prevent burnout. Ultimately, success requires technical leaders to shift from simply managing systems to actively championing thoughtful, strategic business transformation.

Spite-Driven Engineering: A New Blueprint for Cloud Security in the AI Native Era

In a recent InfoQ podcast, Alex Zenla discusses a fresh approach to securing cloud infrastructure, built around the concept of "spite-driven development." This philosophy encourages engineers to tackle fundamental technical frustrations head-on rather than simply layering quick fixes over deeply flawed systems. Zenla points out that much of our current infrastructure relies on fragile foundations, particularly highlighting how shared memory in standard operating system cores fails to provide true security when running multiple applications side-by-side. Instead of accepting these risks, teams need stronger separation methods for their workloads. The conversation also explores the practical realities of using artificial intelligence in development. While AI tools are helpful for building early prototypes, blindly trusting them can introduce dangerous technical debt. Developers still need a deep understanding of the underlying systems to fix issues when things inevitably break. Furthermore, forcing standard graphics processors to handle secure AI tasks is both inefficient and risky, pointing to a need for more specialized hardware. Ultimately, Zenla argues that engineers should stop viewing security and regulation as simple compliance checklists. By taking ownership and building resilient architecture from the ground up, companies can turn strong security into a genuine competitive advantage.

IPv6-only vs IPv6-mostly: Appropriate use cases

As organizations transition their network infrastructures, the terms "IPv6-only" and "IPv6-mostly" are frequently confused, despite serving different environments. Properly defining the scope of these concepts is essential to prevent scalability issues. Describing a full network as "IPv6-only" is rarely accurate today, since many applications still need IPv4 connectivity. Instead, it is more precise to refer to an "IPv6-only access network" paired with an IPv4 transition mechanism. This approach works well for unmanaged environments like mobile and residential networks, allowing the wide area network to operate on IPv6 while maintaining dual-protocol functionality for users. In contrast, the "IPv6-mostly" model was explicitly designed for managed corporate networks. It allows devices to signal they do not need an IPv4 address, reducing reliance on older infrastructure without requiring dedicated network segments. However, applying this approach to residential networks introduces severe communication barriers. Devices would be completely unable to interact with local legacy hardware, such as printers or cameras, without manual configurations. Choosing the appropriate deployment model based on your specific network context is fundamentally critical to ensuring a smooth and functional transition.

6 new rules of IT leadership - and what they replace

The role of the CIO is undergoing a significant transformation, largely driven by the impact of artificial intelligence on the modern business landscape. Rather than merely taking direction from the CEO, today's IT leaders are expected to collaborate directly with top executives to define the company's future vision and architect a completely new, AI-driven organization. This means embracing uncertainty and creating a culture where employees feel safe enough to learn from failure, replacing the outdated "fail fast" mentality with a focus on sustainable growth and psychological safety. Furthermore, IT chiefs can no longer rely solely on business counterparts for operational insights; they must possess a panoramic understanding of all business operations, much like a COO. The financial demands on CIOs have also intensified, requiring them to act more like CFOs by rigorously calculating the total cost of ownership and return on investment for cloud and AI initiatives. Finally, modern IT leadership requires abandoning a one-size-fits-all management style in favor of adapting to the diverse, global, and often remote needs of individual team members, ensuring that everyone can thrive in a rapidly changing environment.

Daily Tech Digest - January 19, 2026

Quote for the day:

"Stop Judging people and start understanding people everyone's got a story" -- @PilotSpeaker

Stop calling it 'The AI bubble': It's actually multiple bubbles, each with a different expiration date

The is actually three distinct layers, each with different economics, defensibility and risk profiles. Understanding these layers is critical, because they won't all pop at once. ... The most vulnerable segment isn't building AI — it's repackaging it. These are the companies that take , add a slick interface and some , then charge $49/month for what amounts to a glorified . Some have achieved rapid initial success, like , which reached approximately $42 million in annual recurring revenue (ARR) in its first year by wrapping GPT models in a user-friendly interface for marketers. But the cracks are already showing. ... Economic researcher points to as an example of the bubble dynamic, noting that the company has made around $1 trillion in AI deals, including a $500 billion data center buildout project, despite being set to generate only $13 billion in revenue. The divergence between investment and plausible earnings "certainly looks bubbly," Bernstein notes. ... But infrastructure has a critical characteristic: It retains value regardless of which specific applications succeed. The fiber optic cables laid during the dot-com bubble weren’t wasted — they enabled YouTube, Netflix and cloud computing. Twenty-five years ago, the original dot-com bubble burst after debt financing built out fiber-optic cables for a future that had not yet arrived, but that future eventually did arrive, and the infrastructure was there waiting.

Modernizing Network Defense: From Firewalls to Microsegmentation

For many years, has been based on the concept of a perimeter defense, likened to a fortified boundary. The functioned as a protective barrier, with a serving as the main point of access control. Individuals and devices within this secured perimeter were considered trustworthy, while those outside were viewed as potential threats. The "perimeter-centric" approach was highly effective when data, applications, and employees were all located within the physical boundaries of corporate headquarters. In the current environment, however, this model is considered not only obsolete but also poses significant risks. ... Microsegmentation significantly mitigates the impact of by transitioning from traditional perimeter-based security to detailed, policy-driven isolation at the level of individual workloads, applications, or containers. By establishing secure enclaves for each asset, it ensures that if a device is compromised, attackers are unable to traverse laterally to other systems. ... Microsegmentation solutions offer detailed insights into application dependencies and inter-server traffic flows, uncovering long-standing technical debt such as unplanned connections, outdated protocols, and potentially risky activities that may not be visible to perimeter-based defenses. ... One significant factor deterring organizations from implementing microsegmentation is the concern regarding increased complexity.

Human-in-the-loop has hit the wall. It’s time for AI to oversee AI

This is not a hypothetical future problem. is already failing in production. When automated systems malfunction — flash crashes in financial markets, runaway digital advertising spend, automated account lockouts or viral content — failure cascades before humans even realize something went wrong. In many cases, humans were “in the loop,” but the loop was too slow, too fragmented or too late. The uncomfortable reality is that human review does not stop machine-speed failures. At best, it explains them after the damage is done. Agentic systems raise the stakes dramatically. Visualizing a multistep agent workflow with tens or hundreds of nodes often results in dense, miles-long action traces that humans cannot realistically interpret. As a result, manually identifying risks, behavior drift or unintended consequences becomes functionally impossible. ... Delegating monitoring tasks to AI does not eliminate human accountability. It redistributes it. This is where trust often breaks down. Critics worry that AI governing AI is like trusting the police to govern themselves. That analogy only holds if oversight is self-referential and opaque. The model that works is layered, with a clear separation of powers. ... Humans shift from reviewing outputs to designing systems. They focus on setting operating standards and policies, defining objectives and constraints, designing escalation paths and failure modes, and owning outcomes when systems fail.

Building leaders in the age of AI

The leaders who end up thriving in the AI era will be those who blend human depth with digital fluency. They will use AI to think with them, not for them. And they will treat this AI moment not as a threat to their leadership but as an opportunity to focus on those elements of their portfolios that only humans can excel at. ... Leaders will need to give teams a set of guardrails (clear values and decision rights) and establish new definitions of quality while fostering a sense of trust and collaboration as new challenges emerge and business conditions evolve. ... Aspiration, judgment, and creativity are “only human” leadership traits—and the characteristics that can provide an irreplaceable competitive edge, especially when amplified using AI. It’s therefore incumbent upon organizations to actively identify and develop the individuals who demonstrate critical intrinsics like resilience, eagerness to learn from mistakes, and the ability to work in teams that will increasingly include both humans and AI agents. ... Organizations must actively cultivate core leadership qualities such as wisdom, empathy, and trust—and they must give the development of these attributes the same attention they do to the development of new IT systems or operating models. That will mean providing time for leaders to do the inner work required to lead others effectively—that is, reflecting, sharing insights with other C-suite leaders, and otherwise considering what success will mean for themselves and the organization.

The Rising Phoenix of Software Engineering

Software is undergoing a tectonic transformation. Modern applications are no longer hand-crafted from scratch. They are assembled from third-party components, APIs, open-source packages, machine-learning models, and now AI-generated snippets. Artificial intelligence, low-code tools, Open-Source Software (OSS), reusable libraries have made the act of writing new code less central to building software than ever before. ... In this new era, the primary challenge is not about builder software faster, cheaper, or more feature-rich. It is how to engineer software safely and predictably in a hostile ecosystem. ... Software engineering, as a discipline, must rise again — not as a metaphor for resilience, but as a mandate for survival. ... The future does not eliminate developers or coders. Assembling, customizing, and scripting third-party components will remain critical. But the accountability layer must shift upward, to professionals trained to reason about system safety, dependencies, and security by design. In other words, software engineers must reemerge as true engineers responsible for understanding not only how their code works, but how and where it runs… and most critically how to secure it. ... To engineer software responsibly, practitioners must model threats, evaluate anti-tamper capabilities, and verify that each dependency meets a baseline of assurance. These tasks were historically reserved for or quality assurance (QA) teams.

The concerning cyber-physical security disconnect

The background of many is in military and law enforcement, which change much slower, but are known for extensive training. The nature of the threats they need to defend against is evolving at a slower pace, and destructive, kinetic threats remain a primary concern. ... The focus of cybersecurity is much more on the insides of an organization. Detection is supposed to catch attackers lurking on compromised devices. Response activities have to consider the entire infrastructure rather than individual hosts. Security measures are spread out across the network, taking a defense-in-depth approach. Physical security is much more outward looking, trying to prevent threats from entering. Detection systems exist within premises, but focus on the outer layers. Response activities are focused on evicting individual threats or denying their access. The majority of security efforts focuses on the perimeter. ... Companies often handle both topics in different teams. Conferences and publications may feature both topics, but often focus on one and rarely address their interdependence. Security assessments like sometimes include a physical component that tends to focus on without involving deep physical security expertise. ... Risks, especially in the form of human threat actors, will always look for the easiest way to materialize. Therefore, they will attack physical assets via their digital components and vice versa, if these flanks are not protected.

Architecting Agility: Decoupled Banking Systems Will Be the Key to Success in 2026

The banking industry is undergoing an evolutionary and market-driven shift. Digital banking systems, once rigid and monolithic, are being reimagined through decoupled architecture, AI-driven intelligence, programmatic technology consumption, and and partnerships. ... Delay is no longer an option — the future of banking is already being built today. To capitalize on these innovations, tech leaders must prioritize digital core banking agility, ensuring integration with new innovations and adapting to evolving market demands. ... Identify suspicious patterns in real time. As illustrated in the figure, a decoupled risk analytics gateway and prompt engine streamlines regulatory reporting and ensures adherence to evolving rules (). Whitney Morgan, vice president at , a fintech provider, states that takes this a notch further by automating regulatory reporting and accelerating product development. ... empowers banks to detect anomalies across large translation datasets with the speed and accuracy that manual processes can’t match. Risk modeling and stress testing will enhance credit risk scoring, market risk simulations, and scenario analysis that drive preemptive and revenue options. ... The banking and financial services innovation race, with challenges in adoption and capturing market advantages, beckons leaders to be nimble and, at the same time, stay focused on the fundamentals. CIOs, CTOs, and other tech leaders can take proactive steps to strike the right balance.

Key Management Testing: The Most Overlooked Pillar of Crypto Security

The majority of security testing in focuses on code correctness or . , however, is mainly considered a procedural issue rather than a technical problem. This is a dangerous false belief. Entropy sources, , and are key to generating. Ineffective randomness, broken device software or a corrupted environment may lead to keys that seem valid but are appallingly weak to attack. The testing mechanisms used to create new wallet addresses for users must be watertight when an exchange generates millions of new addresses. Testing should also be done on key storage. ... The recovery process is one of the most vulnerable areas of key management, yet it is discussed least. Backup and restoration are prone to human error, improperly configured storage, or unsafe transmission. The unfortunate fact about crypto is that recovery mechanisms can be either a saviour or a disaster. Recovery phrases, encrypted backups, and distributed shares need to be repeatedly tested in a real-world, adversarial environment. ... End-to-end lifecycle testing, automatic verification of key states, automated attack simulations and automated recovery protocols that self-heal will be the order of the day. The industry has already become such that key management is no longer a concealed or even supporting part of the security strategies.

Inside the Chip: How Hardware Root of Trust Shifts the Odds Back to Cyber Defenders

Defenders often lack direct control or visibility into the hardware layer where workloads actually execute. This abstraction can obscure low-level threats, allowing attackers to manipulate telemetry, disable software protections, or persist beyond reboots. Crucially, modern attacks are not brute force attempts to break encryption or overwhelm defences. They exploit the assumptions built into how systems start, update, and prove what’s genuine. ... At the centre of this shift is Hardware Root of Trust (HRoT): a security architecture that embeds trust directly into the hardware layer of a device. US National Institute of Standards and Technology (NIST) defines it as “an inherently trusted combination of hardware and firmware that maintains the integrity of information.” In practice, HRoT serves as the anchor for system trust from the moment power is applied. ... For CISOs, HRoT represents an opportunity to strengthen resilience, meet regulatory demands, and finally realise true zero trust. From a resilience standpoint, it changes the balance between prevention and response. By validating integrity from power-on and continuously during operation, it reduces reliance on post-incident investigation and recovery. Compromised devices and systems are stopped early, limiting blast radius and disruption. Regulators are already reinforcing this direction. Frameworks such as the US Department of Defense’s explicitly highlight HRoT as a stronger foundation for assurance.

What AI skills job seekers need to develop in 2026

One of the earliest AI skills involved prompt engineering — being able to get to the necessary AI-generated results by using the right questions. But that baseline skill is being pushed aside by “.” Think of context engineering as prompt engineering on steroids; it involves developing prompts that can deliver consistent and predictive answers. Ideally, “everytime you ask the same question, you always get the same answer,” said , vice president at , a division of . That skill is critical because AI models are changing quickly, and the answers they spout out can differ from day to day. Context engineering is aimed at ensuring consistent outputs despite a rapidly evolving AI ecosystem. ... “Beyond algorithms and coding, the next wave of AI talent must bridge technology, governance and organizational change. The most valuable AI skill in 2026 isn’t coding, it’s building trust,” Seth said. Along those lines, he recommended that job seekers immerse themselves in the technology beyond simply taking a class. “Instead of a course, go to any conference,” Seth said. ... In hiring, genuine AI capability shows up through curiosity and real experience, Blackford said. “Strong candidates can talk honestly about something they tried, what did not work, and what they learned,” he said ... “Things are evolving at such a fast pace that there will be no perfect set of skills,” said Seth. “I would say more than skills, attitudes are more important — that adaptability to change, how quick you are to learn things.”