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 has published an out-of-band security update for the .NET framework that includes a patch for a critical flaw in versions 10.0.0 to 10.0.6 of the Microsoft.AspNetCore.DataProtection NuGet package. CVE-2026-40372, CVSS score 9.1, allows an unauthorized attacker to elevate privileges over a network by forging authentication cookies, due to improper verification of cryptographic signatures. With these privileges, an attacker could induce the application to issue legitimately signed tokens, which will remain valid even after updating to version 10.0.7 unless the DataProtection key ring is rotated. Rahul Bandari, a Senior Program Manager at Microsoft, explains, "the managed authenticated encryptor could compute its HMAC validation tag over the wrong bytes of the payload and then discard the computed hash, which could result in elevation of privilege." Microsoft states that only applications running on Linux, macOS, and other non-Windows operating systems are impacted, specifically those that use Microsoft.AspNetCore.DataProtection 10.0.6 from NuGet, and only if the NuGet copy of the library was actually loaded at runtime, not the shared framework copy. A secondary affected configuration involving versions 10.0.0 through 10.0.6 is detailed in Microsoft's advisory on GitHub. No Windows applications are affected. Users should upgrade Microsoft.AspNetCore.DataProtection to 10.0.7 or later and redeploy; rotate the DataProtection key ring; audit application-level long-lived artifacts; audit plaintext stored inside protected payloads; and review web server logs.

If you're not already including .NET in your non-Windows software inventory, it's a good time to add that. At a minimum, check your Linux/Mac systems by running "dotnet --info" which should help you scale back or eliminate the targets needing the update. Once you deploy the updated runtime or SDK and rebuild/redeploy the apps, don't forget about rotating the DataProtection keyring, as these forged credentials will survive after the vulnerability is fixed. Lastly, you need to look for issues in logs/protected payloads; leverage the Microsoft Advisory on GitHub for detailed information. Triple check any nodes which were Internet facing.

The out-of-cycle patch for this vulnerability means that there must be some level of exploitation that was active or some type of exploitability. If you're using ASP.NET, you should probably upgrade your stack asap.
GitHub
Microsoft
Microsoft
Ars Technica
BleepingComputer
The Hacker News
On Monday, April 20, 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added three vulnerabilities in Cisco Catalyst SD-WAN Manager (formerly known as vManage) to the Known Exploited Vulnerabilities (KEV) catalog, each with a three-day mitigation deadline. All three of the flaws — an incorrect use of privileged APIs vulnerability (CVE-2026-20122), an exposure of sensitive information to an unauthorized actor vulnerability (CVE-2026-20133), and a storing passwords in a recoverable format vulnerability (CVE-2026-20128) — were addressed in a February 25 Cisco security advisory. Federal Civilian Executive Branch (FCEB) agencies have until Thursday, April 23 to mitigate these vulnerabilities in their systems. Also on April 20, CISA added a cross-site scripting vulnerability in Synacor Zimbra Collaboration Suite (CVE-2025-48700) to the KEV catalog with a mitigation due date of April 23. On Wednesday, April 22, 2026, CISA added a high-severity insufficient granularity of access control vulnerability in Microsoft Defender to the KEV catalog. The vulnerability can be exploited to achieve local privilege elevation. The flaw, which was addressed in Microsoft's April 14 monthly security update, has been actively exploited. A week prior to that, a proof-of-concept exploit for the vulnerability was released, and the flaw was nicknamed BlueHammer. FCEB agencies have until May 6, 2026 to mitigate the issue. Other CVEs added to KEV this week include an RCE vulnerability in Marino (CVE-2026-39987), a relative path traversal vulnerability in JetBrains TeamCity (CVE-2024-27199), an improper authentication vulnerability in Quest KACE Systems Management Appliance (SMA) (CVE-2025-32975), an improper authentication vulnerability in PaperCut NG/MF (CVE-2023-27351), and a path traversal vulnerability in Kentico Xperience (CVE-2025-2749).

