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 UsPalo Alto Networks (PAN) has published a security advisory disclosing a critical flaw in PAN-OS that is under active exploitation but will not be patched until May 13, 2026 at the earliest. CVE-2026-0300, CVSS score 9.3, allows an unauthenticated attacker to execute arbitrary code with root privileges by sending specially crafted packets, due to a buffer overflow vulnerability in the PAN-OS User-ID Authentication Portal, affecting PA-Series and VM-Series firewalls. Devices are vulnerable only if both of the following conditions are true: the User-ID portal has been configured, and there is "an interface management profile with response pages enabled and associated with an external/internet-accessible interface." Prisma Access, Cloud NGFW, and Panorama appliances are unaffected. PAN states that "this issue will be fixed in upcoming releases of PAN-OS," versions 10.2, 11.1, 11.2, and 12.1, which are anticipated on May 13 or May 28 depending on the version. While awaiting patches, PAN strongly recommends users disable User-ID Authentication Portal if not required, and otherwise "Restrict User-ID™ Authentication Portal access to only trusted zones ... disable Response Pages in the Interface Management Profile attached to every L3 interface in any zone where untrusted/internet traffic can ingress ... [and] keep Response Pages enabled only on interfaces in trust/internal zones where legitimate users' browsers ingress." PAN's Unit 42 reports unsuccessful exploitation attempts starting April 9, but a week later attackers achieved RCE and injected shellcode; by April 29, the attackers were able to achieve RCE on a second device and download network tunneling and proxy tools. The US Cybersecurity and Infrastructure Security Agency (CISA) added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on May 6, with a remediation deadline of May 9.

CVE-2026-0300 is one of those vulnerabilities where the nuance matters. On paper, this is absolutely a “pay attention now” issue: unauthenticated, network reachable, buffer overflow, potential root-level code execution on a firewall, confirmed exploitation in the wild, and added to CISA KEV. That combination should make every defender sit up a little straighter. But this does **not** mean every Palo Alto Networks firewall on the internet is immediately exploitable. The vulnerable condition depends on the User-ID Authentication Portal (Captive Portal) being enabled and exposed to untrusted networks or the public internet. Also, from the research side, public PoC availability does not automatically equal reliable weaponization. We at Rapid 7 Labs have looked at the available PoC, and as of now, it is not a complete “copy, paste, root shell” situation. That said, I would not get comfortable. Once patches land, diffing becomes easier. AI-assisted analysis may accelerate some parts of that workflow. And when exploitation has been confirmed, when appliances are exposed to the internet, and when patch availability is delayed across versions, defenders do not need social media hype to justify action. The practical guidance is pretty simple: 1. Check whether User-ID Authentication Portal is enabled, 2. Check whether it is reachable from untrusted networks like the internet (Captive portals never should be), 3. Restrict it to trusted internal zones or disable it if it is not required (This is a non-default feature btw), and 4. Prioritize patching as fixed versions become available. This is not a reason to panic, but it is absolutely a reason to verify exposure today.

It's important to note that you need to make sure that your configuration is affected; don't panic. Attackers are going to fingerprint and go after your device regardless of being vulnerable, so make sure that you don't expose any management interfaces and that you limit access to the Authentication Portal, then make sure you're ready to apply the updated PAN-OS as quickly as possible after the release. CVE-2026-0300 is in the CISA KEV with a due date of May 9th, which means you can only apply the mitigations or verify you're not in a vulnerable configuration. Expect DHS reporting requirements for federal agencies with similarly short timeframes.

If you’re a PAN customer, get your high-level management to ask PAN for details on what changes PAN is making in its software testing process and release criteria — a buffer overflow in an authentication portal ought to be found very early in development in security software, never by attackers first.
PAN
Unit42
BleepingComputer
The Hacker News
SecurityWeek
CyberScoop
On Thursday, May 7, Ivanti released updates to address five high-severity vulnerabilities in on-premises Ivanti Endpoint Manager Mobile (EPMM). Ivanti says that one of the flaws, CVE-2026-6973, is being actively exploited. The vulnerability is due to improper input validation in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1, which allows a remotely authenticated user with administrative access to achieve remote code execution. Users are urged to update to a fixed version of Ivanti EPMM. Ivanti also recommends that users review accounts with Admin rights and rotate associated credentials. The other four vulnerabilities addressed in the updates are two improper access control issues: CVE-2026-5786 and CVE-2026-5788; and two improper certificate validation issues: CVE-2026-5787 and CVE-2026-7821.

