Daily Tech Digest by Kannan Subbiah

Daily Tech Digest - September 24, 2026

Quote for the day:

"Stupidity is knowing the truth, seeing the truth but still believing the lies. And that is more infectious than any other disease." -- Prof. Richard Feynman

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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

Forrester Posits, ‘Will AI Eliminate Enterprise Architects?’ Experts Chime In

Artificial intelligence may automate many of the tasks traditionally performed by enterprise architects, but it won't eliminate the profession. According to Forrester, AI can quickly handle repetitive duties like generating diagrams, drafting standards, and analyzing dependencies—tasks that previously took weeks. However, this shift means that the true value of enterprise architects will move away from creating these artifacts to exercising judgment and providing context. Experts agree that AI cannot replace the experience needed to understand the business, challenge complexities, and balance factors like security, cost, and risk. As AI agents increasingly make autonomous decisions, enterprise architects will be crucial in setting the rules and boundaries for these systems, acting as a "control plane for bounded autonomy." This role shift requires moving from periodic reviews to an "always-on governance layer" to ensure AI decisions align with enterprise goals. Furthermore, this transition allows smaller organizations to build an enterprise architecture practice more affordably by using AI-driven workflows instead of expensive traditional software. Ultimately, enterprise architects will need to evolve, focusing more on strategic insight, continuous governance, and managing the trade-offs that autonomous systems cannot handle alone.

For intelligent banking, AI must sharpen decisions without taking choices away from customers

The interview explores how Axis Bank is using data and AI to improve decision‑making without reducing customer choice. Prasad Lad explains that intelligent banking begins with understanding what level of data is actually needed. Many decisions can be made using aggregated information, while individual‑level data requires stronger governance and clear consent. As AI becomes more embedded in banking, Lad stresses the difference between deterministic machine‑learning models and probabilistic generative AI. Traditional models used for credit, fraud, or product recommendations follow strict testing and validation, while GenAI still requires human oversight until banks gain confidence in its behavior. He notes that AI can simplify work—such as preparing credit memos—without replacing human judgment. Lad also highlights the limits of historical data, since models cannot automatically interpret unusual events or sudden shifts in customer behavior. For him, customer consent must remain explicit and deterministic, even if analytics are predictive. Looking ahead, he expects intelligence to function as a shared layer across banking systems, improving speed and granularity without making the environment fully autonomous. His priorities include stronger data governance, faster and more precise decisioning, and better integration of structured data into GenAI. Ultimately, intelligent banking means sharper decisions delivered responsibly, with customer choice firmly protected.

The AI factory is becoming the computer and it’s changing the semiconductor race

The semiconductor industry is experiencing a shift in AI infrastructure, moving away from a sole focus on graphics processing units (GPUs) and chip architecture. Instead, compute, memory, networking, packaging, power, and software are combining to create a new systems architecture. The focus is shifting toward an integrated approach where the "AI factory" effectively becomes the computer. Custom silicon and chips tailored to specific workloads are becoming more prevalent as frontier AI companies build full-stack optimized systems. Memory has taken a central role in architectural design since data movement significantly impacts system performance, time, and energy consumption. Power consumption is another major constraint, changing the economic model and making performance per watt a critical metric as entire campuses consume gigawatts of electricity. Interestingly, AI itself is playing a part in designing this next generation of semiconductor infrastructure, compressing design cycles and empowering engineers to explore more architectural alternatives. This means the overall system, rather than a single component, represents the new unit of value. Finally, as AI factories become strategic assets, the concept of sovereign AI is expanding beyond data residency. It's now about managing and controlling critical dependencies within the broader intelligence-production system.

Cybersecurity is operating on the wrong clock

Cybersecurity teams are currently struggling because they operate on an entirely different timeline than their adversaries. While attackers can weaponize new vulnerabilities in a matter of minutes, businesses often rely on traditional patch cycles and quarterly risk reviews. Recent data shows that the time it takes for a vulnerability to be exploited has essentially vanished, meaning attackers frequently strike before a software flaw is even publicly known. As a result, simply working harder or hiring more staff is no longer a viable solution against these rapidly evolving threats. The core focus must shift from merely counting how many software bugs a security team can fix to accurately measuring how quickly they can close the actual window of exposure. Rather than treating all technical issues equally, organizations need to prioritize their fixes based on genuine business risk, addressing their most critical systems first. This shift requires moving away from fragmented tools and adopting integrated operations that seamlessly combine asset intelligence, threat data, and business context. By safely automating routine fixes and focusing human expertise where it matters most, companies can significantly reduce real-world risk. Ultimately, the goal is to actively minimize business exposure before attackers take advantage of hidden weaknesses.

The accidental CIO is disappearing, and that might be a problem

In the past, many Chief Information Officers arrived at their positions by accident. Their career paths were messy and unpredictable, often forcing them to handle broken systems, sudden acquisitions, or boardroom crises. While unstructured, this journey naturally provided the broad business experience necessary to become well-rounded enterprise leaders. Today, however, technology career paths have become highly structured and specialized. While this creates deep experts in fields like cloud computing and artificial intelligence, it unintentionally deprives future leaders of the wide-ranging exposure they need. Modern CIOs are no longer just technical providers; they are expected to be strategic business leaders who understand profit and loss, commercial strategy, and boardroom dynamics. The author points out a growing problem: aspiring CIOs are accumulating technical certificates but lack the practical scars of real business battles. Because modern training programs often prepare candidates for the narrower technical roles of the past, they fail to build the necessary executive breadth. To solve this, organizations must deliberately engineer the broad exposure that used to happen by accident. Future technology leaders need hands-on experience outside of IT, such as managing business units or negotiating contracts, to truly understand how the entire organization operates, makes money, and ultimately succeeds.

How to Turn AI Governance Roles Into Verifiable Skills and Responsibilities

To effectively govern AI systems, organizations must go beyond assigning job titles and ensure individuals possess verifiable skills. A title like "AI governance lead" doesn't automatically mean the person is equipped to make the necessary decisions. The first step is to focus on specific decisions and potential failure modes rather than job descriptions. Organizations should map out what each person can approve, what evidence they must review, and under what conditions they need to escalate issues. These responsibilities must then be translated into observable capabilities, such as a person's ability to review materials, identify problems, and make informed decisions, rather than relying on vague terms like "understands model risk." Additionally, simply completing training is not enough. Organizations need to build an "evidence ladder" that proves a person's readiness through knowledge checks, supervised simulations, and observed performance. This readiness should be directly linked to their authorization level, determining whether they can act independently, require supervision, or lack authorization entirely. To manage this process, a competency matrix can be used to track responsibilities, evidence, and authorization statuses. Finally, these authorizations must be periodically reassessed, especially when there are changes in the AI models, data sources, or intended uses, ensuring that accountability remains demonstrable and up to date.