Don't get lulled into a false sense of security looking at the KEV where the most recent additions are due in May: the Cisco additions are due April 23, aka yesterday. You should be able to easily cut the list of concerns, as fixes for several of these have been out for a bit. The updates for SD-WAN Manager ware released in February, the Microsoft Defender update was released April 14th, and the Zimbra update was released in February. Verify these are all addressed, and then focus on the other items due in May. Get your weekend back.

If you're a Cisco SD-WAN customer, please upgrade your core infrastructure. I don’t know how else to say this. Look for rogue endpoints in your SD-WAN configuration while you are at it.
It's been a busy week for CISA. The bulk of these KEV entries are from 2025 or earlier. Clearly long enough for any information security professional to prioritize patching.

The so-called "mitigation window" has recently shrunk from weeks to days. Compliance is mandatory only for FCEB agencies. However, the rest of us can use it as an indicator of urgency when scheduling and allocating resources.
The Register
Help Net Security
SC Media
Cisco
HKCERT
BleepingComputer
Vercel, cloud provider and maintainer of Next.js, has updated its advisory about a breach of its internal systems through compromise of an employee's Context.ai app, first disclosed on April 19, 2026. After investigating additional indicators of compromise (IoCs), network requests, and logs of environment variable read events, Vercel found two additional groups of compromised accounts beyond the one account initially reported: some that were also breached as part of this incident, and some that were compromised prior to this incident, "potentially as a result of social engineering, malware, or other methods." Vercel is collaborating with Google Mandiant, GitHub, Microsoft, npm, Socket, AWS, Wiz, and law enforcement to monitor and investigate. Research from Hudson Rock indicates that this breach can likely be traced to a Context.ai employee's system infected with the Lumma infostealer when the employee was downloading game exploits for the video game Roblox, compromising Context.ai support credentials. Context.ai was certified by compliance startup Delve, whose legitimacy has been scrutinized following whistleblower allegations in March; another of Delve's clients was LiteLLM, which that same month suffered a supply chain attack following the compromise of Trivy. Vercel CEO Guillermo Rauch stated in a social media post on Wednesday, April 22, that "threat intel points to the distribution of malware to computers in search of valuable tokens like keys to Vercel accounts and other providers," leading to "rapid and comprehensive API usage, with a focus on enumeration of non-sensitive environment variables" by the attacker. The company has notified affected account holders as well as other organizations suspected to be victims, and there is no evidence of tampering or compromise in Vercel npm packages. Vercel's recommendations remain the same: set Deployment Protection to Standard or higher, rotate Deployment Protection Tokens and environment variables and designate secrets as "sensitive," review recent deployments and the activity log, and search for IoCs.

I keep coming back to an employee downloading exploits for a game on their work computer. I'm not hating on someone looking for cheats/tricks to win games — that is a personal choice — I'm focusing on personal and corporate activities not being adequately separated. Review the total cost of an incident against providing corporate systems. It's not all that hard or expensive to provide virtual environments for cases where you don't want to deliver a physical workstation.
Today’s remote workforce often uses company resources for personal business. In many cases it’s understood and permitted. That said, downloading of video game exploits is not one of them. The angle with Delve is interesting: is it an issue with the company or the compliance regime they measured against? For context, everyone remembers the Target breach, circa 2013. What’s interesting is that they passed a PCI inspection shortly before the incident occurred. Bottom line: compliance doesn’t equal total security.
Vercel
The Hacker News
TechCrunch
TechCrunch
The Register
Hudson Rock
Mozilla used Anthropic's Claude Mythos Preview AI model to search for vulnerabilities in Firefox 150, and Mythos returned 271 security issues. Of those, just over 40 merited CVE designation. Several weeks ago, Mozilla found 22 security issues in Firefox 148 using Anthropic’s Opus 4.6 model. In a blog post, Mozilla CTO Bobby Holley writes that while initially the findings inspired a temporary feeling of "vertigo, ... our experience is a hopeful one for teams who shake off the vertigo and get to work." Holley notes, "So far we’ve found no category or complexity of vulnerability that humans can find that this model can’t. This can feel terrifying in the immediate term, but it’s ultimately great news for defenders. A gap between machine-discoverable and human-discoverable bugs favors the attacker, who can concentrate many months of costly human effort to find a single bug. Closing this gap erodes the attacker’s long-term advantage by making all discoveries cheap."

