reporter

Christian communities in Pakistan are grappling with shock and grief after the killing of the Rev Kamran Salamat, a Presbyterian pastor who was gunned down outside his home in Gujranwala on 5 December.View the full article

The Rev Canon Chris Palmer, currently serving as Canon Treasurer at Exeter Cathedral, has been appointed the next Dean of Winchester, Downing Street has announced.View the full article

If you work in Pune’s technology sector, you’ve likely experienced some common frustrations. Slow software builds that delay deployments, mysterious bugs that only appear in certain environments, and security concerns about third-party code—these aren’t minor annoyances. They’re real obstacles that impact productivity, quality, and deadlines in Pune’s competitive tech market. The solution to these problems often lies in one tool: Nexus Repository Manager. For tech professionals across Pune—whether you’re working in established IT parks, emerging tech hubs, or innovative startups—understanding Nexus can transform how your team manages software development. Rather than adding complexity, Nexus brings organization and efficiency to processes that often become chaotic, creating a foundation for more reliable and secure software delivery. Understanding Common Development Challenges in Pune Imagine a typical day at a Pune software company. Your team is working on an important application update. Every time a developer commits code, the build process begins. But instead of completing quickly, it slows down as it downloads the same dependencies from various internet sources repeatedly. This happens dozens of times daily, consuming bandwidth and adding unnecessary minutes to each build. At the same time, your team encounters confusing bugs. Different developers might have slightly different versions of the same library. Their code works perfectly in isolation, but when combined, unexpected problems emerge. You then spend valuable time—sometimes days—troubleshooting these “works on my machine” issues instead of building new features. Adding to these challenges, security tools often find vulnerabilities in third-party components your team uses. Without a clear system to track which components are used where, addressing these security concerns becomes difficult and time-consuming. Projects face delays, team morale suffers, and your organization’s ability to deliver quality software is compromised. These problems are common across Pune’s tech industry. The root cause typically relates to poor artifact management—the lack of a systematic approach to organizing, storing, and controlling the building blocks of modern software applications. How Nexus Repository Manager Provides Solutions Nexus Repository Manager addresses these challenges through centralized artifact management. Think of it as creating an organized, internal library for all your software components. Instead of each developer’s computer downloading dependencies separately from the internet, Nexus maintains a single, local copy that everyone can access consistently. The benefits are immediate and significant: Faster Builds: Downloads happen over your local network instead of the internet Fewer Bugs: Everyone uses the same approved versions of dependencies Better Security: Components can be scanned for vulnerabilities before entering your system Cost Savings: Reduced bandwidth usage and more efficient storage Improved Collaboration: Consistent environments mean smoother teamwork For Pune companies in regulated industries like finance, healthcare, or enterprise software, this level of control isn’t just convenient—it’s often essential for compliance and maintaining competitive advantage. Who Benefits from Understanding Nexus in Pune? Different roles in Pune’s tech community experience distinct advantages: Software Developers spend less time troubleshooting environmental issues and more time writing quality code DevOps Engineers use Nexus as a foundation for reliable deployment pipelines System Administrators implement and maintain Nexus as a critical organizational service Team Leaders and Project Managers better understand technical workflows that drive team success Quality Assurance Professionals benefit from more consistent testing environments What Comprehensive Nexus Education Should Include Effective Nexus education follows a logical progression from basic concepts to professional implementation: Foundational Knowledge starts with understanding why artifact management matters in modern software development. You’ll learn about different repository types and how they work together to create efficient systems. Practical Implementation Skills cover installing and configuring Nexus, navigating the interface, managing users and permissions, and creating repositories for various technologies. Advanced Configuration focuses on integrating Nexus with your existing tools, setting up automated cleanup and security scans, and creating seamless workflows. Real-World Problem Solving prepares you for professional challenges, including organizing repositories for larger organizations, monitoring system health, troubleshooting issues, and maintaining Nexus effectively. Choosing the Right Learning Approach While many learning resources exist, their effectiveness varies significantly: Learning AspectSelf-Directed LearningStructured EducationKnowledge CoverageOften incomplete with gapsComprehensive and logicalPractical ApplicationMostly observationalHands-on with guidanceExpert AccessLimited or unavailableDirect access availableCurrent InformationMay be outdatedRegularly updatedProblem-Solving SkillsSpecific solutionsSystematic approachesProfessional PreparationTool familiarityImplementation readiness For Pune professionals balancing work and learning, structured education typically delivers better results than trying to assemble knowledge from scattered sources. The Value of Learning from Experienced Practitioners There’s a significant difference between theoretical understanding and learning from professionals who have implemented solutions in real organizations. When instructors have worked with Nexus in environments similar to Pune’s tech companies, students gain practical insights that go beyond documentation. This practitioner perspective characterizes quality technology education. Programs emphasizing real-world application teach not just what to do, but why—developing the judgment and adaptability needed for real workplace challenges. Developing Skills with DevOpsSchool For comprehensive, practical education in Nexus and related technologies, DevOpsSchool focuses on teaching real-world skills. Their programs are designed by active practitioners, ensuring content remains relevant to current industry needs. DevOpsSchool’s approach benefits Pune tech professionals through: Hands-on Learning: Practical exercises simulating real workplace scenarios Flexible Schedules: Formats that accommodate working professionals Continued Support: Access to communities and updated resources Relevant Curriculum: Content reflecting current employer expectations Implementation Focus: Skills immediately applicable to professional work This educational approach proves valuable across Pune’s diverse technology landscape, from established enterprises to growing startups. Learning from Industry Expert Rajesh Kumar Educational quality depends significantly on instructor expertise. At DevOpsSchool, participants learn from experienced professionals like Rajesh Kumar, whose extensive background brings practical depth to learning. With over two decades of experience in DevOps, cloud technologies, security, and infrastructure management, Rajesh Kumar provides more than technical instruction. He shares insights from implementing solutions across different organizations, helping students understand how to make tools like Nexus work effectively in real professional contexts. Learning from such experienced practitioners provides exposure to proven best practices, awareness of common implementation challenges, and strategies for solutions that deliver real value. This educational model develops the professional judgment and problem-solving skills valuable in Pune’s competitive tech sector. How Nexus Skills Support Career Growth in Pune Pune’s expanding technology sector maintains consistent demand for professionals with relevant, practical skills. Developing expertise in Nexus Repository Manager builds capabilities directly applicable to organizational needs. This proficiency demonstrates to employers your ability to: Improve Development Efficiency through optimized build processes Enhance Security through better dependency management Support Reliable Operations with consistent, maintainable systems Facilitate Team Collaboration through standardized environments Contribute to Cost Management via efficient resource use As organizations recognize the importance of robust DevOps practices and software supply chain security, Nexus skills become increasingly valuable for career advancement. Professionals who can implement and manage these systems effectively position themselves for better opportunities in Pune’s dynamic tech market. Taking the Next Step If challenges related to software management, slow builds, or security concerns affect your work, developing Nexus expertise could provide valuable solutions. The next step is finding an effective approach to building this knowledge. For comprehensive, practical education, consider the structured learning path offered by Nexus Training in Pune. This program combines conceptual understanding with hands-on practice, preparing participants to implement Nexus solutions effectively in professional environments. To explore Nexus skill development opportunities: Website: DevOpsSchool Email: [email protected] Phone/WhatsApp (India): +91 84094 92687 Phone/WhatsApp (USA): +1 (469) 756-6329 View the full article