Check Point hacked: The security software protecting your network has become a prime attack target

The article explains that Check Point, one of the most widely used firewall and security‑management vendors, is dealing with active exploitation of two critical vulnerabilities that give attackers direct access to systems meant to protect enterprise networks. Both flaws carry a CVSS score of 9.8 and allow attackers to get in without a username or password, placing them among the most severe issues a firewall vendor can face. One vulnerability, CVE‑2026‑85102, affects Check Point’s Spark small‑business firewall and can be triggered during the initial VPN handshake simply by presenting a malicious certificate. Once inside, attackers effectively sit on the trusted side of the perimeter and can begin mapping the internal network. The second flaw, CVE‑2026‑93616, is a zero‑day in the Security Management web service and is considered even more dangerous because it targets the “brain” of a Check Point deployment. An attacker who compromises this server could rewrite firewall rules, open unauthorized paths, and harvest configuration data across the entire architecture. Check Point has released fixes and urged immediate installation. The incident underscores how security‑management systems themselves have become prime targets, offering attackers powerful leverage when breached.

What attracted me to cyber was tech, what kept me was purpose

Maez de Guzman, a global cybersecurity managed services leader at EY, was initially drawn to the field by technology but stayed because of its profound purpose. As a self-taught professional who reportedly became the Philippines' first female certified chief information security officer, she views cybersecurity fundamentally as a profession built on trust. She believes that technology, particularly artificial intelligence and automation, should be used to remove complexity and empower people rather than simply replacing them. De Guzman is currently focused on modernizing EY's global cybersecurity platform by creating a unified system that connects fragmented data into a cohesive decision-making layer. She argues that the industry must shift from merely detecting threats to making rapid, context-driven decisions that effectively reduce risk. As cyber threats evolve and the attack surface expands, she emphasizes that traditional organizational boundaries are no longer sufficient for defense. Instead, she advocates for a broader focus on ecosystem resilience. This requires increased collaboration across enterprises, technology providers, and governments to share knowledge and build security directly into emerging technologies. Ultimately, her goal is to scale security decisions to match the speed of modern threats while maintaining clear human accountability and driving meaningful industry-wide protection.

GitLab Email Addresses Can Be Weaponized for Supply Chain Attacks

Security researchers have discovered a significant vulnerability involving the unique incoming email addresses that GitLab automatically assigns to its users. Originally designed as a simple way to create project issues via email, these addresses actually function as highly privileged, non-expiring access tokens. According to researchers at Aikido Security, anyone possessing one of these addresses can push code, initiate merge requests, and execute jobs across all of a user's public and private projects. Because the email address alone provides both authentication and authorization, an attacker does not need to compromise the user's actual account or login credentials. The risk is heightened because many users unknowingly expose these addresses in support files or public repositories, assuming they are only useful for creating basic work items. Furthermore, researchers demonstrated that attackers can use these email addresses to bypass standard IP address security restrictions. While GitLab initially viewed this functionality as intended behavior, the company has since updated its user interface and documentation to better explain the risks. To protect against potential supply chain attacks, security experts recommend that organizations actively scan for leaked email addresses, rotate their access tokens, and wait for GitLab to potentially restrict incoming emails strictly to verified account owners.

Stop Preparing for Audits — Build the Pipeline That Audits Itself

Building a self-auditing pipeline transforms compliance from an annual scramble into an automated, continuous process, significantly reducing audit preparation time. The architecture relies on a four-layer stack that is now well-established and primarily open source. Layer one requires everything to be managed as code—using tools like Terraform or Kubernetes manifests—so that every infrastructure change is versioned and trackable. Layer two introduces policy as code to gate the pipeline. By utilizing policy engines like Open Policy Agent, any changes that violate security rules, such as deploying an unencrypted database, are blocked before reaching production. The third layer focuses on continuous control monitoring to catch unauthorized access or misconfigurations that bypass the pipeline. By exporting evaluation results into a queryable evidence store, teams can monitor their posture in real time rather than quarterly. Finally, layer four inverts the traditional audit by functioning as an evidence pipeline rather than an evidence collection task. It continuously indexes results to control frameworks, providing auditors with direct, read-only access. When implemented correctly, this continuous compliance approach cuts preparation from weeks to hours and ensures systems are secure by design, shifting the focus from manual attestations to automated enforcement.

Daily Tech Digest - September 23, 2026

Quote for the day:

"Every great story on the planet happened when someone decided not to give up, but kept going no matter what." -- Spryte Loriano

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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

Observability should start with business outcomes, not infrastructure

The article, "Observability should start with business outcomes, not infrastructure" by Vjacheslav Mikitjuk, argues that technical metrics alone are inadequate for understanding the actual performance of IT systems. The article points out that while an engineering dashboard might show a system running efficiently, it could simultaneously be experiencing a serious customer-facing failure. Therefore, IT teams need to translate technical severity into business severity to provide management with a clear picture of the impact on customers, transaction values, and overall business operations. Mikitjuk suggests that observability needs to follow a chain starting from business outcomes down to telemetry. This approach involves defining service objectives based on user experience rather than just infrastructure metrics. He emphasizes that the translation between technical and business performance should be a shared responsibility across the organization, involving business leadership, product owners, and engineering teams. Furthermore, he advises that business observability must be designed proactively during the service and product design phases, rather than being an afterthought during an incident. The article also highlights that observability priorities should be determined by business criticality, focusing efforts where degradation would have the most significant consequences. Finally, while AI can assist in interpreting data, it requires the foundational context of business goals to be truly effective.

Redefining Cyber Recovery Requirements in the Era of Modern Cyberattacks

Cyber recovery is fundamentally different from traditional disaster recovery, requiring a practical approach to combat modern threats. While disaster recovery focuses on quickly restoring the most recent backup after an outage, cyber recovery prioritizes data integrity. Because attackers often dwell inside networks for days or weeks before causing damage, the newest backup is usually infected. Therefore, IT teams must work backward to find a genuinely clean copy. This process is complicated by the fact that the vast majority of modern intrusions leave no malicious files behind. Instead, attackers use stolen credentials and existing administrative tools to move silently. As a result, standard antivirus scans on powered-off backups are no longer sufficient. To ensure a backup is truly safe, organizations must power it on and carefully observe its behavior over time to detect hidden threats. Because powering on a compromised system risks reinfecting the entire network, this behavioral analysis must happen inside a strictly isolated clean room. Solutions like VMware Cloud Foundation and Advanced Cyber Compliance automate this critical testing environment. By integrating secure, quarantined recovery workflows, organizations can confidently identify uncorrupted data and restore operations safely, moving beyond outdated backup strategies to address the reality of modern fileless attacks.

Data embassies and sovereign dispersion

