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 UsMicrosoft subsidiary Nuance has agreed to pay $8.5 million to settle a class action lawsuit over the MOVEit file transfer breach. The proposed settlement, which admits no liability on Nuance's part, is scheduled for a final approval hearing on March 31, 2026. The lawsuit was filed by customers who claim Nuance did not adequately protect personal data that were compromised by attacker exploiting the SQL injection vulnerability in Progress Software's MOVEit file transfer software. Nuance, which was acquired by Microsoft in 2022, is "best known for its medical transcription and speech recognition systems." Nuance was one of many organizations breached through the MOVEit vulnerability; the Nuance breach alone is estimated to have compromised information belonging to 1.225 million people.
Note to self, you can outsource the function (data movement) but not the responsibility (data protection). We can happily argue over drinks whether this is a settlement to make the lawsuit go away; the issue remains that their claim that thousands of other customers relied on the solution for securely handling data didn't absolve Nuance from their due diligence to verify the security was actually where it needed to be. This is why you need to regularly ensure that you have security settings for outsourced services that both remain in effect and are based on the current guidance/best practices.
With this settlement, whom claimants go after has expanded when it comes to supply chain attacks. It does raise the question: what are the expectations of users of third party products that are later compromised? I suspect that MSFT Nuance will simply go after Progress Software to recover their settlement costs.
A drop in the bucket for MS, but such suits may rise above the nuisance level.
Microsoft is reminding customers that support for Windows 10 will end on October 14, 2025, giving users just under two months to decide what to do next. "On October 14, 2025, Windows 10, version 22H2 (Home, Pro, Enterprise, Education, and IoT Enterprise editions) will reach end of servicing. October 14, 2025 will also mark the end of support for Windows 10 2015 LTSB and Windows 10 IoT Enterprise LTSB 2015. The October 2025 monthly security update will be the last update available for these versions. After this date, devices running these versions will no longer receive monthly security and preview updates containing protections from the latest security threats." Microsoft urges users to update to Windows 11 or migrate to Windows 11 in the cloud. Some users may find that their older PCs do not have the capacity to upgrade to Windows 11. However, for the first time, users have the option of enrolling their personal PCs running Windows 10 in the Extended Service Update (ESU) program, which provides support for one additional year. ESU is available for a nominal fee; if you sync Windows 10 settings to the cloud via Windows Backup or pay 1,000 Microsoft reward points, the fee is waived. Note that on October 24, 2025, Microsoft is also ending support for Office 2016 and Office 2019.
That option to enroll in ESU is attractive, but really just kicks the can down the road: you are ultimately going to have to deal with updates. You should already have an inventory of which systems are unable to run Windows 11 and be phasing in the replacements. You may have OT system components running Windows 10 which cannot be updated/replaced; make sure that you've got adequate protections, particularly for media/data migration. Don't overlook the end of support for Office 2016/2019 as well; the options are to go to Office 2024 or Microsoft 365.
Organizations should have a well-established plan for software and should upgrade within a year of major update. Windows 11 has been out for four years. Staying on End-of-Life software is not practicing reasonable cybersecurity.
It now seems clear that use of Windows 10 is going to persist well beyond October 14, 2025. Users of Windows 10 must consider how to manage the risk that vulnerabilities in it will continue to be discovered and exploited.
BleepingComputer
Engadget
Tom's Guide
ZDNet
Microsoft
The US National Institute of Standards and Technology (NIST) has finalized the latest revision of its Digital Identity Guidelines. The document was first published in 2004, with major revisions published in 2011, 2013, 2017, and now July 2025. The updated document notes that "the composition, models, and availability of identity services have significantly changed, ... as have the considerations and challenges of deploying secure, private, and usable services to users," and centers its guidance on "roles and functions that entities perform as part of the overall digital identity model." Among the expansions and reorganizations, SP-800-63-4 adds a "user-controlled wallet federation model," performance metrics to continuously evaluate digital identity systems, and a subsection addressing AI and ML in digital identity services. In August 2025, NIST also published NISTIR 8584, "Face Analysis Technology Evaluation (FATE) MORPH, Part 4B: Considerations for Implementing Morph Detection in Operations." The document provides information, strategies, and tools for organizations to secure their identity systems against fraudulent morphed photos. Mei Ngan, an author of the report, states, "Morphing attacks are happening, and there are ways to mitigate them [...] The best way is to not allow users the opportunity to submit a manipulated photo for an ID credential in the first place."
We've been wondering about how deepfakes/AI impact ID proofing, and NIST is publishing guidance worth a read for ways to raise the bar. Passkeys, FIDO, subscriber controlled wallets and metrics for continuous evaluation are all worth some consideration. The good news is these technologies have matured and are more supported, available, and stable, making it much more viable (read: easier and less expensive) to implement.
In a world of increasing threat, increasing use, uses, and users, increasing reliance on IAM, and more secure and convenient alternatives, most identities are secured only by passwords. This new guidance attempts to address this, among other things. In the face of this authoritative guidance it will be harder to continue to do the wrong thing.
Dark Reading
Fedscoop
Help Net Security
NIST
NIST
Plex has released Plex Media Server (PMS) version 1.42.1.10060 and strongly recommends that users update immediately to apply a fix for a "potential security issue" impacting PMS 1.41.7.x to 1.42.0.x. Plex sent emails to customers who may be running outdated versions of PMS, urging them to update, either through their regular server management page or downloaded directly from the Plex site as a package. Neither a CVE nor a description of the vulnerability appear in the security notice, but Plex states that they were made aware of the flaw through their bug bounty program. BleepingComputer notes that Plex does not often email customers about specific vulnerabilities, possibly further emphasizing the unspecified flaw's severity. Plex estimates their media streaming software has over 25 million users worldwide.
This is noteworthy as Plex has rarely reached out to users over resolved vulnerabilities. You may want to bug friends who missed the email. The fixed version was released August 8th and can be applied via manual download or via the PMS management page. The only information currently shared about the flaw is that it was a discovered and reported through their bug bounty program.
Among 29 CVEs addressed by the August 2025 Cisco Secure Firewall ASA, Secure FMC, and Secure FTD Software Security Advisory Bundled Publication, 11 are rated medium severity, 17 are high severity, and one carries CVSS score 10.0. This maximum-severity flaw affects the RADIUS (Remote Authentication Dial-In User Service) subsystem implementation of Cisco Secure Firewall Management Center (FMC) Software versions 7.0.7 and 7.7.0. CVE-2025-20265 allows an unauthenticated remote attacker to inject arbitrary shell commands and execute them at a high privilege level by crafting malicious inputs while entering credentials authenticated at the configured RADIUS server, exploiting a lack of proper handling of user input. Cisco's advisory specifies that exploitation requires "Cisco Secure FMC Software [to] be configured for RADIUS authentication for the web-based management interface, SSH management, or both." Cisco provides a link to instructions for checking whether RADIUS is configured, and notes that while there are no workarounds, customers who have evaluated the impact and applicability of using another type of authentication in their environment besides RADIUS may mitigate risk by instead using, for example, "local user accounts, external LDAP authentication, or SAML single sign-on (SSO)." The flaw was discovered during internal testing, and Cisco Product Security Incident Response Team (PSIRT) has not observed evidence or announcements of active exploitation.
FMC version 7.0.7 and 7.7.0 are impacted if RADIUS authentication is enabled. Unfortunately, there are no workarounds; you need to apply the update. This is a good time to consider alternatives to RADIUS such as LDAP or SAML (SSO). Think carefully before looking at local accounts; there are too many ways that can go wrong.
Cisco
Cisco
CyberScoop
BleepingComputer
SecurityWeek
The Register
Microsoft says that malware dubbed “PipeMagic” is being actively deployed by a threat actor group to lay the groundwork for launching ransomware attacks. PipeMagic is a modular backdoor that pretends to be a ChatGPT Desktop Application. According to Microsoft, "Beneath its disguise, PipeMagic is a sophisticated malware framework designed for flexibility and persistence. Once deployed, it can dynamically execute payloads while maintaining robust command-and-control (C2) communication via a dedicated networking module. As the malware receives and loads payload modules from C2, it grants the threat actor granular control over code execution on the compromised host. By offloading network communication and backdoor tasks to discrete modules, PipeMagic maintains a modular, stealthy, and highly extensible architecture, making detection and analysis significantly challenging." Microsoft discovered the malware while looking into the exploitation of a use-after-free vulnerability (CVE-2025-29824) in the Windows Common Log File System Driver that allows attackers to escalate privileges. The flaw was disclosed in April 2025.
CVE-2025-29824, CVSS score 7.8, was addressed in the April 2025 Windows update, so you should be good there. On the other hand, with the excitement over AI and related tools, double down on making sure that only legitimate tools are installed. PipeMagic has been around since 2022 and continues to evolve; it uses DLL hijacking and mimics a Google Chrome update file "googleupdate.dll". IoCs along with detailed analysis can be found in posts from Microsoft, Kaspersky and BI.ZONE. Your EDR tools should be able to detect PipeMagic.
The patch for the privilege escalation flaw in CLFS has been out since late April – I’d like to hear from Microsoft if they have also closed other “use-after-free” flaws before they become zero day attack paths.
Normal hygiene. Prefer software from trusted sources in tamper-evident packaging. Restrict "write" access to program libraries. Apply patches on a timely basis.
Researchers from Imperva and Tel Aviv University are warning of a new variant of 2023's HTTP/2 Rapid Reset vulnerability that "tricks the server into resetting its own streams," allowing denial-of-service (DoS) attacks without directly violating protocol. CVE-2025-8671, CVSS score not yet provided, allows an attacker to cause denial of service by exploiting incorrect stream accounting using malformed frames or flow control errors, opening streams and triggering the server to reset them; backend processing continues despite streams being considered closed at the protocol level, ultimately creating "an unbounded number of concurrent streams on a single connection." Vendor-specific CVEs have also been issued for F5, Apache Tomcat, Netty, and IBM, and Jetty is also affected. Imperva notes that mitigation should be a priority, and "defenses must go beyond traditional client-side rate limiting," to include stricter protocol validation, stream state enforcement, anomaly detection and behavioral monitoring, connection-level rate controls, regular updates, and defensive hardening. Deepness Lab notes that more than 60% of top sites use HTTP/2, and the protocol carries approximately a third of global HTTP traffic.
Imperva
Deepness Lab
NIST
The Hacker News
SecurityWeek
Dark Reading
Workday, a Human Resources provider serving over 11,000 organizations and 70 million people worldwide, published a blog post on August 15, 2025, disclosing a data breach of its third-party customer relationship management (CRM) platform. The post indicates that the system was breached by threat actors who impersonated human resources or IT personnel over the phone or by text, and Workday believes this attack is associated with a broader social engineering campaign targeting large organizations. Upon discovery of the breach, Workday "cut the access" immediately and implemented additional preventative safeguards. While Workday states that customer tenants and data within them do not appear to have been accessed, business contact information characterized as "commonly available" was stolen including "names, email addresses, and phone numbers," which could be exploited for future social engineering attempts. The post assures customers that Workday will never request credentials or sensitive information over the phone, indicating that official communications will come only from "trusted support channels." BleepingComputer reports that Workday's email notification to customers revealed that the breach was discovered on August 6. TechCrunch notes that Workday’s blog post was published with a “noindex” tag intended to block search engines from indexing the disclosure.
Social engineering for credentials strikes again. This attack is the work of the ShinyHunters extortion group, which targets Salesforce CRM instance access using social engineering. I'm recommending phishing resistant MFA because it works. Yes, it can be a chore to deploy (it's gotten lots easier), and it's worth it. Another thing to argue with your response team - do you publish flaw notifications with a "noindex" tag or not? Make a documented decision, so you're not re-hashing or having an embarrassing moment when the chips are down.
The human factor continues to be a weak link in cybersecurity. If they haven’t done so already, organizations should add a social engineering module as part of the quarterly cybersecurity training.
Reliance on passwords will be implicated.
Workday
BleepingComputer
TechCrunch
The Register
The Record
Dark Reading
Researchers from Talos Intelligence have observed malicious cyber activity conducted by an advanced persistent threat (APT) actor with ties to China. The APT group appears to be targeting Taiwanese "web infrastructure entities." The campaign exploits known vulnerabilities in unpatched, internet-exposed servers to gain initial access. From there, the intruders conduct reconnaissance to determine if the compromised server is of value to them. If it is, they "pivot to additional systems in the enterprise to proliferate and conduct malicious activities," including deploying a shellcode loader to help launch Cobalt Strike and other tools.
At its root, this APT group is exploiting poor patch management practices of organizations. The group really doesn’t matter; any nefarious actor will have the same level of success. The best defense remains to update systems within 24-48 hours as patches are made available.
UK-based telecommunications provider Colt Technology Services disclosed last week that they were experiencing a cyber incident that was causing outages. The incident has disrupted the availability of the company's customer portal and other services. Colt acknowledged that "One of our protective measures involved us proactively taking some systems offline, which has led to the disruption of some of the support services we provide to our customers." Colt has been posting regular updates to their status page to keep customers informed.
The Register
Dark Reading
Gov Infosecurity
BleepingComputer
Colt
SANS Internet Storm Center StormCast Tuesday, August 19, 2025
MFA Bombing; Cisco Firewall Management Vuln; F5 Access for Android Vuln
https://isc.sans.edu/podcastdetail/9576
Keeping an Eye on MFA Bombing Attacks
Attackers will attempt to use authentication fatigue by “bombing” users with MFA authentication requests. Rob is talking in this diary about how to investigate these attacks in a Microsoft ecosystem.
https://isc.sans.edu/diary/Keeping+an+Eye+on+MFABombing+Attacks/32208
Critical Cisco Secure Firewall Management Center Software RADIUS Remote Code Execution Vulnerability
An OS command injection vulnerability may be abused to gain access to the Cisco Secure Firewall Management Center software.
F5 Access for Android vulnerability
An attacker with a network position that allows them to intercept network traffic may be able to read and/or modify data in transit. The attacker would need to intercept vulnerable clients specifically, since other clients would detect the man-in-the-middle (MITM) attack.
https://my.f5.com/manage/s/article/K000152049 SANS Internet Storm Center StormCast Monday, August 18, 2025
5G Attack Framework; Plex Vulnerability; FortiWeb Exploit; Flowise Vuln
https://isc.sans.edu/podcastdetail/9574
SNI5GECT: Sniffing and Injecting 5G Traffic Without Rogue Base Stations
Researchers from the Singapore University of Technology and Design released a new framework, SNI5GECT, to passively sniff and inject traffic into 5G data streams, leading to DoS, downgrade and other attacks.
Plex Vulnerability
Plex patched a vulnerability in the Plex Media Server. Make sure you have updated to at least 1.42.1.
https://forums.plex.tv/t/plex-media-server-security-update/928341
FortiWeb Exploit Public
A security researcher published details about the recent FortiWeb vulnerability, including demonstrating a PoC exploit.
Flowise OS vulnerability
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Browse ArchiveHow can your Security Champions program adapt to the age of AI-powered development? Take a look at Snyk's latest whitepaper - your roadmap to integrating AI security considerations into your Security Champions program. Discover insights to: - Empower Security Champions to integrate security into the AI development lifecycle. - Understand the AI threat landscape and scale AI governance frameworks. - Measure success with KPIs for AI security integration. Elevate your security champions in the age of AI.
Webcast | SANS Cloud Security Exchange 2025 | Thursday, August 21, 2025 at 10:30AM ET Industry leaders from AWS, Google, and Microsoft will come together for a full day of cloud-first strategies, cutting-edge threat insights, and practical security solutions. Join live or watch on your own time.
Survey | Detection & Response: Transforming Cybersecurity Operations: AI, Automation, and Integration Help shape the future of detection and response strategies. Take our short survey and share your insights, your input will guide industry benchmarks and best practices.
Webcast | Balancing On-Prem and Cloud Security: Strategic Considerations for Modern Organizations | Tuesday, September 16, 2025 at 1:00PM ET Explore the trade-offs between cloud and on-prem security in today's AI-driven threat landscape, and learn how integrated platforms can streamline operations.