This new capability changes where vulnerability discovery sits in the software lifecycle. If AI can find bugs this cheaply, it belongs inside CI/CD as a continuous function, not a periodic test at the end. Code should not advance through the pipeline unless it has passed automated adversarial analysis the same way it passes unit tests. It also raises the bar for remediation discipline. Finding hundreds of issues is only useful if teams can triage, prioritize, and fix them quickly without breaking the build. That means tighter integration between security findings and developer workflows, along with better tooling to separate signal from noise. Developers also need to assume that any logical flaw will be discovered, either by their tools or someone else’s. The practical response is to design with failure in mind, enforce secure coding patterns, and treat security checks as part of normal engineering quality rather than a separate activity.

Interesting new categorization of human versus machine discoverable flaws. As tools such as Mythos continue to evolve and file flaws, the question of responding to them becomes more complicated. In this case, Mozilla addressed all 271 flaws in Firefox 150; you're going to have to have a conversation about how to address an increased number of discovered flaws and the criteria for addressing them versus accepting the risk. Document this fully.

Firefox 150 is out now. I would suspect you will see a large number of “vulnerabilities” being released over the next 6-12 months. What’s interesting here is that while there are 271 vulnerabilities, they are being rolled into 41 CVEs. If you are used to 1:1 CVE-to-vulnerability mappings, you will be surprised to see many vulnerabilities bundled together.
This is undoubtedly a ‘game changer.’ Mythos has a great opportunity to change the economics of bug finding. Given the number of issues found, it doesn’t appear to be new classes of bugs that only AI could have discovered, but rather extensions of known classes of vulnerabilities. The really, really good news is that with a simple restart of the Firefox browser, one is updated and a threat vector is eliminated. Automation in patching must become the norm for cyber defenders to stay ahead of what’s coming.

And here was me, using Firefox because I do not trust Chrome. Prefer purpose-built clients for sensitive applications.
Mozilla
WIRED
ZDNET
The Register
SC Media
Apple released updates for iOS and iPadOS on Wednesday, April 22, 2026 to address a logging issue in which notifications marked for deletion could be unexpectedly retained on the device. The vulnerability (CVE-2026-28950) was addressed with improved data redaction. The FBI reportedly leveraged the vulnerability to access incoming Signal messages on a suspect's iPhone, even after the Signal app was deleted from the device. During a federal trial in March, "an FBI agent testified that the agency was able to access Sharp's incoming Signal messages because copies of their content had been saved on her phone's push notification database." The Signal app's push notification default configuration shows both the sender's name and a portion of the message's content. While users have the option of changing that configuration to display only the sender's name, the owner of the iPhone in question had not made that change. Prior to the Apple updates, the iPhone would store the content of Signal push notifications in internal memory. Apple has fixed the issue in iOS and iPadOS 18.7.8 and 26.4.2. The fix should also prevent this issue from occurring in other messaging apps.

This update only applied to iOS and iPadOS and installs pretty quickly. The update removes any preserved notifications, Signal or otherwise, so you don't have to make sure that you address those. Take a look at your profile settings for any private messaging apps and make sure your notification settings match your comfort levels.

While this vulnerability would have affected a very small number of people, it demonstrates that privacy is harder than it looks. The prompt fix is evidence of Apple's continuing commitment.
ZDNET
Help Net Security
Infosecurity Magazine
BleepingComputer
SecurityWeek
The Hacker News
NIST
Apple
Apple
A third former ransomware negotiator has pleaded guilty to conspiring to commit ransomware attacks against US companies in 2023. Angelo Martino, who worked as a ransomware negotiator for companies experiencing ransomware attacks, began helping operators of the Blackcat/ALPHV ransomware extort companies by sharing confidential information he had access to through his position at a cyber incident response company. That information helped the threat actors maximize the amount of ransom they would be paid by the companies they were extorting. Martino also admitted that he and two other individuals, Ryan Clifford Goldberg and Kevin Tyler Martin, deployed BlackCat ransomware between April and November 2023; Goldberg and Martin also leveraged their experience from within the cybersecurity industry to launch the attacks. They pleaded guilty to related charges in December 2025.