We are either at the dawn of AI-driven malware that rewrites itself on the fly, or we are seeing vendors and threat actors exaggerate its capabilities. Recent Google and MIT Sloan reports reignited claims of autonomous attacks and polymorphic AI malware capable of evading defenders at machine speed. Headlines spread rapidly across security feeds, trade publications, and underground forums as vendors promoted AI-enhanced defenses. Beneath the noise, the reality is far less dramatic. Yes, attackers are experimenting with LLMs. Yes, AI can aid malware development or produce superficial polymorphism. And yes, CISOs should pay attention. But the narrative that AI automatically produces sophisticated malware or fundamentally breaks defenses is misleading. The gap between AI’s theoretical potential and its practical utility remains large. For security leaders, the key is understanding realistic threats today, exaggerated vendor claims, and the near-future risks that deserve planning. What even is polymorphic malware? Polymorphic malware refers to malicious software that changes its code structure automatically while keeping the same core functionality. Its purpose is to evade signature-based detection by ensuring no two samples are identical at the binary level. The concept is by no means new. Before AI, attackers used encryption, packing, junk code insertion, instruction reordering, and mutation engines to generate millions of variants from a single malware family. Modern endpoint platforms rely more on behavioral analysis than static signatures. In practice, most so-called AI-driven polymorphism amounts to swapping a deterministic mutation engine for a probabilistic one powered by a large language model. In theory, this could introduce more variability. Realistically, though, it offers no clear advantage over existing techniques. Marcus Hutchins, malware analyst and threat intelligence researcher, calls AI polymorphic malware “a really fun novelty research project,” but not something that offers attackers a decisive advantage. He notes that non-AI techniques are predictable, cheap, and reliable, whereas AI-based approaches require local models or third-party API access and can introduce operational risk. Hutchins also pointed to examples like Google’s “Thinking Robot” malware snippet, which queried the Gemini AI engine to generate code to evade antivirus. In reality, the snippet merely prompted AI to produce a small code fragment with no defined function or guarantee of working in an actual malware chain. “It doesn’t specify what the code block should do, or how it’s going to evade an antivirus. It’s just working under the assumption that Gemini just instinctively knows how to evade antiviruses (it doesn’t). There’s also no entropy to ensure the ‘self-modifying’ code differs from previous versions, or any guardrails to ensure it actually works. The function was also commented out and not even in use,” Hutchins wrote in a post deleted from LinkedIn. As the researcher observes, evasion alone is strategically meaningless unless it can reliably support a functioning malicious capability. Mature threat actors value reliability over novelty, and traditional polymorphism already meets that need. What real advances is AI providing for attackers? AI’s true impact today isn’t autonomous malware, but speed, scale, and accessibility when it comes to generating malicious payloads. Think of large language models serving as development assistants: debugging code, translating samples between languages, rewriting and optimizing scripts, and generating boilerplate loaders or stagers. This lowers technical barriers for less experienced actors and shortens iteration cycles for skilled ones. Social engineering has also improved. Phishing campaigns are cleaner, more convincing, and highly scalable. AI rapidly generates region-specific lures, industry-appropriate pretexts, and polished messages, removing the grammatical red flags that defenders once relied on. Business email compromise attacks that already depend on deception rather than technical sophistication particularly benefit from this shift. Generative AI tools can produce superficial variations in malware code by renaming variables or slightly rearranging structures. This occasionally bypasses basic static scanning, but rarely defeats modern behavioral detection, and often introduces instability that is unacceptable for well-resourced criminal operations. For established threat actor groups that require uptime and dependable performance, this unpredictability becomes a disadvantage. The net effect isn’t improved sophistication, but a rise in accessibility: more actors, even inexperienced ones, can now produce “good enough” malware. Earlier this year, a crude ransomware strain appeared in the Visual Studio marketplace as a test extension. John Tuckner of Secure Annex dubbed it “AI slop” ransomware that was poorly written, unstable, and operationally unadvanced. The sample highlighted how easily AI-assisted code can be bundled and distributed, not its ingenuity. “Ransomware has appeared in the VS Marketplace and makes me worry,” Tuckner posted on X. “Clearly created through AI, it makes many mistakes like including decryption tools in extension. If this makes it into the marketplace through [sic], what impact would anything more sophisticated cause?” Inflated AI claims draw industry pushback The gap between marketing-driven AI narratives and practitioner skepticism is clear. A recent Anthropic report claimed a “highly sophisticated AI-led espionage campaign” targeting technology companies and government agencies. While some viewed this as proof that generative AI is embedded in nation-state cyber operations, experts were skeptical. Veteran security researcher Kevin Beaumont criticized the report for lacking operational substance and providing no new indicators of compromise. BBC cyber correspondent Joe Tidy noted that activity likely reflected familiar campaigns, not a new AI-driven threat. Another researcher, Daniel Card emphasized that AI accelerates workflows but does not think, reason, or innovate autonomously. Across these discussions, one pattern remains consistent: AI hype collapses under technical scrutiny. Why AI polymorphic malware hasn’t taken over If AI can accelerate development and generate endless variations of code, why has genuinely effective AI polymorphic malware not become commonplace? The reasons are practical rather than philosophical. Traditional polymorphism works well: Commodity packers and crypters generate huge variant volumes cheaply and predictably. Operators see little benefit in switching to probabilistic AI generation that may break functionality. Behavioral detection reduces benefits: Even if binaries differ, malware must still perform malicious actions (e.g. C2 communication, privilege escalation, credential theft, and lateral movement) which produce telemetry independent of code structure. Modern EDR, NDR, and XDR platforms detect this behavior reliably. AI reliability issues: Large language models hallucinate, misuse libraries, or implement cryptography incorrectly. Code may appear plausible but fail under real-world conditions. As stated earlier, for criminal groups, instability is a serious operational risk. Infrastructure exposure: Local models can leave forensic traces and third-party APIs risk abuse detection and logging. These risks further deter disciplined threat actors. Most successful adversaries may still use AI for support tasks like research, phishing, translation, automation but not completely trust it with generating core payloads for their offensive operations. What CISOs and defenders should watch out for The real danger isn’t underestimating AI but misunderstanding its risk. Autonomous self-rewriting malware isn’t the immediate threat. Instead, attackers operate faster and at greater scale: Automation and propagation. Recurrent malware campaigns like Shai-Hulud illustrate how attackers can use automation to dramatically increase efficiency, blast radius and the extent of disruption, without introducing novel technical logic. (This recurring campaign used automation, not necessarily AI). In later iterations, automated propagation spread the malware rapidly across environments and downstream dependencies, even though the payloads remained identical. This meant defenders could still rely on stable indicators such as hashes, static exfiltration URLs, and YARA rules, but they had far less time to react before impact cascaded across registries, build systems, and developer environments. The risk shift was not smarter malware, but faster, wider execution at machine speed. Rapid variant iterations. Building on the previous point, AI can shorten the time between concept and deployment. Malware families can cycle during a single incident, increasing the value of behavioral detection, memory analysis, and retroactive hunting. Social engineering at scale. AI-generated phishing, pretexting, and tailored messages improve quality and reach. Identity infrastructure (credentials, MFA, access workflows) remains a key attack surface. Defenders should focus on email security, user behavior analytics, and authentication resilience. Volume and noise. More actors can produce “good enough” malware, raising the number of low-quality but operationally usable threats. Automation and prioritization in SOC operations are becoming even more essential to prevent response teams from being overwhelmed with noise and burnout. Vendor skepticism. Marketing claims of AI-specific protection don’t guarantee superior detection. CISOs should demand transparent testing, real-world datasets, validated false-positive rates, and proof that protections promised by “novel” products extend beyond lab conditions. AI is reshaping cybercrime, but not in the cinematic way some vendors suggest. Its impact lies in speed, scale, and accessibility rather than self-modifying malware that breaks existing defenses. Mature threat actors still rely on proven techniques. Polymorphism isn’t new, behavioral detection remains effective, and identity remains the primary entry point for attackers. Today’s “AI malware” is better understood as AI-assisted development rather than autonomous innovation. For CISOs, the key takeaway is a compression of time and effort for attackers. The advantage shifts to those who can automate, iterate faster, and maintain visibility and control. Preparing for this reality means doubling down on behavioral monitoring, identity security, and response automation. Right now, speculative self-aware malware is less of a risk than the real-world efficiency gains AI provides to attackers: faster campaign tempo, greater scale, and a lower barrier to entry for capable abuse. The hype is louder, but the operational impact of that acceleration is where leadership judgment now matters most. View the full article

