Showing posts with label MDR. Show all posts
Showing posts with label MDR. Show all posts

Daily Tech Digest - July 25, 2026


Quote for the day:

“People will never forget how you made them feel.” -- Maya Angelou

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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


Seeing AI Agents Is Not Enough. Security Teams Must Enforce What They Can Do

As organizations increasingly adopt artificial intelligence to handle everyday tasks, finding out where these AI programs operate is only the first step. The article points out that simply tracking these programs provides a false sense of safety. Unlike regular software or human workers with predictable routines, AI programs often adapt their actions based on goals, making standard access controls inadequate. Because they can reason and take action independently across various systems, the real security challenge lies in strictly enforcing what they are allowed to do. To achieve this, security teams must understand the core intent behind each program. This means correlating who owns the program, what it is designed to achieve, and what tools it needs to access. Rather than waiting for something to go wrong and cleaning up the mess, organizations should set clear rules that govern AI behavior before actions occur. For example, a customer support tool might need to read histories but should never be allowed to export bulk data. Ultimately, managing these tools safely requires a unified approach that spans the entire organization. Success comes not just from knowing an AI tool exists, but from confidently controlling its boundaries, actions, and overall purpose.


The air gap is a myth and other OT security truths

In a recent interview, Benjamin Bachmann, Director of Group Information Security at Bilfinger, addresses key realities of securing industrial operations and dispels common misconceptions about operational technology security. He explains that attackers targeting industrial environments are generally not looking to steal data or trade secrets. Instead, they want to disrupt operations and gain control over physical processes. He also notes that the idea of a completely isolated network, or air gap, is largely a myth in today's connected plants. To handle security incidents effectively without compromising safety or uptime, Bachmann emphasizes the need for engineering and security teams to establish containment protocols long before an emergency occurs. He points out that while older industrial equipment lacks modern security features, its highly predictable network traffic makes it easier to spot unauthorized activity through careful monitoring and network segmentation. Regarding ransomware, Bachmann observes that attackers often price their demands based on the cost of operational downtime. Therefore, the most effective defense involves rapid recovery plans and the ability to maintain partial operations safely, which removes the attacker's leverage. Finally, he challenges the common belief that human error is the weakest link in security, arguing instead that fragile system architectures are the actual root problem.


Why enterprises should care about Nokia’s AI-RAN platform

Nokia recently announced an artificial intelligence driven platform designed to fundamentally change how mobile network infrastructure operates. Traditionally, mobile networks rely on rigid, specialized hardware that limits adaptability and requires frequent physical upgrades. The new approach separates the network software from the physical hardware, running operations on flexible graphics processing units instead. This shift effectively turns the radio network into a programmable computer. The immediate benefit for network operators is significant performance improvements. By using complex algorithms, the platform can double the usable capacity of existing wireless spectrum bands by the year 2028, avoiding the need for expensive new spectrum licenses. Furthermore, it easily adapts to changing data traffic patterns caused by modern applications. However, the most critical shift is in potential business models. Because the platform operates like a standard computing environment, it supports a new application layer where developers can create practical tools. This allows operators to generate revenue beyond basic internet connectivity. Practical applications include turning cell towers into sensor networks for environmental monitoring, providing accurate tracking for warehouse robots, and offering dedicated computing power for local data processing. Ultimately, this software driven strategy allows network providers to continuously update features and increase efficiency without relying on constant hardware replacements.


AI adoption in OT security outpaces governance controls

According to a recent industry survey, industrial organizations are rapidly adopting artificial intelligence for operational technology (OT) cybersecurity, yet formal governance and safety controls are lagging significantly behind. While nearly ninety percent of surveyed organizations are evaluating or using AI to monitor networks, detect threats, and support security operations, only about fifteen percent have implemented an enforced AI policy tailored to industrial environments. The technology is primarily deployed in advisory roles for monitoring and analysis rather than direct industrial control. However, errors in AI classification or alerting could still negatively affect equipment availability and safety. Implementation challenges are primarily rooted in poor data quality, lack of proper labeling, and the difficulty of integrating modern AI tools with legacy operational systems. Furthermore, respondents expressed concerns about the physical risks of AI system failures or cyberattacks manipulating AI outputs, as adversaries increasingly use similar technology to enhance their attacks. Most organizations currently rely on informal human oversight rather than documented protocols. Experts suggest that to maintain operational control, companies should ensure their use of AI does not exceed the authority supported by their current security controls, evidence, and operating models. Robust governance and formal consequence mapping are essential for safe integration.


CIOs beware: DNS KSK rollover could kick off wave of mysterious outages