“Ransomware negotiator” is kind of like “blackjack dealer” as far as both the employer and customer needing strong assurances in order to trust them in their job. Which is one reason casinos have cameras closely monitor dealer actions at every table. One action to take: have a proactive talk with corporate legal to determine if special contractor liability levels are needed if management decides to use such services.

Martino's name rings a bell as his name was disclosed back in March. (See NewsBites Vol. 28 Num. 20, March 17, 2026). It's encouraging to see he's pleading guilty and faces a maximum penalty of 20 years in jail. Authorities have seized about $10 million in assets from him, including vehicles, digital currency, fishing boat, and food truck. The question remains of how companies like DigitalMint are going to ensure their staff are not conspiring similarly. Make sure to have a detailed conversation about this should you find yourself hiring a ransomware responder.
The Register
Infosecurity Magazine
Justice
A bill known as the SECURE Data Act has been introduced in the US House of Representatives by Republican legislators, described as a comprehensive "national framework for consumer privacy rights and the protection of personal data." The International Association of Privacy Professionals (IAPP) notes that the bill is positioned to preempt existing state-level privacy laws if adopted, and that while it conforms with existing laws in Virginia and Kentucky, certain common topics are absent, such as data protection impact assessments, AI and automated decision-making technologies, and obligation to recognize universal opt-out mechanisms. The bill also lacks private right of action, which would allow consumers to directly sue companies in violation of the law.
The bill begins by outlining consumer rights, which include the right to opt out of data processing for targeted advertising, sale, and profiling, as well as to access, correct, delete, and obtain a copy of collected data. Controllers that collect data must either comply or decline (subject to appeal) within 45 days of a consumer's request, but this can be extended by another 45 days "when reasonably necessary." The section on data security mandates that controllers "establish, implement, and maintain reasonable administrative, technical, and physical data security practices to protect the confidentiality, integrity, and accessibility of personal data and that are appropriate to the volume, sensitivity, and nature of such personal data." The bill presumes this to be the case if a controller's code of conduct or certification meets the bill's criteria, or if its security practices adhere to "widely-accepted technical specification" or "third-party attestation" and its data security program "reasonably conforms to a relevant Federal or widely-accepted international risk management framework" for addressing security risks and incidents. Extensive provisions are made to free controllers from restrictions when engaging with law enforcement, legal claims, contracts and services, safety concerns, security incidents and subsequent investigation/litigation, and research. This includes allowing unrestricted collection and processing of personal data to conduct internal research, effectuate a recall, identify and repair a technical error, and perform broadly-defined internal operations.

Having a single data privacy act, versus fifty, is desirable and is going to be easier for implementers to get right. This bill covers a lot of ground including opt-out, corrections and retrieval of privacy data, even categorizing teen data (under 16) as sensitive data. This version mirrors legislation in Kentucky, Virginia, and Washington, and is likely to be enhanced as the legislative process continues, hopefully addressing the currently identified shortfalls. Read the IAPP analysis and watch the expected additions from the House Subcommittee for Commerce, Manufacturing and Trade.

