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 UsFollowing the completion of an investigation conducted collaboratively with Mandiant, SonicWall now says that a data breach disclosed last month affects all customers who use the company's cloud backup services to store firewall configuration files, which contain sensitive information. Initially, SonicWall said the September incident affected just five percent of the company's customers. In a write-up of the incident, SonicWall says that the compromised files “contain encrypted credentials and configuration data; while encryption remains in place, possession of these files could increase the risk of targeted attacks." The document also offers affected users containment and mitigation guidance, including deleting existing cloud backups, changing account credentials, rotating shared secrets and passwords, and recreating new backup files locally.
SonicWall thoroughly botched this incident. At first, SonicWall claimed that a small percentage of cloud accounts were compromised by brute forcing, suggesting customers used weak passwords. Blaming customers for the incident turned out to be wrong, and it looks like ALL uploads to the “MySonicWall” cloud were compromised. It will be interesting to see if SonicWall will, in some way, reimburse customers for the company’s negligence or if customers will be stuck with a lot of unpaid extra work. SonicWall would be well advised to look at any of the excellent open source solutions that will encrypt the ENTIRE configuration before uploading it to the cloud, or that offer convenient on-premises backup solutions.
The pilfered backup files — including device settings, network configurations, firewall rues, VPN configuration/settings/policies, user and group accounts — are encoded, and individual credentials and secrets are separately encrypted. Gen 7 devices encrypt this with AES, while Gen 6 firewalls use 3DES. Note the local administrator account is not included in the backup. Regardless, the safe move is to change all credentials included in the backup, either manually or by applying the updated preferences file from SonicWall. Read the instructions carefully, including the remediation playbook, before applying that file; it's to disrupt TOTP bindings, IPSEC VPNs, and user access, so you need to plan and communicate/coordinate both with users and with your help desk.
Well, the results are in: 100 percent of customers are affected. Seems a bit more than a rounding error from first reports of the incident. Hopefully, SonicWall customers didn’t wait for the final analysis, instead opting to follow the mitigation guidance provided earlier.
Help Net Security
The Register
BleepingComputer
The Hacker News
Infosecurity Magazine
SecurityWeek
SonicWall
Salesforce does not intend to pay a ransom demanded by cyberthreat actors who claim to have stolen 1 billion records from Salesforce customers. The CRM company contacted their affected customers earlier this week, warning of "credible threat intelligence" that the data thieves plan to leak the stolen information. The threat actors said that they would not release the data if Salesforce paid the demanded ransom by Friday, October 10. A Salesforce representative has confirmed that the company "will not engage, negotiate with, or pay any extortion demand."
The demand, from Scattered LAPSUS$ Hunters, is to release data obtained from previous intrusions, not new breaches, such as the ShinyHunters SalesLoft Drift breach. Salesforce needs to stick to their guns in this high-stakes game of chicken. Watch how this plays out; this will be a good scenario for a tabletop deep dive.
Colin Powell’s quote seems appropriate here: "Bad news isn’t wine, it doesn’t improve with time.” Kudos to the Salesforce communications team for getting out in front of the possible bad press. Customers usually respect being informed early.
The Register
Gov Infosecurity
Ars Technica
BleepingComputer
SC Media
Gov Infosecurity
In a statement posted to social media, Germany's Federal Justice Minister Stefanie Hubig said that "Germany will not agree to" a European Union proposal that would allow private messages, even those sent over end-to-end encrypted messaging platforms, to be scanned. Hubig added that "random chat monitoring must be taboo in a constitutional state; Private communication must never be placed under general suspicion." Known as Chat Control, the proposal is mean to help law enforcement protect children from abuse. Signal Foundation President Meredith Whittaker said that the end-to-end encrypted messaging app will leave the EU market if Chat Control becomes law.
This is very welcome news and hopefully will put an end to this proposal. I wrote an opinion piece on why chat control poses such a threat to our online security and privacy: "Proposed EU Chat Control regulation could create surveillance state"
https://www.irishexaminer.com/opinion/commentanalysis/arid-41700062.html
Surveillance vs. privacy is an ongoing debate. This proposal would move us from problematic back door/decryption, when requested, to continuous decryption of end-to-end encrypted messages. If enacted, expect users to seek out applications that claim to thwart such surveillance, which could lead to a propagation of malicious replacements for WhatsApp, Signal, etc.
There will always be tension between law enforcement and a citizen’s right to privacy. Typically, law enforcement uses the worst case scenario (potential child abuse) to make its point. My question: should 99 percent lose their right to privacy for the one percent? Germany is saying NO. As expected, governments will continue attempting to chip away at end-to-end encryption protections; we’ve seen recent examples in the UK and Sweden.
California's Governor has signed into law several bills that gives that state's residents more control over their own data. Specifically, one of the bills, AB 656, "requir[es] social media companies to make canceling an account straightforward and clear – and ensur[es] that cancellation triggers full deletion of the user’s personal data." Another bill, AB 566, "requires browsers to give users the ability to opt out of the sale of their personal data across the web with one click instead of requiring Californians to exercise this right with each individual website they visit." A third bill, SB 361, "strengthens the Data Broker Registration Law by providing consumers with more information about the personal information collected by data brokers and who may have access to consumers’ data."
Especially with AI use growing, more data owner control needs to happen. Requiring opt-in would be better, but forcing companies to make it easier to opt-out is a step in the right direction that other states will copy.
The trick is implementation timelines. AB 566, simplified browser opt-out, is due to be implemented January 1, 2027. Currently users are downloading plugins or privacy enhanced browsers, so this is a win. SB 361, data broker data deletion and disclosure, has an effective date of January 1 2026, with an implementation due August 1, 2026. AB 656, social media account and deletion, doesn't have a timeline, meaning it goes into effect immediately. It also states that a new login to the account being deleted doesn't cancel the deletion request. I have had users unknowingly extend/revive a deleted account when logging into the wrong account, which is frustrating to all involved.
Washington, DC-based law firm Williams & Connolly has disclosed a "cybersecurity incident" in which threat actors breached some systems and accessed attorneys' email accounts. The firm is known to represent high-profile clients, including politicians, tech companies, and financial institutions. A statement from Williams & Connolly reads, in part, "Based on the Firm’s investigation, conducted in conjunction with cyber experts at CrowdStrike, the threat actor is believed to be affiliated with a nation-state actor responsible for recent attacks on a number of law firms and companies." While Williams & Connolly did not name a particular nation-state, some news outlets have suggested that Chinese threat actors are responsible for those attacks. In a September 24 blog, Mandiant Incident Response and Google Threat Intelligence Group (GTIG) reported that they were "tracking BRICKSTORM malware activity, which is being used to maintain persistent access to victim organizations in the United States," including legal services, and "attribute this activity to UNC5221 and closely related, suspected China-nexus threat clusters that employ sophisticated capabilities."
Mandiant has released a scanner to detect BRICKSTORM activity. It implements the G_APT_Backdoor_BRICKSTORM_3 YARA rule. The activity is stealthy and leverages backdoors designed to bypass EDR and provide long term access. Make sure you have sufficient hardening and monitoring of all internet-facing systems and double down on appliances and management interfaces which should have strict limitations on connections.
The Record
SecurityWeek
Document Cloud
The US Cybersecurity and Infrastructure Security Agency (CISA) has added a stored cross-site scripting vulnerability in Zimbra Collaboration Suite (ZCS) to the Known Exploited Vulnerabilities (KEV) catalog. The flaw "exists in the Classic Web Client due to insufficient sanitization of HTML content in ICS files." The vulnerability was exploited earlier this year in cyberattacks targeting Brazil's military. Zimbra addressed the vulnerability in updates released in January 2025. Researchers at StrikeReady recently published a blog detailing the vulnerability and the attack, which "leveraged a malicious .ICS file, a popular calendar format." US Federal Civilian Executive Branch (FCEB) agencies have until October 28 to mitigate the vulnerability.
Zimbra released the 9.0.0 P44, 10.0.13, and 10.1.5 patches in January 2025, which you should have applied. Mitigations include blocking ICS files and disabling the classic web interface, which is going to be more painful than the update. Even so, read the release notes carefully; there are changes to the SOAP API needed for the update, particularly if you have a custom change password implementation. The StrikeReady blog has the IoCs for this attack.
SC Media
The Hacker News
BleepingComputer
StrikeReady
Zimbra
NIST
Researchers at Microsoft Threat Intelligence are investigating "payroll pirate" attacks that have been targeting employee profiles on "third-party human resources (HR) software as a service (SaaS)" to redirect salary payments from legitimate accounts to accounts controlled by the attackers. Microsoft writes that "these attacks don’t represent any vulnerability in [a particular] platform or product, but rather financially motivated threat actors using sophisticated social engineering tactics and taking advantage of the complete lack of multifactor authentication (MFA) or lack of phishing-resistant MFA to compromise accounts." Microsoft's blog includes an analysis of the campaign: how the attackers gained initial access to systems, evaded detection, and maintained persistence. It follows with mitigation and protection guidance.
The attackers are grabbing MFA tokens via phishing emails with bogus login links to log in to those accounts to then phish users from a legitimate source. Once in the end-user account, they would initiate the steps to modify their bank account and set up rules to eliminate any messages relating to these changes. It comes down to measures we can all use. Implement phishing-resistant MFA, verify inbox rules, particularly forwarding and mail deletion rules, and look for the IoCs from Microsoft.
On January 19, 2038, at eight seconds past 3:14 UTC, 2,147,483,648 seconds will have passed since the start of the Unix epoch (midnight UTC on January 1, 1970), and consequently any 32-bit signed integer variable storing this number will overflow in computer systems that measure Unix time. This overflow will create a value interpreted as a negative number representing December 13, 1901, and may cause systems to crash. While this and the similar Network Time Protocol (NTP) rollover have been known for decades, researchers at the Epochalypse Project are warning that 32-bit timestamps are widespread in critical infrastructure systems. Legacy industrial control systems, internet of things devices, transportation and energy systems, medical equipment, financial systems, telecom infrastructure, certain vehicles, and many more systems are vulnerable to possible "cascading" failures well before the deadline if manipulated by a threat actor through "GPS spoofing, NTP injection, file format field tampering, [or] protocol timestamp manipulation." The researchers note that many vulnerable systems may be difficult to interface with and update, despite the extent of integration and reliance on them. The project's website lists specific testing and remediation guidelines for the general public and for many roles in industry, government, and technology. Dover Fueling Solutions released a security update for ProGauge fuel tank gauge products in mid-September 2025 to fix a vulnerability that would allow an attacker to change the system time.
Good reminder for those in the transportation field where planes, trains, and automobiles have long lifetimes and lots of embedded controllers and for Operational Technology in general. Design plans and requests for proposal specifications in 2026 and beyond should include addressing this issue.
This is going to impact your OT/ICS systems rather than your general purpose ones. 2038 isn't that far away in a universe of systems designed for a 20-30 year lifecycle. More subtly, e-readers, embedded systems, car infotainment, and smart TVs may also be impacted. The good news is you have eleven years to plan and implement replacements or updates; work with your OT/appliance system owners to start planning now so you can both spread the capital investment and reduce the list of vulnerable devices.
Google has announced the creation of a new dedicated program to incentivize the reporting of AI flaws in Google and Alphabet AI products: the AI Vulnerability Reward Program (AI VRP). Since 2023, AI issues had been integrated into the existing Abuse Vulnerability Reward Program, but following the success of this integration came the need for additional clarity on scope and rewards for reporting abuse risks and security issues, prompting the launch of a separate program. Google's AI VRP includes "issues where interaction with a Large Language Model (LLM) or other Generative AI (GenAI) system, such as a natural language interaction, is an integral part of the vulnerability or abuse issue," but similar issues in Vertex AI and Google Cloud fall under the Google Cloud Vulnerability Rewards Program instead. The program's scope excludes "prompt injections, jailbreaks, and alignment issues," though the company still encourages users to report these "content-related issues" through "in-product feedback, and not through the VRP." The updated program rules offer specific lists of qualifying and non-qualifying vulnerabilities and report types. Rewards ascend by severity of the vulnerability and by "product tier" within Google: "Flagship" products such as Google search, Gemini Apps, and core Google Workspace applications; "Standard" products such as Google AI Studio, Jules, and non-core Workspace applications; and "Other" products such as lower-tier integrations and third-party applications. The largest base reward is US$20,000 — for reporting "Rogue Actions" in a Flagship product — and possible bonuses for novelty and report quality can raise the amount to US$30,000.
Many of us using AI are finding workarounds as well as weird/unexpected behavior. The question of "is this a bug or is it a feature?" remains, with one reported via the VRP and the other through in-product feedback. Fortunately, Google's AI VRP includes a rules page you need to reference before you report, including a detailed table of which type of actions should be reported there.
Google has a good track in running a well-managed bug bounty program, but for AI the “content-related” side of threats, vulnerabilities, misuse, and abuse need early and aggressive action. It would be good to see the other major AI platforms to fill this critical leadership role.
Seems like a reasonable extension of the VRP that brings clarity to what is considered a vulnerability. Did it need to be a separate program? Not sure, but that’s GOOG’s decision to make.
In a Form 8-K filing with the US Securities and Exchange Commission (SEC), BK Technologies Corporation disclosed that it "detected potentially suspicious activity involving its information technology ("IT") systems" in mid-September 2025. The incident resulted in minor disruption to "a limited number of non-critical systems." The company also disclosed "an unauthorized third-party may have obtained access to and acquired non-public information within the Company’s custody and control, which potentially includes records pertaining to current and former employees," but did not provide details about how many individuals were affected. BK Technologies manufactures handheld and vehicle radios used by US police, fire, and military organizations.
To date, no gang has taken credit for this attack. The concern is that information will be used to phish or impersonate workers to obtain further IP relating to their radios.
SANS Internet Storm Center StormCast Friday, October 10, 2025
RedTail Observations; SonicWall; CrowdStrike; Attack Surface Mapping in an Agentic World
https://isc.sans.edu/podcastdetail/9650
Building Better Defenses: RedTail Observations
Defending against attacks like RedTail is more then blocking IoCs, but instead one must focus on the techniques and tactics attackers use.
SonicWall: It wasn’t the user’s fault
SonicWall admits to a breach resulting in the loss of user configurations stored in its cloud service
CrowdStrike has Issues
CrowdStrike fixes two vulnerabilities in the Windows version of its Falcon sensor.
Interrogators: Attack Surface Mapping in an Agentic World
A SANS.edu master’s degree student research paper by Michael Samson
https://isc.sans.edu/researchpapers/pdfs/michael_samson.pdf
SANS Internet Storm Center StormCast Thursday, October 9, 2025
Polymorphic Python; ssh ProxyCommand Vuln; Framelink Figma MCP Server Vulnerability
https://isc.sans.edu/podcastdetail/9648
Polymorphic Python Malware
Xavier discovered self-modifying Python code on Virustotal. The remote access tool takes advantage of the inspect module to modify code on the fly.
https://isc.sans.edu/diary/Polymorphic+Python+Malware/32354
SSH ProxyCommand Vulnerability
A user cloning a git repository may be tricked into executing arbitrary code via the SSH proxycommand option.
https://dgl.cx/2025/10/bash-a-newline-ssh-proxycommand-cve-2025-61984
Framelink Figma MCP Server CVE-2025-53967
Framelink Figma’s MCP server suffers from a remote code execution vulnerability.
https://thehackernews.com/2025/10/severe-figma-mcp-vulnerability-lets.html
SANS Internet Storm Center StormCast Wednesday, October 8, 2025
FreePBX Exploits; Disrupting Teams Threats; Kibana and QT SVG Patches
https://isc.sans.edu/podcastdetail/9646
FreePBX Exploit Attempts (CVE-2025-57819)
A FreePBX SQL injection vulnerability disclosed in August is being used to execute code on affected systems.
https://isc.sans.edu/diary/Exploit+Against+FreePBX+CVE202557819+with+code+execution/32350
Disrupting Threats Targeting Microsoft Teams
Microsoft published a blog post outlining how to better secure Teams.
Kibana XSS Patch CVE-2025-25009
Elastic patched a stored XSS vulnerability in Kibana
https://discuss.elastic.co/t/kibana-8-18-8-8-19-5-9-0-8-and-9-1-5-security-update-esa-2025-20/382449
QT SVG Vulnerabilities CVE-2025-10728, CVE-2025-10729
The QT group fixed two vulnerabilities in the QT SVG module. One of the vulnerabilities may be used for code execution
Catch up on recent editions of NewsBites or browse our full archive of expert-curated cybersecurity news.
Browse ArchiveHow To Win In the Federal Cloud - Join us on October 23, 2025 @2:00 PM ET. FedRAMP authorizations have doubled in 2025. Join top government and industry leaders in this virtual session as they unpack federal cloud and AI adoption - including strategies to ensure your SaaS solution is is "federal-ready."
SANS Cyber Solutions Fest | SOC Track | Wednesday, November 5, 2025 @ 10:00 AM ET This focused track explores the ever-evolving world of Cloud IAM, diving into modern strategies, common missteps, and emerging tools designed to help organizations reclaim control over sprawling identities and creeping permissions.
Webcast | Tanium Autonomous Endpoint Management: Next-Gen Endpoint Visibility Fueling SecOps and IT Ops with AI | Wednesday, November 12, 2025 @ 3:30 PM ET Join Matt Bromiley, SANS instructor and Chris Schwind, Word Wide Technology Field CISO for a first look at Tanium Autonomous Endpoint Management (AEM), a next-generation platform that unifies IT and Security operations with AI-driven intelligence.
Discover how AI is reshaping Breach and Attack Simulation. Join SANS and industry leaders at The BAS Summit 2025. Reserve your spot now.