Showing posts with label data pipeline. Show all posts
Showing posts with label data pipeline. Show all posts

Daily Tech Digest - September 14, 2026


Quote for the day:

“The only sustainable competitive advantage is an organisation’s ability to learn faster than the competition.” -- Peter Senge

🎧 Listen to the audio debrief on YouTube

▶ Play Audio Digest

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


Post-Quantum Cryptography Is Becoming Mandatory For Financial Institutions

As quantum computers become more powerful, they will eventually break the cryptography that currently protects financial data. This presents a serious risk for banks and insurers, especially for long-term records that adversaries might steal now to decrypt later. The solution is post-quantum cryptography (PQC), a set of new mathematical formulas that even quantum computers cannot easily solve. Importantly, PQC runs on standard computers and integrates into existing systems like TLS. The main hurdle for financial institutions is not buying quantum hardware, but updating decades of old, intertwined software before the threat becomes a reality. Standards are already being finalized, and regulators are beginning to expect actionable roadmaps from the financial sector. To prepare, institutions must first build a complete inventory of their current cryptographic tools and identify where their systems are most vulnerable. Since no single algorithm is guaranteed to be safe forever, organizations should design flexible architectures that allow them to swap out encryption methods as needed. Addressing this transition requires strong cross-team collaboration and commitment from leadership. By acting now to map their risks and pilot hybrid solutions, financial firms can control their migration timeline rather than scrambling at the last minute.


Attackers already understand your software supply chain better than you do

The article argues that attackers now understand modern software supply chains better than the organizations that rely on them, and that AI is accelerating this gap. It describes how recent incidents—such as the Miasma malware packages and the Axios compromise—show that threats often begin with small, trusted open‑source components that slip quietly into developer workflows. Because most commercial software depends heavily on open‑source code, many companies lack visibility into what they are actually running in production or how quickly they could respond if a critical flaw appeared. Attackers exploit this blind spot by targeting overlooked dependencies and developer tools rather than traditional network perimeters. The piece explains how malicious packages spread rapidly through CI/CD pipelines, bypassing controls and creating large downstream risk before anyone notices. It also notes that AI‑driven automation allows attackers to discover vulnerabilities and coordinate exploits far faster than defenders can react, especially when security teams are slowed by technical debt and manual processes. The article concludes that software supply chain security has become a national‑level concern and that organizations need continuous, automated controls capable of identifying risks, enforcing policies, and reducing exposure before attackers take advantage of weaknesses they already understand.


When Spec-Driven Development Pays off

With AI coding assistants becoming standard infrastructure in software engineering, the primary bottleneck has shifted from writing code to verifying it. This shift raises critical governance questions regarding accountability, intent divergence, and the division of oversight between humans and models. Regulatory frameworks like the EU AI Act and NIST risk management guidelines increasingly demand documented controls, making "careful review" an insufficient strategy for managing AI-generated code. A recent study examined the popular response of "spec-driven development"—treating detailed specifications (business rules, high-level design, and low-level design) as a governing contract for AI output. Interestingly, establishing a strict specification baseline did not inherently make human reviewers better at finding bugs. Instead, it transformed code review from an ambiguous task into a contract-anchored, highly accountable process where behavioral drift could be clearly attributed to specific requirements. While writing a specification first and generating code from it improved outcomes by treating the spec as a governing artifact rather than just a prompt, the benefits on simpler tasks were largely due to improved reasoning rather than the spec itself. Ultimately, specification governance proves to be a worthwhile investment primarily for complex, multi-constraint tasks handled by capable but imperfect AI models.


Your data architecture was built for predictable consumers

The article explains how traditional enterprise data architectures were built for a world where data consumers behaved in predictable, uniform ways, and why that model no longer fits today’s environment. It describes how organizations once supported thousands of users working from the same carefully designed application, with stable access patterns that made governance manageable. As dashboards, APIs, notebooks, microservices, and specialized tools multiplied, consumption became more varied — and agentic AI has now pushed this shift even further. Instead of one shared interface, those same users may rely on thousands of individualized agents or applications, each creating its own access paths, combinations, and entitlement decisions. The piece notes that while personalization becomes easier at the application layer, the underlying infrastructure and security teams face growing complexity, with more dynamic demand and harder‑to‑govern patterns. It highlights capital markets as an early testing ground, where zero tolerance for inconsistency has driven architectures that coordinate changing consumer behavior. The article argues that a governed data consumption layer — the outward‑facing part of a broader data fabric — can reduce repeated integrations, protect sensitive systems, and enforce consistent access and audit controls. It concludes by urging CIOs to evaluate where such an approach adds value as human and machine consumers increasingly access and act on data in unpredictable ways.