Since 2000, there have been dozens of federal data privacy acts proposed in the US — many stronger than this one, many just as weak. At this point, anything likely to even get to a vote would be unlikely to do anything meaningful. Consumer protection will likely be higher with the current state-by-state approach.
A couple things the bill gets wrong: choosing opt out versus opt in and the ability for data collectors to have up to 90 days to expunge data at consumer request; 45 days is more than sufficient. We as a country do need a national data privacy law, so this is a step in the right direction. That said, I’m not sure this legislation meets the privacy bar for Americans.
US House
IAPP
CyberScoop
StateScoop
The Record
MeriTalk
At a joint hearing by the Subcommittee on Border Security and Enforcement and the Subcommittee on Cybersecurity and Infrastructure Protection titled, “Online Scams, Crypto Fraud, and Digital Extortion: An Examination of How Transnational Criminal Networks Target Americans,” Cynthia Kaiser, Senior Vice President, Halcyon Ransomware Research Center and former deputy assistant director at the FBI’s Cyber Division between 2022 and 2025, told the panel that "The gap between the severity of these crimes and the consequences that follow needs to close." Kaiser called on legislators to "champion three specific authorities" to help close this gap: First, call on the departments of State, Justice, and Treasury to evaluate whether the activity of ransomware actors "who knowingly and repeatedly target hospitals" can be designated as terrorism, which would allow for "asset freezing, heightened Intelligence Community collection authorities, expanded travel restrictions, and significant diplomatic consequences for nations harboring these individuals." Second, Kaiser urged the panel to "request a report from the Department of Justice on the feasibility and appropriateness of pursuing homicide charges in cases where ransomware attacks on healthcare facilities resulted in documented patient deaths." US federal law allows prosecutors to pursue murder charges when deaths occur in the commission of certain felonies, even if the intent was not lethal. Finally, Kaiser called for legislators to fully fund and reauthorize the State and Local Cybersecurity Grant Program. Other witnesses testifying at the hearing include Ari Redbord, Global Head of Policy, TRM Labs; Joshua Bercu, Senior Vice President, Policy, USTelecom – The Broadband Association; and Megan Stifel, Chief Strategy Officer, Institute for Security and Technology.

Having worked in Health IT for many years, I have seen a lack of rigor in how IT and the medical community have cobbled together their systems. Because most regulations focus on the manufacturing of equipment for patient safety, the core of the IT network is unregulated. This has led to unfortunate consequences, such as inadequate segmentation and poor thinking around IT systems. Unlike the financial sector, which has a very strong monetary incentive to secure its systems, the focus in healthcare is primarily on patient safety as it pertains to the medical equipment. If the focus can be shifted so that there is the same level of regulatory pressure in health IT itself, you may see more significant change.

An eye-catching headline, but one consequence could be authorities pursuing negligent homicide charges against healthcare providers who grossly deviated from accepted industry practices in protecting life-critical systems and services.

Sounds a lot like making the punishment fit the crime. There are two things here: Law enforcement, US and international, have done amazing work to take down cyber criminals, and the first ask is to update the definitions of cybercrimes. Broadening the definition of cyber terrorism would allow use of counterterrorism tools in fighting cybercrime, and would provide an increased deterrent once demonstrated. The second is to increase funding for supporting activities such as the state cyber grants and CISA, to provide needed support for investigations and long term security. While this makes its way through the system, focus on the fundamentals and keep an eye on any outcome you could leverage to help raise the bar for you.
No doubt that the penalty doesn’t fit the crime and more can be done. That said, terrorism and the death penalty? That might be going just a bit too far. The grant program, yes absolutely it should be reauthorized and fully funded.

Healthcare is both vulnerable and targeted. Cyberattacks put health and safety at risk. Crimes against it deserve special treatment.
The Register
Nextgov/FCW
YouTube
House
Interrail customers have received communications from parent company Eurail B.V. warning them that personal data stolen in a cybersecurity incident in December 2025 "has been offered for sale on the dark web and a sample dataset has been published on Telegram." The company first notified customers of the breach in mid-January, and the DiscoverEU program stated at the time that data including "name, surname, date of birth or age, passport/ID information or photocopies, email address, postal address and country of residence, phone number, bank account reference (IBAN)," and certain health data may have been accessed. Disclosure letters sent in March estimated the number of affected individuals at 308,777, and mentioned only names and passport numbers as having been accessed. The UK Passport Office has reportedly advised cancelling passports to prevent identity fraud, and customers across Europe are struggling with practical, personal, and financial repercussions of the data leak, according to The Guardian. Eurail states that it has notified all customers whose data appeared in the leaked dataset, and recommends customers "remain vigilant for suspicious communications, update their passwords and monitor their accounts for any unusual activity."

