SEC595: Applied Data Science and AI/Machine Learning for Cybersecurity Professionals


Experience SANS training through course previews.
Learn MoreLet us help.
Contact usBecome a member for instant access to our free resources.
Sign UpWe're here to help.
Contact UsLate last week, Anthropic began rolling out Claude Code Security to a limited group of enterprise and team customers. The new feature can scan software codebases, detect vulnerabilities, and suggest fixes. The announcement appears to have caused concern among investors; some cybersecurity stocks fell several points on Friday. As described by Anthropic, Claude Code Security "scans codebases for security vulnerabilities and suggests targeted software patches for human review." Users can join a waitlist for access to Claude Code Security. Scope of use terms require that users "will only use Claude Code Security to scan code that [their] company owns and to which [their] company holds all necessary rights to scan." They are prohibited from using "Claude Code Security to scan code owned by or licensed from third parties, including but not limited to open source projects or repositories other than those included in [their] company's codebase(s)."

This is really exciting. AI tools like Claude Code are fully capable of ingesting large volumes of source code and analyzing it to generate new code/modules, so this seems like a natural extension to that capability. Beyond scanning only the code in scope, ensure that developers are using corporate instances rather than training personal repositories on corporate software deficiencies. Have your developers show you the controls they have on software projects as well as the approval process for implementing suggested fixes. Yes, fixes are only implemented with human approval, and you want to not only verify that but also understand how the fixes are assessed/tested.
Seems like just another tool in the cybersecurity toolbox. They also include the terms of use clause to protect against nefarious use [said cheekily]. It’s doing what AI does reasonably well: automating repetitive tasks. And there is still the human review loop… for now. One does wonder, though, if it would have caught the CrowdStrike boo-boo before the inadvertent coding error caused travel mischief for days.
Help Net Security
CyberScoop
The Register
Silicon Angle
Anthropic
"It’s like an AI-powered assembly line for cybercrime, helping less skilled workers produce at scale." Amazon Threat Intelligence has observed attacks leveraging commercial generative AI services to breach more than 600 FortiGate firewalls worldwide between January 11 and February 18, 2026. The campaign was "consistent with pre-ransomware operations" and relied on AI to scale up attacks "exploiting exposed management ports and weak credentials with single-factor authentication" rather than targeting FortiGate vulnerabilities. Amazon believes the threat actor to be opportunistic, financially motivated, unaffiliated with known threat groups, and low in technical skill, focusing on a high volume of well-known attack techniques and simply moving on from any targets with hardened defenses. Operational security failures revealed the threat actor's publicly accessible infrastructure containing "AI-generated attack plans, victim configurations, and source code for custom tooling" bearing idiosyncrasies and limitations of AI-generated code. The threat actor's initial access tools scanned for internet-exposed FortiGate management interfaces and attempted authentication with commonly reused credentials, seeking configuration files containing credentials and network information. Once inside a targeted network, the threat actor used "well-known open-source offensive tools," attempting to access credential databases, move laterally, and compromise backup infrastructure. The threat actor's own documentation confirms these attacks "largely failed when attempting to exploit anything beyond the most straightforward, automated attack paths." Amazon provides indicators of compromise and guidance for defense and mitigation, noting that as AI-augmented attacks increase, "strong defensive fundamentals remain the most effective countermeasure: patch management for perimeter devices, credential hygiene, network segmentation, and robust detection for post-exploitation indicators."

While AI is being leveraged to facilitate these attacks, the target remains single-factor authentication and exposed management ports, which are issues regardless of the tools being leveraged to exploit them, and which you can address. Don't overlook weaknesses or oversight on the "internal" network. Take this as an indicator that our adversaries are working to better identify weaknesses and act on them more quickly, so the window of "nobody noticing" is shrinking. Security by obscurity, hiding in plain sight, works for a magic act and may be tempting, but it is never a wise plan in system engineering. We can do better than that.
AWS
The Register
The Hacker News
BleepingComputer
SecurityWeek
On February 17, 2026, the npm package for Cline CLI, an open-source terminal-based AI coding assistant with over five million installations, was compromised and modified to simultaneously and covertly install OpenClaw. Security researcher Adnan Khan discovered a prompt injection flaw in Cline's issue triage workflow (which itself is automated with Claude) in December 2025, warning of the risk of supply chain attack "if a threat actor were to obtain the production publish tokens." Despite over a month of attempts to contact Cline developers and executives, Khan received no response until after he publicly disclosed the flaw on February 9; the developers' patch was released an hour after Khan's disclosure. On February 10, Khan contacted the Cline team again after receiving an anonymous message that the sender had "obtained valid NPM and OpenVSX credentials for Cline." Although Cline developers rotated credentials the following day, they missed an exposed npm token that was then used on February 17 to publish Cline CLI 2.3.0, which contained one change: a post-install script installing OpenClaw. Khan suspects that his own proof-of-concept exploit was used by the attacker. Version 2.3.0 was active for eight hours before Cline developers revoked the token and deprecated the compromised release, noting that "npm publishing now uses OIDC provenance via GitHub Actions." Cline CLI users must update to 2.4.0 or higher and check for unauthorized OpenClaw installation. The OpenClaw agent has raised serious security concerns (covered in NewsBites Volume 28, numbers 7, 8, and 12) and has been described by news sources and industry professionals as a "security nightmare."

