top of page

Cybersecurity Weekly Update: 2–16 November 2026

Writer: SOC Team
SOC Team
12 minutes ago
7 min read

1. UK NCSC Annual Review 2026 Highlights AI-Driven Cyber Threats and Critical Infrastructure Risks


The United Kingdom's National Cyber Security Centre (NCSC) published its Annual Review 2026: State of the Cyber Nation, reporting 1,831 cyberattack reports and 80 nationally significant incidents over the preceding 12-month period. The review highlighted the growing role of artificial intelligence (AI) in accelerating vulnerability discovery and exploitation, warning that existing security weaknesses are being exposed faster than organisations can adapt their defences.

Alongside the review, the NCSC outlined initiatives to strengthen national cyber defence, including its Cyber Adversary Simulation scheme, which is intended to help critical organisations assess their security through assured providers. The review also emphasised the importance of addressing longstanding security weaknesses, strengthening authentication and improving organisational resilience against increasingly sophisticated cyber threats.

The findings highlight the growing pressure on organisations responsible for critical infrastructure and essential services. AI-assisted attacks could reduce the time between vulnerability discovery and exploitation, increasing the importance of effective vulnerability management, continuous asset discovery and incident response preparedness.


CVE IDs: No specific CVEs were assigned to the developments discussed in the annual review.

Why It Matters: AI is increasing the speed and scale at which attackers can identify and exploit security weaknesses. Organisations operating in defence, financial services, healthcare and critical infrastructure must ensure that internet-facing assets, authentication systems and recovery processes are adequately protected.

Actions: Conduct regular vulnerability assessments and identify internet-facing assets that may be exposed to exploitation. Prioritise critical vulnerabilities and implement phishing-resistant authentication, including passkeys where supported. Test incident response and disaster recovery procedures to ensure that systems and services can be restored following a major cyber incident.


2. Vanderbilt University Disrupted by Cyberattack Claimed by BYOD Ransomware Group


Vanderbilt University confirmed a cybersecurity incident, prompting the institution to instruct students, faculty and staff to shut down university devices and disconnect from campus Wi-Fi while containment activities were initiated. The university worked with external cybersecurity partners and government agencies to investigate the incident and limit further disruption.

The BYOD ransomware group subsequently claimed responsibility for the attack, alleging that it had encrypted university databases, compromised domain controllers and stolen student, employee and research information. The group also claimed to have obtained more than one million Social Security numbers. However, these data-theft and compromise claims had not been independently confirmed by the university during the reporting period.

The incident affected access to university systems and cloud-based services, with the university gradually restoring services. Community-wide password resets were also required as part of the recovery process.

The incident demonstrates how attacks against higher education institutions can affect multiple interconnected systems, including identity infrastructure, research environments and administrative services. Compromising domain controllers could also provide attackers with opportunities to access additional systems and move laterally across an organisation's network.


CVE IDs: No CVE has been assigned to the incident.

Why It Matters: Universities manage large and complex IT environments containing sensitive personal information, research data and interconnected identity systems. A compromise of central authentication infrastructure could disrupt access to multiple services and increase the risk of unauthorised access to sensitive information.

Actions: Review identity and authentication logs for suspicious account activity, privilege escalation and unusual authentication attempts. Verify the integrity of domain controllers and investigate potential lateral movement across the network. Enforce password resets where compromise is suspected, revoke potentially compromised sessions and strengthen MFA enforcement. Ensure that critical systems and research data are protected by isolated and tested backups.


3. TSMC Confirms Employee Data Exposure Through Third-Party Cloud Provider


Taiwan Semiconductor Manufacturing Company (TSMC) confirmed that employee information had appeared online without authorisation after an incident involving systems operated by a third-party cloud service provider. The exposed information reportedly belonged to current and former employees. Threat actors claimed to have obtained approximately 6.9 GB of data containing records associated with around 46,000 individuals, although these figures have not been confirmed by TSMC.

TSMC stated that there was no evidence that its own systems had been compromised and confirmed that the exposed information matched data held by a cloud service provider. The company also clarified that the information was unrelated to its manufacturing operations and customer-related data. TSMC indicated that it was working with the service provider, investigating authorities and external cybersecurity specialists to establish the circumstances surrounding the exposure.

The incident highlights the security risks associated with organisations relying on external providers to process and store sensitive business information. Although TSMC reported no compromise of its core infrastructure, the exposure demonstrates how weaknesses within a supplier's environment can affect an organisation's data security without a direct breach of its primary network.


CVE IDs: No CVE has been assigned to the incident.

Why It Matters: Third-party cloud providers often process sensitive employee, customer and operational information. A security incident affecting a supplier can expose organisational data even when the organisation's own infrastructure remains secure. This creates additional privacy, regulatory and reputational risks.