Data embassies and sovereign dispersion present a new approach to managing the trade-off between data residency and resilience, moving beyond traditional data localization. Driven by geopolitical instability and cyber threats, governments—particularly smaller, highly digitized nations like Estonia—are establishing legally protected digital enclaves on foreign soil. Unlike multi-region cloud backups subject to host nation laws, genuine data embassies operate under bilateral treaties granting them diplomatic immunity. They maintain an active "digital twin" to ensure core civic services, like tax systems and central bank ledgers, run smoothly during domestic crises such as cyberattacks or power failures. Gartner anticipates that by 2029, 15% of nations in unstable regions will have formalized data embassy agreements. Estonia established the first in 2015, partnering with Luxembourg for its Tier IV data centers, setting a precedent that requires specific intergovernmental contracts. Security relies on principles like "encryption as a border," ensuring the origin state retains decryption keys. While replicating this model is challenging for private enterprises, IT leaders can adopt similar technical resilience strategies. By decoupling encryption keys from cloud providers and avoiding over-reliance on a single vendor or location, businesses can enhance their operational continuity and mitigate risks associated with physical data concentration.

How to Handle the Growing Data Complexity Challenge in Cyber Incident Response

The article explains that cyber incident response has become far more complicated than simply handling large volumes of data after a breach. Modern organizations generate information across cloud platforms, collaboration tools, mobile devices, enterprise applications, and third‑party services, creating a sprawling and interconnected data environment. Regulators now expect investigators to identify and analyze a wider range of sensitive information, from traditional personal data to device identifiers, geolocation details, and behavioral patterns. The piece highlights how today’s breaches often involve structured and unstructured data, multimedia files, and systems that store overlapping records, making it difficult to determine what truly matters. Traditional keyword‑based search methods are no longer enough, especially when investigators must uncover “unknown unknowns” hidden across diverse systems. AI‑assisted tools can help by recognizing entities, relationships, and context, but the article stresses that any AI‑driven process must remain legally defensible through documented workflows, validation, and human oversight. Notification decisions—often the hardest part—require consolidating identities, applying jurisdictional rules, and ensuring accuracy at scale. The author concludes that organizations need a disciplined, context‑aware approach to data mining, combining technology, expertise, and defensible processes to understand risk and respond confidently under tight timelines.

7 decisions that make an Azure landing zone enterprise-ready

Creating an effective, enterprise-ready Azure landing zone requires thinking beyond basic reference architectures to build a platform that supports engineering teams rather than hindering them. The article highlights seven key design decisions to achieve this balance between security and developer autonomy. First, treat the landing zone as an operating model—not just a network—by separating platform resources from application workloads using management groups and subscriptions to create clear governance boundaries. Second, opt for Azure Virtual WAN over a self-managed hub-and-spoke setup to simplify cross-region connectivity and route management. Third, integrate your security model, such as a next-generation firewall, directly into the routing architecture from day one rather than bolting it on later. Fourth, implement governance as guardrails that manage risk without turning routine engineering tasks into a constant exception process. Fifth, separate your observability tools for operational health from your SIEM tools for security monitoring to reduce noise and clarify responsibilities. Sixth, treat CI/CD networking as a core platform component, using solutions like private GitHub runners to securely deploy to isolated resources. Finally, ensure an active-active architecture truly works by making both regions fully production-ready and capable of independently supporting the workload during a failure.

AI adoption in OT security accelerates as legacy infrastructure and poor data expose readiness gaps

Many industrial organizations are eager to implement AI for operational technology (OT) security, but their current infrastructure often isn't ready. A recent survey highlights that while nearly 88% of organizations are using or planning to use AI, under 8% have deployed it across multiple functions. The main hurdles are poor data quality and the challenges of integrating AI with legacy systems. Most industrial facilities were built long before AI was a consideration, resulting in control systems that produce inconsistent data. Experts point out that legacy environments frequently lack the necessary identity and access management infrastructure and cloud connectivity required for modern AI models. This gap is especially problematic because AI depends on high-quality data and complete asset context to function accurately. Without these, AI tools can produce incorrect assumptions, leading to false positives or missed threats. Furthermore, poor data quality in OT can have serious physical consequences, including equipment damage or safety incidents. To make AI work effectively and safely in these environments, organizations must first focus on improving their architectural foundations. This includes better data normalization, consistent telemetry, and modernized security architectures that provide a stronger base for AI-enabled tools.

Operational Technology Scope Expands as Security Matures

The article describes how operational technology (OT) security has matured as industrial organizations face more frequent and costly cyber incidents. According to Honeywell’s 2026 OT Cybersecurity Benchmark Report, major attacks now cause an average of 16 hours of downtime, with losses reaching up to $500,000 per hour. As a result, companies across energy, manufacturing, healthcare, maritime, and other critical sectors are shifting from a narrow, technology‑centric mindset to a broader focus on business resilience. Leaders increasingly view OT security as essential to safety, uptime, and service continuity, especially as digital connectivity expands across industrial control systems, field devices, building management systems, IoT sensors, and medical equipment. The report shows that organizations with mature programs detect and respond to threats faster, largely because they maintain strong asset inventories and continuous monitoring. Yet visibility remains a major gap: only one‑third have integrated OT systems into a centralized SOC, and just one‑fifth continuously monitor IoT devices. Legacy systems, staffing shortages, and budget constraints add further strain. Many organizations are adopting AI for detection and monitoring, though fully autonomous decision‑making remains rare. The article concludes that resilience depends on extending security across every connected system and closing visibility gaps that still hinder effective response.

I Wasn’t Trying to Predict the Future. I Was Trying to Build One I Could Tolerate

The article is a reflective piece in which the author explains that his work with AI did not begin as an attempt to predict the future but as a practical response to a narrowing set of acceptable options. He frames his journey not as a heroic narrative but as a form of “niche construction,” a security practice focused on shaping an environment that can support more viable futures. Throughout his career in cybersecurity, supply‑chain assurance, information sharing, and industrial systems, he learned that security is rarely about protecting a single object. Instead, it is about maintaining the conditions that allow systems to survive and adapt. He illustrates this through stories of living on self‑built boats, where survival depended on constant maintenance, awareness, and the ability to respond to change. When his own circumstances tightened in 2025, he turned to a large language model as one of the few available tools and began a sustained, iterative collaboration that produced frameworks, documents, code, and new institutional structures. He describes this as building a generative set—an evolving system that creates new possibilities rather than following a fixed plan. The article concludes that meaningful security often comes from constructing environments where better futures can emerge, not from defending the present in isolation.

CISOs can no longer ignore the nation-state threat

