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 UsThe US Cybersecurity and Infrastructure Security Agency (CISA) added an authentication bypass in Palo Alto Networks (PAN) GlobalProtect portal and gateway to its Known exploited Vulnerabilities (KEV) catalog with a mitigation deadline of Monday, June 1 for Federal Civilian Executive Branch (FCEB) agencies. On May 13 PAN released an advisory and updates for the vulnerability, which affects PAN-OS as well as Prisma Access versions 10.2 and 11.2. The advisory states, "issue affects firewalls with GlobalProtect portal or gateway configured when authentication override cookies are enabled and a specific certificate configuration exists." Researchers at Rapid7 detected exploitation of the vulnerability within days of its disclosure; they write that "Successful exploitation of this vulnerability allows a remote unauthenticated attacker to successfully establish a VPN connection through the GlobalProtect gateway of an affected appliance." At the time of the first advisory the vulnerability was rated medium severity, but as reports of exploitation emerged, PAN raised its rating to high severity with highest urgency.

Seems like more and more KEV entries have short timelines. In this case added 5/29, due 6/1. That short timeline reflects the level of malfeasance. Setting aside the urgency in the KEV, and the fact that Palo Alto rates this a high severity/urgency issue, you should be way ahead of that as it's a boundary protection device and should be on your “address flaws immediately” list. The fix is to update PAN-OS or Prisma Access to a fixed version. Note that the fix regenerates the authentication cookie for the GlobalProtect Portal or Gateway using a more secure method, requiring any users to re-authenticate regardless of having a valid cookie. That should be the only visible impact to users.

There are specific conditions to take advantage of this bug, but according to Rapid7, this bug is actively being exploited. While it’s not comfortable to say for many engineers, you’ll have to find a release that fits your train that patches this bug. I would recommend sooner rather than later, just like I would for any other firewall manufacturer.
Palo Alto Networks
Rapid7
The Register
Dark Reading
Help Net Security
The Hacker News
BleepingComputer
SecurityWeek
NIST
Fourteen US legislators have signed a letter to Defense Department (DoD) CIO Kirsten Davies, asking that the agency take steps "to protect US military personnel from the serious counterintelligence and force protection threat posed by the collection and sale of personal information, including cell phone location data, by data brokers." Specifically, the legislators are concerned that the phones used by military personnel are known to be leaking location data; they write that "DoD has now confirmed to Congress that foreign adversaries are exploiting commercially available location data to target U.S. military personnel in war zones." They urge DoD to "disable the advertising ID on all DoD issued smartphones and issue a policy mandating that DoD personnel disable the advertising ID on all personal phones brought onto DoD facilities or taken to overseas deployments; remove web browsers that are designed to facilitate data collection by Google and other advertising companies, such as Google Chrome, from DoD unclassified computers and smartphones ... [and] pre-install on DoD devices and require the use by DoD personnel of privacy-focused web browsers that protect users with anti-tracking cyber defenses, such as ad blocking and the Global Privacy Control (GPC)...; and coordinate with the California Privacy Protection Agency to enroll all DoD personnel who are California residents in the state’s universal data broker Delete Request and Opt-out Platform, and coordinate with other states that create similar systems."

This raises the issue of personal versus corporate devices, and the OPSEC risks when allowed on-site. While you don't face the same risks as DOD, it's not a bad idea to talk through the risks they introduce and make sure that you've got appropriate compensating controls. Smartphones are so ubiquitous, it's easy to overlook that people have a powerful two-way recording and transmitting device, with camera, in their pocket.
Two updates to Connecticut Data Privacy Act (CTDPA) are set to take effect on July 1, 2026, and Connecticut Governor Ned Lamont has also now signed into law Senate Bill 4 (SB4), which includes several provisions intended to provide residents with greater personal data protection, including additional amendments to the CTDPA. The initial updates passed in May lower the threshold of the law’s applicability based on the number of state residents whose data a company processes, from 100,000 to 35,000. The updates also expand the scope of the law to include businesses that process sensitive data or sell personal data. There are additional protections for minors and for certain AI practices. SB4, which takes effect October 1, 2026, includes provisions requiring the Commissioner of Consumer Protection to establish an accessible deletion mechanism program, requiring data brokers to register with the state, redefining "facial recognition technology" and "publicly available information," and prohibiting the sale, sharing, transfer or allowance of access to precise geolocation data.