We are either at the dawn of AI-driven malware that rewrites itself on the fly, or we are seeing vendors and threat actors exaggerate its capabilities. Recent Google and MIT Sloan reports reignited claims of autonomous attacks and polymorphic AI malware capable of evading defenders at machine speed. Headlines spread rapidly across security feeds, trade publications, and underground forums as vendors promoted AI-enhanced defenses. Beneath the noise, the reality is far less dramatic. Yes, attackers are experimenting with LLMs. Yes, AI can aid malware development or produce superficial polymorphism. And yes, CISOs should pay attention. But the narrative that AI automatically produces sophisticated malware or fundamentally breaks defenses is misleading. The gap between AI’s theoretical potential and its practical utility remains large. For security leaders, the key is understanding realistic threats today, exaggerated vendor claims, and the near-future risks that deserve planning. What even is polymorphic malware? Polymorphic malware refers to malicious software that changes its code structure automatically while keeping the same core functionality. Its purpose is to evade signature-based detection by ensuring no two samples are identical at the binary level. The concept is by no means new. Before AI, attackers used encryption, packing, junk code insertion, instruction reordering, and mutation engines to generate millions of variants from a single malware family. Modern endpoint platforms rely more on behavioral analysis than static signatures. In practice, most so-called AI-driven polymorphism amounts to swapping a deterministic mutation engine for a probabilistic one powered by a large language model. In theory, this could introduce more variability. Realistically, though, it offers no clear advantage over existing techniques. Marcus Hutchins, malware analyst and threat intelligence researcher, calls AI polymorphic malware “a really fun novelty research project,” but not something that offers attackers a decisive advantage. He notes that non-AI techniques are predictable, cheap, and reliable, whereas AI-based approaches require local models or third-party API access and can introduce operational risk. Hutchins also pointed to examples like Google’s “Thinking Robot” malware snippet, which queried the Gemini AI engine to generate code to evade antivirus. In reality, the snippet merely prompted AI to produce a small code fragment with no defined function or guarantee of working in an actual malware chain. “It doesn’t specify what the code block should do, or how it’s going to evade an antivirus. It’s just working under the assumption that Gemini just instinctively knows how to evade antiviruses (it doesn’t). There’s also no entropy to ensure the ‘self-modifying’ code differs from previous versions, or any guardrails to ensure it actually works. The function was also commented out and not even in use,” Hutchens wrote in a post deleted from LinkedIn. As the researcher observes, evasion alone is strategically meaningless unless it can reliably support a functioning malicious capability. Mature threat actors value reliability over novelty, and traditional polymorphism already meets that need. What real advances is AI providing for attackers? AI’s true impact today isn’t autonomous malware, but speed, scale, and accessibility when it comes to generating malicious payloads. Think of large language models serving as development assistants: debugging code, translating samples between languages, rewriting and optimizing scripts, and generating boilerplate loaders or stagers. This lowers technical barriers for less experienced actors and shortens iteration cycles for skilled ones. Social engineering has also improved. Phishing campaigns are cleaner, more convincing, and highly scalable. AI rapidly generates region-specific lures, industry-appropriate pretexts, and polished messages, removing the grammatical red flags that defenders once relied on. Business email compromise attacks that already depend on deception rather than technical sophistication particularly benefit from this shift. Generative AI tools can produce superficial variations in malware code by renaming variables or slightly rearranging structures. This occasionally bypasses basic static scanning, but rarely defeats modern behavioral detection, and often introduces instability that is unacceptable for well-resourced criminal operations. For established threat actor groups that require uptime and dependable performance, this unpredictability becomes a disadvantage. The net effect isn’t improved sophistication, but a rise in accessibility: more actors, even inexperienced ones, can now produce “good enough” malware. Earlier this year, a crude ransomware strain appeared in the Visual Studio marketplace as a test extension. John Tuckner of Secure Annex dubbed it “AI slop” ransomware that was poorly written, unstable, and operationally unadvanced. The sample highlighted how easily AI-assisted code can be bundled and distributed, not its ingenuity. “Ransomware has appeared in the VS Marketplace and makes me worry,” Tuckner posted on X. “Clearly created through AI, it makes many mistakes like including decryption tools in extension. If this makes it into the marketplace through [sic], what impact would anything more sophisticated cause?” Inflated AI claims draw industry pushback The gap between marketing-driven AI narratives and practitioner skepticism is clear. A recent Anthropic report claimed a “highly sophisticated AI-led espionage campaign” targeting technology companies and government agencies. While some viewed this as proof that generative AI is embedded in nation-state cyber operations, experts were skeptical. Veteran security researcher Kevin Beaumont criticized the report for lacking operational substance and providing no new indicators of compromise. BBC cyber correspondent Joe Tidy noted that activity likely reflected familiar campaigns, not a new AI-driven threat. Another researcher, Daniel Card emphasized that AI accelerates workflows but does not think, reason, or innovate autonomously. Across these discussions, one pattern remains consistent: AI hype collapses under technical scrutiny. Why AI polymorphic malware hasn’t taken over If AI can accelerate development and generate endless variations of code, why has genuinely effective AI polymorphic malware not become commonplace? The reasons are practical rather than philosophical. Traditional polymorphism works well: Commodity packers and crypters generate huge variant volumes cheaply and predictably. Operators see little benefit in switching to probabilistic AI generation that may break functionality. Behavioral detection reduces benefits: Even if binaries differ, malware must still perform malicious actions (e.g. C2 communication, privilege escalation, credential theft, and lateral movement) which produce telemetry independent of code structure. Modern EDR, NDR, and XDR platforms detect this behavior reliably. AI reliability issues: Large language models hallucinate, misuse libraries, or implement cryptography incorrectly. Code may appear plausible but fail under real-world conditions. As stated earlier, for criminal groups, instability is a serious operational risk. Infrastructure exposure: Local models can leave forensic traces and third-party APIs risk abuse detection and logging. These risks further deter disciplined threat actors. Most successful adversaries may still use AI for support tasks like research, phishing, translation, automation but not completely trust it with generating core payloads for their offensive operations. What CISOs and defenders should watch out for The real danger isn’t underestimating AI but misunderstanding its risk. Autonomous self-rewriting malware isn’t the immediate threat. Instead, attackers operate faster and at greater scale: Automation and propagation. Recurrent malware campaigns like Shai-Hulud illustrate how attackers can use automation to dramatically increase efficiency, blast radius and the extent of disruption, without introducing novel technical logic. (This recurring campaign used automation, not necessarily AI). In later iterations, automated propagation spread the malware rapidly across environments and downstream dependencies, even though the payloads remained identical. This meant defenders could still rely on stable indicators such as hashes, static exfiltration URLs, and YARA rules, but they had far less time to react before impact cascaded across registries, build systems, and developer environments. The risk shift was not smarter malware, but faster, wider execution at machine speed. Rapid variant iterations. Building on the previous point, AI can shorten the time between concept and deployment. Malware families can cycle during a single incident, increasing the value of behavioral detection, memory analysis, and retroactive hunting. Social engineering at scale. AI-generated phishing, pretexting, and tailored messages improve quality and reach. Identity infrastructure (credentials, MFA, access workflows) remains a key attack surface. Defenders should focus on email security, user behavior analytics, and authentication resilience. Volume and noise. More actors can produce “good enough” malware, raising the number of low-quality but operationally usable threats. Automation and prioritization in SOC operations are becoming even more essential to prevent response teams from being overwhelmed with noise and burnout. Vendor skepticism. Marketing claims of AI-specific protection don’t guarantee superior detection. CISOs should demand transparent testing, real-world datasets, validated false-positive rates, and proof that protections promised by “novel” products extend beyond lab conditions. AI is reshaping cybercrime, but not in the cinematic way some vendors suggest. Its impact lies in speed, scale, and accessibility rather than self-modifying malware that breaks existing defenses. Mature threat actors still rely on proven techniques. Polymorphism isn’t new, behavioral detection remains effective, and identity remains the primary entry point for attackers. Today’s “AI malware” is better understood as AI-assisted development rather than autonomous innovation. For CISOs, the key takeaway is a compression of time and effort for attackers. The advantage shifts to those who can automate, iterate faster, and maintain visibility and control. Preparing for this reality means doubling down on behavioral monitoring, identity security, and response automation. Right now, speculative self-aware malware is less of a risk than the real-world efficiency gains AI provides to attackers: faster campaign tempo, greater scale, and a lower barrier to entry for capable abuse. The hype is louder, but the operational impact of that acceleration is where leadership judgment now matters most. View the full article