How to level up from security pro to security leader

Transitioning from a technical cybersecurity professional to a Chief Information Security Officer requires a fundamental shift in perspective. While a strong technical foundation is helpful, it is no longer enough to reach the executive level. Aspiring security leaders must learn to translate complex technical risks into clear business priorities. This means understanding how the company generates revenue and balancing security needs with broader organizational goals. Rather than being seen as the resident tech expert, successful leaders act as strategic partners who build trust across various departments, including finance, legal, and operations. Developing strong communication skills and business sense is far more valuable than mastering specific coding languages. Gaining broad experience, such as managing budgets or working in cloud engineering, can provide the highly valued background that modern employers expect. Additionally, finding experienced mentors and maintaining a genuine curiosity for new technologies will naturally foster leadership growth. Security professionals are advised to present themselves with calm confidence, take ownership of their mistakes, and avoid being overly rigid about their long term career paths. By focusing on delivering meaningful impact and collaborating effectively in their current roles, aspiring executives can position themselves for the transition from technical expert to trusted business leader.


Enterprise AI Security: ChatGPT, Claude, Gemini and Copilot Compared

As artificial intelligence tools transition from experimental chatbots to integrated enterprise solutions, businesses face new security challenges. Platforms like ChatGPT, Claude, Gemini, and Microsoft Copilot now connect directly to internal emails, cloud storage, and code repositories, shifting the primary risk from external data leaks to internal data exposure and unauthorized actions. No single platform is perfectly secure, as each presents unique vulnerabilities. For ChatGPT, the main governance gap lies between secure enterprise accounts and the personal accounts employees might still use. Claude’s agent capabilities pose a different risk: because it can execute commands and modify code, overly broad permissions could lead to unintended software changes. Meanwhile, both Gemini and Microsoft Copilot respect existing workspace access controls, but they act as powerful search engines that expose years of accumulated, poorly managed permissions. They do not bypass security rules, but they make forgotten, overshared documents instantly discoverable to employees. Additionally, all platforms face the threat of prompt injection, where hidden instructions in external files manipulate the AI. To safely adopt these tools, organizations must clean up internal access permissions, separate consumer from enterprise usage, define clear data retention policies, and strictly monitor what internal systems the AI can currently access.


Why AI shouldn't be the one repairing your data pipelines

As organizations expand their use of autonomous artificial intelligence systems to make operational decisions in real time, the traditional concept of self-healing data pipelines is no longer sufficient. While modern cloud architectures can quickly replace failed components, data failures in complex enterprise environments rarely present themselves as complete systemic crashes. Instead, these issues manifest as silent degradation, such as undocumented changes in source systems, misaligned business logic, or untrackable errors that compromise downstream models and regulatory reports. To support advanced business operations, engineering leaders must transition from reactive, automated repairs to autonomous data governance and resilient infrastructure. A critical component of this shift involves prioritizing deterministic solutions over heuristic guesswork. While artificial intelligence is highly effective at detecting anomalies and triggering alerts, relying on automated scripts to guess how to fix crucial records risks introducing synthetic errors into auditable systems. Rather than letting artificial intelligence independently repair data pipelines, organizations should pair machine learning detection with predefined, policy-driven workflows that isolate problems and apply historical fallback logic. By treating data reliability as a core business risk and building systems that actively defend and remediate quality issues in real time, enterprises can establish a secure foundation for their critical operations.


When security creates friction, employees find workarounds

When workplace security measures become too complicated or time-consuming, employees often look for easier ways to get their jobs done. According to a recent report, forty percent of workers globally admit to using unauthorized personal devices or applications when official technology fails them. In the Asia-Pacific region, this problem is particularly noticeable, with many staff members turning to unapproved platforms like public AI tools just to meet deadlines or respond to customers quickly. While these workarounds usually stem from a genuine desire to be productive rather than malicious intent, they create significant risks because organizations cannot secure or govern activity that they cannot see. This phenomenon, often called "shadow AI," highlights a disconnect between security rules and everyday operational needs. Instead of just blocking unapproved tools, leaders should view these behaviors as a clear signal that current systems are causing too much friction. The most effective way to reduce this hidden risk is to integrate security naturally into daily workflows. By prioritizing user experience and making the secure option the easiest one to use, companies can better protect their data while still empowering their teams to work efficiently.