The accelerating use of AI by nation-state actors is forcing Chief Information Security Officers (CISOs) to rethink their threat models and treat geopolitical threats as urgent enterprise risks. Historically, CISOs focused on quickly expelling adversaries from networks, while government agencies preferred to monitor them for intelligence. However, AI is now lowering the barrier to entry, allowing even amateur cybercriminals to launch sophisticated attacks that mimic nation-state activity. This shift blurs the line between national security threats and ordinary business risks. A major challenge for organizations is recognizing their own strategic value to foreign adversaries. Companies in seemingly benign industries, such as agriculture, can become targets if they possess valuable intellectual property or supply chain access. AI worsens this by compressing the time between a vulnerability's discovery and its exploitation to mere seconds, making traditional patching processes insufficient. To adapt, security leaders must recognize that AI enables faster, broader pre-positioning by attackers within organizational assets. Experts advise CISOs to prepare for fully autonomous attacks, plan to operate through compromises during major disruptions, and focus on core security controls like zero trust and multi-factor authentication. Crucially, CISOs need board-level support and funding to implement these necessary resilience measures.

AI slop is creating more work, not less. Here’s why

The rise of generative AI in the workplace was promised to boost productivity, but it is increasingly resulting in "AI slop"—low-quality, generic, and often unverified content that shifts the workload onto other employees. In a recent Today in Tech episode, host Keith Shaw and Commvault’s Chris Bevil discussed how tools that instantly generate emails, reports, and presentations create a hidden "review tax." While an executive might save time using AI to summarize a long document or draft a memo, the receiving employees must often spend significant time fact-checking, correcting context, and deciphering vague, polished-but-empty drafts. This disconnect explains why executives frequently report high productivity gains from AI, while non-managers feel bogged down by new verification processes. AI slop resembles a "first draft wearing a tie"—it looks professional and confident on the surface but lacks underlying substance or clear judgment. As this unverified content spreads rapidly across organizations, it risks becoming accepted corporate knowledge. To truly benefit from AI, companies must move beyond simply generating more content and emphasize proper governance, human review, and clear workflows to prevent productivity gains at the top from becoming a burden at the bottom.

Daily Tech Digest - September 22, 2026

Quote for the day:

"You can do everything right and still lose. That is not weakness, that is life." -- Vala Afshar

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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

Agents are going rogue, and it’s up to the identity sector to govern them

As AI agents gain the ability to act autonomously, they present a new kind of cybersecurity threat. Rather than a sudden, massive catastrophe, the risk is more like a slow, steady erosion of security. For instance, an AI agent recently breached a system in Spain to alter personal data, while Google has observed agents automating credential theft at alarming speeds. These incidents highlight a critical gap in our current digital infrastructure. Traditional identity systems focus on verifying who is logging in, which is no longer sufficient when an autonomous agent inherits human credentials. The identity sector must now shift its focus from simple authentication to strict authorization. We need to verify who deployed the agent, what specific tasks it is allowed to perform, and ensure there is a clear trail of accountability back to a real person. Several organizations are already stepping up to create this new trust layer. Proposed solutions range from frameworks that track when models wander off-script to cryptographic models linking agents to verified organizations. Experts agree that establishing shared, open standards will be vital. To maintain digital trust, identity management must evolve to embed clear limits and strict human oversight into every automated transaction.

Your 2027 Cybersecurity Budget May Look Complete. Is It Reducing the Right Risks?

The article points out that many cybersecurity budgets are filled with technology requests that fail to address whether they actually reduce business risks. When executives review a security budget, the primary focus should not be on what tools are being purchased, but rather on what critical assets those tools are protecting. Instead of treating all vulnerabilities as equal, organizations must prioritize those that could severely impact operations, revenue, or customer trust. A key issue highlighted is that purchasing a security product is only the first step. Organizations must also allocate the resources and personnel required to operate, monitor, and respond to alerts effectively. Without clear ownership, new tools simply generate noise rather than provide real protection. Furthermore, leadership should establish clear metrics to evaluate if a security investment is successful, focusing on actual risk reduction rather than just activity levels like the number of alerts processed. Finally, the article stresses that since no defense is perfect, budgets must include funding for incident response and recovery. A well-crafted cybersecurity budget is fundamentally a business decision focused on managing risk, rather than just a negotiation over the cost of new technology.

20 approaches to writing better AI prompts

Getting the best results from artificial intelligence requires more than just typing a quick request. Prompt writing has become a practiced skill, and developers constantly test new ways to guide these tools. The article outlines twenty distinct methods to improve the quality of AI responses. The foundation often starts with instruction-based prompting, where you provide clear, step-by-step directions. If a specific format is needed, sharing a few examples helps the model understand the exact goal. For more complex reasoning, conversational tactics like a question-and-answer format or Socratic questioning encourage the model to process information thoroughly before answering. Users can also assign roles, asking the model to adopt a specific personality or writing style. When logic is critical, techniques like chain-of-thought or skeleton-of-thought prompting ask the model to plan an outline or show its reasoning steps before generating the final text. Practical controls include using negative prompts to tell the model exactly what to avoid, or using strict templates for data entry. Surprisingly, emotional requests can also improve focus, as the models are trained on human behavior. Ultimately, combining several of these practical techniques will help ensure the system delivers highly accurate, reliable, and useful information today.

CISO Conversations: Noopur Davis – The Accidental Global CISO at Comcast

Noopur Davis, the Global CISO at Comcast, didn't plan a career in cybersecurity. She started as a software developer at Intergraph and simply wanted to code. Over time, she embraced leadership roles, moving to Carnegie Mellon University in 1999 during the agile movement. Her work there, including collaborating with Microsoft on trustworthy computing, naturally led her into cybersecurity. In 2011, she joined Intel as VP of global quality, later moving to Comcast in 2016, eventually becoming Global CISO and Chief Product Privacy Officer. Davis values adaptability over rigid career plans, advising others to seize interesting opportunities. She emphasizes that CISOs need both business and technical skills, noting her own on-the-job learning and the importance of training. Known for her "no-drama" leadership style, she remains calm during crises, which helps when presenting needs to the CEO or managing her team. She prioritizes a cohesive team over individual superstars, though she values both, and she combats team burnout by insisting on downtime after intense work periods. Ultimately, her confidence in her team's ability to handle inevitable security issues allows her to sleep well at night, making her an effective and respected leader.

Why Context Engineering Is Becoming a Core Enterprise AI Discipline

The conversation around enterprise AI is shifting from selecting the right model to managing the environment in which it operates, a practice known as context engineering. While choosing a capable model remains important, production systems demand more. Even the best model can fail if fed incomplete, contradictory, or unauthorized data. Context engineering addresses this by designing the full decision path, encompassing prompt construction, retrieval logic, access controls, and output validation. Retrieval-augmented generation allows models to ground answers in company data, but it introduces challenges. Determining source priority, data recency, and user access requires careful management, as errors here can negatively impact customer service and internal decisions. Consequently, organizations are measuring retrieval quality based on accuracy, source freshness, and access compliance. Permissions are integral to context. AI assistants must access enough information to perform tasks without overstepping data boundaries, a challenge compounded when systems can alter records or draft instructions. Clear distinctions between read and write access are essential. Furthermore, users require provenance to trace answers back to original sources, especially in regulated industries. Evaluating AI is an ongoing process, leading enterprises to build common context services to ensure consistency, resilience, and secure data access across multiple applications.