Given the continuing lack of US national data privacy legislation, states will continue to raise the bar to try to protect consumers. This one makes needed advances on addressing some controversial topics, like direct-to-consumer genetic services, data broker registration and disclosure, and other areas. Make sure your legal counsel is aware of the legislation.
This move aligns with a broader trend of states adopting California-style privacy protections. While a comprehensive, GDPR-like federal data privacy law remains the ultimate goal, states will continue enacting localized legislation to protect their residents in the absence of national standards.

The new CTDPA threshold is just about 1% of the state's population, and also includes a provision making the CTDPA applicable to businesses that process sensitive data or offer personal data for sale regardless of size. If these changes sound familiar, they were inspired by California's "Delete Act," requiring the creation of a state portal for residents to delete their information from registered data brokers with a single click. If you're processing sensitive data for Connecticut residents, pay close attention to requirements and deadlines; some changes, like the threshold change, go into effect July 1, while others, like the delete portal and use of personal data to train AI, go into effect October 1. The updates change the definition of sensitive data to include certain types of government identifiers, financial account-related elements, and SNS, and also add an express prohibition on selling sensitive data without consumer consent. Read the alert from Wiley Law for considerations of immediate actions required.

Data brokers operate in an ethically gray domain. One necessary step in regulating them is identifying them. We need severe penalties for dealing in PII and failing to register.
StateScoop
Wiley Law
Inside Privacy
Legiscan
CGA
Gogs, an open-source project allowing developers to run their own self-hosted Git services, has a critical vulnerability affecting all supported platforms, which as of this writing has not been fixed by Gogs maintainers and has not been assigned a CVE. Rapid7 reports that any authenticated user can achieve remote code execution on the server by using a malicious branch name when creating a pull request, exploiting the "rebase before merging" merge operation to inject the '—exec' flag into 'git rebase.' The researchers rated this flaw with a CVSS score of 9.4, noting that while rebase merging is not on by default, Gogs default settings permit an attacker to create and become the owner of an account and a repository, then enable rebase merging with a settings toggle. At least four other argument injection flaws in Gogs have been patched since 2024, but this attack bypasses the measures that hardened other vulnerable functions. Rapid7 recommends that defenders search for a specific error as an indicator of compromise (IoC) in the Gogs server logs, as well as possible artifacts, tokens, or payload files. While Gogs acknowledged Rapid7's report of this flaw on March 28, 2026, maintainers have not released a patch or communicated further. Users can mitigate by disabling open registration, preventing users from creating repositories, and continually auditing the "rebase before merging" setting, as "there is no global or organization-level setting to restrict this."

Read that again: while the Gogs rebase merging feature is off by default, and self-registration is on by default, the attackers are able to create an account and repo and then turn it on. Once on, RCE can be used to access any repo on the server, public or private, possibly accessing secrets in a repo or compromising the server. Until there is a fix, you're going to want to disable self-registration, limit repository creation, and watch the rebase merge setting. Rapid7 published an IoC to help you keep an eye on things. Gogs advises checking for updated versions weekly following the supported upgrade paths, which means you can't skip minor versions.

It’s been a while since we’ve seen a remotely exploitable Windows service on a domain controller being exploited like this. I would recommend not just patching but also checking to ensure that your endpoint protection can detect this exploit and under what conditions. This is the first remotely exploitable bug I can remember in which we have AI Agents that can potentially modify the code to work around existing protections.
The Achilles' heel of open-source projects is their time-to-patch, as they rely heavily on volunteer labor. Nevertheless, their patch cycles remain competitive with those of commercial, for-profit, security vendors.