On Dec. 7, the House and Senate Homeland Security Committees released their compromise version of the 2026 National Defense and Authorization Act (NDAA), a nearly 3,100-page piece of legislation that contains a host of provisions to fund several Department of Defense cybersecurity efforts in fiscal year 2026. Although cybersecurity is referenced hundreds of times across the NDAA, the legislation contains provisions that, once the law becomes effective, will mark significant shifts in how the US military manages major cybersecurity tasks, particularly in the timely arena of protecting mobile communications of top brass and AI deployments, as well as more understated, but potentially high-impact, infosec duties. Although numbers chronically vary widely for NDAA cyber expenses, depending on the source or the year, according to a July budget request from the CFO for the Defense Department, the cyber activities in the NDAA request for FY2026 are approximately $15.1 billion, or 4.1% more than the previous year’s request. This cyber budget bump stands in stark contrast to proposed double-digit cuts for civilian agencies. Around $9.1 billion of that amount goes to pure cybersecurity efforts, with the rest allocated to not clearly defined “cyberspace operations” of US Cyber Command, the Defense Intelligence Agency, the Defense Threat Reduction Agency, the National Security Agency, and the Office of the Under Secretary of Defense, Research and Engineering. Around $611.9 million of the total was allocated to DoD cyber research for the “deployment and modernization of existing capabilities and technologies that advance next generation cybersecurity and cyberspace operations programs.” Securing mobile phones for top officials Few cyber risks are as operationally consequential as insecure mobile communications, and the NDAA directly targets this gap with new mandates for how the Pentagon procures and protects devices for top officials. The bill requires that, no later than 90 days after enactment, the DoD will ensure that each wireless mobile phone and all related telecommunications the department provides to senior military officials or any other employee who performs sensitive national security functions are acquired under contracts or other agreements that require enhanced cybersecurity protections. Under the bill, enhanced cybersecurity protections mean encrypted data, capabilities to mitigate or obfuscate persistent device identifiers, including periodic rotation of network or hardware identifiers to reduce the risk of inappropriate tracking of the activity or location of the wireless mobile phones, and the capability to monitor the wireless mobile phones continuously. Under the legislation, 180 days after the bill’s enactment, the Secretary of Defense must submit to the relevant congressional defense committees a report detailing the mobile telecommunications contracts the Pentagon has entered pursuant to these provisions, how it determined which employees these mobile provisions apply to, and the total costs of wireless mobile phones and telecommunication services involved. It is likely no coincidence that these provisions follow the so-called Signalgate incidents from earlier this year. During those incidents, the current DoD head Pete Hegseth shared over Signal via his private mobile device “nonpublic” information that identified “the quantity and strike times of manned US aircraft over hostile territory over an unapproved, unsecure network approximately two to four hours before the execution of those strikes,” according to a report released on Dec. 2 by the department’s inspector general. AI and machine learning security and procurement requirements Recognizing that AI now underpins everything from battlefield planning to intelligence analysis, the bill introduces sweeping requirements to safeguard these systems from emerging digital threats. The NDAA spells out a spate of policy and procurement practices that the military should meet regarding artificial intelligence and machine learning (ML). First, the DoD, in consultation with other Federal agencies, has 180 days after the date of enactment to develop and implement a department-wide policy for the cybersecurity and associated governance of AI and ML systems and applications, as well as the models for AI and ML used in national defense applications. The policy must protect against security threats to AI and machine learning, including model serialization attacks, model tampering, data leakage, adversarial prompt injection, model extraction, model jailbreaks, and supply chain attacks. It also must employ cybersecurity measures throughout the life cycle of systems using artificial intelligence or machine learning. Moreover, the policy must reflect the adoption of industry-recognized frameworks to guide the development and implementation of AI and ML security best practices. Likewise, it must follow standards for governance, testing, auditing, and monitoring of systems using artificial intelligence and machine learning to ensure the integrity and resilience of such systems against corruption and unauthorized manipulation. Finally, the AI and machine learning policy must accommodate training requirements for the department’s workforce to ensure personnel are prepared to identify and mitigate vulnerabilities specific to AI and ML. The bill further spells out physical and cybersecurity procurement requirements for AI and machine learning systems. It specifies that the defense secretary must develop a framework for the implementation of cybersecurity and physical security standards and best practices relating to AI and ML technologies to mitigate risks to the department from the use of such technologies. The NDAA specifies that the framework must cover all relevant aspects of the security of AI and ML systems, including the risk posed to and by the DoD workforce, including insider threat risks, training and workforce development requirements regarding artificial intelligence security awareness, artificial intelligence-specific threats and vulnerabilities, professional development and education, supply chain threats (including counterfeits), tampering risks, unintended exposure or theft of AI systems or data, security management practices and more. It also requires the framework to draw on existing frameworks, including the NIST Special Publication 800 series and existing DoD frameworks, including the Cybersecurity Maturity Model Certification framework. Finally, under the legislation, the framework must prioritize the most highly capable AI systems that may be of highest interest to cyber threat actors, based on risk assessments and threat reporting, and impose requirements for security on contractors. Other AI provisions under the NDAA require the DoD to revise the mandatory training on cybersecurity for members of the Armed Forces and civilian employees of the department to include content related to the unique cybersecurity challenges posed by artificial intelligence. The bill further says that by April 1, 2026, the DoD needs to establish a task force on AI sandbox environments to identify, coordinate, and advance department-wide efforts to develop and deploy AI sandbox environments necessary to support experimentation, training, familiarization, and development across the military. Other noteworthy cyber-related NDAA provisions Beyond mobile security and AI governance, the NDAA includes a broad array of cyber measures with strategic implications across defense, intelligence, and international partnerships. The following are among the more noteworthy cybersecurity provisions in the compromise bill: Commercial spyware: The bill contains a “sense of Congress” statement that there is a national security need for the legitimate and responsible procurement and application of cyber intrusion capabilities, including efforts related to counterterrorism, counternarcotics, and countertrafficking. It expresses the view that the proliferation of commercial spyware presents significant and growing risks to national security, including to the safety and security of government personnel. It suggests that the US should oppose the misuse of commercial spyware “to target individuals, including journalists, defenders of internationally recognized human rights, and members of civil society groups, members of ethnic or religious minority groups, and others for exercising their internationally recognized human rights and fundamental freedoms, or the family members of these targeted individuals.” It also further stipulates that the US should coordinate with allies and partners to prevent the export of commercial spyware tools to end-users likely to use them for malicious activities, and to share information on this issue with allies robustly. Evaluation of national security risks posed by foreign adversary acquisition of American multiomic data: The bill stipulates that not later than 270 days after its enactment, the director of national intelligence, in consultation with the secretary of defense, the US attorney general the secretary of health and humans services, the secretary of commerce, the secretary of homeland security, the secretary of state, and the national cyber director, shall complete an assessment of risks to national security posed by human multiomic data from US citizens that is collected or stored by a foreign adversary from the provision of biotechnology equipment or services. Multiomic data combines different types of biological data, such as genomics, transcriptomics, proteomics, and metabolomics, to provide a complete picture of a biological system. Biological data for artificial intelligence: The legislation calls for tiered levels of cybersecurity safeguards and access controls for the storage of biological data and contains requirements for the protection of the privacy of individuals. Cybersecurity regulatory harmonization: By June 1, 2026, the DoD must harmonize the cybersecurity requirements applicable to the defense industrial base, reduce the number of such requirements that are unique to a specific contract or other agreement, and submit to the congressional defense committees a report on the actions taken to carry out the harmonization. Cybersecurity and resilience annex in Strategic Rail Corridor Network assessments: The legislation says the defense secretary, in coordination with the transportation secretary and the homeland security secretary, should conduct a periodic evaluation of the Strategic Rail Corridor Network. The assessment must include an annex containing a review of the cybersecurity and the resilience of the physical infrastructure of the Strategic Rail Corridor. The Strategic Rail Corridor is the interconnected network of rail corridors important to national defense and military mobility, as defined by the Department of Defense and the Federal Railroad Administration. Cyber workforce recruitment and retention: The billrequires the defense secretary to fix the rates of basic pay for military employees working on cyber with a pay rate on par with comparable employees elsewhere in the government. Supporting cybersecurity and cyber resilience in the Western Balkans: The NDAA contains a “sense of Congress” statement that the United States support for cybersecurity, cyber resilience, and secure ICT infrastructure in Western Balkans countries will strengthen the region’s ability to defend itself from and respond to malicious cyber activity conducted by nonstate and foreign actors, including foreign governments, that seek to influence the region. Demonstration of real-time monitoring capabilities to enhance weapon system platforms: If funds are available, the secretary of defense, in coordinationwith the undersecretary of defense for acquisition andsustainment and the service acquisition executives, will carry out a demonstration to equip selected weapon systemplatforms with onboard, near real-time, end-to-end serialbus and radio frequency monitoring capabilities to detectcyber threats and improve maintenance efficiency. View the full article