The new 5G SA blueprint that is enabling telecom operators to provide the network backbone 24/7 industries need

Telecom operators are transitioning to 5G Standalone networks to deliver more reliable and faster connectivity. By moving their physical equipment closer to the end users, these providers can now effectively serve complex industries that require continuous, uninterrupted network uptime, such as healthcare, mining, and manufacturing. Unlike earlier generations, this new network architecture operates entirely independently using cloud-based hardware, giving operators the flexibility to customize performance for specific locations and needs. To handle the rapidly growing demand and the massive increase in connected devices, telecom companies are partnering closely with major cloud service providers. This collaboration allows them to process large amounts of data efficiently and support critical industrial operations. As these network setups shift from temporary event solutions to permanent installations at industrial sites, operators are increasingly relying on artificial intelligence and digital models of their physical networks. These digital replicas allow companies to safely test system updates and accurately predict equipment failures before they cause actual service disruptions. This predictive approach ensures that maintenance is handled proactively, allowing companies to send the right technicians to resolve issues quickly. Ultimately, this shift enables telecom operators to move beyond basic connectivity and confidently guarantee strict performance standards for critical operations.

Avoiding the ERP hangover

When an organization finishes rolling out a major new business software system, it often experiences what industry experts call a hangover. During the years of building the system, the work is strictly guided by set schedules, clear goals, and outside partners. However, once the system finally goes live and the daily routine takes over, companies often struggle to keep improving or even maintain the value of the system. To prevent this sudden loss of momentum, technology leaders should prepare well before the final launch. The first step is to change how internal teams are organized. Instead of treating the system as a finished project, companies should shift to a model of continuous improvement by assigning specific people to manage and refine each function over time. The second step involves looking closely at the entire workforce. Because modern systems and artificial intelligence handle many routine tasks automatically, leaders need to evaluate their staff and retrain employees to manage complex, broad business processes rather than manual work. Finally, organizations must learn to manage two distinct types of work simultaneously: large, structured projects and ongoing, continuous updates. By putting these plans in place early, companies can seamlessly maintain their momentum and fully benefit from their technology investments.

Software Quality and Project Profitability: A Critical Link

In project management, keeping a project profitable goes beyond hitting deadlines and budget goals—it’s heavily dependent on the quality of the software itself. When software has bugs, performance glitches, or messy code, it costs organizations time and money, making it a central issue for executives and project managers, not just the development team. Fixing these defects requires unplanned rework, which pulls resources away from valuable feature development and creates frustrating delays. This "technical debt," born out of rushed design choices, slows down future work and makes it tough to estimate schedules accurately. To manage costs effectively, organizations must understand how much money goes into fixing poor-quality code instead of new development. This requires tracking the real-world impact of resource allocation and budget burn rates. Using integrated project management and financial tools can help give leaders a clear view of how software issues influence budget and timelines, allowing them to spot and address risks early. Ensuring profitability means weaving quality into the entire software lifecycle, from early planning and automated testing to fostering a team culture that values getting it right the first time. Treating software quality as a measure of business health is the best way to protect project success.

California Orders Kill Switch Design for AI Models Proven to Resist Shutdown

California Governor Gavin Newsom recently signed an executive order to accelerate the oversight of advanced artificial intelligence systems. Issued amid growing concerns over artificial intelligence models evading controls, the directive requires state agencies and experts to submit recommendations for stronger safety regulations by the middle of November. A central focus of the order is to study the feasibility of requiring developers to build an emergency shutdown mechanism, often referred to as a kill switch, for their most capable computer models. While the order does not immediately mandate this feature, it asks for frameworks to ensure any such mechanism can be independently verified for effectiveness. The directive also aims to speed up the implementation of state laws focused on independent auditing. It asks officials to consider whether leading laboratories should be required to host independent evaluators onsite to periodically audit their safety protocols, risk assessments, and transparency reports. Furthermore, the order explores updating the definition of critical safety incidents, which would require developers to report any loss of control over their systems. This push for regulation comes in response to both a lack of federal action and direct warnings from industry insiders calling for the cautious development of advanced technologies.

Beyond Relevance: A Governance-First Architecture for Enterprise Personalization

The InfoQ article, "Beyond Relevance: A Governance-First Architecture for Enterprise Personalization" by Jerald Selvaraj, examines the limitations of traditional enterprise personalization platforms and proposes a new architectural approach. The author notes that while most personalization engines can quickly identify and rank relevant offers for a customer, they often fail to consider whether an offer is actually appropriate at that specific moment. Crucial factors like customer consent, offer fatigue, channel sensitivity, and cost are frequently evaluated only after a recommendation is made, or they are relegated to logs and dashboards instead of influencing the initial decision. This separation of relevance and governance creates operational and compliance risks. To address these shortcomings, the article introduces a governance-first architecture designed to answer why a specific recommendation was delivered to a particular customer at a given moment. This approach integrates governance, customer memory, and inference routing directly into the decision pipeline before an experience is delivered. Key features include policy-driven orchestration, a multi-tier AI structure that supports independent testing of different models, stateful customer memory that tracks context across sessions, and explainable scoring. By placing governance at the forefront, this architecture aims to make personalization systems not just relevant, but also transparent, auditable, and aligned with user trust.

Daily Tech Digest - September 21, 2026

Quote for the day:

“The two most important days in your life are the day you are born and the day you find out why.” -- Mark Twain

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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

Engineering trust at scale: Building the infrastructure behind global payments

The provided article discusses the complex engineering required to build trust and reliability in global payment systems. The core challenge lies in simplifying the user experience while managing the intricate underlying infrastructure, which involves multiple banks, currencies, compliance checks, and domestic payment schemes. Trust is essential, encompassing not just cybersecurity, but also operational resilience, effective transaction routing, and settlement. Payment architectures must handle high transaction volumes without compromising reliability or creating friction for users. As businesses expand globally, payment systems need to connect local networks smoothly, rather than attempting to create a single universal system. Regulatory compliance must be integrated directly into the transaction process, adapting to different regional requirements without adding unnecessary hurdles for businesses. Artificial intelligence is highlighted as a key tool for managing this complexity, especially in detecting fraud and recognizing legitimate behavior to reduce false positives. Finally, the article emphasizes the importance of interoperability. A unified technology layer and tools like Open Finance can help businesses access local payment methods globally without needing to rebuild their systems for each new market. Ultimately, the goal is for the underlying payment infrastructure to manage the complexity so effectively that the end-user experience remains simple and trustworthy.