If you're using Cline CLI, make sure you're on 2.4.0+ and don't have any unexpected OpenClaw installations. While the easy target may be watching out for unexpected OpenClaw installations, the bigger concerns are: How responsive are your open-source package maintainers to disclosed vulnerabilities? How do you make sure security fixes are comprehensive? And does this fit within your risk appetite? This isn't about throwing Cline, AI or OpenClaw under the bus; this is about making sure that you have the needed security/processes to support your team and its pressure to deliver. Start with a conversation about what they are doing and the challenges they face, including any workarounds they've had to implement and why, and then improve.
Adnan Khan
GitLab
The Register
The Hacker News
Cisco Blog
A ransomware attack has prompted the University of Mississippi Medical Center (UMMC) to temporarily stop operating its clinics across the state. UMMC has canceled scheduled elective surgeries and other appointments at those locations; the appointments will be rescheduled after the attack has been mitigated. UMMC became aware of the attack early on Thursday, February 19, and the clinics are expected to remain closed through Tuesday, February 24. Hospitals and emergency departments are open and operating under downtime procedures. The disruptions extend to UMMC's EPIC electronic medical record system, so staff are recording patient information with pen and paper. UMMC is working with the US Department of Homeland Security (DHS) and the Cybersecurity and Infrastructure Security Agency (CISA) with assistance from the Federal Bureau of Investigation (FBI).

Kudos to UMMC for jumping on this immediately, calling in help from DHS, CISA, and the FBI. To date, nobody has taken credit for the attack, and UMMC is disinclined to pay any ransom. The hard part will be having a conversation about preventing recurrence, particularly avoiding eyerolls when someone says resiliency. We know the drill: EDR, MFA, monitoring, differential backup and redundancy/fail-over coupled with regular testing. Have a serious conversation about how you'd rebuild/recreate outsourced services (hosted/cloud/etc.), and then try it — your team needs the confidence and experience for when the chips are really down.
South Carolina-based molecular diagnostics company Vikor Scientific, now known as Vanta Diagnostics, has disclosed that a ransomware attack against one of its vendors compromised electronic protected health information (PHI). The incident targeted Catalyst RCM, a revenue cycle management company. The incident also affected KorGene, a molecular testing lab owned by Vikor Scientific, as well as KorPath, a Florida-based anatomical pathology lab and Vanta Diagnostics partner. Vikor Scientific reported the incident to the US Department of Health and Human Services Office for Civil Rights (HHS OCR) as affecting the PHI of nearly 140,000n individuals. According to a breach notification posted on the Catalyst RCM website, the company learned of suspicious activity on its secure file management system "on or about November 13, 2025." A subsequent investigation "determined that an authorized login and password to our system were used to access one server between November 8, 2025, and November 9, 2025, and copied data without permission creating an unauthorized use of the data." Compromised data include names, dates of birth, payment card information, medical treatment history, diagnosis information, and health insurance information. Catalyst RCM is notifying affected individuals by mail.

Points for detecting the unauthorized access and having a separate system for transferring sensitive documents, but points off for reusable credentials. File/information exchange systems are a huge target, and you really can't depend on single-factor authentication. I see someone in the back saying we encrypt the files as well. Good, but how robust is that encryption, and how are the keys managed? Better still, discover who understands how you're protecting these information exchanges and verify you are following (current) security best practices.
Increasingly, compromised credentials are used to gain initial access; here is the latest example. Multi-factor authentication is ubiquitous today and is one of the most effective means to counter credential theft. Unfortunately, it doesn’t appear to have been enabled on the Catalyst network. Would you consider that reasonable cybersecurity?
The US Cybersecurity and Infrastructure Security Agency (CISA) has added a pair of vulnerabilities in the Roundcube Webmail web-based email client to the Known Exploited Vulnerabilities (KEV) catalog. Both are reportedly being actively exploited. CVE-2025-49113 is a critical deserialization of untrusted data vulnerability that could be leveraged to achieve remote code execution. It affects Roundcube Webmail before 1.5.10 and 1.6.x before 1.6.11; Roundcube released updates to address the flaw in June 2025. CVE-2025-68461 is a high-severity cross-site scripting vulnerability that affects Roundcube Webmail before 1.5.12 and 1.6 before 1.6.12; Roundcube released patches for the vulnerability in December 2025. Both CVEs have mitigation deadlines of March 13, 2026 for Federal Civilian Executive Branch (FCEB) agencies.