Building software in Mumbai comes with its own set of unique challenges. The fast-paced environment, tight deadlines, and high expectations can make even small technical issues feel overwhelming. If you’ve ever dealt with slow builds that delay your entire team, mysterious bugs that appear out of nowhere, or security alerts that seem impossible to trace, you’re not alone. These problems affect developers, DevOps engineers, and IT managers across the city, from Andheri’s startup hubs to Bandra Kurla Complex’s corporate towers. The good news is there’s a practical solution that addresses these everyday frustrations: Nexus Repository Manager. This tool isn’t another complicated system to learn—it’s actually designed to simplify your workflow. By understanding and implementing Nexus, Mumbai tech professionals can transform how their teams handle software dependencies, making the entire development process smoother, faster, and more secure. The Real-World Problems Mumbai Tech Teams Face Picture this common scenario in a typical Mumbai tech office. Your team is working against a deadline for a new feature launch. Every time someone pushes code, the build process begins. But instead of taking seconds, it drags on for minutes as it downloads the same libraries and dependencies from various internet sources. This happens multiple times a day, wasting both time and valuable bandwidth. At the same time, team members encounter frustrating inconsistencies. One developer has a slightly different version of a crucial library than another. Their individual code works fine, but when combined, it causes unexpected errors. The team then spends hours—sometimes days—tracking down these “works on my machine” problems instead of making progress on their actual project. Meanwhile, security tools flag potential vulnerabilities in third-party components your team is using. But without a clear system to track which projects use which components, addressing these security concerns becomes a guessing game. Delays pile up, frustration grows, and the company’s competitive edge suffers. These issues all stem from one root cause: disorganized management of software components. In Mumbai’s competitive tech landscape, where speed and reliability can make or break a project, this organizational gap creates unnecessary roadblocks that teams simply shouldn’t have to deal with. How Nexus Provides a Straightforward Solution Nexus Repository Manager offers a surprisingly simple approach to these complex problems. Think of it as creating a centralized, organized library for all the software components your team uses. Instead of each developer downloading the same files separately from the internet, Nexus maintains one local copy that everyone can access quickly and consistently. The changes this brings are both immediate and significant. Build times often drop dramatically because downloads happen over your local network rather than the unpredictable internet. Version conflicts disappear because everyone uses the exact same approved versions of libraries and dependencies. Security improves because you can check components before they enter your system, catching potential issues early. Costs decrease as you reduce bandwidth usage and eliminate redundant downloads. For Mumbai companies working in regulated industries like finance, healthcare, or e-commerce, this control isn’t just about efficiency—it’s often about compliance and risk management. Nexus transforms what was once a source of daily frustration into a system that supports your team’s success and your company’s stability. Who Benefits from Understanding Nexus? The value of Nexus extends across different roles within Mumbai’s tech ecosystem: Software Developers spend less time troubleshooting environmental issues and more time writing quality code. They experience fewer interruptions and can focus on what they do best—solving problems and creating features. DevOps Engineers find Nexus provides a reliable foundation for their continuous integration and deployment pipelines. It helps ensure consistency across environments and makes automated processes more predictable and secure. System Administrators gain a critical service to manage that directly supports development teams. They learn to implement Nexus in ways that are secure, scalable, and aligned with organizational needs. Team Leaders and Project Managers better understand the technical workflows that enable their teams to succeed. This knowledge helps them identify bottlenecks, allocate resources effectively, and support their teams with the right tools and processes. Even Quality Assurance Professionals benefit from Nexus because consistent environments mean more reliable testing results and fewer false positives that waste valuable testing time. What Learning Nexus Actually Involves Quality Nexus education breaks down into logical, manageable steps that build your understanding progressively: You start with the fundamentals—understanding why artifact management matters in today’s development world. You’ll learn basic concepts like the different types of repositories and how they work together to create an efficient system. This foundation is crucial for making good decisions later. Then comes practical application—installing and configuring Nexus in various environments. You’ll learn to navigate the interface, set up users with appropriate permissions, and create the repositories your team needs for different technologies like Java, JavaScript, or Docker containers. Next, you explore advanced functionality—connecting Nexus to your existing tools and workflows. This includes setting up automated cleanup, configuring security scans, and integrating with CI/CD systems and build tools so everything works together seamlessly. Finally, you prepare for real-world scenarios—learning best practices for organizing repositories in larger organizations, troubleshooting common problems, and maintaining your Nexus instance for long-term reliability and performance. Why Structured Learning Makes a Difference While you can find bits and pieces of information about Nexus online, structured learning provides a more complete and reliable path to mastery. Random tutorials and YouTube videos often cover specific features without explaining how they fit into the bigger picture. You might learn how to perform a particular task but miss the underlying principles that make Nexus effective. Structured education, on the other hand, builds knowledge systematically. You learn concepts in a logical order, with each new topic building on what came before. You get to ask questions and receive guidance from experienced professionals. Most importantly, quality structured learning includes hands-on practice—you don’t just watch someone else do it, you actually work through exercises that build real skills you can apply immediately in your Mumbai workplace. This approach saves time in the long run and gives you the confidence to implement Nexus solutions effectively rather than just following step-by-step instructions without understanding why. The Advantage of Learning from Experienced Professionals There’s a meaningful difference between learning theoretical concepts and learning from people who have actually solved real problems with the tools they’re teaching. When your instructors have worked with Nexus in environments similar to those in Mumbai—with tight deadlines, complex requirements, and teams that need to collaborate effectively—you gain practical insights that go beyond textbook knowledge. This practical perspective is what makes certain learning platforms stand out. DevOpsSchool focuses on providing education that’s directly applicable to the workplace. Their courses emphasize hands-on skills and real-world scenarios, taught by professionals who understand what Mumbai tech teams actually need. The instructor’s experience particularly matters. Learning from someone with extensive practical experience like Rajesh Kumar means you’re not just learning how Nexus works—you’re learning how to use it effectively in professional contexts. You gain insights into common pitfalls to avoid, strategies for implementing solutions that actually work for teams, and approaches to communicating the value of these tools to different stakeholders within an organization. This kind of education doesn’t just teach you to use a tool—it helps you become more effective in your role and advance in your career. How Nexus Skills Support Career Growth in Mumbai Mumbai’s technology sector rewards professionals who can demonstrate tangible value to their organizations. When you understand and can implement Nexus Repository Manager effectively, you’re showing that you can: Increase team efficiency by reducing build times and eliminating frustrating environmental issues Enhance security by implementing controlled processes for managing software components Reduce costs by optimizing resource usage and minimizing wasted bandwidth Improve software quality through consistent environments and reliable dependency management Support better collaboration by creating systems that work consistently for everyone on the team These are practical benefits that managers and organizations notice. Whether you’re seeking advancement within your current company, exploring opportunities at other Mumbai-based organizations, or looking to expand your consulting capabilities, Nexus expertise represents a valuable skill that’s in demand across the city’s diverse tech landscape. Taking the Next Step If the challenges of dependency management, slow builds, and security concerns are affecting your team’s productivity, learning Nexus could provide meaningful solutions. The next step is finding an effective way to build this knowledge. For comprehensive, practical education focused on real-world application, the Nexus Training in Mumbai program offered by DevOpsSchool provides structured learning designed for working professionals who need skills they can apply immediately. To learn more about course details, schedules, and enrollment options: Website: https://www.devopsschool.com/ Email: [email protected] Phone/WhatsApp (India): +91 84094 92687 Phone/WhatsApp (USA): +1 (469) 756-6329 View the full article

Save up to 87% with a Surfshark coupon code, 3 months of VPN free today, and more December 2025 discounts from WIRED.View the full article

Save up to 77% on 2-year plans and get 3 free months with our NordVPN discount codes.View the full article

Save on top services at LegalZoom, like LLC registration, incorporation, estate plans, and more with coupons and deals from WIRED.View the full article

Whether you’re looking to upgrade your internet or get the latest phone, we’ve got you covered with our selection of AT&T coupons and deals.View the full article

Students can get a Hulu plan for $1.99 per month. Get more details on this and other great deals below.View the full article

Fortinet, Ivanti, and SAP have moved to address critical security flaws in their products that, if successfully exploited, could result in an authentication bypass and code execution. The Fortinet vulnerabilities affect FortiOS, FortiWeb, FortiProxy, and FortiSwitchManager and relate to a case of improper verification of a cryptographic signature. They are tracked as CVE-2025-59718 andView the full article