BRICS digital sovereignty meets the interoperability test

The recent New Delhi BRICS Declaration sets forth an ambitious vision for technology that attempts to balance national control with global connectivity. The core challenge outlined in the document is how member nations can achieve digital sovereignty and self-reliance without sacrificing the interoperability that modern networks require. Rather than proposing a disconnected or isolated tech ecosystem, the declaration emphasizes building strong, nationally controlled digital public infrastructure (DPI) that can securely communicate across borders. This balancing act applies across several layers of technology. For DPI, it means countries maintain control over their own identity and data systems while ensuring they can interface with others. For physical infrastructure, the focus is on developing resilient submarine cables to reduce reliance on external entities, though the exact technical details remain under review. In terms of future technology and supply chains, the group is pushing for collaborative research and common, globally interoperable security standards. Ultimately, the declaration suggests that true digital sovereignty isn't about isolating a nation's network, but rather participating in global digital systems without becoming overly dependent on outside suppliers or infrastructure. The success of this vision will depend heavily on the upcoming technical and engineering decisions.


Why Data Governance Still Isn’t Driving Better Decisions (or Transformation)

Many organizations have invested heavily in data governance, setting up dedicated offices, policies, and committees. Despite this, the actual business impact often remains elusive. Compliance is still a manual process, and decisions are frequently made using data of uncertain quality. The core issue is that while data governance manages data, it often fails to govern the decisions that data is supposed to inform. This disconnect is a flaw in both the design and deployment of current governance models. For years, the standard approach has been to identify critical data, assign ownership, and implement controls, largely driven by regulatory requirements like GDPR. While this model has improved awareness and traceability, it often falls short of delivering measurable business value. Data offices struggle to prove their return on investment, and business teams may bypass governance processes that they feel slow them down without offering real benefits. The initial focus on inventorying and controlling data made sense as a starting point. However, these are backward-looking control systems. To truly drive business performance, data governance needs to evolve from merely a control mechanism into a forward-looking decision system that actively supports and prepares organizations for future actions.

Daily Tech Digest - June 11, 2025


Quote for the day:

"The key to success is to focus on goals, not obstacles." -- Unknown



The future of RPA ties to AI agents

“Unlike RPA bots, that follow predefined rules, AI agents are learning from data, making decisions, and adapting to changing business logic,” Khan says. “AI agents are being used for more flexible tasks such as customer interactions, fraud detection, and predictive analytics.” Kahn sees RPA’s role shifting in the next three to five years, as AI agents become more prevalent. Many organizations will embrace hyperautomation, which uses multiple technologies, including RPA and AI, to automate business processes. “Use cases for RPA most likely will be integrated into broader AI-powered workflows instead of functioning as standalone solutions,” he says. ... “RPA isn’t dying — it’s evolving,” he says. “We’ve tested various AI solutions for process automation, but when you need something to work the same way every single time —without exceptions, without interpretations — RPA remains unmatched.” Radich and other automation experts see AI agents eventually controlling RPA bots, with various robotic processes in a toolbox for agents to choose from. “Today, we build separate RPA workflows for different scenarios,” Radich says. “Tomorrow, with our agentic capabilities, an agent will evaluate an incoming request and determine whether it needs RPA for data processing, API calls for system integration, or human handoff for complex decisions.”


The path to better cybersecurity isn’t more data, it’s less noise

SOCs deal with tens of thousands of alerts every day. It’s more than any person can realistically keep up with. When too much data comes in at once, things get missed. Responses slow down and, over time, the constant pressure can lead to burnout. ... The trick is to start spotting patterns. Look at what helped in past investigations. Was it a login from an odd location? An admin running commands they normally don’t? A device suddenly reaching out to strange domains? These are the kinds of details that stand out once you understand what typical system behavior looks like. At first, you won’t. That’s okay. Spend time reading through old incident reports. Watch how the team reacts to real alerts. Learn which ones actually spark investigations and which ones get dismissed without a second glance. ... Start by removing logs and alerts that don’t add value. Many logs are never looked at because they don’t contain useful information. Logs showing every successful login might not help if those logins are normal. Some logs repeat the same information, like system status messages. ... Next, think about how long to keep different types of logs. Not all logs need to be saved for the same amount of time. Network traffic logs might only be useful for a few days because threats usually show up quickly. 