CVE-2026-6973, improper input validation, CVSS score 7.2, is also in the CISA KEV with a due date of Mother's Day (May 10). This flaw requires admin privileges to exploit. Don't focus on that one flaw, there are others, and while the other vulnerabilities are more severe, one fix covers them all: update to the latest version of EPMM, 12.6.1.1, 12.7.0.1 or 12.8.0.1. If you're still on version 12.6 or 12.7, you also need to move to 12.8. Don't forget to review admin accounts and rotate credentials where necessary.

The recommendation to review administrator accounts and rotate credentials is important, as patching alone may not address post-compromise activity. As we say from the recent Stryker incident where their own MDM was used to wipe all their managed devices, any system used to manage mobile endpoints should be treated as a high-value asset and protected accordingly.
The developer of DAEMON Tools, a virtual drive and disk image shareware program, has confirmed that its supply chain experienced "unauthorized interference" resulting in the release of compromised installation packages for DAEMON Tools Lite version 12.5.1. Disc Soft Ltd. credits Kaspersky for identifying and analyzing the compromise. Disc Soft "received notification" of the issue around 7:00 GMT on May 5, 2026, and within 12 hours had isolated and secured affected systems, removed unsafe files from distribution, audited the build and release pipeline, rebuilt and validated installation packages, and strengthened security controls and monitoring. DAEMON Tools Lite version 12.6.0.2445 is the latest release, which "no longer exhibits the behavior" discovered by Kaspersky. No other products were affected, including DAEMON Tools Ultra and DAEMON Tools Pro. Disc Soft recommends that any users who downloaded DAEMON Tools Lite 12.5.1 during the affected period uninstall the application, run a full system antivirus scan, and then download version 12.6.0.2445 or later. Kaspersky reports that the supply chain had been compromised since April 8, delivering a multi-stage infection: the initial payload collects and relays network and device information to the attacker's server, and the secondary payload is backdoor malware. While the reconnaissance stage reached over 100 organizations across Russia, Brazil, Turkey, Spain, Germany, France, Italy, and China, Kaspersky only observed the backdoor stage reaching about a dozen organizations profiled by the first stage, mainly government, science, manufacturing, and retail sector systems in Russia, Belarus, and Thailand. Disc Soft is continuing to investigate the root cause of the attack, and has not verified any attribution claims.

Points to Kaspersky for reporting the issue to Disc Soft, and kudos to Disc Soft for jumping on it, both releasing a fixed version quickly and taking steps to remediate and prevent recurrence. Regardless of VDP problems introduced by "AI Slop," acting on reported issues remains important. Verify sure you're ready to respond to input like this, to include fixes as well as addressing any infrastructure shortcomings and messaging. May be a good topic for your next tabletop. If you're running the free DAEMON Tools Lite version 12.5.1, don't just update — uninstall, scan your system for issues, then install version 12.6. Since you're looking at your DAEMON Tools status, make sure that any paid versions are also up to date.
Targeting a product like DAEMON Tools says that the attacker had a specific target or targets in mind. That level of analysis speaks to it being nation-state sponsored. Attacks like this are incredibly difficult to defend against, as the source is typically trusted. If you’re caught up in this supply chain attack, follow the mitigation guidance and monitor your network.

Suppliers should be held financially liable for damages from shipping malicious, as opposed to merely shoddy, code.
DAEMON Tools
Ars Technica
BleepingComputer
The Record
TechCrunch
SecurityWeek
This week, Cisco published nine security advisories to address 14 CVEs across its product line. Five of the CVEs are rated high-severity: a remote code execution vulnerability (CVE-2026-20034) and a server-side request forgery vulnerability (CVE-2026-20035) in Cisco Unity Connection; a SNMP denial-of-service vulnerability (CVE-2026-20185) in Cisco SG350 and SG350X Series Managed Switches; a remote device denial-of-service vulnerability (CVE-2026-20167) in Cisco IoT Field Network Director; and a connection exhaustion denial-of-service vulnerability (CVE-2026-20188) in Cisco Crosswork Network Controller and Cisco Network Services Orchestrator, which requires a manual reboot for system recovery. The advisories also address medium-severity vulnerabilities in Cisco Slido, Cisco Prime Infrastructure, Cisco Identity Services Engine, and Cisco Enterprise Chat and Email Lite Agent.