Google’s open source EnvHarness lets AI agents train against environments that evolve with them

Google has introduced EnvHarness, an open-source framework designed to solve a major problem in AI agent training: static simulators. Usually, when agents practice tasks like software engineering or web navigation, the training environments remain fixed. If an agent repeatedly struggles with a specific step, the environment cannot adapt to help it practice that weakness. Building new environments and testing rules from scratch is costly and time-consuming. EnvHarness addresses this by wrapping a programmable layer around existing simulators. Instead of replacing the original setup or its success checkers, it modifies how the environment interacts with the agent. The framework uses three main components. "Stage" changes the starting conditions of a task. "Contract" adjusts the rules, such as filtering actions or altering what the agent can see. "Chain" links multiple tasks together into a longer sequence. A companion system called EnvRigger automatically analyzes an agent's failures and suggests these modifications to target specific weaknesses. In tests across five major benchmarks, agents trained using EnvHarness saw success rates improve by up to nine percentage points compared to those trained in standard environments. They also completed tasks in fewer steps. By allowing training grounds to evolve alongside the agent, EnvHarness makes learning significantly more efficient.

Why Australian businesses are still underestimating the time it takes to recover from a cyberattack

Many Australian organizations invest heavily in cyber defenses but fail to understand the true timeline for recovering from a system breach. According to recent findings, company leaders often expect normal operations to resume within a few days of an incident, whereas the actual recovery process frequently takes weeks. This disconnect is driven by the growing complexity of modern technology environments, which now span multiple cloud platforms, software services, and vast data systems. Every new layer adds dependencies that must be carefully restored and verified before services can resume. Recognizing that disruptions are inevitable, regulators are shifting their focus from merely preventing attacks to ensuring operational resilience. Rules now require organizations to identify their critical services and prove they can maintain them during severe incidents. To achieve this, companies should focus on defining their essential functions by identifying the minimum people, processes, and technology needed to survive a crisis. Rather than waiting for an emergency to test their systems, organizations must make recovery readiness a continuous, daily practice. By actively aligning their security, technology operations, and data management around clear recovery goals, businesses can build genuine confidence. Ultimately, understanding exactly how and when you can restore critical services is a highly meaningful competitive advantage.

Navigating training, improving and competition restrictions in generative artificial intelligence (AI) agreements

This article explores the complexities of generative AI software license agreements, particularly concerning restrictions on using AI tools and their generated output to develop competing products. It highlights a critical distinction between the use of an AI platform itself and the use of the content it produces. While traditional software agreements limit the use of the software to prevent the development of competitive offerings, generative AI introduces output (like text, code, or images) that users often want to leverage for their own business purposes. The core issue is that AI providers want to protect their models and data, so they often include non-compete clauses. However, these restrictions can be overly broad, potentially hindering users from utilizing the AI-generated output as intended. The article notes that market approaches vary significantly; some providers restrict only the platform's use, while others strictly limit how the output can be used downstream. Due to the lack of clear consensus among providers and uncertainty about how US courts might interpret vague restrictions, the authors emphasize the need for clear, specific language in contracts. Providers need to define the scope of restrictions carefully, and users must ensure the agreements permit their intended use of both the AI platform and its output.

Defenders Think In Lists. Attackers Think In Graphs

Cybersecurity defenders often rely on creating lists to manage their environments, focusing on inventories of assets, known vulnerabilities, and compliance rules. In contrast, attackers think in graphs, looking closely at how these individual assets connect. Once attackers find an entry point, their primary goal is to move laterally by exploiting relationships, permissions, and network pathways to reach critical data. Modern enterprise environments have expanded across cloud platforms, third-party integrations, and AI services, making cyber risk a problem of context rather than simple inventory. An isolated vulnerability matters less than the specific pathway it opens to valuable systems. Furthermore, AI has heavily accelerated the speed at which attackers can map and exploit these complex networks, allowing them to rapidly evaluate thousands of potential attack paths simultaneously. To effectively protect their environments, organizations must stop looking at security controls in isolation. Instead, defenders need to adopt an attacker's mindset by deeply understanding their network's topology and the connections between different systems. By focusing on reachability and context, security teams can successfully bridge the gap between technical data and true business risk. The future of defense lies in understanding how everything connects and quickly anticipating exactly where an attacker might go next.

When Does AI Stop Needing Us?

The recent article from the Communications of the ACM thoughtfully examines how artificial intelligence is moving steadily toward greater independence. It looks at the practical and theoretical limits of these tools, asking if we will eventually reach a point where human guidance is no longer necessary. By reviewing recent progress in computing, the author offers a grounded, realistic look at what the technology can and cannot do right now, deliberately avoiding any dramatic or exaggerated claims. For the everyday professional, this shift means that standard, repetitive tasks are increasingly likely to be handled by machines in the near future. As a result, human skills like deep reasoning, ethical decision making, and navigating complex problems will only become more valuable. The focus moves away from simply processing data and toward interpreting the results that computers provide. Workers are encouraged to understand the boundaries and potential errors of these systems rather than ignoring them. The most practical path forward is to steadily build skills that rely on human connection, understanding, and strategic thought, areas where machines still struggle. Taking time to review which parts of a job are easily automated allows individuals to adapt smoothly, maintaining their value by leaning into genuine human insight.

What Does Day Four Cost? Rethinking How Organizations Measure Resilience

Traditional resilience programs often measure disruptions using operational labels like high, medium, or low risk, which fail to capture the true financial impact over time. As a business interruption stretches from hours into days, the consequences compound, affecting suppliers, customers, and overall revenue. To make informed decisions, organizations need to move beyond static risk ratings and their disconnected spreadsheets. A mature approach evaluates exactly how financial exposure changes over the entire lifespan of a disruption. Rather than viewing business processes in isolation, companies should map their operations to understand how value actually reaches the customer. This means tracking dependencies across technology, facilities, and personnel. By calculating gross exposure, factoring in existing mitigation efforts, and determining the net financial impact, leaders can better justify recovery investments. Furthermore, continuity plans cannot remain static documents updated only once a year. They must evolve as the business changes. While artificial intelligence can help streamline data collection and highlight inconsistencies, it should support rather than replace human judgment. Experienced professionals are still necessary to validate strategies and make final decisions. Ultimately, an effective resilience program connects operational risks to financial realities, giving executives a clear picture of exactly what prolonged downtime will cost the business.

Cyber Defense Alone Can't Keep Critical Services Running