A seemingly routine security update to the internet’s domain name system could trigger unexpected network outages for organizations between October 2026 and January 2027. The event, known as a Key Signing Key rollover, updates the cryptographic key that verifies network responses. While the central update itself is simple, many organizations possess vast networks of unmapped connections hidden within older applications, custom scripts, external services, and forgotten software containers. Because these hidden areas operate outside normal oversight, they may fail to process the new key correctly. When these older configurations fail, the resulting disruptions rarely announce themselves as a domain name problem. Instead, they often look like random application timeouts, broken logins, or unreachable partner networks. This misdirection can force support teams to spend hours troubleshooting the wrong issues before realizing the core problem stems from a missed network update. Although widespread failure of primary systems is unlikely, even isolated disruptions in specific departments or manufacturing lines can cause severe operational delays. Experts advise technology leaders to treat this upcoming change with calm focus. Rather than viewing it as a simple infrastructure chore, organizations can use this event as a practical opportunity to improve their internal visibility and strengthen overall system resilience.


The metrics organizations should track to measure their cyber resilience

As cyber disruptions become an unavoidable reality, organizations must shift from merely aspiring to cyber resilience to making it a measurable operational capability. Relying on traditional technical metrics, like counting patched vulnerabilities or software alerts, is no longer sufficient. These measurements do not reflect a company's ability to maintain its operations during a crisis. Instead, leaders should measure resilience by its actual business impact. The first step is identifying the minimum viable business, which includes the critical services and functions that must remain active or be restored immediately to fulfill the organization's core mission. From there, time becomes the most valuable metric. Organizations should track how quickly they can detect, contain, and recover from an incident to minimize both the depth and duration of the disruption. Furthermore, standard questionnaires and self-assessments are inadequate for testing true readiness. Practical, realistic exercises, such as tabletop simulations and recovery drills, are necessary to uncover gaps in decision-making and communication under stress. Because businesses operate within interconnected ecosystems, resilience must also extend to suppliers and third-party partners. Ultimately, these practical metrics serve as a vital leadership tool, guiding investment decisions and proving that a company can confidently withstand and operate through significant cyber events.


The Compliance Timelines Are Converging: Every Road Now Leads to a Cryptographic Bill of Materials

Over the next few years, multiple security regulations and government standards are converging, bringing strict new deadlines for organizations to track and manage their encryption methods. Past transitions to newer security standards were difficult because companies simply did not know where their outdated encryption was hidden. Now, with the looming threat of advanced computers capable of breaking current encryption, the stakes are even higher, especially since adversaries can steal sensitive encrypted data today and unlock it later. Many organizations mistakenly rely on basic certificate scanners, but these tools fail to detect encryption deeply embedded in software applications, operating systems, and databases. To properly secure their networks and meet these overlapping rules, companies must build a complete map of their encryption assets and understand how they interact. This comprehensive record is known as a Cryptographic Bill of Materials. By adopting this approach, teams can identify vulnerabilities, map relationships between systems, and prioritize updates without guesswork. The most effective strategy is to start by taking a realistic inventory of all current encryption practices across the entire organization. Doing so allows leaders to confidently prepare for future requirements, adapt to new standards, and maintain continuous oversight of their digital security. It is a vital step.


Recovery Readiness Is the New Measure of Cybersecurity Success

For decades, the primary goal of cybersecurity was preventing attacks by building strong defenses like firewalls and detection systems. While prevention remains a highly foundational element, the rapidly evolving threat landscape, driven by sophisticated ransomware, nation-state actors, and artificial intelligence, means that simply keeping attackers out is no longer a realistic finish line. Today, stakeholders recognize that even the most secure organizations can suffer breaches. As a result, the standard for cybersecurity success has firmly shifted from strict prevention toward operational recoverability. Instead of just tracking technical vulnerabilities, leaders, customers, and boards are now asking how quickly and confidently a business can actually restore its critical services after a cyber incident. Preserving trust and reputation now depends on resilient recovery processes rather than simply avoiding compromise. However, true recovery readiness cannot be assumed from written plans or annual exercises alone; it requires continuous validation as cloud infrastructure, hidden business dependencies, and technologies evolve. Moving forward, companies must treat operational recoverability as a vital business metric. By understanding their recovery posture, organizations can prioritize investments based on actual business impact, reduce uncertainty during a crisis, and ensure they survive and thrive even after a serious cyberattack occurs.


Why MDR Is Essential for Big Data Security