Time to make sure all your Cisco products, not just your routers, are up to date. We all caught the manual reboot for Cisco CNC and NSO, but don't overlook that CVE-2026-20188 can be used to "permanently" crash these systems, also requiring manual intervention. Move to CNC 7.2 and NST 6.4.1.3 or 6.5, including the manual restart, before active exploitation ramps up; this is less painful than recovery from a permanent crash.
Operators of US critical infrastructure (CI) must take proactive steps to ensure they are ready to sustain essential operations under the conditions of a geopolitical crisis, says new guidance from the US Cybersecurity and Infrastructure Security Agency (CISA). The "CI Fortify" initiative urges owners and operators to focus immediately on isolation and recovery capabilities. "Operators should assume that in a conflict scenario third-party connections–such as telecommunications, internet, vendors, service providers, and upstream dependencies–will be unreliable and that threat actors will have some access to the OT network." Preparing for isolation ensures service does not shut down during an emergency as a result of cyberattacks or degraded communications via third-party connections. Operators should set a service delivery target for critical customers, determine the infrastructure needed to meet that target while isolated, update business continuity plans and engineering processes to anticipate weeks or months of isolation while still maintaining safe operations, and track isolation information from CISA and the Sector Risk Management Agency (SRMA). Preparing for recovery includes "documenting systems, backing up critical files, and practicing the replacement of systems or the transition to manual in case isolation fails and components are rendered inoperable," as well as addressing communications dependencies and workarounds with managed service providers, system integrators, and vendors. CISA notes that this emergency planning and documentation will aid in isolating compromised systems from unauthorized access and will yield better overall continuity across all disruptions. The CI Fortify page also includes a call to action for non-operators, describing the roles of vendors and suppliers, managed service providers and integrators, and volunteers in protecting critical infrastructure.

Do you know if any OT/Industrial Control Systems in your shop are considered critical infrastructure? How about by local designation, versus by CISA? If you haven't recently verified that designation, it'd be good idea to revisit to make sure you're not missing anything. Now ask: what's your resilience stance for these systems? With that in mind, review the CI Fortify alert for things you can do and resources you can leverage. I'm sure you've been told by people we trust that systems can operate in isolation, or that we can restore systems quickly, but have you verified that? That could be an enlightening project.

The electrical grid represents an existential vulnerability for the US. Without it, perhaps as few as ten percent of us can survive for thirty days. The operators of the grid have a demonstrated ability to recover from component failures or changes to capacity or load. They are pretty good at recovery after extreme weather events. Against cyberattacks, kinetic attacks, and EMP, not so much. While CI Fortify may help, the industry has proven to be slow to change.

While this guidance is aimed at US critical infrastructure, the lessons apply globally. Regional conflicts increasingly include cyber activity against civilian infrastructure, and geography offers little protection. Operators of critical services, wherever they are based, should plan for isolation, degraded connectivity, and recovery from destructive attacks.
Sound guidance from CISA. That said, organizations, both private and public, that operate critical infrastructure should already have business continuity plans in place that include recovery. If they don’t, well, that’s not exhibiting a reasonable standard should they suffer a breach.
CISA
SecurityWeek
The Record
CyberScoop
The Australian government has announced the appointment of the country's Cyber Incident Review Board, as established under the Cyber Security Act 2024. The review process will take place after a cyber incident has occurred and the initial investigation and response are complete. The purpose of the Board is to "identify the contributing factors to cyber incidents to help sectors prepare for future cyber attacks ... [and] provide recommendations to government and industry on its findings." The Board will not make any determinations as to who is at fault for a cyber incident. The Board may request information from entities involved in the cyber incidents they investigate; if the entities are not forthcoming with the requested information, the Board Chair will have "limited information gathering powers to compel relevant information from entities involved." Narelle Devine, Telstra Global Chief Information Security Officer, will chair the Board, which will have six additional standing members. The Board will also solicit applications for and select members of an Expert Panel with expertise in cyber security, legal matters, and other relevant sector‑specific fields to support Board in the review process.

Good to see Australia establishing this review board focusing on “post-incident reviews of significant cybersecurity incidents” and pledging to deliver “actionable recommendations to the Federal Government and to industry.” The Australian government has been proactive in driving government and industry to evolve to essential security hygiene levels — over time an effective IRB can help accelerate this even with limited powers.

This is a very welcome development and something I have been calling for over 10 years: https://www.theregister.com/security/2017/11/24/treat-infosec-fails-like-plane-crashes-but-hopefully-with-less-death-and-twisted-metal/1225317. Independent post-incident reviews without a blame culture can help other organisations learn and improve their cybersecurity posture.