It was expected this data would get out and be used for ID theft and other nefarious purposes. Take steps to protect and secure your Identity. Consider recommended actions carefully, including lead time for obtaining a new passport. In the US, routine issuance is four to six weeks but gets longer from late winter into the summer.

Data leaks. Given the number of organizations that one deals with, and the greed of buyers for PII, one must assume compromise. For the individual, security requires that one freeze one's credit, monitor accounts on a timely basis, and verify all out-of-band confirmations that they receive. For those using PII for identity verification, at a minimum, expect agreement of two identifying numbers issued by different authorities, e.g. state, nation, bank, communication provider (driver's license number or equivalent, passport number or equivalent, bank card numbers, e-mail and postal addresses, and phone numbers). The more you collect and more agreement you find, the better your decision. Modern systems enable one to efficiently collect not merely credential numbers, but images of the applicant and their credentials. After making your decision, record it and a description of information you based it on. However, do not retain PII after the decision has been made. The more you retain, and the longer you hold it, the greater the potential for leakage and the less we can all enjoy any privacy.
SANS Internet Storm Center StormCast Friday, April 24, 2026
Apple Update; Bitwarden Compromise; ASP.NET Core Patch
https://isc.sans.edu/podcastdetail/9906
Apple Patches Exploited Notification Flaw
https://isc.sans.edu/diary/Apple+Patches+Exploited+Notification+Flaw/32922
Bitwarden CLI Compromised
https://socket.dev/blog/bitwarden-cli-compromised
https://community.bitwarden.com/t/bitwarden-statement-on-checkmarx-supply-chain-incident/96127
Microsoft Security Advisory CVE-2026-40372 – ASP.NET Core Elevation of Privilege
https://github.com/dotnet/announcements/issues/395
SANS Internet Storm Center StormCast Thursday, April 23, 2026
Stealing Telegram Sessions; Checkmarx Compromise; Oracle CPU; Firefox Patches
https://isc.sans.edu/podcastdetail/9904
Beyond Cryptojacking: Telegram tdata as a Credential Harvesting Vector, Lessons from a Honeypot Incident
Checkmarx Compromise
https://socket.dev/blog/checkmarx-supply-chain-compromise
Oracle Quarterly Critical Patch Update
https://www.oracle.com/security-alerts/cpuapr2026.html
Firefox 150 - Mythos AI
https://blog.mozilla.org/en/privacy-security/ai-security-zero-day-vulnerabilities/
SANS Internet Storm Center StormCast Wednesday, April 22, 2026
WAV Malware; GitHub OAUTH Phishing; Perforce Settings
https://isc.sans.edu/podcastdetail/9902
A .WAV With A Payload
https://isc.sans.edu/diary/A+WAV+With+A+Payload/32910
The Phishy GitHub Issue Case
https://x.com/_atsika/status/2046256213935972433
P4WNED: How Insecure Defaults in Perforce Expose Source Code Across the Internet
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Webinar | What's Working & What's Ahead in Cyber Defense | Thursday, April 30, 2026 at 8:30 AM EDT Discover the tactics, tools, and tradecraft you need to detect threats, respond fast, and adapt smarter—straight from the experts themselves at Secure Your Fortress 2026.
RSAC Webcast: Decryption at Scale | May 7, 2026 at 1:00 PM ET. Encryption is advancing fast—and with it, the challenge of maintaining visibility across your network. As protocols like TLS 1.3 and QUIC become standard and post-quantum methods emerge, security teams must rethink how they inspect and defend encrypted traffic without creating blind spots.
Webinar | 2026 SANS CTI Survey Insights: From Indicators to Insights: How CTI Empowers Both Practitioners and Decision-Maker | Thursday, May 21 at 10:30 AM ET
Spring Cyber Solutions Fest | May 5-7, 2026. Learn from SANS experts and build skills in emerging technologies, cloud security, detection and response, exposure management, and insider threats, malware, and ransomware.