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 Unit 42 has published threat research describing a high severity vulnerability affecting the Gemini AI agent as implemented in the Chrome browser prior to 143.0.7499.192. CVE-2026-0628, CVSS score 8.8, allows an attacker to inject scripts or HTML into a privileged page by convincing a user to install a malicious Chrome extension, due to insufficient policy enforcement in WebView tag in Chrome. Unit 42 notes that exploitation could "[allow] malicious extensions with basic permissions to hijack the new Gemini Live in Chrome browser panel," leading to privilege escalation that gives an attacker control of the device camera and microphone, the ability to take screenshots of websites, and access to local directories and files. Following responsible private disclosure by Unit 42 on October 23, 2025, Google released a fix for the flaw on January 5, 2026. Unit 42's research highlights the unique security risks posed by browsers with agentic AI integration, explaining that the vulnerability allowed an extension with basic permissions through the declarativeNetRequests API to intercept and change the properties of hxxps[:]//gemini.google[.]com/app when loaded in the Gemini panel, giving the extension some of Gemini's powerful and privileged capabilities. "This difference in what type of component loads the Gemini app is the line between by-design behavior and a security flaw. An extension influencing a website is expected. However, an extension influencing a component that is baked into the browser is a serious security risk." Anupam Upadhyaya, senior vice president of product management for Palo Alto Networks' Prisma SASE, stated to Dark Reading that "designers should build in real-time inspection of prompts, AI responses, and rendered content directly inside the browser, where users, data, and AI interact," and consider browsers as both "a primary attack surface and a potential control plane."

The introduction of AI into the browser reintroduces some attack planes, as it's operating at a high privilege level, potentially exfiltrating data, bypassing same-origin policy, and triggering privileged browser functions. Beyond updating to the latest Chrome, consider carefully before adding or enabling AI extensions to browsers.

Using an LLM to browse the internet in 2026 feels like hacking in the early 2000s. Think of it as having a very naive child running through the internet and trusting everything. Not surprising you will see so many different vectors here.
PAN
Dark Reading
ZDNET
The Hacker News
SecurityWeek
The Microsoft Defender Security Research Team has published a blog describing their observation of "phishing-led exploitation of OAuth’s by-design redirection mechanisms." The scheme targets both public and private sector organizations and "uses silent OAuth authentication flows and intentionally invalid scopes to redirect victims to attacker-controlled infrastructure without stealing tokens." The researcher identified and removed several malicious OAuth applications but cautioned that "related OAuth activity persists and requires ongoing monitoring."

This attack is clever. It uses invalid OAUTH information, forcing a redirect to the error site, ensuring a re-authentication event, no SSO, then a malicious ZIP is downloaded. The IoCs from Microsoft include domains and URL patterns which you can filter out to limit this type of attack. Also review Redirect URI and OAUTH 2 best practices to make sure that you've stacked the deck in favor of your users.

Think carefully about the use of federated authentication. There are safer alternatives for convenience.
The US Cybersecurity and Infrastructure Security Agency (CISA) has updated its malware analysis report for RESURGE malware. The updated report offers "deeper technical insight into RESURGE to provide network defenders with enhanced understanding and tools to identify, mitigate, and respond to RESURGE." CISA analysis indicates "that RESURGE can remain latent on systems until a remote actor attempts to connect to the compromised device ... [and] assesses that RESURGE may be dormant and undetected on Ivanti Connect Secure devices and remains an active threat." RESURGE involves the exploitation of CVE-2025-0282, a critical stack-based buffer overflow/out-of-bounds write vulnerability in certain versions of Ivanti Connect Secure, Ivanti Policy Secure, and Ivanti Neurons for ZTA gateways. The updated report includes indicators of compromise (IoCs) and detection signatures.