This is going to be interesting. These are non-punitive, no-fault reviews to help others prepare, and the board has been formed with seven appointees. Confidentiality and information protection are key to a function like this. The potential benefit is huge with the caveat that, of late, we keep coming back to cyber hygiene basics as root causes.
Congratulations to Australia, as they now join the EU and UK in having incident review boards. What will be even better is coordination of cyber incident investigation amongst nations. Hopefully the US will reestablish its Cyber Safety Review Board and rejoin this important endeavor.
The US Federal Trade Commission (FTC) has reached a proposed settlement with Kochava, an Idaho-based data broker, and its subsidiary Collective Data Solutions, over the company's sale of geolocation data. Among the data Kochava sells is geolocation data that can pinpoint a device's location to within 10 meters. An FTC investigation prompted a 2022 lawsuit that alleged Kochava was selling this information without consumers' knowledge or consent. The settlement "prohibit[s] ... Kochava and its subsidiary from selling, sharing or disclosing sensitive location data without consumers’ affirmative express consent." The settlement also requires Kochava and Collective Data Solutions to develop and implement a program to ensure that they do not disclose sensitive location data; implement a program to ensure that consumers have provided consent for any and all location data obtained by the company; notify the FTC if they become aware that a third-party has shared sensitive data in violation of the requirements; allow consumers to request the names of businesses or individuals to whom their data were sold, providing consumers with a clear and simple way to withdraw consent for the sale of device location data; and develop "a data retention schedule that will require the deletion of data on an established timeframe."

This started back in 2023 and really put data brokers on notice that they are going to have to ensure they have withdrawable consent, and a data retention schedule, before sharing users' data. You really don't want to get crosswise with the FTC; make sure that you know what data you're sharing, how it was obtained/retained and permissions are appropriate. Kochava was lucky to avoid a fine. FTC rulings historically come at a (significant) cost and don't involve a court battle as was done in this case.
Laws and regulations are slowly catching up to an industry peddling user data. There are now four states (CA, VT, TX, and OR) with data broker laws, as well as 20 states that have enacted comprehensive consumer privacy laws. It’s starting to feel that data brokers’ days are numbered, which is a good thing from my perspective.
The Record
HIPAA Journal
Gov Infosecurity
FTC
FTC
FTC
Instructure, the company which maintains the Canvas learning management system (LMS) platform, has released its final status page update responding to a data breach disclosed on May 1, 2026. The company states that Canvas is fully operational, and recommends users enforce MFA on privileged accounts, review admin access, and rotate API tokens or keys. CISO Steve Proud stated in previous announcements that an unauthorized threat actor accessed names, email addresses, student ID numbers, and messages among users, also causing service outages and prompting security measures that included revoking credentials and rotating application keys. Affected institutions are publishing their own notices and communicating with students and faculty about the impact of the breach, including encouraging vigilance for phishing attempts due to the data theft. Harvard University, Rutgers University, Duke University, the University of Minnesota, and others have reported unauthorized posts appearing on Canvas allegedly by the threat actor. Instructure has not disclosed the nature or scope of the breach, and has not yet communicated through other channels nor commented to news sources.

You know how you have services that support MFA but you've been kicking the can on implementing that? Me too; it's time to go there. Not just for admin accounts, but for everyone. Remember those privilege escalation flaws that keep coming up? Now overlay the AI worker accounts that seem to be propagating, which seem to need lots of privilege to "just work." Line up your use cases and start plugging away, and plan to iterate more than once as you gain experience and as offerings mature.

A timely reminder that outsourcing to third parties requires organisations to understand how they should respond to a compromise of their systems hosted by that provider. Organisations should ensure contracts with cloud and SaaS providers include clear obligations for incident notification, transparency, and support during a breach.

While all Internet-facing applications must offer strong authentication options, it is often difficult to get one's users and customers to opt in.
Instructure
Dark Reading
TechCrunch
BleepingComputer
Harvard Crimson
Rutgers
Duke Chronicle
Star Tribune
Matthew Issac Knoot, of Nashville, Tennessee, and Erick Ntekereze Prince, of New York, have each been sentenced to 18 months in prison for their roles in schemes enabling North Korean citizens to pose as legitimate US IT workers. Knoot and Prince both hosted laptop farms at their homes, installing remote desktop applications on the machines to make it appear that people in North Korea were working from US residences. The fraudulent employment of the workers affected nearly 70 US companies. Knoot was sentenced in Tennessee on May 1; the judge ordered him to pay $15,100 in restitution to the companies that hired the fraudulent workers, and to forfeit an additional $15,100. Prince was sentenced in Florida on May 6; the judge also ordered him to forfeit $89,000, the amount he was paid to assist with the scheme.