The further up in the supply chain a vulnerability is, the greater the number of processes it might contaminate.
Rapid7
SecurityWeek
The Register
The Hacker News
BleepingComputer
Centre for Cybersecurity Belgium (CCB) has updated its advisory for Microsoft's May 2026 Patch Tuesday to include a warning that the Windows Netlogon vulnerability (CVE-2026-41089) is being actively exploited. The critical remote code execution vulnerability can be exploited without "any prior privileges or user interaction and can be executed remotely." The flaw is due to a stack-based buffer overflow issue and can be exploited by "send[ing] a specially crafted network request to a Windows server that is acting as a domain controller." CCB urges users to apply patches as soon as possible. Microsoft released fixes for the vulnerability on Tuesday, May 13, and updates are available for Windows Server versions 2012 and newer. "The Netlogon Remote Protocol, [is] an RPC interface that is used for user and machine authentication on domain-based networks; to replicate the user account database for operating systems earlier than Windows 2000 backup domain controllers; to discover, manage, and maintain domain relationships of domain members and domain controllers across domains."

The patches for the flaw were released in last week's "Patch Tuesday" update. Track getting those deployed, as you're probably down to servers or other specialized environments. Make sure ALL of your DCs are updated.
Serious vulnerability alert: Don’t wait for CISA KEV updates. Be proactive and patch your Windows Server software now.
Help Net Security
BleepingComputer
SecurityWeek
CCB
MSRC
Microsoft
NIST
The US Department of Commerce's Office of the Inspector General (DOC OIG) performed an audit of the US National Institute for Standards and Technology (NIST), evaluating to what extent NIST's management of the National Vulnerability Database (NVD) is timely, effective, and sustainable. The OIG states that while enriched NVD records are a vital resource for cybersecurity professionals, NIST has failed to meet this standard. The report cites four main problems, the first of which is a growing backlog of unprocessed vulnerabilities due to unrealistic plans, inadequate actions, ineffective prioritization, and siloed enrichment sources. The OIG urges a comprehensive strategic plan for the NVD's overall role and a plan for managing the backlog with specific analysis of capacity, target dates and milestones, and prioritization processes. The second problem is several inefficiencies in the enrichment process. The OIG believes that shifting analysts' time away from severity score calculation could save NIST approximately $800,000, and suggests that the NVD make use of external enrichment for Common Platform Enumeration (CPE) applicability statements. The third problem is unnecessary duplication of parallel enrichment work by NIST and by the CVE program run by the US Cybersecurity and Infrastructure Security Agency (CISA). The OIG believes that lack of coordination with CISA has already led to $200,000 in waste. The fourth problem is a lack of transparent communication about the state of the backlog, which frustrates stakeholders and degrades confidence in the program, and should be resolved with a clear communication strategy. NIST responded to a draft of the report, concurring with all recommendations and outlining efforts to enact them, while taking issue with the report's characterization of NIST through subjective language, lack of context, and lack of acknowledgment for NIST's obligations under US law to perform certain NVD functions.

As uncomfortable as this sounds, one does have to wonder if decentralizing this would provide more timely access to the information. Having a single large funnel like NIST and the NVD does mean there will be some backlog. I’m more concerned about the upcoming deluge in this space, so this report is timely.
The OIG report is just stating the obvious for anyone in cybersecurity. Unfortunately, government agencies often get caught up competing with one another instead of collaborating. Honestly, it might be time for NIST to hand this responsibility over to a non-profit organization to manage.

The lack of enrichment on CVEs has been a challenge, and having that information is helpful with doing analysis and prioritization. That said, with the rate of flaw discovery, anything to make the supporting processes from NIST and CISA NVD & CVE management more efficient, in an era of shrinking budgets, will hopefully help us all.