Gorodenkoff | shutterstock.com Model Context Protocol (MCP) verbindet KI-Agenten mit Datenquellen und erfreut sich im Unternehmensumfeld wachsender Beliebtheit. Allerdings ist auch MCP nicht frei von Sicherheitslücken, wie entsprechende Entdeckungen, etwa beim SaaS-Anbieter Asana oder dem IT-Riesen Atlassian gezeigt haben. Inzwischen hat sich jedoch einiges in Sachen MCP-Sicherheit getan. Einerseits wurden mit Blick auf das Kernprotokoll etliche Fortschritte erzielt. Beispielsweise in Form von Support für OAuth sowie für Authentifizierungs-Server von Drittanbietern und Identity-Management-Systeme. Darüber hinaus wurde inzwischen auch eine offizielle MCP Registry geschaffen, die einen Überblick über sichere, öffentlich verfügbare MCP-Server bietet. Dennoch bestehen weiterhin Sicherheitslücken, die sich für diverse Cyberschandtaten ausnutzen lassen – Prompt Injection, Tool Poisoning, Token-Diebstahl, Server-übergreifende Attacken oder manipulierte Messages sind nur einige von vielen Beispielen. Mit anderen Worten: Unternehmen, die sich beim Aufbau von Agentic-AI-Systemen einen Wettbewerbsvorteil verschaffen wollen, müssen erhebliche Anstrengungen unternehmen, um zu gewährleisten, dass sensible Daten nicht nach außen dringen. Glücklicherweise gibt es diverse Tools, die dabei Unterstützung versprechen. In diesem Artikel lesen Sie: was Security-Tools für MCP leisten sollten, und welche Angebote in diesem Bereich interessant sind. Das sollten MCP-Sicherheitslösungen können Die Gefahr von Datenlecks, Prompt Injections und weiteren Sicherheitsbedrohungen besteht unabhängig davon, ob Unternehmen: ihre eigenen KI-Agenten mit MCP-Servern von Drittanbietern, ihre eigenen MCP-Server mit Drittanbieter-Agenten, oder ihre eigenen Server mit den eigenen Agenten verbinden. Soll heißen: Unternehmen müssen in jedem Fall Autorisierungen und Berechtigungen überprüfen, detaillierte Zugriffskontrollen implementieren und alles protokollieren. Daraus ergeben sich auch die Anforderungen für MCP-Sicherheitslösungen. Diese sollten bieten: MCP-Servererkennung. Für Mitarbeiter eines Unternehmens ist es einfach, MCP-Server herunterzuladen und zu nutzen. Mit Scan-Services für MCP-Server können Unternehmen sämtliche Instanzen von Schatten-MCP-Servern in ihrer Umgebung finden. Laufzeitschutz. KI-Agenten kommunizieren mit MCP-Servern in natürlicher Sprache. MCP-Sicherheits-Tools sollten deshalb in der Lage sein, diese Kommunikation auf Sicherheitsprobleme wie Prompt Injections hin zu überwachen. Authentifizierungs- und Zugriffskontrollen. Das MCP-Protokoll unterstützt inzwischen OAuth, aber das ist nur ein erster Schritt. Für zusätzliche Sicherheit empfehlen sich Tools mit integrierten Kontroll-Frameworks für Zero Trust und Least Privilege. Logging und Observability. Tools und Plattformen sollten zudem die Möglichkeit bieten, MCP-Protokolle zu sammeln, Sicherheitsteams über Richtlinienverstöße zu informieren, Compliance-Daten zu erfassen oder Protokolle in die bestehende Sicherheitsinfrastruktur einzuspeisen. MCP-Security-Angebote Im Folgenden haben wir die Anbieter von MCP-Security-Tools in drei Kategorien aufgeteilt. Diese Aufstellung erhebt keinen Anspruch auf Vollständigkeit. Hyperscaler Für Unternehmen, die sich vollständig auf eine bestimmte Cloud-Plattform verlassen, bieten die MCP-Tools des jeweiligen Hyperscalers einen einfachen Einstieg. Amazon Web Services (AWS) hat Mitte 2025 seine eigene agentenbasierte KI-Plattform eingeführt. Amazon Bedrock AgentCore umfasst ein Gateway, das mehrere Protokolle unterstützt (darunter auch MCP), ein Identity-Management-System sowie Observability. Microsoft bietet einen grundlegenden Azure-MCP-Server an, inklusive Support für Azure Key Vault. Darüber hinaus unterstützen auch Azure AI Foundry Agent Service und Azure API Management das Model Context Protocol. Zudem bietet Microsoft mit dem Agent Framework auch ein Open-Source-Entwicklungskit, das sowohl MCP als auch Agent2Agent unterstützt und beispielsweise Schutz vor Prompt Injections verspricht. Google Cloud kündigte Anfang 2025 seine MCP Toolbox für Datenbanken an – inklusive integrierter Authentifizierung und Observability. Außerdem hat der Hyperscaler auch eine Referenzarchitektur veröffentlicht, um MCP-Server auf seiner Cloud-Plattform abzusichern. Große Plattformanbieter Der IT-Dienstleister Cloudflare hat mit MCP Server Portals ein Tool veröffentlicht, mit dem Unternehmen MCP-Verbindungen zentralisiert absichern und überwachen können. Die Funktion ist Bestandteil der Cloudflare-One-Plattform. Palo Alto Networks hat mit Blick auf MCP-Sicherheit mehrere Eisen im Feuer. Mit Prisma AIRS hat das Unternehmen einen eigenen, intermediären MCP-Server veröffentlicht. Dieser sitzt zwischen den KI-Agenten und dem eigentlichen MCP-Server und erkennt schadhafte Inhalte und Daten. Das Tool MCP Security ist hingegen Bestandteil von Cortex Cloud WAAS und überprüft die MCP-Kommunikation an der Netzwerkgrenze auf bösartige Aktivitäten. SentinelOne gewährt mit seiner Singularity Platform ebenfalls Einblick in die MCP-Interaktionskette und bietet zum Beispiel Warnmeldungen und automatisierte Incident Response für MCP-Server auf lokaler oder Remote-Ebene. Daneben hat auch Broadcom MCP-Sicherheitsfunktionen für VMware Cloud Foundation angekündigt, die künftig mehr Sicherheit für agentenbasierte Workflows gewährleisten sollen. Startups Die Plattform von Acuvity verspricht, MCP-Server umfassend abzusichern. Dafür sorgt laut dem Anbieter eine Kombination aus Least-Privilege-Execution, unveränderlichen Laufzeiten, kontinuierlichen Schwachstellenscans, Authentifizierung und Bedrohungserkennung. Das API-Security-Startup Akto hat eine MCP-Security-Plattform im Angebot. Sie umfasst ein Discovery Tool, um MCP-Server in Unternehmensumgebungen zu identifizieren, Security-Testing-Werkzeuge sowie Monitoring- und Threat-Detection-Funktionen. Invariant Labs bietet mit MCP-Scan ein quelloffenes Tool, das die statische Analyse und Echtzeitüberwachung von MCP-Servern ermöglicht. Mit Guardrails hat das Startup auch ein kommerzielles Produkt im Angebot. Dabei handelt es sich um einen Proxy. Der zwischen KI-Agenten und MCP-Servern sitzt und vor Security-Risiken schützen soll. Das Tool befähigt Anwender außerdem dazu, Richtlinien aufzusetzen. Die AI Security Fabric-Plattform von Javelin addressiert ebenfalls das Thema MCP-Sicherheit. Etwa mit Funktionen wie MCP-Server auf Risiken zu scannen oder Datenanfragen zu überprüfen. Lasso Security stellt ein Open-Source-MCP-Gateway zur Verfügung, das die Konfiguration und das Lebenszyklusmanagement von MCP-Servern ermöglicht und Messages um sensible Informationen bereinigt. (fm) Sie wollen weitere interessante Beiträge rund um das Thema IT-Sicherheit lesen? Unser kostenloser Newsletter liefert Ihnen alles, was Sicherheitsentscheider und -experten wissen sollten, direkt in Ihre Inbox. View the full article

People Images | shutterstock.com Was gut ist, kommt bekanntlich wieder. So auch das Experten-Netzwerk von CSO Deutschland, Computerwoche und CIO.de. Selbst wenn Sie davon noch nie zuvor etwas gehört haben: Vertrauen Sie uns, dieses Comeback ist eine gute Sache! Personal Brand als Experte ausbauen Denn das deutschsprachige Experten-Netzwerk von Foundry ermöglicht Ihnen als IT- oder Business-Entscheider, Fachexperte oder auch Wissenschaftler ab sofort, sich mit eigenen Fach- oder auch Meinungsbeiträgen (mehr) Sichtbarkeit im B2B-Umfeld zu verschaffen. Und diese ist (potenziell) nicht nur auf den deutschen Sprachraum beschränkt. Egal ob Sie Ihrem VMware- oder SAP-Ärger Luft verschaffen, eine eigene Perspektive auf die europäischen Bestrebungen zur digitalen Unabhängigkeit werfen, oder die besten Management- und Security-Ansätze für Multi-Agenten-Teams mit ihren Peers teilen möchten – als Mitglied des Experten-Netzwerks stehen Ihnen unsere B2B-Plattformen zu diesem Zweck offen (nach vorheriger Themenabstimmung 😊). Und damit nicht genug: Experten bieten sich etliche weitere Optionen, um ihre Personal Brand mit Hilfe unserer Markenwelt auf verschiedenen Ebenen zu stärken. Interessiert? Dann bewerben Sie sich jetzt direkt für das Experten-Netzwerk von CSO Deutschland, Computerwoche und CIO.de. Alle weiteren Infos finden Sie hier. View the full article