This is really a message to others who are working to bypass restrictions on working with North Korea; it's a federal crime. The DOJ's National Security Division continues to pursue those conducting similar schemes which threaten national security. In the meantime, be diligent with remote workers, verifying not only that they are who they claim to be, but also that corporate assets are truly used as intended. Consider in-person validation which is harder to spoof. If you think you have discovered a laptop farm, the FBI would like to hear from you.
In this case the sentence feels 'light' given the harm caused to the companies. Harm includes more than just the amount of money lost.
CyberScoop
The Register
BleepingComputer
US DoJ
A US federal judge in Ohio has sentenced Deniss Zolotarjovs to 102 months (8.5 years) in prison for his role as a negotiator for several ransomware groups. Zolotarjovs, who is from Latvia, was arrested in the country of Georgia in 2023 and extradited to the US in 2024. In July 2025, he pleaded guilty to charges of money laundering and wire fraud. While he was not involved in launching the ransomware attacks, Zolotarjovs analyzed data stolen from ransomware victims to determine what level of ransom should be demanded and whether the data should be published if the victims refused to pay.

Zolotarjovs supported the Conti ransomware gang, which used many names when extorting victims including Conti, Akira, Karakut, Royal, TommyLeaks and Schoolboys. He was very effective at finding ways to ensure a ransom payout from victims. While the investigation provided information about other gang members, don't drop your guard when it comes to ransomware, as gangs continue to recruit and to be lucrative.

This case shows that ransomware gangs depend on more than just the people who deploy malware. Negotiators, money launderers, access brokers, and data analysts all play important roles in the criminal ecosystem. Law enforcement action against these supporting roles is essential to disrupting ransomware groups.
SANS Internet Storm Center StormCast Friday, May 8, 2026
AI Generated Dashboard; Ivanti Patches; Redis Vuln
https://isc.sans.edu/podcastdetail/9924
An Adaptive Cyber Analytics UI for Web Honeypot Logs
https://isc.sans.edu/diary/An+Adaptive+Cyber+Analytics+UI+for+Web+Honeypot+Logs+Guest+Diary/32962
Ivanti May Patchday
Redis Security advisory: [CVE‑2026‑23479] [CVE‑2026‑25243] [CVE-2026-25588] [CVE‑2026‑25589] [CVE-2026-23631]
SANS Internet Storm Center StormCast Thursday, May 7, 2026
.DE DNSEC Fail; PAN OS 0-Day Patched; Android Security Bulletin
https://isc.sans.edu/podcastdetail/9922
Technical issue with .de domains
https://blog.denic.de/en/technical-issue-with-de-domains-resolved/
CVE-2026-0300 PAN-OS: Unauthenticated user initiated Buffer Overflow Vulnerability in User-ID Authentication Portal
https://security.paloaltonetworks.com/CVE-2026-0300
Android Security Bulletin — May 2026 CVE-2026-0073
https://source.android.com/docs/security/bulletin/2026/2026-05-01
SANS Internet Storm Center StormCast Wednesday, May 6, 2026
Cleartext Passwords in Edge; SSL.com Root Rotation; DAEMONTOOLS Backdoor
https://isc.sans.edu/podcastdetail/9920
Cleartext Passwords in MS Edge? In 2026?
https://isc.sans.edu/diary/Cleartext+Passwords+in+MS+Edge+In+2026/32954
SSL.com rotates its root certificate today
https://isc.sans.edu/diary/SSLcom+rotates+their+root+certificate+today/32956
DAEMONTOOLS Compromise
https://therecord.media/hackers-compromise-daemon-tools-global-supply-chain-attack
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Development leaders must scale AI without letting security become a brake. This eBook provides a 4-step blueprint to achieve Secure at Inception, ensuring prevention and velocity reinforce each other. Learn to shift from gatekeeper to enabler, use Snyk Studio to embed guardrails into AI workflows, and future-proof your organization for AI-native applications.
Webinar | SANS 2026 Cybersecurity Readiness in Government Survey Insights: Is the Public Sector Ready for the Next Cyber Threat? | Thursday, May 28 at 10:30AM ET
Webinar | From Alerts to Insight: How Agentic AI Elevates Security Teams | Wednesday, May 27 at 1:00PM ET.
Webinar | Risk-Adaptive DLP Strategy Guide | Monday, May 18 at 3:30PM ET. Learn modern DLP strategies using behavioral context, AI visibility, and adaptive policies to protect data while enabling productivity and reducing risk.