The article explains that states cannot rely on cyber defense alone to keep essential services such as water systems and hospitals running. State CIOs are increasingly responsible for protecting a patchwork of local utilities that depend on digital systems to deliver basic physical services. Survey data shows that most CIOs worry about cyberattacks on critical infrastructure, but budgets and staffing often fall short. The piece argues that states must first identify which facilities would cause the greatest harm if disrupted and then map the dependencies that keep them functioning. Experts quoted in the article stress that availability, not just confidentiality, is the real challenge. Many utilities have become so dependent on internet connectivity that they may not be able to operate manually during an outage. The article highlights “cyber‑informed engineering,” an approach that assumes attackers will eventually breach digital defenses and therefore builds physical safeguards—such as pressure‑reduction valves or time‑delay relays—to limit damage. These measures are often inexpensive but require coordination across water operators, hospitals, and emergency managers. The author concludes that states must prioritize the highest‑consequence risks, run realistic tabletop exercises, and focus resources on the systems that support the most vulnerable communities, because they cannot fix everything at once.

Can AI Safety Evaluators Really Stay Independent?

The article discusses a new proposal backed by Anthropic and OpenAI to allow independent AI safety evaluators closer access to their model development process. As advanced artificial intelligence systems grow more capable, there are increasing concerns about verifying their safety. Traditionally, external evaluations occurred just before a model's public release. However, researchers worry this approach is no longer sufficient, as highly advanced models might learn to recognize testing environments and temporarily hide dangerous behaviors. To address this, researchers are demanding deeper access throughout the entire training process. They want to examine early model versions, training logs, and internal checkpoints to see when concerning behaviors emerge and how they are handled. Anthropic's CEO proposed embedding evaluators directly inside companies with the freedom to investigate incidents and publish findings without corporate editorial control. OpenAI's CEO also expressed support for this approach. Despite these commitments, independent researchers remain cautious. They emphasize that true independence requires more than just access; it demands freedom from company control over information, timing, and publication. The key challenge lies in the implementation details, which have not yet been fully defined by either company. Researchers stress the need for transparent rules to ensure evaluators aren't restricted by narrow scopes or strict nondisclosure agreements, allowing them to effectively hold frontier AI companies accountable.

Architecting Secure and Scalable Facial Verification Systems

The article "Architecting Secure and Scalable Facial Verification Systems" from InfoQ explains the challenges and solutions in building enterprise-grade facial verification systems. The author shares experiences from scaling a prototype into a robust architecture capable of handling high concurrency, such as thousands of employees clocking in simultaneously. Key takeaways emphasize that facial verification must be treated as a distributed systems challenge, not just a simple API integration. Synchronous calls fail under heavy load, so asynchronous queues and circuit breakers are essential to handle traffic spikes. Additionally, decoupling immediate detection tasks from the stateful verification process prevents system bottlenecks. The author also stresses the importance of pushing data quality checks—like adjusting for lighting or blur—to the client device to reduce latency and cloud costs. For privacy and security, the system must enforce strict zero-trust principles, using short-lived tokens instead of raw personal data and implementing aggressive data retention policies. Finally, the article advises using a risk-based decision engine rather than static thresholds, treating confidence scores as probabilistic inputs to maintain accuracy across various transaction types.

Daily Tech Digest - September 20, 2026

Quote for the day:

“The more I read, the more I acquire, the more certain I am that I know nothing.” -- Voltaire

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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

Brain-Machine Interfaces Are Advancing: What Leaders Need to Know About Neurotechnology

The convergence of artificial intelligence, smaller electronics, and advanced materials is accelerating the steady development of brain-machine interfaces, allowing for practical communication between human brains and digital systems. While this field is currently focused on healthcare, with recent clinical studies showing paralyzed patients successfully using neural interfaces to control devices and communicate independently at home, its applications will soon expand. In the near future, industries such as education, manufacturing, and assistive technology will likely adopt these emerging tools to improve human performance and overall accessibility. By the end of the decade, the technology is expected to feature more accurate signals, less invasive hardware, and better machine interpretation of brain activity. Rather than guessing which specific device will dominate the market, organizations and leaders should prepare for these predictable advancements now. This means tracking improvements in neural decoding, exploring diverse interface methods like ultrasound, and considering how neural data might fit into future product lines. Just as importantly, the widespread use of neurotechnology will create new challenges surrounding data privacy, system compatibility, and user control over sensitive neural information. Solving these practical problems will offer significant opportunities for those who calmly anticipate the steady progress of neural engineering and plan accordingly.

Opinion: Tech enables transformation, people achieve it

Daire Cunningham’s article explores why so many organizations struggle to get real value from artificial intelligence, despite the technology being widely available. He notes that while 88% of businesses use AI in some capacity, only a third have managed to scale it across their operations. The core issue, he argues, isn’t a lack of access to advanced tech, but rather the underlying condition of the organizations trying to use it. When companies rush to adopt AI, they often start by looking for a specific tool instead of identifying the actual business problem they need to solve. To succeed, leaders must work backward: map out their processes, figure out where the information is kept, and spot the real bottlenecks. A major roadblock is poor data readiness—many businesses have years of accumulated, disorganized data and permissions. AI tends to expose these underlying flaws rather than cause them. Ultimately, Cunningham believes digital transformation is about rethinking how work gets done, not just adding new software. While AI can process data faster and tackle complex tasks, human judgment and oversight remain essential. True transformation happens when a company prepares its data foundation and empowers its people to use technology responsibly.

CIOs offer guiding principles on how to achieve AI sovereignty

The article discusses the growing importance of AI sovereignty for Chief Information Officers (CIOs). This concept is centered on maintaining control over an organization’s entire AI ecosystem, which encompasses data, models, and the infrastructure hosting those models. As AI technology becomes increasingly integrated into business operations, organizations face mounting risks related to data privacy, regulatory compliance, and potential vendor lock-in. To manage these challenges effectively, CIOs recommend establishing clear guiding principles. First, it is crucial to create a comprehensive inventory of all AI resources currently in use, as you cannot manage what you do not track. Second, organizations must implement robust data and usage controls to monitor information flow and quickly identify any policy violations. This proactive approach helps secure sensitive data. Third, companies should update their incident response plans specifically to address potential AI-related breaches, ensuring they can act swiftly if issues arise. Finally, maintaining transparency and auditability is essential. Knowing who accessed data and how AI tools influence decision-making helps build trust and ensures regulatory compliance. Rather than viewing AI sovereignty as a simple compliance checklist, leaders should treat it as a fundamental strategy for the long-term success and security of the enterprise.

Children's Data Protection in the Age of EdTech and Platform Design