Gorodenkoff | shutterstock.com Model Context Protocol (MCP) verbindet KI-Agenten mit Datenquellen und erfreut sich im Unternehmensumfeld wachsender Beliebtheit. Allerdings ist auch MCP nicht frei von Sicherheitslücken, wie entsprechende Entdeckungen, etwa beim SaaS-Anbieter Asana oder dem IT-Riesen Atlassian gezeigt haben. Inzwischen hat sich jedoch einiges in Sachen MCP-Sicherheit getan. Einerseits wurden mit Blick auf das Kernprotokoll etliche Fortschritte erzielt. Beispielsweise in Form von Support für OAuth sowie für Authentifizierungs-Server von Drittanbietern und Identity-Management-Systeme. Darüber hinaus wurde inzwischen auch eine offizielle MCP Registry geschaffen, die einen Überblick über sichere, öffentlich verfügbare MCP-Server bietet. Dennoch bestehen weiterhin Sicherheitslücken, die sich für diverse Cyberschandtaten ausnutzen lassen – Prompt Injection, Tool Poisoning, Token-Diebstahl, Server-übergreifende Attacken oder manipulierte Messages sind nur einige von vielen Beispielen. Mit anderen Worten: Unternehmen, die sich beim Aufbau von Agentic-AI-Systemen einen Wettbewerbsvorteil verschaffen wollen, müssen erhebliche Anstrengungen unternehmen, um zu gewährleisten, dass sensible Daten nicht nach außen dringen. Glücklicherweise gibt es diverse Tools, die dabei Unterstützung versprechen. In diesem Artikel lesen Sie: was Security-Tools für MCP leisten sollten, und welche Angebote in diesem Bereich interessant sind. Das sollten MCP-Sicherheitslösungen können Die Gefahr von Datenlecks, Prompt Injections und weiteren Sicherheitsbedrohungen besteht unabhängig davon, ob Unternehmen: ihre eigenen KI-Agenten mit MCP-Servern von Drittanbietern, ihre eigenen MCP-Server mit Drittanbieter-Agenten, oder ihre eigenen Server mit den eigenen Agenten verbinden. Soll heißen: Unternehmen müssen in jedem Fall Autorisierungen und Berechtigungen überprüfen, detaillierte Zugriffskontrollen implementieren und alles protokollieren. Daraus ergeben sich auch die Anforderungen für MCP-Sicherheitslösungen. Diese sollten bieten: MCP-Servererkennung. Für Mitarbeiter eines Unternehmens ist es einfach, MCP-Server herunterzuladen und zu nutzen. Mit Scan-Services für MCP-Server können Unternehmen sämtliche Instanzen von Schatten-MCP-Servern in ihrer Umgebung finden. Laufzeitschutz. KI-Agenten kommunizieren mit MCP-Servern in natürlicher Sprache. MCP-Sicherheits-Tools sollten deshalb in der Lage sein, diese Kommunikation auf Sicherheitsprobleme wie Prompt Injections hin zu überwachen. Authentifizierungs- und Zugriffskontrollen. Das MCP-Protokoll unterstützt inzwischen OAuth, aber das ist nur ein erster Schritt. Für zusätzliche Sicherheit empfehlen sich Tools mit integrierten Kontroll-Frameworks für Zero Trust und Least Privilege. Logging und Observability. Tools und Plattformen sollten zudem die Möglichkeit bieten, MCP-Protokolle zu sammeln, Sicherheitsteams über Richtlinienverstöße zu informieren, Compliance-Daten zu erfassen oder Protokolle in die bestehende Sicherheitsinfrastruktur einzuspeisen. MCP-Security-Angebote Im Folgenden haben wir die Anbieter von MCP-Security-Tools in drei Kategorien aufgeteilt. Diese Aufstellung erhebt keinen Anspruch auf Vollständigkeit. Hyperscaler Für Unternehmen, die sich vollständig auf eine bestimmte Cloud-Plattform verlassen, bieten die MCP-Tools des jeweiligen Hyperscalers einen einfachen Einstieg. Amazon Web Services (AWS) hat Mitte 2025 seine eigene agentenbasierte KI-Plattform eingeführt. Amazon Bedrock AgentCore umfasst ein Gateway, das mehrere Protokolle unterstützt (darunter auch MCP), ein Identity-Management-System sowie Observability. Microsoft bietet einen grundlegenden Azure-MCP-Server an, inklusive Support für Azure Key Vault. Darüber hinaus unterstützen auch Azure AI Foundry Agent Service und Azure API Management das Model Context Protocol. Zudem bietet Microsoft mit dem Agent Framework auch ein Open-Source-Entwicklungskit, das sowohl MCP als auch Agent2Agent unterstützt und beispielsweise Schutz vor Prompt Injections verspricht. Google Cloud kündigte Anfang 2025 seine MCP Toolbox für Datenbanken an – inklusive integrierter Authentifizierung und Observability. Außerdem hat der Hyperscaler auch eine Referenzarchitektur veröffentlicht, um MCP-Server auf seiner Cloud-Plattform abzusichern. Große Plattformanbieter Der IT-Dienstleister Cloudflare hat mit MCP Server Portals ein Tool veröffentlicht, mit dem Unternehmen MCP-Verbindungen zentralisiert absichern und überwachen können. Die Funktion ist Bestandteil der Cloudflare-One-Plattform. Palo Alto Networks hat mit Blick auf MCP-Sicherheit mehrere Eisen im Feuer. Mit Prisma AIRS hat das Unternehmen einen eigenen, intermediären MCP-Server veröffentlicht. Dieser sitzt zwischen den KI-Agenten und dem eigentlichen MCP-Server und erkennt schadhafte Inhalte und Daten. Das Tool MCP Security ist hingegen Bestandteil von Cortex Cloud WAAS und überprüft die MCP-Kommunikation an der Netzwerkgrenze auf bösartige Aktivitäten. SentinelOne gewährt mit seiner Singularity Platform ebenfalls Einblick in die MCP-Interaktionskette und bietet zum Beispiel Warnmeldungen und automatisierte Incident Response für MCP-Server auf lokaler oder Remote-Ebene. Daneben hat auch Broadcom MCP-Sicherheitsfunktionen für VMware Cloud Foundation angekündigt, die künftig mehr Sicherheit für agentenbasierte Workflows gewährleisten sollen. Startups Die Plattform von Acuvity verspricht, MCP-Server umfassend abzusichern. Dafür sorgt laut dem Anbieter eine Kombination aus Least-Privilege-Execution, unveränderlichen Laufzeiten, kontinuierlichen Schwachstellenscans, Authentifizierung und Bedrohungserkennung. Das API-Security-Startup Akto hat eine MCP-Security-Plattform im Angebot. Sie umfasst ein Discovery Tool, um MCP-Server in Unternehmensumgebungen zu identifizieren, Security-Testing-Werkzeuge sowie Monitoring- und Threat-Detection-Funktionen. Invariant Labs bietet mit MCP-Scan ein quelloffenes Tool, das die statische Analyse und Echtzeitüberwachung von MCP-Servern ermöglicht. Mit Guardrails hat das Startup auch ein kommerzielles Produkt im Angebot. Dabei handelt es sich um einen Proxy. Der zwischen KI-Agenten und MCP-Servern sitzt und vor Security-Risiken schützen soll. Das Tool befähigt Anwender außerdem dazu, Richtlinien aufzusetzen. Die AI Security Fabric-Plattform von Javelin addressiert ebenfalls das Thema MCP-Sicherheit. Etwa mit Funktionen wie MCP-Server auf Risiken zu scannen oder Datenanfragen zu überprüfen. Lasso Security stellt ein Open-Source-MCP-Gateway zur Verfügung, das die Konfiguration und das Lebenszyklusmanagement von MCP-Servern ermöglicht und Messages um sensible Informationen bereinigt. (fm) Sie wollen weitere interessante Beiträge rund um das Thema IT-Sicherheit lesen? Unser kostenloser Newsletter liefert Ihnen alles, was Sicherheitsentscheider und -experten wissen sollten, direkt in Ihre Inbox. View the full article

Here are the answers for The New York Times Mini Crossword for Dec. 10.View the full article

Many enterprises use GitHub Action Secrets to store and protect sensitive information such as credentials, API keys, and tokens used in CI/CD workflows. These private repositories are widely assumed to be safe and locked down. But attackers are now exploiting that blind trust, according to new research from the Wiz Customer Incident Response Team. They found that threat actors are using exposed GitHub Personal Access Tokens (PATs) to access GitHub Action Secrets and sneak into cloud environments, then run amok. “The root cause issue is the presence of these secrets in repos,” said David Shipley of Beauceron Security. “Cloud service provider access keys are gold, they can be extraordinarily long lived, and that’s what [attackers are] sniffing around for.” GitHub Action Secrets aren’t secrets anymore Wiz estimates that 73% of organizations using private GitHub Action Secrets repositories store cloud service provider (CSP) credentials within them. When PATs, which allow developers and automation bots to interact with GitHub repositories and workflows, are exploited, attackers can easily move laterally to CSP control planes. PATs can become a “powerful springboard” that allows attackers to impersonate developers and carry out a range of activities, explained Erik Avakian, technical counselor at Info-Tech Research Group. It’s like having a backstage pass into a company’s cloud environments, he said. “Once they’re holding that valid PAT, they can do all sorts of things in GitHub that lead directly back into a company’s AWS, Azure, GCP, or other types of cloud services, because GitHub treats that PAT like the real developer,” he said. With that access, threat actors can “poke around” various repositories and workflows and look for anything that hints at cloud access, configuration items, scripts, and hidden secrets, he noted. If they get access to real cloud credentials, they “have the keys to the company’s AWS bucket, Azure subscriptions, and other workflows.” They can then spin up cloud resources, access databases, steal source code, install malicious files such as crypto miners, sneak in malicious workflows, or even pivot to other cloud services, while setting up persistence mechanisms so they can return whenever they want. “At that point, basically anything you can do in the cloud, so can they,” said Avakian. Easily evading detection Wiz found that a threat actor with basic read permissions via a PAT can use GitHub’s API code search to discover secret names embedded directly in a workflow’s yaml code, accessed via “${{ secrets.SECRET_NAME }}.” The danger is that this secret discovery method is difficult to monitor because search API calls are not logged. Further, GitHub-hosted Actions run from GitHub-managed resources that use legitimate, shared IP addresses not flagged as malicious. Attackers can abuse secrets, impersonate workflow origins to exploit trust, and potentially access other resources if code is misconfigured or reused elsewhere in the workflows. They can also persistently access the system. In addition, if the exploited PAT has write permissions, attackers can execute malicious code and remove workflow logs and runs, pull requests, and ‘created branches’ (isolated copies of codebases for dev experimentation). Because workflow logs are rarely streamed into security incident and event management (SIEM) platforms, attackers can easily evade detection. Also, notably, a developer’s PAT with access to a GitHub organization makes private repositories vulnerable; Wiz research found that 45% of organizations have plain-text cloud keys stored privately, while only 8% are in public repositories. Shipley noted: “In some developers’ minds, a private repo equals safe, but it’s clearly not safe.” How enterprise leaders can respond To protect themselves against these threats, enterprises should treat PATs as they would any other privileged credentials, Avakian noted. Cloud infrastructure and cloud development environments should be properly locked down, essentially “zero trustifying” them through micro segmentation and privileged user management to contain them and prevent lateral pivoting. “Like any other credentials, tokens are best secured when they have reasonable expiration dates,” said Avakian. “Making tokens expire, rotating them, and using short-lived credentials will help thwart these types of risks.” Least privilege everything and give accounts only the rights they need, rather than an ‘admin everything’ approach, Avakian advised. More importantly, move cloud secrets out of GitHub workflows and ensure that the proper amount of monitoring and log review processes are in place to flag surprise or unexpected workflow or cloud creation events. Beauceron’s Shipley agreed, saying that enterprises need a multi-pronged strategy, good monitoring, instant response plans, and developer training processes that are reinforced with “meaningful consequences” for non-compliance. Developers must be motivated to follow secure coding best practices; building a strong security culture in developer teams is huge. “You can’t buy a blinky box for that part of the problem,” he said. “Criminals have stepped up their game,” said Shipley. “Organizations don’t have a choice. They have to invest in these areas, or they will pay.” Also, stop blindly trusting GitHub repos, he added. “The nature of repos is that they live forever. If you don’t know if you have cloud secrets inside your repos, you need to go and find them. If they’re there, you need to change them yesterday, and you need to stop adding new ones.” If there is an upside, he noted, it’s that enterprises are “victims of their own success” as they’ve raised the bar with multi-factor authentication (MFA). Gains in general security awareness makes it more difficult for criminals to obtain access and identities and compromise systems. “In some ways, this is a good sign,” said Shipley. “In a hilarious kind of way, it means [the criminals] are now moving into deeper levels requiring more effort.” This article originally appeared on InfoWorld. View the full article