Roundcube is the default Webmail interface for the widely used cPanel web hosting control panel, going back to around 2008. If you've got cPanel, odds are you have Roundcube. Roundcube just released new security updates, so make sure you're on 1.5.13 or 1.6.13. There are as many as ten prior actively exploited Roundcube vulnerabilities CISA is tracking, and Shodan observes over 46,000 Roundcube installations that are internet accessible. If it needs to be exposed to the internet, make sure that it's protected, updated and secured.
The Hacker News
BleepingComputer
SecurityWeek
NIST
Roundcube
NIST
Roundcube
The US Department of Energy (DoE) has fixed a vulnerability in an Office of Critical Minerals and Energy Innovation portal that allowed anyone to register and use email accounts that appeared to be associated with DoE but were never verified to be associated with authorized individuals. The individual controlling such an account "could request internal documents, direct recipients to malicious attachments or insert themselves into ongoing program discussions without suspicion." Researcher Ronald Lovelace is credited on DoE's responsible vulnerability disclosure page, but the department has provided no details about the issue. According to Nextgov/FCW, Lovelace discovered the vulnerability "us[ing] a standard reconnaissance method called subdomain enumeration to uncover the verification flaw."

Having spent time in DoE, including responding to the directive to have VDP information on all websites, it's nice to see that reported incidents are responded to and the reporters acknowledged. Ronald Lovelace is an independent cybersecurity researcher; as such, he reported the vulnerability to multiple sources (CISA, DOE, IG), which means DoE will have some explaining to do. Make sure that your VDP process is sufficiently responsive such that reporters don't feel compelled to go through multiple channels to elicit a timely response.
Nextgov/FCW
Responsible Disclosure
The US Federal Bureau of Investigation (FBI) has published a FLASH alert with guidance for organizations to guard against ATM jackpotting, an attack that involves both physical and software/firmware level manipulation of cash machines to dispense currency on demand. The attacks target the physical ATM, not customer accounts. Since 2020, the FBI has received reports of more than 1,900 jackpotting incidents. In 2025 alone, more than 700 incidents were reported with losses exceeding US $20 million. The threat actors use malware tailored to the attacks: for example, "Ploutus malware exploits the eXtensions for Financial Services (XFS), the layer of software that instructs an ATM what to physically do." Jackpotting attacks depend on having physical access to the ATMs. The FLASH alert lists indicators of compromise (IoCs), including digital IoCs, persistent mechanisms, and physical interaction IoCs. Suggested mitigations cover physical and hardware security, as well as logging (enabling, maintaining, and preserving logs), auditing (ATM devices, changing default credentials, and conducting pre-production assessments), network security (IP whitelisting), endpoint detection and response (anti-malware and anti-virus, software whitelisting), and threat intelligence, including familiarization with maintenance schedules, participating inn information sharing through industry groups, and training employees to be alert to anomalies that could indicate jackpotting attacks. Organizations are asked to report suspicious activity to their local FBI field office (www.fbi.gov/contact-us/field-offices) or the FBI Internet Crime Complaint Center (www.ic3.gov).

Imagine, if you would, deploying thousands of Windows devices in public locations, that you encourage customers to come use for trusted transactions, loaded with thousands in cash. Let's kick it up a notch: add portable devices that can be deployed at an event. What could go wrong? While physical access is needed for a jackpotting attack, ATMs are already out in public. The goal is to bypass the controls from the bank or the ATM itself causing the machine to dispense its cash. If they don't just physically access the cash via the maintenance hatch, they find a logic compromise, or even replace the drive. Too often a common key opens the device and there is no alert that it is being accessed. If you're involved with ATMs, use the notice to develop a checklist and verify you have the recommended controls. In addition to the FBI list, make sure that you've got multi-person rules in place as well; no counting or manipulating the cash without observation. Now get your PenTest team to check for gaps in your armor and address them.
If you have physical access to the device, in this case enabled through generic keys, it’s typically game over. What’s interesting, though, is that the vendor seems to put more physical security controls into protecting the money versus protecting the electronics used to dispense cash. Lesson learned the hard way...
IC3
Gov Infosecurity
SC Media
SecurityWeek
A federal grand jury in California has indicted three former Google engineers on charges of conspiracy to commit trade secret theft from Google and other leading technology companies, theft and attempted theft of trade secrets, and obstruction of justice. Two of the defendants, sisters Samaneh Ghandali and Soroor Ghandali, worked at Google before going to work for an unnamed organization, identified as Company 3; Mohammadjavad Khosravi, who is married to one of the sisters, worked at an organization identified as Company 2. The defendants exfiltrated confidential and sensitive data," including trade secrets related to processor security and cryptography and other technologies."