RESURGE hooks the web process looking for a specific connection attempt, indefinitely. It uses a fake Ivanti certificate to make sure that interaction is with the agent, not with legitimate Ivanti software. Most definitely grab the IoCs for the persistent malware and see if you have remnants. Also watch for the transmission of the fake Ivanti certificate, as it's sent unencrypted. Reference the updated CISA AR25-087A malware analysis report for the latest IoCs and information.
Excellent analysis by CISA. For me, I’d rather skip to the end and just mitigate the threat. If that’s the case, factory reset and update the software to the latest version, does the trick.
BleepingComputer
CISA
CISA
CISA
NIST
Researchers from the University of California, Riverside, have presented a paper detailing new classes of machine-in-the-middle (MitM) cyberattacks that allow Wi-Fi clients to attack other clients on the same network by bypassing Wi-Fi access point (AP) client isolation mechanisms. Dubbed "AirSnitch," the series of attacks break past the isolation meant to protect against ARP poisoning and ICMP redirects; "every tested router and network was vulnerable to at least one attack," including routers from Netgear, Tenda, D-Link, TP-Link, ASUS, Ubiquiti, LANCOM, and Cisco, plus those running DD-WRT and OpenWrt. The attack techniques include abusing a shared Group Temporal Key (GTK), gateway bouncing, port stealing, and combining techniques to obtain full bi-directional MitM. The paper cites three root causes: "First, Wi-Fi keys that protect broadcast frames are improperly managed and can be abused to bypass client isolation. Second, isolation is often only enforced at the MAC or IP layer, but not both. Third, weak synchronization of a client’s identity across the network stack allows one to bypass Wi-Fi client isolation at the network layer instead, enabling the interception of uplink and downlink traffic of other clients as well as internal backend devices." The researchers' techniques can also be used in enterprise networks to steal uplink RADIUS packets and set up a rogue RADIUS server to intercept traffic and credentials. The researchers characterize isolation mechanisms as "inconsistent, ad hoc, and often incomplete," lacking standardization across vendors, and state, "this defense was added by vendors without proper public review. [...] We hope our work motivates standardization groups to more rigorously specify the requirements of client isolation and that Wi-Fi vendors will implement the same more securely." SANS instructors James Leyte-Vidal and Larry Pesce hosted a webinar on Monday, March 2, 2026, evaluating the impact of the findings. Their recommended mitigations include immediately implementing VLAN segmentation and IP spoofing prevention; in the near-term, requesting per-client GTK randomization, implementing MAC spoofing prevention, and centralizing controller decryption; and in the long term, standardizing to MACsec and IEEE 802.11: https://www.sans.org/webcasts/airsnitch-how-worried-should-you-be

Wi-Fi Client isolation is likely enabled if you're using your guest SSID on your AP, as most vendors are enabling that by default for the "guest" network. We've been hearing for years that the best option is to implement VLANs on our Wi-Fi, and I'm sure many of us have been kicking that can down the road. It's time. First, make sure you're on supported devices. Second (good, bad, or otherwise) make sure you're on the latest firmware for you router and that it's keeping you there automatically as this evolves; firmware updates are likely to address isolation. Third, start implementing and testing VLANs.
NDSS Symposium
Ars Technica
TechRadar
Tom’s Hardware
A Greek court has convicted four people associated with Intellexa, a spyware company, on charges related to "illegal wiretapping of government ministers, military officials, and journalists." The four individuals include Intellexa's founder, his former wife and business partner, an Intellexa executive — all of whom were sanctioned by the US government in 2024 — and an individual who owns a Greek company that purchased Intellexa's Predator spyware. All have been sentenced to eight years in prison. In March 2022, a Greek journalist discovered that his phone had been infected with Predator spyware and that "he had been wiretapped by the Greek National Intelligence Service." Several months later, a Greek politician learned that his phone had been infected with spyware as well. In all, Intellexa spyware was found to have been used against more than 90 Greek citizens between 2020 and 2021.

Interestingly, if the conviction and prison sentence stands, countries that have treaties with Greece will no longer be doing business with Intellexa. Arguments persist as to whether spyware such as Predator is good or bad. Even so, make sure your devices are protected from the introduction of spyware like Predator or Pegasus by keeping them updated, only using approved app stores, and limiting functionality in risky areas, such as enabling lockdown mode.
Interesting judgment by the Greek court. Should it be the product vendor who is held liable, or the user, the Greek government in this case? Sure, many products can be used for nefarious purposes, and yes, this product is purpose-built for that scenario, but it was sold to the government. Curious as to your opinion...