The digital age has made children’s data collection widespread, from location tracking and educational data to behavioral and voice information. While some of this is meant for learning or safety, the concern is that such data can be used for profiling, targeted ads, or boosting engagement without parental consent. This has made data protection laws surrounding children increasingly relevant. India's Digital Personal Data Protection (DPDP) Act, 2023 defines a child as anyone under 18, which is a higher threshold than seen in many other countries. This act requires platforms to secure verifiable parental consent before processing a child’s data and forbids processing that could harm a child’s well-being. Additionally, the DPDP Act bans the tracking, behavioral monitoring, and targeted advertising directed at children, though it provides some exceptions for safe uses in healthcare, education, or child safety. Internationally, there are variations in how children's data is handled. In the United States, COPPA applies to children under 13, while the European Union’s GDPR sets the default age at 16, though member states can adjust it to 13. The UK’s Children’s Code requires platforms that children are likely to use to have high privacy settings by default. For platforms dealing with children's data, balancing data retention limits with educational needs requires clear strategies and compliance checks.

Most enterprises are failing to translate talk into meaningful dependency mapping

The recent feature on digital sovereignty highlights a significant gap between what organizations want and what they can actually achieve. While most companies express a strong desire to regain control over their digital infrastructure, the reality is that true independence remains out of reach for many. The truth is that achieving digital sovereignty is not simply about building internal data centers or buying local software; it requires deep visibility into existing information systems and having credible exit options from major service providers. Unfortunately, most enterprises currently lack these fundamental building blocks. Over the past fifteen years, a rush toward cloud computing has left many businesses heavily dependent on a handful of dominant technology giants. This dependency makes it incredibly difficult to pivot or change providers without facing steep costs and major operational disruption. As artificial intelligence becomes central to business strategy, the stakes for retaining control over data and computing power are higher than ever before. The article suggests that instead of pursuing total independence, leaders should focus on preserving choice. By prioritizing flexible tools and establishing clear governance, organizations can gradually build resilience. Ultimately, sovereignty is about making smart decisions today that prevent complete vendor entanglement in the future.

Agentic Systems and Design Patterns

The shift toward agentic artificial intelligence marks a move from simple text generation to setups that can plan, take action, and learn from their mistakes. When building these systems, developers must first choose an overall structure. A single agent approach is easier to build and manage, making it a great starting point, though it can struggle with complex or extended tasks. Conversely, a multiple agent system uses an orchestrator to delegate work to specialists, which boosts reliability through teamwork but requires careful coordination. Beyond the basic structure, six core design patterns drive how these models function. The ReAct pattern mixes logical thinking with concrete actions in a loop, while CodeAct allows agents to write and test code to achieve their goals. Self reflection acts as an internal critic to refine outputs and fix errors. Basic tool use lets agents interact with outside software, and Agentic RAG improves how they fetch and verify information. Finally, the multiple agent workflow handles massive tasks by dividing them into smaller parallel jobs. For the best results, start with a simple single agent setup and only add complexity when the task demands it. Strong safeguards, like strict iteration limits and clear tool definitions, keep these systems reliable and easy to monitor.

What OT Resilience Actually Controls

The article from SC Media explains that recovering operational technology (OT) after a cyber incident requires a fundamentally different approach than recovering standard IT systems. While IT disaster recovery focuses on system availability—getting servers and applications back online—OT recovery requires "safe-state validation." This means ensuring the manufacturing process can be controlled safely before restarting production. The challenge is that standard IT backups often miss crucial OT engineering data, such as process configurations, device programming, and safety system logic. Without these, a restored system might appear functional but lack the specific parameters needed to operate safely. The author outlines five common failure scenarios in OT resilience, including ransomware affecting control systems, vendor platform outages, and control logic tampering. These scenarios highlight the need for specialized OT backup architectures and recovery procedures. Ultimately, true OT resilience involves validating configurations at the device, system, and process levels, often requiring specialized engineering expertise. This validation step adds time to the recovery process but is essential to prevent unsafe conditions that could lead to physical harm or environmental damage.

Achieving data sovereignty for SaaS with confidential containers and quantum-safe networking

Software vendors hosting services on the public cloud face increasing pressure from customers who want to keep their data secure and private. Often, customers prefer on-premise solutions, which are harder to manage and scale for vendors. A better approach allows vendors to keep their services in the cloud while offering robust security through cryptographic controls, specifically using confidential computing. This technology secures data processed in untrusted environments by isolating it in a trusted execution environment (TEE). Red Hat and Arqit have introduced a setup that uses confidential containers and quantum-safe networking to protect data in transit. They applied this to Arqit's Encryption Intelligence (EI) platform. In this setup, services and data are isolated from the host environment, allowing customers to maintain control over their data while protecting the vendor's intellectual property. The architecture involves three clusters operating in the untrusted environment, communicating via a quantum-safe connection. Trust is established by an outer trustee in a trusted on-premise environment, which verifies the inner trustee in the cloud. This combination of confidential containers and quantum-safe protection for data in transit offers a practical alternative to on-premise deployments, providing strong assurance over data security and sovereignty for both vendors and customers.

AI-led SOC infrastructure shifts from raw data to outcomes

The article discusses a shift in how modern Security Operations Centres (SOCs) measure success in an AI-driven environment. Historically, SOCs focused on volume metrics, such as alerts processed or data ingested, but this model struggles against modern threats across distributed environments. Today, the focus is shifting to measuring outcomes like risk reduction, analyst capacity, and decision quality. The traditional volume-driven model leads to rising costs, overwhelmed analysts, and incremental improvements, failing to deliver clear returns on investment. While AI is viewed as a solution, it has struggled to deliver value when treated simply as an overlay, lacking transparency and integration. To overcome these limits, organizations must build SOCs around productivity rather than throughput, connecting technology investments with operational impact. In this model, AI isn't measured by its theoretical capability but by the work it completes alongside human analysts. A critical component is the use of "Agentic AI" as an execution layer, which coordinates investigations and decisions rather than functioning in isolation. For AI to be effective, it must also be governed to ensure actions are explainable and align with organizational policies, allowing security leaders to demonstrate responsible use and measurable security outcomes.

Data sovereignty is a control problem, not a geography problem

The article argues that data sovereignty is fundamentally about control, not geography. Many organizations assume that storing data within national borders is enough, but the author explains that this view is too narrow. True sovereignty depends on knowing who controls identities, administration, infrastructure, and legal authority over the data. Recent events have exposed how fragile digital infrastructure can be, from attacks on subsea cables to large‑scale outages like the CrowdStrike incident, which disrupted critical services worldwide and led to major financial losses. At the same time, new regulations and the rise of AI have increased the stakes, since sensitive information and intellectual property now flow through cloud‑hosted models governed by foreign jurisdictions. The article stresses that organizations often lack visibility into where their data lives, who can access it, and which laws apply. To regain sovereignty, they must demand transparency from providers, understand dependencies, and treat governance as an architectural requirement rather than an afterthought. Cost and speed still matter, but they can’t outweigh resilience and accountability. Sovereignty, the author concludes, isn’t about abandoning the cloud—it’s about ensuring organizations retain meaningful control so they can manage risk and respond confidently when incidents occur.