The EU challenges Google and Cloudflare with its very own DNS resolver that can filter dangerous traffic

The DNS4EU wants to be an alternative to major US-based public DNS services (like Google and Cloudflare) to boost the EU's digital autonomy by reducing European reliance on foreign infrastructure. This isn't only an EU-developed DNS, though. The DNS4EU comes with built-in filters against malicious domains, like those hosting malware, phishing, or other cybersecurity threats. The home user version also includes the possibility to block ads and/or adult content. ... The DNS4EU, which the EU ensures "will not be forced on anyone," has been developed to meet different users' needs. The home users' version is a public and free DNS resolver that comes with the option to add filters to block ads, malware, adult content, or all of these, or none. There's also a dedicated version for government entities and telecom providers that operate within the European Union. As mentioned earlier, the DNS4EU comes with a built-in filter to block dangerous traffic alongside the ability to provide regional threat intelligence. This means that a malicious threat discovered in one country could be blocked simultaneously across several regions and countries, de facto halting its spread. ... The Senior Director for European Government and Regulatory Affairs at the Internet Society, David Frautschy Heredia, also warns against potential risks related to content filtering, arguing that "safeguards should be developed to prevent abuse."


AgenticOps: How Cisco is Rewiring Network Operations for the AI Age

AI Canvas is where AgenticOps comes to life. It’s the industry’s first generative UI built for cross-domain IT operations, unifying NetOps, SecOps, IT, and executives into one collaborative environment. Powered by real-time telemetry from Meraki, ThousandEyes, Splunk, and more, AI Canvas brings together data from across the stack into one intelligent, always-on view. But this isn’t just visibility. It’s AI already operating. When a service issue hits, AI Canvas pulls in the right data, connects the dots, and surfaces a live picture of what matters—before anyone even asks. Every session starts with context, whether launched by AI or by an IT engineer. Embedded into the AI Canvas is the Cisco AI Assistant, your interface to the agentic system. Ask a question in natural language. Dig into root cause. Explore options. The AI Assistant guides you through diagnostics, decisions, and actions, all grounded in live telemetry. And when you’re ready to share, just drag your findings into AI Canvas. From there, with one click you can invite collaborators—and that’s when the canvas comes fully alive. Every insight becomes part of a shared investigation with AI Canvas actively thinking, collaborating, and evolving the UI at every step. But it doesn’t stop at diagnosis—AI Canvas acts. It applies changes, monitors impact and share outcomes in real time.


8 things CISOs have learned from cyber incidents

Brown believes there are often important lessons that come out of breaches, whether it’s high-profile ones that end up in textbooks and university courses, or experiences that can be shared among peers through conference panels and other events. “Always look for good to come from events. How can you help the industry forward? Can you help the CISO community?” he says. ... Many incident-hardened CISOs will shift their approach and their mindset about experiencing an attack first-hand. “You’ll develop an attack-minded perspective, where you want to understand your attack surface better than your adversary, and apply your resources accordingly to insulate against risk,” says Cory Michel, VP security and IT at AppOmni, who’s been on several incident response teams. In practice, shifting from defense to offence means preparing for different types of incidents, be it platform abuse, exploitation or APTs, and tailoring responses. ... The playbook needs clear guidance on communication, during and after an incident, because this can be overlooked while dealing with the crisis, but in the end, it may come to define the lasting impact of a breach that becomes common knowledge. “Every word matters during a crisis,” says Brown. “Of what you publish, what you say, how you say it. So, it’s very important to be prepared for that.”


The five security principles driving open source security apps at scale

Open-source AI’s ability to act as an innovation catalyst is proven. What is unknown is the downside or the paradox that’s being created with the all-out focus on performance and the ubiquity of platform development and support. At the center of the paradox for every company building with open-source AI is the need to keep it open to fuel innovation, yet gain control over security vulnerabilities and the complexity of compliance. ... Regulatory compliance is becoming more complex and expensive, further fueling the paradox. Startup founders, however, tell VentureBeat that the high costs of compliance can be offset by the data their systems generate. They’re quick to point out that they do not intend to deliver governance, risk, and compliance (GRC) solutions; however, their apps and platforms are meeting the needs of enterprises in this area, especially across Europe. ... “EU AI Act, for example, is starting its enforcement in February, and the pace of enforcement and fines is much higher and aggressive than GDPR. From our perspective, we want to help organizations navigate those frameworks, ensuring they’re aware of the tools available to leverage AI safely and map them to risk levels dictated by the Act.”


