Remedios Moreno

Remedios Moreno

Cybersecurity Product Manager, Application Security Services at Telefónica Tech

Cybersecurity
PHP2Shell and Node2Shell: how a SOC responds to a critical vulnerability
Recent vulnerabilities affecting PHP and Node.js have once again put organisations' response capabilities to the test. Identifying affected systems, checking the protections available and coordinating remediation are among the tasks that call for specialist teams. Critical vulnerabilities in widely used technologies On 21 October, the vulnerabilities known as PHP2Shell were disclosed. They are linked to flaws in the way PHP processes requests which, under certain conditions, can allow remote code execution. Around the same time, Node2Shell was also disclosed, a vulnerability in the Brotli decompression component used by Node.js and other technologies. Exploitation can result in service failures, information disclosure or code execution, depending on the conditions in the environment. The concern stems from how widely these technologies are used in web applications, corporate portals, digital services and APIs. PHP2Shell also has a particularly noteworthy aspect: Artificial Intelligence played an important role in the research and discovery of the vulnerabilities. It is an example of how these capabilities are accelerating software analysis and changing response times in Cybersecurity. However, the fact that an organisation uses PHP or Node.js does not necessarily mean that its systems are exploitable. The risk depends on the versions installed, their configuration, the components in use and their exposure. ■ When an alert of this severity emerges, it is essential to identify the affected assets and prioritise the response based on their criticality. AI is accelerating vulnerability research and changing response times. How do Operations teams respond to an alert like this? The disclosure of a critical vulnerability triggers a series of analysis and review tasks. One of the first is to examine the available information, cross-check security guidance and assess how the environments covered by managed services may be affected. To do this, specialists can draw on asset inventories, vulnerability analysis tools and security posture management platforms. These capabilities help identify affected versions, insecure configurations and exposed assets, including services or APIs that were not properly recorded in the inventory. At the same time, teams review the available protections and assess how effective they are against known exploitation techniques. Specialist teams analyse attack patterns, assess the severity of alerts and prioritise incidents. For web applications and APIs protected by a WAF, this may involve checking existing signatures, reviewing security policies and considering new rules to block specific malicious requests. Teams also analyse security events to identify exploitation attempts, check which protections are working and detect possible changes in attack behaviour. This monitoring is important because information about a vulnerability evolves during the first few days. New exploitation techniques, additional indicators or updates to existing protections may emerge. ■ Specialists need to interpret these changes and decide whether adjustments are required, while ensuring that new rules do not inadvertently block legitimate users. The analysis also needs to identify services and APIs that are missing from the inventory. The value of a SOC: analysing, prioritising and coordinating the response A critical vulnerability can generate thousands of exploitation attempts in a short period of time. However, receiving a high volume of attack attempts does not necessarily mean that a compromise has occurred. One application may be successfully blocking thousands of malicious requests, while another system with far less activity may show indicators that warrant urgent investigation. The experience of SOC analysts is essential in distinguishing between these situations. By monitoring and correlating events, specialist teams can analyse attack patterns, assess the severity of alerts and prioritise incidents according to their potential impact. In particularly critical situations, teams may also step up monitoring of affected assets and increase the SOC's analysis and response capacity. Specialists in Telefónica's SOC identify affected assets, review protections and coordinate remediation. Managing the situation also requires coordination across different teams. While specialists responsible for protection measures review security policies, application and infrastructure owners need to check affected versions, apply the relevant updates and verify that the vulnerabilities have been remediated. Perimeter security controls can reduce exposure while this work is under way, although their coverage is limited and depends on the vulnerability itself and the inspection capabilities of the technology being used. If there are signs that a system may have been compromised, digital forensics and incident response (DFIR) specialists may become involved to determine how access was gained, what actions the attacker took and the extent of the compromise. Containment measures may also be considered, such as restricting certain communications between systems to make it harder for an attacker to move laterally through the network. ■ Coordination between the SOC, specialist teams and technical owners makes it possible to respond to these situations while taking both security and service continuity into account. The value of the SOC lies in distinguishing between attack attempts and signs of compromise, and in coordinating the response. What we can learn from PHP2Shell and Node2Shell These cases highlight several recommendations for businesses and public administrations. Know your assets and their true exposure. Maintaining an up-to-date inventory, identifying unknown applications and APIs, and regularly assessing vulnerabilities make it easier to determine which systems require priority attention. Apply fixes and verify that they work. Installing the relevant patches remains essential. Where updates require planning, it is worth reviewing which additional measures can temporarily reduce risk and then verifying that the vulnerability has been remediated. Maintain detection and response capabilities. Threats evolve, exploitation techniques change and measures applied initially may need to be adjusted. PHP2Shell and Node2Shell are recent examples of situations that organisations will continue to face. Specialist expertise, continuous review of protections and coordination with system owners help reduce exposure and respond to security incidents more effectively. ■ A managed SOC provides operational continuity, specialist expertise and the ability to coordinate response across different teams and technologies, always within the agreed service scope. Knowing your assets, verifying remediation and maintaining response capabilities are essential to reducing exposure. Cybersecurity AI-Native SecOps: framework for assessing the maturity of an Artificial Intelligence enabled SOC September 21, 2026
November 12, 2026
Cybersecurity
AI & Data
Data leakage and AI: how to reduce risk in the enterprise
Generative Artificial Intelligence has been adopted across businesses much faster than other corporate technologies were in the past. It has not required major implementation projects or months of integration. In many cases, all it has taken is opening a browser. Today, it is common to use AI to summarise a document, review a contract, analyse code, prepare a presentation or search for information. The problem is that this is not always done using tools that the company has assessed and authorised. And sometimes it is not even obvious that AI is being used: it may be embedded in a SaaS application, a browser extension, a development tool or behind an API. This range of uses that fall wholly or partly outside the company's control is what we call shadow AI. And it raises a particularly important question for Cybersecurity teams: what information are we sharing with these systems and what happens to it afterwards? The company needs to know what information it shares with AI and what happens to it afterwards. Data leakage can start with a prompt There is no need to imagine a sophisticated attack. Potential data exposure can begin with something as routine as copying and pasting. A developer enters a few lines of code into an assistant to find an error. Someone in Finance uploads a spreadsheet to generate a summary. A sales professional asks an AI system to improve a proposal before sending it to a customer. These are perfectly understandable actions from the user's point of view. The problem arises when that content also contains credentials, personal data, customer information, proprietary code or internal documentation. From a technical perspective, entering information into an AI system means transferring data so that it can be processed. This may happen directly through a prompt, by attaching a file or by granting access to a corporate repository. From a security perspective, what matters is understanding what data leaves the organisation, where it goes, under what conditions and with what safeguards. ■ In addition, data does not flow in only one direction. An assistant connected to internal documentation may also retrieve information that the user making the query should not be able to access if repository permissions are not properly enforced throughout retrieval and response generation. This becomes particularly important as AI connects to document management systems, code repositories, knowledge bases and other enterprise applications. Security starts with knowing what data we share with AI. Shadow AI extends beyond AI chatbots One common mistake is to reduce shadow AI to the use of unauthorised public chatbots. The reality is much broader. It may involve a personal account being used for a work-related task, but it may also be an AI feature built into an application that the company has already approved. It could be an extension capable of reading the contents of a web page or email, an internal application that accesses a model through an API, or an agent with permission to retrieve information and perform actions in other systems. Public models, enterprise services and models deployed on the company's own infrastructure may also coexist. This means that blocking a list of domains is only of limited effectiveness. Even an approved tool can present very different risk profiles depending on the account being used, its configuration, the connectors enabled, the data it receives or the provider's terms governing the retention and use of that information. ■ The question should therefore not simply be which AI applications are allowed. It is also necessary to consider what they can be used for and what data they can handle. Approving a tool does not mean authorising every possible use. Before applying controls, understand how AI is actually being used It is difficult to protect what you cannot see. An AI security strategy should begin by building a sufficiently accurate picture of how AI is being used across the company. This means more than simply creating an inventory of applications. It is important to understand which users and business areas use them, whether they access them through personal or corporate accounts, whether they upload files, how much information they share and which internal applications are accessing models through APIs. The arrival of agents also raises new questions. Which repositories can they access? What permissions do they have? Can they only retrieve information, or can they also modify it? Can they send an email, create a file or initiate a process? To build this picture, organisations can combine data from browsing activity, network traffic, endpoints, identities and Cloud applications. The aim is to understand actual usage before deciding where controls should be applied. ■ This analysis often reveals something else that matters: some AI tools may already be embedded in teams' day-to-day workflows, even though they have never undergone a formal assessment. It is not enough to know which AI tools are being used: you also need to know who is using them and what information they are sharing. Not all use cases carry the same level of risk Translating into English a text already published on a corporate website does not present the same risk as uploading a customer database, analysing proprietary code or summarising confidential documentation. That is why an effective AI policy needs to take into account both the characteristics of the tool and the context in which it is used. There are technical questions that should be reviewed: where information is processed, how it is encrypted, how long it is retained, what identity and administrative controls the service provides, whether data may be used to improve or train models, and whether the company can disable specific features. Based on those factors, a tool may be authorised for certain types of information, allowed only through enterprise accounts, restricted to specific users or blocked altogether when it does not provide the necessary safeguards. ■ The simpler this policy is for users, the better. When someone is about to paste a document into an assistant, they are not going to consult a twenty-page procedure. The rules need to translate into concrete decisions: which tool can I use, what data can I use with it and for what task? Controls should reflect the AI tool, the data it receives and the task it performs. AI controls need to be applied closer to the data Once actual usage is understood, controls can be applied at different layers. Web and Cloud application security solutions can help identify AI services and control how they are accessed. Depending on the technology used, it may be possible to distinguish between corporate and personal accounts or apply controls to specific actions, such as uploading a file or pasting information into an application. Data protection adds another layer. DSPM helps discover where sensitive data is located, classify it and understand who can access it, while DLP can take action when that information is shared with AI services, ranging from a warning to blocking the action. ■ Applications developed by the company itself introduce another control point: the AI Gateway. Centralising model access through the gateway makes it possible to authenticate applications, control which providers and models may be used, manage quotas and costs, log requests and apply policies to prompts and responses. It also helps avoid a common problem in rapidly expanding environments: the proliferation of access keys across multiple applications and teams. Protecting data also means controlling how it reaches AI. With AI agents, controlling prompts is not enough The shift towards agentic systems changes part of the security problem. A traditional chatbot receives information and returns a response. An agent can go much further: query a database, access a repository, send an email, modify a record or initiate a process. At this point, the issue is no longer only about protecting information, but also about controlling actions. Least privilege, credential separation and traceability become essential. An agent should not automatically inherit all the privileges of the user or application running it. Retrieving information and acting on it should require separate permissions. For certain operations, it will also be necessary to require human approval before an action is executed. Not because every decision made by an agent is necessarily dangerous, but because the impact of an error changes fundamentally when the system stops generating text and starts modifying real systems. ■ Something similar applies to RAG architectures. If an assistant queries corporate documentation, the permissions defined in the original repository should continue to be enforced throughout retrieval and response generation. Otherwise, we may build a technically sound system that ends up showing valid information to the wrong person. Authorising an AI agent to retrieve information does not mean authorising it to modify or send it. Log only what is needed without creating new risks Traceability is necessary for investigating incidents and checking whether policies are working, but indiscriminately storing prompts and responses can create additional copies of sensitive information. Wherever possible, logging should be limited to metadata (user, application, model, date, type of information and action taken), and the content should be appropriately protected when retaining it is unavoidable. Integrating these events with monitoring and response capabilities can also help detect anomalous behaviour or repeated attempts to circumvent controls. Logging everything sent to AI systems and everything they return can create unnecessary copies of sensitive information. From visibility to control The aim is not to slow AI adoption, but to bring it into the enterprise without losing control of information. Blocking all AI tools does not necessarily eliminate shadow AI: it may drive users towards personal accounts, unmanaged devices or less visible services. A more practical approach is to start by identifying which tools are being used and for what purpose, classify them by risk and provide approved corporate alternatives before applying graduated controls. Warnings may be sufficient in some cases, reserving blocking for clear risk scenarios such as sending credentials, regulated information or sensitive documentation to unauthorised services. With the arrival of agents, the question is also no longer limited to what information AI can access, but what actions we allow it to perform. ■ Managing this balance will become an increasingly important part of Cybersecurity strategy: enabling the company to benefit from AI capabilities while keeping information, permissions and actions within known and controlled boundaries. More information → To benefit from AI without losing control of information, organisations need to understand how it is being used and apply controls according to the risk of each use case. Cybersecurity AI & Data Security and compliance in Generative AI applications like ChatGPT and DeepSeek April 15, 2026
November 4, 2026
Cybersecurity
Microsegmentation: the decisive response against attackers’ lateral movement
Security neither begins nor ends at access points. Threats infiltrate, adapt, and move with alarming ease in increasingly distributed, dynamic, and complex technology environments. The adoption of hybrid and multicloud architectures, along with the rise of microservices and containers, has multiplied the internal attack surface, making control and visibility far more difficult. In this scenario, one of the most critical risks is the lateral movement of attackers: their ability to advance silently within the network once they have compromised a vulnerable server, endpoint, or application. Instead of stopping at that initial target, they leverage internal connections and excessive permissions to escalate towards sensitive data, critical applications, or high-value business systems. This dynamic has been a determining factor in ransomware campaigns, industrial espionage, and advanced persistent threats. Lateral movement is an attacker’s silent weapon, and microsegmentation is the line in the sand that stops it. Microsegmentation has become one of the most effective measures to curb this type of threat. It allows organizations to control traffic between workloads, limit the spread of incidents, and contain their impact without compromising operational continuity. ■ At Telefónica Tech, we see this approach as a fundamental pillar for implementing a Zero Trust architecture, where every communication must be verified before it is allowed. Thanks to the combination of granular visibility, adaptive control, and immediate response, microsegmentation not only strengthens resilience but also helps organizations trust their digital capabilities, maintain business continuity, and comply with increasingly demanding regulations such as the DORA regulation or the NIS2 directive. Visibility: the foundation of microsegmentation The first step in protecting a digital environment is to fully understand it. Microsegmentation provides complete and continuous visibility into communications between users, applications, processes, servers, and cloud environments. Through a centralized dashboard, it is possible to build a dynamic map of all interactions within the infrastructure, showing which applications communicate with each other, how data flows to databases, and what external connections exist. This precise picture helps uncover hidden dependencies, unnecessary or misconfigured flows, and potential security gaps. You can’t protect what you can’t see: microsegmentation delivers a full X-ray of internal communications. This visibility is not only a technical advantage but also a key requirement in today’s regulatory landscape. Having clear, verifiable evidence of how internal communications are managed is essential to demonstrate control and governance to auditors and regulators. Granular policies to block unauthorized movement Once the organization has a detailed understanding of its digital ecosystem, microsegmentation enables the definition of highly precise security policies. Instead of relying on static rules based on IP addresses or network perimeters, logical controls are designed and aligned with the function of each application or service. This means that each workload can communicate only with the resources it truly needs to operate. For example, an application server may access its associated database, but not another database or a different backup system. In this way, routes that an attacker could exploit for lateral movement are effectively closed. Policies can be adapted quickly and scaled across hybrid and multicloud environments without redesigning the existing architecture. This makes adoption progressive and minimizes impact on critical operations. With microsegmentation every workload speaks only to what it truly needs, shutting down the paths attackers rely on. Immediate response and regulatory compliance Microsegmentation not only prevents but also improves detection and response capabilities. By maintaining control over every communication flow, any unauthorized access attempt can be identified and blocked in real time. This drastically reduces containment time in the event of an incident and prevents an attack from escalating into a major crisis. In addition, the ability to generate clear, exportable reports facilitates compliance with regulations such as DORA or NIS2, which require organizations to demonstrate operational resilience, incident traceability, and the application of least privilege principles. With microsegmentation, security teams can provide verifiable evidence that risks are being effectively managed. By controlling every communication flow, organizations can block intrusions on the spot and prove resilience to regulators. Use cases for microsegmentation The value of microsegmentation becomes tangible in multiple business scenarios. In the financial sector, for example, banks and insurers rely on core systems that require maximum protection. With microsegmentation, critical applications such as payment engines can be isolated from less sensitive environments, preventing an intrusion in a peripheral system from compromising the business core. Moreover, this granular control helps meet DORA requirements, which demand evidence of operational resilience and risk governance. In the field of digital healthcare, hospitals operate connected medical devices and electronic health record applications, often supported by legacy systems that are difficult to patch. Through microsegmentation, these devices can be isolated and restricted to communicate only with strictly authorized servers, preventing them from becoming entry points for attackers and ensuring the availability of critical medical services. In the manufacturing industry, where industrial control systems (OT) coexist with IT networks, microsegmentation makes it possible to clearly separate the two domains. Thus, an attack on the corporate network cannot spread to the production plant, ensuring the continuity of industrial processes even in the event of a cyber incident. In multicloud environments, microsegmentation provides a unified layer of control over workloads distributed across hyperscalers, or on-premise datacenters. This prevents security inconsistencies between platforms and provides visibility into hidden dependencies between distributed services, optimizing both protection and architecture. In ransomware containment scenarios, microsegmentation is critical. If a server is compromised, the attack is isolated because it cannot spread to other systems or to backups. The impact is drastically reduced, and recovery is much faster. From banking to healthcare and manufacturing, microsegmentation keeps critical environments safe and stops a breach from snowballing into a crisis. Microsegmentation as a strategic investment Beyond its role as a security control, microsegmentation is consolidating as a strategic investment for organizations aiming to strengthen their digital capabilities. It reinforces business continuity, enables agile adaptation to regulatory requirements, and fosters trust in an increasingly distributed and complex environment. Microsegmentation isn’t just a technical safeguard, it’s a strategic investment aligned with Zero Trust and business continuity. This approach naturally aligns with Zero Trust principles, by establishing granular controls that ensure no communication or traffic flow is trusted without prior verification. Its implementation makes it possible to stop lateral movement within the network, block attacks before they escalate, and act proactively against increasingly sophisticated threats such as ransomware. ■ Microsegmentation is not a passing trend but a structural component of infrastructure and application cyber resilience. At Telefónica Tech, we accompany companies on this journey with solutions that turn security into a sustainable competitive advantage and reinforce digital trust in the long term. Learn more → Cyber Security The strategic role of the SOC in enterprise Cyber Security management August 20, 2025 Photo: cookie_studio / Freepik.
September 22, 2025
Cybersecurity
Protection and resilience of applications and infrastructure against cyber threats
Digitalisation has transformed every industry. In the banking and insurance sector, applications enable instant transactions, mobile operations and 24/7 services, but they require robust security to prevent fraud and API attacks. In healthcare, electronic health records and telemedicine systems offer faster patient care but require the protection of highly sensitive data and compliance with strict privacy regulations. In retail and e-commerce, applications have become the face of the business, handling massive traffic peaks that must be managed without downtime, while ensuring the security of customers' payment data. In the public sector, digital transformation is bringing services closer to citizens—but it also exposes critical infrastructure to constant threats. Across all these sectors, applications have become the core of operations. They are a driver of innovation, competitiveness and growth, but also a prime target for attackers seeking to compromise the supply chain, exploit weak configurations or breach underlying infrastructure. Securing them is a strategic necessity. Securing applications and infrastructure is not optional—it's a strategic necessity. Visibility: the starting point One of the biggest challenges in modern security is the lack of real visibility. Many companies and organisations don’t even know how many applications are exposed to the internet, which open-source dependencies contain vulnerabilities, or what network configurations and permissions are active in their cloud environments. This lack of awareness creates blind spots—“shadow IT”—where unmanaged services become open doors for attackers. Visibility is not just about creating an inventory; it also means being able to link assets to their criticality, understand dependencies and assess risk in real time. Without a complete map of the environment, any security strategy ends up being reactive—always one step behind the threat. You can’t protect what you can’t see: visibility is the starting point. Continuous scanning: beyond static snapshots For years, security relied on one-off audits or occasional code reviews. But in today’s dynamic environments, where changes occur hourly, that’s no longer enough. Applications constantly integrate new third-party dependencies, cloud configurations change daily, and new vulnerabilities (CVEs) emerge at a relentless pace. An environment that was secure yesterday could be exploitable tomorrow. This is why the trend today is toward continuous scanning. Static and dynamic analysis tools (SAST/DAST), dependency vulnerability scanners, and infrastructure-as-code (IaC) reviews are being integrated directly into CI/CD pipelines. This allows issues to be detected before deployment—and ensures continued monitoring of what’s already in production. Security stops being a static snapshot and becomes a continuous surveillance flow. What was secure yesterday may be exploitable tomorrow. Hardening: strengthen from the ground up Hardening is the art of reducing the attack surface to a minimum. It’s not about installing more tools, but about properly configuring what already exists. At the application level, this means applying the principle of least privilege, protecting secrets with dedicated managers, encrypting data both in transit and at rest, and disabling any function or port that is not strictly necessary. At the infrastructure level, hardening involves securing operating systems, containers and network services. It means strictly configuring access policies in Kubernetes, segmenting production and development environments, and ensuring that deployed software meets recognised benchmarks such as CIS. Hardening isn’t about installing more—it’s about configuring better. The main challenge here is cultural: in the race to deliver faster, many organisations overlook basic security, leaving gaps that become much more costly to fix later. Runtime security: defending the unexpected Even with good hardening practices and continuous scanning in place, there will always be uncertainty about what happens at runtime. That’s where runtime security comes in: detecting and stopping malicious behaviour in real time, before the impact becomes critical. Runtime security spans multiple technologies: A WAAP (Web Application & API Protection) can block real-time attacks on applications and APIs, mitigating injection attempts, bot abuse or unauthorised access. A CNAPP (Cloud Native Application Protection Platform) combines CSPM, workload protection and compliance capabilities to provide continuous visibility and defence for cloud-native applications. Runtime vulnerability management helps identify which vulnerabilities are actually exploitable in a specific environment and prioritise them based on real-world criticality. Microsegmentation enables granular control over network traffic, preventing attackers from moving laterally between systems. The challenge is not just having these technologies, but integrating them in a way that generates useful and actionable alerts. Security teams can’t handle thousands of false positives—they need contextual intelligence to distinguish noise from real danger. The key isn’t generating more alerts—it’s generating more contextual intelligence. Regulatory compliance: from checklist to continuous practice Regulatory pressure is not uniform: it varies by sector and the type of data each organisation handles. In the financial sector, regulations such as DORA in Europe require digital resilience, incident recovery capabilities and strict third-party governance. Standards like PCI-DSS are essential for protecting cardholder data in banking and retail. In healthcare, regulations like HIPAA in the US or GDPR in Europe focus on the confidentiality and traceability of medical data. The public sector in Spain and the EU must comply with the National Security Framework (ENS) or directives such as NIS2, aimed at securing essential services and critical infrastructure. Compliance is no longer a checklist—it’s a continuous practice. The challenge is not just to pass audits by preparing paperwork and showing reports, but to make compliance a continuous operational practice. This means automating evidence collection, embedding security controls into development and operational processes, and generating real-time reports for auditors and business stakeholders. Compliance is no longer a checklist—it’s a continuous practice. An organisation managing thousands of financial transactions can’t rely on quarterly reviews—it needs live security that can demonstrate compliance with applicable regulations at any time. Only then can compliance become a trust enabler for customers and partners, rather than a burden. DevSecOps culture: security as a shared responsibility No technical solution will succeed without a cultural shift. In many organisations, security is still handled by an isolated team that acts as an auditor at the end of the development cycle. In a world of continuous deployments, this is unworkable—it becomes a bottleneck and stifles innovation. Security is a shared responsibility—not the job of an isolated team. The DevSecOps approach integrates security from the start as a natural part of the software development lifecycle. Developers should have simple tools to identify flaws in their own code, SRE and DevOps teams should have visibility into the infrastructure, and security analysts should act as collaborators—not gatekeepers. The key is to stop seeing security as a blocker and start seeing it as an enabler: the earlier a flaw is detected and fixed, the lower the cost and risk. Conclusion Securing modern applications and infrastructure is no longer about perimeters—it’s about end-to-end resilience. Organisations that want to stay protected must invest in full visibility, continuous scanning, hardening at both application and infrastructure level, real-time protection through advanced technologies, built-in compliance, and a mature DevSecOps culture. In a landscape where cyberattacks are inevitable, the difference between a vulnerable and a resilient organisation lies not in whether it will be attacked, but in its ability to detect, contain and respond in time. ■ Want to learn more about how to protect not only your applications but also the infrastructure that supports them? More information → Cyber Security DevSecOps vs SSDLC: Which is the best secure development strategy? February 25, 2025
September 9, 2025