Sam Altman’s appearance on The Tonight Show is part of a larger charm offensive currently being waged by the tech establishment.View the full article

Microsoft is finishing 2025 by issuing only 57 patches for Windows and other products for December Patch Tuesday, but one vulnerability is already being exploited as a zero day and needs to be addressed fast. It’s an escalation of privilege vulnerability in Windows Cloud Files Mini Filter Driver (CVE-2025-62221), described as a use-after-free problem in which a program tries to use a block of memory that has already been returned to system control. The attack complexity is low. The worst case scenario is that a threat actor could leverage it to escalate access privileges. “Elevation of privilege bugs turn a foothold into a full breach,” Satnam Narang, senior staff research engineer at Tenable, said in an email, “as attackers often use them to conduct post-compromise activity after they have gained initial access through other means, such as social engineering or exploitation of another flaw. “Windows Cloud Files Mini Filter Driver is an attractive target because it is a file system driver that enables cloud applications to access file system functionalities,” he added. Jack Bicer, director of vulnerability research at Action1, said patching this vulnerability is “the most urgent concern” because it is actively being exploited by any attacker who can get any level of local access. “Active exploitation means real incidents are already occurring,” he pointed out. “This vulnerability is likely to be combined with phishing, browser-based attacks, malicious documents, or other initial footholds to achieve full system takeover. The attack potential includes disabling security tooling, accessing sensitive information, moving laterally across the organization’s network, and establishing persistent high-privilege access. Because the impacted driver is widely deployed across enterprise environments, the exposure is broad and the potential operational consequences significant.” IT executives should ensure operational teams allocate resources to accelerated patching, enforce least-privilege access controls, and strengthen monitoring for anomalous activity across systems that cannot be patched immediately, he stressed. “A focused, time-bound remediation plan, beginning with actively exploited and RCE vulnerabilities, will provide the greatest reduction in organizational risk and the strongest defense against potential widespread compromise,” he said. Unfortunately, said Kevin Breen, senior director of cyber threat research at Immersive, Microsoft has not provided any details on how this exploit is being abused or provided any indicators of compromise, making it harder for defenders to start proactive threat hunting. Holes in Exchange Server Michael Walters, president of Action1, drew attention to two vulnerabilities in Microsoft Exchange Server: CVE-2025-64666, an escalation of privilege (EoP) hole allowed by improper input validation; CVE-2025-64667, which allows a threat actor to spoof over a network. While rated Important and assessed as exploitation Less/Unlikely, Walters notes that these flaws affect core messaging and identity surfaces, and can become critical when chained, such as by spoofing enabling phishing, or EoP facilitating mailbox theft. Tyler Reguly, associate director of R&D at Fortra, said CSOs should assign priority to two other vulnerabilities that Microsoft rated as critical this month. CVE-2025-62557, a use after free vulnerability in Microsoft Office that allows an unauthorized attacker to execute code locally; CVE-2025-62554, described as an access of resource using incompatible type (‘type confusion’) hole in Microsoft Office that allows an unauthorized attacker to execute code locally. Because these list the Outlook Preview Pane as an attack vector, they worry Reguly. “I always find that one of the scariest attack vectors that can be listed,” he said. “Vulnerabilities that don’t rely on user interaction are vulnerabilities that we want to pay attention to.” Copilot hole for those using JetBrains Breen of Immersive also said organizations using GitHub Copilot for the JetBrains application development platform should patch a hole in Copilot promptly, before threat actors find a way to exploit it. The vulnerability report states that it’s possible to gain the ability for code execution on affected hosts by tricking the LLM into running commands that bypass the guardrails and appending instructions to the user’s “auto-approve” settings, Breen notes. This can be achieved through a Cross Prompt Injection, he said, where the prompt is modified, not by the user, but by the LLM agents as they craft their own prompts based on the content of files or data retrieved from a Model Context Protocol (MCP) server. Although Microsoft has marked this exploitation as Less Likely, Breen said, CSOs taking a risk-based approach should note that developers typically have access to API keys and secrets that could enable a large attack surface for attackers. SAP vulnerabilities Separately, SAP’s Security Notes for December include four HotNews Notes, two of which are given CVSS scores in the 9s: note #3685270 [CVE-2025-42880] patches a code injection vulnerability in SAP Solution Manager. According to researchers at Onapsis, a remote-enabled function module could allow an authenticated attacker to inject arbitrary code, leading to a high impact on the confidentiality, integrity, and availability of the system. The vulnerability is patched by adding appropriate input sanitization to the affected function module. Given the central role of SAP Solution Manager in the SAP system landscape, Onapsis strongly recommends that this be patched quickly; note #3685286, [CVE-2025-42928], was issued after Onapsis was able to exploit a deserialization vulnerability in the SAP jConnect SDK for Sybase Adaptive Server Enterprise (ASE) to launch remote code execution by providing specially crafted input to the component. “A successful exploit requires high privileges, preventing the vulnerability from being tagged with a CVSS score of 10.0,” Onapsis said; note #3683579 affects SAP Commerce Cloud customers. SAP Commerce Cloud uses a version of Apache Tomcat that is vulnerable to CVE-2025-55754 and CVE-2025-55752. This security note, with a CVSS score of 9.6, provides fixes that include a patched version of Apache Tomcat. If unpatched, these flaws put the application’s confidentiality, integrity and availability at high risk, says Onapsis. note #3668705, tagged with a CVSS score of 9.9, was initially released on SAP’s November Patch Day and patches a Code Injection vulnerability in SAP Solution Manager. This note was updated with additional correction instructions. Advice for 2026 Finally, with this last batch of patches for the year from Microsoft, Fortra’s Tyler Reguly provided some context. “In 2025, Microsoft patched 1275 vulnerabilities,” he said in an email. “Which should mean roughly 106 vulnerabilities each month, yet December only saw 70 vulnerabilities when you include the third-party CNA vulnerabilities. If all things were equal, December should account for 8.3 % of all CVEs fixed by Microsoft. Instead December only contains 5.5% of this year’s total CVEs. I suppose we can thank Microsoft for an early Christmas gift.” “If I were in charge of all aspects of security for an enterprise, as we wrap up the year and think about 2026 budgets,” he added, “I’d probably be thinking about the two critical Office vulnerabilities that impact the Preview Pane and consider the email protections that I have in place and where I can make investments in 2026 to further improve the email security of my organization. Between ‘silent attacks’ that utilize the preview pane, phishing, and all the other risks that come to us via email, it is one of the places where organizations can still do more to shore up their security posture and put themselves in a good place.” View the full article

Keep your home secure during your holiday trips with the best cameras, tested by CNET's experts -- now on sale for the holidays.View the full article

The ad-supported option disappears Dec. 31, meaning you'll need a paid plan to keep watching.View the full article

The CEO of the AI data center provider, which has Nvidia as an investor and a supplier, described the environment as a "violent change" in demand.View the full article

Pebble today announced the Pebble Index 01, a simple smart ring that's designed for recording information. It is equipped with a microphone and a button to start a recording, but little else. Priced at $75, the Index 01 does not require an internet connection or a subscription, and it doesn't record unless the button is pressed. Recordings are sent to a connected smartphone, and can be saved as a note, added to a calendar, or set as a reminder. Information is processed by open source speech-to-text and AI models locally on an iPhone or Android smartphone. It is customizable, and single or double button clicks can be set to control different actions like switching to a new song, taking a photo, or activating smart home devices. The device is made from stainless steel, and it is available in three colors, including silver, gold, and black. Sizes range from 6 to 13. It is resistant to water, and no charging is necessary. Pebble says the battery will last for 12 to 15 hours of recording, which equates to 10-20 recordings per day that are 3-6 seconds in length. Since there is no replaceable battery and no option to charge, the ring is meant to be recycled when the battery dies. The Pebble Index 01 is priced at $75 and is available for pre-order from the Pebble website. It will ship in March 2026, and after that, the price will increase to $99.Tag: Pebble This article, "Pebble Unveils $75 iPhone-Compatible Smart Ring for Quick Voice Recordings" first appeared on MacRumors.com Discuss this article in our forums View the full article

Led by Naveen Rao, the former head of AI at Databricks, the new hardware startup is valued at $4.5 billion.View the full article