Managed Detection and Response is becoming increasingly vital as organizations generate massive amounts of data and face more sophisticated threats. In our highly connected world, the convergence of traditional corporate networks and operational technology creates significant vulnerabilities. Industrial systems, which were once completely isolated, now frequently connect to cloud platforms and corporate systems, greatly expanding the potential attack surface. Consequently, security teams must sift through enormous volumes of business data to identify subtle anomalies and hidden threats before they cause widespread damage. A robust Managed Detection and Response strategy provides continuous monitoring and specialized expertise, which is especially critical for operational technology environments like manufacturing, energy, and utilities. Unlike standard information technology environments, these physical systems prioritize safety and continuous operation above all else, meaning security measures cannot simply shut down critical processes when a threat is suspected. Top providers address this challenge by delivering specialized detection and response tailored to the unique constraints of industrial control systems. They bridge the gap between information technology and operational technology, helping leaders reduce physical risks, adhere to critical infrastructure regulations, and protect essential services. By partnering with an experienced provider, companies gain the necessary visibility and rapid response capabilities to secure their complex data environments with assurance and operational continuity.


Europe's Multilingual Reality Exposes AI Security Gaps

While large language models can process text in dozens of languages, their included safety guardrails are overwhelmingly optimized for English. This English focus creates significant security vulnerabilities for organizations operating in multilingual environments, particularly across Europe. Although a model might fluently answer prompts in languages like German, Spanish, or Swahili, its ability to detect and block malicious actions, such as prompt injections and jailbreaks, often drops significantly compared to English. Attackers exploit this gap by translating harmful commands into lesser used languages to bypass security filters. Research shows that some models are vastly more likely to provide actionable responses to unsafe prompts when queried in these regional languages. Relying on translation security layers, where inputs are translated to English before being checked, can alter the true intent of a prompt, sometimes masking malicious commands within benign contexts. To address these serious vulnerabilities, experts recommend moving beyond basic translation filters. Organizations should instead adopt native language guardrails that evaluate the original input, conduct rigorous security testing that includes mixed language scenarios and diverse cultural contexts, and deploy active runtime firewalls. As the modern regulatory landscape, including new artificial intelligence legislation in Europe, demands better risk management, ensuring consistent safety across all supported languages is becoming a critical operational necessity.

Daily Tech Digest - June 14, 2026


Quote for the day:

“If you think compliance is expensive, try non‑compliance.” -- Paul McNulty

🎧 Listen to this digest on YouTube Music

▶ Play Audio Digest

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


Segmentation Works for OT If Operators Are Paying Attention

Network segmentation remains a foundational strategy for securing operational technology, but its ultimate effectiveness relies heavily on active and continuous human oversight. Many organizations mistakenly view network segmentation as a static, one-time project designed during a workshop, rather than as an ongoing operational practice that evolves over time. This fixed mindset creates dangerous security gaps, as real-world industrial environments change quickly while network diagrams remain completely outdated. Furthermore, the practical execution of traditional segmentation and newer microsegmentation models faces severe real-world hurdles. Traditional firewalls are frequently undermined by user convenience workarounds, such as technicians introducing unmanaged, internet-connected personal laptops onto the factory floor, or by unpatched vulnerabilities within the firewalls themselves. Meanwhile, microsegmentation is regularly impossible to implement because older legacy infrastructure cannot accommodate security software agents or survive the disruptive downtime required for vital updates. Compounding the issue, companies often overuse segmentation by dumping too many diverse industrial systems into a single isolated zone, meaning one compromised machine can expose the entire segment. To fix these systemic flaws, security experts recommend adopting enforceable policies that continuously verify user access. Operators must look past static blueprints, regularly auditing endpoint logs and identifying unrecognizable addresses to catch unauthorized connections before clever attackers can exploit them.


In Conversation with Simon Stone and Simon Barrows: Adventures in Architecture as Code

As organizations grow in scale and speed, traditional architecture diagrams often become outdated, subjective, and disconnected from actual operations. A recent interview with Simon Stone and Simon Barrows explores the transition from relying on these static diagrams to adopting Architecture as Code, a method that treats architectural knowledge as living, version-controlled data. This shift is increasingly practical today because modern artificial intelligence can efficiently gather and organize data from various scattered sources. By keeping architecture as structured data, teams can automatically generate up-to-date diagrams on demand, test for consistency, and cleanly link business strategies directly to technology investments. This approach changes the architect's role from drawing static pictures to managing data quality, working more like a software engineer. Instead of constantly updating documents, architects can rely on automated tests for routine checks and focus their time on complex decisions. However, converting old, fragmented documents into a single, reliable dataset remains a significant challenge. To succeed, the speakers advise starting small. Rather than attempting a massive overhaul all at once, organizations should identify a specific, high-value problem to solve first. By focusing on a clear initial use case, companies can build a solid foundation and gradually expand their structured architecture, ultimately creating a more transparent, efficient, and well-aligned technical environment.