The currently available resources are not up to the task. While this is partially a budget allocation issue, money alone cannot expand the resources. Training takes time.
Google has updated the Chrome stable channel to version 148. The newest version of the browser includes fixes for 151 security issues, 22 of which are rated critical. The majority of the critical vulnerabilities are use-after-free issues. Google detected 134 of the vulnerabilities internally. Two of the critical flaws were awarded $43,000 bug bounty payments: an out-of-bounds write issue in GPU (CVE-2026-9872) and a use-after-free issue in network (CVE-2026-9873). Three additional vulnerabilities were found by external researchers: a use-after-free vulnerability in Dawn (CVE-2026-9874), an out-of-bounds read in WebGL (CVE-2026-9875), and a use-after-free issue in WebGL (CVE-2026-9876).

Don't ignore that Update button. Note that Chromium-based browsers like Brave, Edge, Opera, etc. also have updates. While you're looking, make sure that Firefox update from May 26 also got deployed.

Google says "Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL." But they never say these tools weren’t used (or were used and didn’t work) *before* releasing the code.

Browsers are so complex and are changed so often that is not possible to know that the one that one is using is in a trustworthy state. Moreover, there are so many instances of them, each used for multiple applications, that the value of a successful compromise makes them attractive targets. Prefer purpose built clients for sensitive applications.
Dutch Police in collaboration with the National Cyber Security Centre of the Netherlands (NCSC-NL) announced on May 28, 2026 that they had taken down the infrastructure of a large botnet located in the Netherlands. Following a report from a security researcher, the authorities discovered 200 servers hosting a botnet that controlled at least 17 million devices, seized several of these servers, and directed the hosting provider to take the botnet offline due to "criminal activities." The press release did not include specific details on known attacks from this botnet, nor what type of devices were involved, but the NCSC-NL links to a recent article they published on residential proxy networks, explaining that these can range from legitimate voluntary proxy services, to other services that make the user's device part of a proxy network without their knowledge, to malware that infects a device and establishes a proxy connection. The residential IP addresses of devices in these networks make malicious traffic routed through them more difficult to detect and block. The NL Times alleges that the botnet taken down by this action was related to a Russian residential proxy service called ASOCKS, but this has not been independently confirmed. This law enforcement action follows closely on arrests and seizures by the Netherlands Fiscal Information and Investigation Service (FIOD) in connection with a Russian web hosting company under sanctions by the EU.

When I read a story like this, I go two places: First I applaud the agencies, in this case the Dutch Police & NCSC-NL, for the takedown; second, I check my IoT devices to make sure they're copacetic. How the heck did there get to be so many devices on our home networks? These days, with all the dependencies on your Internet connection, you need to be a bit less cavalier about booting your Internet gateway, but you should still make sure it's set to automatically apply updates, when the impact is minimal, and then check to see that it really is keeping up. Also check the configuration to make sure management is still not allowed externally, that the strongest possible authentication is used, and that the configuration is still as expected — no surprises or unknowns.
Kudos to law enforcement for an excellent operation. While the specific types of compromised devices haven’t been disclosed, the sheer scale (17 million) strongly suggests consumer IoT devices. As security professionals know, consumer hardware is rarely updated and routinely lacks robust access controls. Unfortunately, this leaves these devices highly susceptible to being corralled by the next botnet herder.
NCSC-NL
Ars Technica
The Register
The Hacker News
BleepingComputer
SecurityWeek
The FBI's Internet Crime Complaint Center (IC3) has published a public service announcement warning that cybercriminals are spoofing the Fédération Internationale de Football Association (FIFA) websites in attempts to steal sensitive information. The June issue of the SANS OUCH! newsletter also addresses FIFA scams, which prey on fans eager for tickets, streaming opportunities, and merchandise. FIFA 2026 World Cup matches will be played in Canada, Mexico, and the US between June 11 and July 19, 2026.

If you're doing phishing exercises, it's a good time to consider World Cup themed lures to accompany a message to not get caught up in the excitement of the pending FIFA events. The IC3 bulletin includes spoofed domains to add to your blocking, along with tips, some well-known, that are easily rolled into your message to users.