Actions: Review third-party providers that process or store sensitive organisational information. Verify contractual security requirements, access controls, encryption standards and incident notification procedures. Restrict vendor access to the minimum required permissions and monitor third-party account activity. Organisations potentially affected should establish whether their information was exposed and follow applicable breach notification and credential protection procedures.


4. Maersk Investigates Legacy-System Breach Following Ransomware Extortion Claim


Global shipping and logistics company Maersk launched an investigation into a reported cybersecurity breach involving legacy infrastructure after the WhiteArmor ransomware group claimed responsibility. Maersk confirmed unauthorised access and data extraction from one of its local legacy systems inherited through a previous acquisition. The company stated that the incident appeared to be isolated to the affected system and that it did not anticipate disruption to customer operations.

The WhiteArmor group subsequently claimed that it had stolen approximately 100 GB of logistics-related data and issued an extortion demand. The group reportedly linked the stolen information to a platform associated with LF Logistics, a company acquired by Maersk. However, Maersk had not confirmed the claimed data volume or the group's description of the stolen information.

The incident highlights the risks associated with maintaining older infrastructure within large enterprise environments. Legacy servers and applications can introduce security weaknesses when they are no longer actively maintained, monitored or included in regular vulnerability management programmes. Such systems may also remain connected to business-critical infrastructure despite lacking modern security controls.


CVE IDs: No CVE has been assigned to the incident.

Why It Matters: Logistics companies support global supply chains and depend on interconnected systems to manage transportation, inventory and business operations. Legacy infrastructure that falls outside normal security monitoring can create opportunities for attackers to access sensitive information, disrupt operations and carry out extortion.

Actions: Identify legacy servers, applications and infrastructure that are no longer actively maintained or monitored. Apply available security updates and isolate unsupported systems from critical business networks where possible. Review authentication records, endpoint activity and network traffic for suspicious access or lateral movement. Maintain offline or immutable backups and ensure that recovery procedures account for systems supporting critical logistics operations.


5. Microsoft 365 Outage Disrupts Email and Collaboration Services Worldwide


Microsoft experienced a major Microsoft 365 service outage affecting access to several cloud-based productivity services, including Outlook, Microsoft Teams and Copilot. The disruption affected businesses, government organisations and educational institutions that rely on Microsoft 365 for email, communication and daily operations.

According to Microsoft's service updates, the disruption involved Exchange Online servers unexpectedly failing automated health checks and being removed from service. This placed additional demand on the remaining servers, contributing to further service degradation. Microsoft reported no indication that the incident was caused by malicious activity. Service availability gradually improved, although some users continued experiencing intermittent access issues and delays in email delivery.

The incident highlighted the operational challenges organisations face when essential business services depend on centralised cloud platforms. Organisations relying exclusively on Microsoft 365 for communication may also experience difficulties coordinating incident response activities when email and collaboration services become unavailable.


CVE IDs: No CVE has been assigned. The incident was reported as a service availability disruption rather than a confirmed security vulnerability or cyberattack.

Why It Matters: Microsoft 365 supports essential business functions, including email, collaboration and incident response communications. Service disruptions can delay operational decisions, affect customer communications and prevent security teams from coordinating effectively during an incident.

Actions: Establish alternative communication channels that remain available during cloud service disruptions. Monitor Microsoft 365 Service Health notifications and maintain documented procedures for responding to service outages. Identify business-critical processes that depend on Outlook and Teams, and establish alternative arrangements for urgent communications. Regularly test business continuity and disaster recovery plans to ensure that essential operations can continue when cloud services become unavailable.


Key Recommendations

  1. Prioritise Vulnerability Management: Monitor newly disclosed and actively exploited vulnerabilities, including Microsoft's November security updates. Identify affected assets, prioritise internet-facing systems and verify that security patches have been successfully deployed.

  2. Strengthen Third-Party Security: Review the security posture of cloud providers, suppliers and external service providers. Enforce appropriate access controls, monitor vendor activity and establish clear security and incident notification requirements.

  3. Secure Legacy Infrastructure: Identify unsupported and unmonitored systems across organisational environments. Apply available updates, restrict unnecessary network access and isolate legacy infrastructure from critical business systems.

  4. Improve Identity and Access Security: Enforce MFA and phishing-resistant authentication where supported. Regularly review privileged accounts, investigate suspicious authentication activity and implement appropriate credential reset procedures following suspected compromise.

  5. Strengthen Incident Response and Recovery: Maintain tested incident response procedures and ensure that critical systems have secure, isolated backups. Establish alternative communication channels and rehearse recovery scenarios involving ransomware incidents, third-party breaches and cloud service outages.

  6. Improve Security Monitoring: Monitor endpoint, identity, network and cloud activity for suspicious authentication attempts, privilege escalation, lateral movement and unauthorised data access. Ensure that legacy systems and third-party integrations are included in security monitoring wherever technically possible.

bottom of page