10 Indispensable Prompts Our Team Refuses to Build Without

The recent Google Cloud blog post highlights a collection of practical prompts that their engineering teams rely on to build better software. Rather than using AI just to write code faster, these developers use specific prompts to challenge their own assumptions and catch mistakes early. The shared prompts cover a wide range of everyday programming tasks. For example, some developers ask the AI to act as a strict architect to help refine product requirements without making the design too complex. Others use it to run thorough code reviews, instructing the tool to grade their work on a harsh scale to ensure systems are truly reliable. There are also prompts designed to build testing plans, clean up unused code and forgotten comments, check software permissions for compliance, and weigh the pros and cons of different technical choices. Additionally, the team uses prompts to automatically review code changes and identify potential flaws in code that was generated by AI itself. Ultimately, the article suggests that treating AI as a critical partner rather than a simple code generator helps developers release software with greater confidence. By routinely asking hard questions and checking for hidden weaknesses, engineering teams can improve the overall quality of their work and avoid unexpected failures.


AI Governance in Enterprise Adoption: Why Trust Will Define the Next Wave of Innovation

Artificial intelligence is steadily moving from isolated experiments into the daily operations of the financial services sector. As companies integrate these systems into everything from fraud detection to customer service, the primary challenge is no longer about the technology itself, but rather about building institutional trust. With the arrival of more autonomous systems, financial organizations must handle complex new risks that go beyond simple technical errors. These risks involve broad operational dependencies, data security, and the complications of unapproved tool usage by employees. Because of this, companies are shifting away from unrestricted public tools and moving toward carefully governed internal environments. Setting clear rules and maintaining structured oversight should not be viewed as an obstacle to progress. Instead, sensible governance provides the necessary foundation for organizations to innovate safely and reliably. By establishing clear boundaries and maintaining accountability, businesses give their teams the confidence to adopt new capabilities while assuring regulators and customers that their data remains secure. Ultimately, the companies that succeed in this new landscape will not necessarily be the fastest to implement the latest tools. They will be the ones that recognize safe, transparent, and continuous oversight as a strategic advantage, proving that responsible management is a fundamental requirement for sustainable growth in modern finance.


Rethinking MDR as Attackers and Defenders Embrace AI

Traditional managed detection and response models are struggling to keep pace with modern cybersecurity threats. Historically, these services relied on human analysts to monitor networks and investigate potential issues. However, as attackers increasingly use advanced automation to launch faster and more complex campaigns, human-led teams simply cannot process the massive volume of alerts generated daily. Because of this, analysts are forced to prioritize severe warnings, leaving roughly sixty percent of alerts unreviewed. Unfortunately, attackers know this and deliberately hide their activity within these overlooked, low-severity notifications. Furthermore, the quality of human investigation can vary depending on shift times and workload, leading to inconsistent security outcomes. To address these vulnerabilities, organizations are moving toward automated systems. In this new approach, computers automatically investigate every single alert, regardless of its initial severity rating or the time of day. Instead of acting as a simple filter, the system conducts a deep, technical analysis of all warnings in seconds, providing a consistent and thorough review. This allows human security teams to shift their focus from manual discovery to making informed decisions based on the system's verified findings. Ultimately, adopting this automated approach ensures complete alert coverage, eliminates blind spots, and provides organizations with full ownership of their own network data.


The Intelligent Factory: Navin Nathani on How Manufacturing’s Next Competitive Edge Is Being Built on Data, Resilience, and Industrial AI

In modern manufacturing, competitive advantage no longer relies solely on scale and cost, but on the speed and quality of broad company decisions. Navin Nathani emphasizes that navigating current disruptions requires connected operations rather than delayed reporting. To achieve this, technology is shifting from a supportive background function to the core operating system of the business. Organizations are focusing on practical technology updates, such as modernizing resource planning software and moving information storage to the internet. These practical upgrades establish stability and build trust among employees, making them more open to further changes. As office networks and factory machinery converge, manufacturing plants become more connected, which necessitates a stronger focus on security to protect production from emerging online threats. Furthermore, the industry is gradually adopting artificial intelligence for specific applications like anticipating equipment repairs and better supply planning. Rather than serving as a replacement for human workers, this technology acts as a useful assistant that helps identify patterns and prevent equipment failures before they occur. However, successful implementation relies heavily on maintaining disciplined processes and accurate data. Ultimately, the future of manufacturing lies in using connected information to shift from reacting to problems to preventing them, ensuring that daily operations remain stable in an unpredictable environment.