As with any large event, scammers will be in full force. What I would be looking out for is a social media lure that is AI-generated to lure people to sites.
Cybercriminals are highly opportunistic, always looking to capitalize on world events. The best defense against these tactics remains the classic rule: Stop, Think, Act. It’s an elementary school strategy that remains one of our most effective tools in cybersecurity.

This is an evergreen story. Substitute “latest popular topic/event” for FIFA and the advice given stands.
Charter Communications, a Fortune 100 US telecom and media corporation, confirmed in a May 26 statement to news sources that it experienced a data breach. Charter stated, "We are aware of the situation, following our security protocols and are in the process of alerting appropriate authorities. No sensitive personal information (PI) or customer proprietary network information (CPNI) data was exfiltrated by the threat actor as a result of recent activity," but the company has offered no further information about the timing, nature, or scope of the breach, and has not verified any threat actor claims. CPNI is a type of data regulated by US law, designating information about a telecom customer's phone usage data, call patterns, charges, services, and other details, in order to limit how this information may be controlled and shared. On May 28, the Charter breach was added to Troy Hunt's HIBP, connected with a dataset published online that included 4.9 million unique email addresses along with names, physical addresses, and phone numbers, plus a subset including Charter employees' job titles.

ShinyHunters is taking credit for the breach, claiming to have 42 million records containing PII, and is attempting to extort ransom in exchange for the data not being released. ShinyHunters leverages captured credentials to take advantage of SSO and then access SaaS applications such as Salesforce, MS 365, Google Workspace, SAP, Slack, etc. This is a good time to make sure you've got phishing-resistant MFA in place.
BleepingComputer
BleepingComputer
SecurityWeek
The Register
HIBP
SANS Internet Storm Center StormCast Tuesday, June 2, 2026
Netlogon Exploit; Unidentified RAT; Windows Netlogon Exploited; RedHat npm Affected; Dashlane Bruteforce Attack
https://isc.sans.edu/podcastdetail/9954
Unidentified RAT pushes NetSupport RAT
https://isc.sans.edu/diary/Unidentified+RAT+pushes+NetSupport+RAT/33034
CVE-2026-41089: Windows Netlogon Vulnerability Exploited
RedHat npm Packages Affected
https://www.aikido.dev/blog/red-hat-npm-packages-compromised-credential-stealing-worm
Dashlane Locking Accounts after Brute Force
https://status.dashlane.com/pages/5aabcb89fccc4b04d3774443
My Upcoming Classes
https://www.sans.org/profiles/dr-johannes-ullrich
SANS Internet Storm Center StormCast Monday, June 1, 2026
Bitskrieg; Gogs Unpatched Vuln; Oracle Critical Updates; PAN-OS Exploited
https://isc.sans.edu/podcastdetail/9952
Announcing Bitskrieg
https://deadeclipse666.blogspot.com/2026/05/announcing-bitskrieg.html
Vulnerability in Gogs
https://www.rapid7.com/blog/post/ve-authenticated-rce-via-argument-injection-gogs-unfixed/
Oracle Critical Security Patch Update Advisory - May 2026
https://www.oracle.com/security-alerts/cspumay2026.html
GlobalProtect Authentication Bypass Vulnerabilities CVE-2026-0257
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
If your hybrid network feels like a digital city at risk, you’re ready to join Operation Horizon. AWS, Akamai, Palo Alto, and 2Bsecure join AlgoSec in a game-inspired webinar where you'll encounter real Zero Trust challenges and unlock expert guidance. Register now; the mission begins tomorrow.
SANS 2026 Government Cybersecurity Readiness (Survey Insights Event) | Is the public sector ready for the next cyber threat? Explore key findings, emerging risks, and resilience strategies. Recording available now.
ICS Summit Solutions Track | Tuesday, June 9 | Chaired by Dean Parsons, see live demos, real-world attack case studies, and proven OT/ICS defenses.
Webinar | The Exposure Gap: From Vulnerability Management to AI-Driven Attack Surface Control | Tuesday, June 16 | Learn how organizations can close the growing gap between exploitable vulnerabilities and limited remediation capacity.