What We Wish We Knew About Container Security

Each container maps to a process ID in Linux. The illusion of separation is created using kernel namespaces. These namespaces hide resources like filesystems, network interfaces and process trees. But the kernel remains shared. That shared kernel becomes the attack surface. And in the event of a container escape, that attack surface becomes a liability. Common attack vectors include exploiting filesystem mounts, abusing symbolic links or leveraging misconfigured privileges. These exploits often target the host itself. Once inside the kernel, an attacker can affect other containers or the infrastructure that supports them. This is not just theoretical. Container escapes happen, and when they do, everything on that node becomes suspect. ... Virtual machines fell out of favor because of performance overhead and slow startup times. But many of those drawbacks have since been addressed. Projects leveraging paravirtualization, for example, now offer performance comparable to containers while restoring strong workload isolation. Paravirtualization modifies the guest OS to interact efficiently with the hypervisor. It eliminates the need to emulate hardware, reducing latency and improving resource usage. Several open source projects have explored this space, demonstrating that it’s possible to run containers within lightweight virtual machines. 


The unseen risks of cloud data sharing and how companies can safeguard intellectual property

For many technology-driven sectors, intellectual property lies at their core. This is particular to the fields of software development, pharmaceuticals, and design innovation. For companies in these fields, IP theft can have serious consequences. Unfortunately, cybercriminals increasingly target valuable IP because it can be sold or used to undermine the original creators. According to the Verizon 2025 Data Breach Investigation Report, nearly 97 per cent of these attacks in the Asia-Pacific region are fuelled by social engineering, system intrusion and web app attacks. This alarming trend highlights the urgent need for stronger data protection measures. ... While cloud platforms present unique challenges for securing IP, they also offer some potential solutions. One of the most effective ways to protect data is through encryption. Encrypting files before they are uploaded to the cloud ensures that even if unauthorised access is gained, the data remains unreadable without the proper decryption key. For organisations that rely on cloud platforms for collaboration, file-level encryption is crucial. This form of encryption ensures that sensitive data is protected not just at rest but throughout its entire lifecycle in the cloud. Many cloud platforms offer built-in encryption tools, but companies can also implement third-party solutions to enhance the protection of their intellectual property.


The Critical Role of a Data Pipeline in Security

By implementing a data pipeline and prioritizing the optimization and reduction of data volume before it reaches the SIEM, organizations can stay on budget and still ensure that all necessary data can be thoroughly examined. Data pipelines also lead to tangible reductions in both storage and processing expenses. ... The decrease in the sheer volume of data that the SIEM must handle directly can significantly reduce the total cost of SIEM operations. In addition to volume reduction, data pipelines improve the quality of data delivered to SIEMs and other tools — filtering out repetitive noise and enriching logs for faster queries, increased relevance, and prioritization of the most critical security events. Data pipelines also introduce efficiency by automating the collection, processing, and routing of data. By reducing alert fatigue through intelligent anomaly detection and prioritization, data pipelines can significantly speed up incident resolution times. Beyond immediate threat detection and cost savings, data pipelines also aid in maintaining compliance with privacy regulations like GDPR, CCPA, and PCI. They help provide clear data lineage, making it easier to track the origin and transformations of data. 


Why you need diverse third-party data to deliver trusted AI solutions

Data diversity refers to the variety and representation of different attributes, groups, conditions, or contexts within a dataset. It ensures that the dataset reflects the real-world variability in the population or phenomenon being studied. The diversity of your data helps ensure that the insights, predictions, and decisions derived from it are fair, accurate, and generalizable. ... Before you start your data analysis, it’s important to understand what you want to do with your data. A keen understanding of your use cases and data applications can help identify gaps and hypotheses you need to work to solve. It also gives you a method for seeking the data that fits your specific use case. In the same way, starting with a clear question provides direction, focus, and purpose to the whole process of text data analysis. Without one, you’ll inevitably gather irrelevant data, overlook key variables, or find yourself looking at a dataset that’s irrelevant to what you actually want to know. ... When certain voices, topics, or customer segments are over- or underrepresented in the data, models trained on that data may produce skewed results: misunderstanding user needs, overlooking key issues, or favoring one group over another. This can result in poor customer experiences, ineffective personalization efforts, and biased decision-making.