​Knowing When To Let Go Is A Leadership Skill

In her article, Kendra MacDonald explains that true leadership requires knowing when to persevere and when to simply let go. Drawing from her personal experiences with family planning, she notes that while society often celebrates grit and determination, effective leaders must also exercise clear judgment. They need to recognize whether their ongoing efforts are actually helpful or just delaying an inevitable outcome. MacDonald highlights that some situations and relationships cannot be repaired, and forcing people to agree is not always the answer. Instead, she advises leaders to accept differences as realities rather than problems to solve. When setbacks occur, it is essential to learn from them without taking the failure personally or letting emotions cloud objective facts. Furthermore, she stresses the importance of facing difficult conversations directly, as avoiding them only prolongs frustration for everyone involved. Honest communication, even when disappointing, is far more useful than giving false hope. Most importantly, MacDonald points out that holding onto the wrong opportunity or strategy drains team energy. By walking away from poorly fitting client relationships or unworkable strategies, leaders create space for fresh ideas and better matches. Ultimately, stepping back from a failing path is not a lack of resilience; rather, it is often the clearest demonstration of confident leadership.


The Real Cost of Unclear Technology Ownership

Unclear technology ownership is a direct threat to a company's operational stability and financial health. When no single person is accountable for a specific technology, organizations suffer from chronic delays, wasted spending, and repeated audit failures. Teams might look busy with meetings and project updates, but without a clear decision maker, this activity often hides a lack of actual progress. The costs show up as hidden labor, duplicated efforts, and lingering security vulnerabilities. This lack of ownership usually breaks down in critical areas like access management, data reporting, and vendor relationships. When systems fail or security incidents occur, fragmented responsibility means no one knows who should act first. As a result, small problems quickly escalate into costly crises. Furthermore, when executives and board members receive vague answers or see the same issues repeatedly, they quickly lose trust in the team's ability to manage risk. To fix this, companies do not need massive new programs. Instead, they must assign one accountable executive to each major risk area and give them the real authority to make decisions and control budgets. Organizations should establish a clear path for reporting bad news and ensure that board updates focus on actionable decisions rather than just listing activities. Clear ownership replaces confusion with stable, reliable progress.


AI Is Here to Stay. The Real Challenge Is Operating It Securely

Artificial intelligence is now a standard tool for writing software, with AI-generated code already running in major projects like OpenStack. However, its rapid adoption introduces significant operational and security challenges. Because AI produces code so quickly, human reviewers struggle to keep up, making it harder to ensure software remains secure and maintainable. Even more concerning is the rise of autonomous AI agents. Organizations often grant these agents broad permissions to access production environments, ignoring decades of security practices like the principle of least privilege. While AI capabilities advance rapidly, security features like containment and auditing lag behind. To operate AI securely, teams must apply proven engineering practices. First, organizations should use automated gating systems like Zuul. By testing how new code interacts with dependencies before it merges, gating prevents errors from reaching production. This acts as a vital check against the high volume of AI-written code. Second, teams should use strong hardware isolation, such as Kata Containers, to protect sensitive information. Standard containers share a core operating system, posing security risks in shared environments. Kata provides lightweight virtual machine isolation, ensuring data processed by an agent remains secure. Ultimately, enforcing strict access limits, adopting automated quality checks, and maintaining reliable backups are essential steps for operating AI safely.


Security in the Post-Mythos Era

The emergence of advanced artificial intelligence capable of instantly discovering and exploiting software vulnerabilities has fundamentally shifted the timeline of cybersecurity. While the core principles of network defense remain unchanged, the sheer speed at which new threats materialize means organizations can no longer rely on software patching as their primary shield. Because AI systems can weaponize flaws in minutes, human-driven patching cycles simply cannot keep pace. To survive, organizations must adopt a layered strategy that holds strong when patching inevitably falls behind. The first critical step is returning to basic system hardening. This means strictly enforcing multi-factor authentication, removing unnecessary network services, and dividing networks into isolated segments to prevent attackers from moving freely. When preventive measures fail, robust detection and response systems serve as the vital safety net. Security teams must assume some attacks will break through and focus on identifying the behavioral signs of an intruder, rather than relying solely on known threat lists. Finally, organizations must actively test these defenses. Regularly checking network boundaries and practicing response plans ensures that controls work in reality, not just on paper. AI has accelerated the speed of risk, making foundational preparation and rigorous testing the most reliable path to security.