This is a story that dates back to a 2022 scandal with a journalist’s phone and spyware. The details here are still fuzzy to me as I am not a lawyer, and definitely not versed in Greek law, but what I will comment on is that if you are going to write sketchy software that spies on people, maybe don't call it “Predator.”
ICIJ
Amnesty
The Record
In a report to their state legislature, the University of Hawai'i said that an August 2025 ransomware attack compromised personal information of as many as 1.24 million individuals at the University of Hawai'i Cancer Center (UHCC). The attack was detected on August 31, 2025, and was disclosed publicly in January 2026; at that time, the number of affected individuals had not been determined. Once the encrypted data were decrypted, UHCC was able to establish that "a majority of the files related to a specific cancer study and largely contained only research data with no Personal Information about the research subjects." Further investigation uncovered " a set of files dating back to the 1990s containing Social Security numbers for study participants. These Social Security numbers were used in the 1990s to identify research participants before UH began using a different convention for identifying research subjects." The University of Hawaii is taking steps to notify affected individuals. They have also strengthened their systems' security measures by deploying endpoint protection software that is monitored 24/7, rebuilding compromised systems, bringing in outside expertise, and other measures.

A lesson learned here about being aware of what information is still around. 30 years ago, many of us used Social Security numbers and other PII more frequently and openly than we do today. While we have changed our processes and protections, what about archived copies of information, which may still include that information? Make sure it's protected/isolated. It's so easy to be dismissive (It's old, no longer accurate, etc.) based on the relevance of the context under which that information was captured, but that PHI/PII is still current and accurate.

What struck me about this story is that data from the 1990s was compromised. One needs to ask the question: is that data is still needed, and if not, why was it not securely removed? Remember, if you don't need the data, you don't need to store it, and therefore you don't have to worry about protecting it.
The US Cybersecurity and Infrastructure Security Agency (CISA) has published an Industrial Control System (ICS) advisory for multiple vulnerabilities in Gardyn Home Kit, a smart indoor vertical hydroponic gardening system. CISA notes that "successful exploitation of these vulnerabilities could allow unauthenticated users to access and control edge devices, access cloud-based devices and user information without authentication, and pivot to other edge devices managed in the Gardyn cloud environment." Two of the flaws are critical: CVE-2025-29631 may allow an attacker to execute arbitrary operating system commands on a target Home Kit; and CVE-2025-1242 is a critical hard-coded credentials issue that may result in an attacker gaining full administrative access to the Gardyn IoT Hub, exposing connected devices to malicious control. Two of the flaws are high severity: CVE-2025-29628 is caused by a Gardyn Azure IoT Hub connection string being downloaded over an insecure HTTP connection, leaving the string vulnerable to interception and modification through a man-in-the-middle attack, and which may result in the attacker capturing device credentials or taking control of vulnerable home kits; and CVE-2025-29629 is caused by Gardyn Home Kit firmware using weak default credentials for secure shell access. Fixes are available and users are advised to update their Gardyn firmware and mobile app as soon as possible.
IoT devices are the new attack surface to exploit, and the bad guys know that. A few reasons: 1) Vendor rush to market; 2) Lack of security engineering experience; 3) Vendor difficulty in updating product; and 4) Poor user administration/monitoring. These four vulnerabilities tick most of those boxes.

If I'm tracking, you have an insecure (cleartext) connection, default credentials, successful MiTM attack, RCE, and lateral movement. Two bits of good news. First, there is no evidence yet of active exploitation, and second, there are fixes which deploy easily. The fix is to update to version 619 or later of the Gardyn firmware and version 2.11.0 or later of the mobile app. After applying the updates, make sure that your settings and schedules are as planned. Also isolate your Gardyn system, as you would other OT systems, limiting access to legitimate authorized devices and use cases.

It’s strange to see CISA issue a warning for a home gardening kit that I am not sure is in wide use. Not sure if this is truly worth the callout, given the difference between a Gardyn Home Kit and, say, a control system in a water utility. It’s good someone is calling it out, but should it be CISA?
South Korea's National Tax Service has apologized for inadvertently publishing a recovery phrase that allowed seized cryptocurrency to be stolen. On February 26, the Tax Service announced that it had seized cash and luxury items from individuals who were delinquent on their taxes. The seized funds included 6.9 billion Korean won (€4.03 million / US$4.7 million) in virtual assets. The announcement was accompanied by a photograph that included a seed phrase that could be used to access cryptocurrency funds. In an odd turn of events, the seized virtual funds were stolen twice. The first time, the funds were taken from the crypto wallet and then returned; the thief claimed to have been acting "out of curiosity." Several hours later, the funds were stolen again and have not been returned. However, as the register notes, "the one tiny upside in this whole mess is that the heist was of course recorded on a blockchain, so the Tax Service has asked Korea’s National Police Agency to track down whoever emptied the wallet."