Given my background in government, I'm reminded of spy rings and other espionage cases. This is a reminder that your sensitive/confidential information is also a target; IP theft is not just the stuff of spy novels. If you're wondering where role management and DLP are important, here is a good example. Google's protections alerted them to the access and movement of that sensitive information. Ask how you're protecting sensitive/confidential information, and how often those accesses are reviewed. Verify you can detect unauthorized information access/flow. Don't limit the scope to PII or PCI; make sure your secret sauce remains so.
Data Loss Prevention technology exists for a reason and has proven to be quite effective.
Oleksandr Didenko of Kyiv, Ukraine, has been sentenced to five years in prison for his role in a scheme that stole identities of US citizens and sold them to people in North Korea for fraudulently obtaining employment with US tech companies. Didenko operated a company that facilitated the use of stolen identities; he also managed the proxy identities and facilitated operations of at least three laptop farms that were used to disguise the North Korean workers’ locations. Didenko pleaded guilty to charges of wire fraud conspiracy and aggravated identity theft in November 2025. He has agreed to forfeit more than US $1.4 million and has been ordered to pay US $46,550 in restitution and serve 12 months of supervised release.

He sold more than 2,500 identities and paid co-conspirators to operate laptop farms in Virginia, Tennessee, and California, resulting in about 900 fake workers spread across 40 US companies. It is good news that he was caught, the domain was shut down, and he is facing consequences, but he's not the only one doing this. The task remains to fully vet remote workers, not only strongly verifying their identity, but also meeting them in-person on a regular basis. Make sure they are using company-approved remote configurations for remote systems and monitor for unexpected use patterns.
Back of the napkin calculation: 1.4M divided by 4 equals 350K. Not bad, but then there are expenses to operate the laptop farm and pay off a few individuals. And most importantly, the North Koreans get their sizable cut. It makes one wonder, does this form of cybercrime actually pay?
CyberScoop
The Register
SecurityWeek
Justice
SANS Internet Storm Center StormCast Tuesday, February 24, 2026
Malicious JPEG Analysis; Calibre Vuln; jsPDF object injection; Roundcube Exploited
https://isc.sans.edu/podcastdetail/9822
Another day, another malicious JPEG
https://isc.sans.edu/diary/Another+day+another+malicious+JPEG/32738
Calibre Path Traversal Leading to Arbitrary File Write and Potentially Code Execution CVE-2026-26064 CVE-2026-26065
https://github.com/kovidgoyal/calibre/security/advisories/GHSA-72ch-3hqc-pgmp
https://github.com/kovidgoyal/calibre/security/advisories/GHSA-vmfh-7mr7-pp2w
CVE-2026-25755: PDF Object Injection in jsPDF (addJS Method)
https://github.com/ZeroXJacks/CVEs/blob/main/2026/CVE-2026-25755.md
Roundcube Webmail Exploited CVE-2025-49113
https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10
https://www.openwall.com/lists/oss-security/2025/06/02/3
SANS Internet Storm Center StormCast Monday, February 23, 2026
Japanese Phishing; AI Agents Ignoring Instructions; Starkiller MFA Phishing
https://isc.sans.edu/podcastdetail/9820
Japanese-Language Phishing Emails
https://isc.sans.edu/diary/JapaneseLanguage+Phishing+Emails/32734
'God-Like' Attack Machines: AI Agents Ignore Security Policies
https://www.darkreading.com/application-security/ai-agents-ignore-security-policies
Starkiller: New Phishing Framework Proxies Real Login Pages to Bypass MFA
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Browse ArchiveCrowdStrike 2026 Global Threat Report: AI Accelerates Adversaries and Reshapes the Attack Surface. The most anticipated threat intelligence report of the year is now available, and it reveals how threat actors are weaponizing AI to supercharge attacks and evade detection. Get to know their latest tradecraft and learn how to outpace AI-enabled cybercrime.
SANS OSINT Summit in Arlington VA | Monday, March 16, 2026 | Join us at the premier event for cybersecurity professionals, investigators, threat analysts, and open-source researchers shaping the future of intelligence gathering.
Survey Results Webinar | Wednesday, March 11, 2026, at 10:30 AM EDT | 2026 SANS State of Identity Threats & Defenses Survey Insights Event: How Identity Became the New Security Perimeter—And What’s Next.
Free Virtual Event | Tuesday, March 17, 2026, at 10:00 AM EDT | SANS Leadership Summit Solutions Track.