Remember the Hawaiian Emergency Management Agency report in 2018 with the password on a yellow sticky in the background? Yeah, same idea — be careful what you include when publishing photos and videos, to include meta (EXIF) data. Make sure you include a review process when publishing information, and if you're redacting information, make sure it is securely done so it can't be revealed.
I had to check if we had time traveled to April 1st and it was all a good joke. Unfortunately not the case, and a lesson learned to blur out important details in crime scene pictures before releasing. As the SANS editors often say, evildoers are agile and quick to execute on an opportunity.

The blockchain tells all and never forgets. While it facilitates obscuration by distribution, that takes planning and organization.
Chosun
Heise
The Register
BleepingComputer
Cisco Talos has published a threat spotlight describing a campaign of multi-stage cyberattacks ongoing since December 2025, targeting primarily US education institutions and healthcare facilities with persistent backdoor malware. The attackers gain initial access through social engineering and phishing via email, leading to the execution of a PowerShell script that downloads a Windows batch script dropper, which in turn "orchestrates a DLL sideloading technique to execute the malicious DLL while simultaneously conducting anti-forensic cleanup." The DLL operates as a loader to "download, decrypt, and execute malicious payloads within legitimate Windows processes," ultimately connecting to a command-and-control (C2) IP address resolved through DNS-over-HTTPS (DoH, giving the DLL its nickname, “Dohdoor”) and evading EDR to inject a payload believed to be Cobalt Strike Beacon into legitimate binaries. Talos provides indicators of compromise (IoCs), as well as a ClamAV signature and SNORT security identifiers.

Make sure your team has the IoCs and is making sure you're clean and blocking traffic appropriately, then go talk to your user education team. This appears to start with social engineering and phishing, so we need to make sure we're getting the message across to the users. Make sure they're not just checking the box here — it needs to sink in.
SANS Internet Storm Center StormCast Tuesday, March 3, 2026
Finding URLs in ZIPs in RTFs; Merkle Tree Certificates; Taming Agentic Browsers
https://isc.sans.edu/podcastdetail/9832
Quick Howto: ZIP Files Inside RTF
https://isc.sans.edu/diary/Quick+Howto+ZIP+Files+Inside+RTF/32696
Keeping the Internet fast and secure: introducing Merkle Tree Certificates
https://blog.cloudflare.com/bootstrap-mtc/
Taming Agentic Browsers: Vulnerability in Chrome Allowed Extensions to Hijack New Gemini Panel
https://unit42.paloaltonetworks.com/gemini-live-in-chrome-hijacking/
SANS Internet Storm Center StormCast Monday, March 2, 2026
Reversing Fake Fedex; Abusing .ARPA; MSFT Authenticator Update; Apex One Vuln; Special AirSnitch Webcast
https://isc.sans.edu/podcastdetail/9830
Fake Fedex Email Delivers Donuts!
https://isc.sans.edu/diary/Fake+Fedex+Email+Delivers+Donuts/32754
Abusing .ARPA: The TLD that isn’t supposed to host anything
MC1179154 - Microsoft Authenticator app: Upcoming changes to jailbreak and root detection
https://mc.merill.net/message/MC1179154
SECURITY BULLETIN: Apex One and Apex One (Mac) - February 2026
https://success.trendmicro.com/en-US/solution/KA-0022458
Special Webcast: AirSnitch – How Worried Should You Be?
https://www.sans.org/webcasts/airsnitch-how-worried-should-you-be
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Browse ArchiveStandard detection rules are missing the newest evasion tactics. The Red Report 2026 maps 1.1 million malicious samples to the MITRE ATT&CK framework. Discover how adversaries use trigonometric sandbox evasion and weaponize trusted cloud APIs to stay hidden. Download the report to see the Top 10 techniques and validate your posture.
Survey Results Webinar | Wednesday, March 11, 2026, at 10:30 AM EDT | 2026 SANS State of Identity Threats & Defenses Survey Insights Event: How Identity Became the New Security Perimeter—And What’s Next.
Free Virtual Summit | Tuesday, March 17, 2026, at 10:00 AM EDT | SANS Leadership Summit Solutions Track 2026 | Join experts from SANS, Microsoft and Daylight Security as they discuss frameworks and actionable approaches that address today's leadership challenges.
Webinar | Wednesday, March 18, 2026 at 3:30 PM EDT | AI-Human Collaboration in Modern SOCs.