CISA and USCG Identify Areas for Cyber Hygiene Improvement After Conducting Proactive Threat Hunt at US Critical Infrastructure Organization

The Cybersecurity and Infrastructure Security Agency (CISA) and US Coast Guard (USCG) are issuing this Joint Cybersecurity Advisory to present findings from a recent CISA and USCG hunt engagement. The purpose of this advisory is to highlight identified cybersecurity issues, thereby informing security defenders in other organizations of potential similar issues and encouraging them to take proactive measures to enhance their cybersecurity posture.
CISA led a proactive hunt engagement at a US critical infrastructure organization with the support of USCG analysts. During hunts, CISA proactively searches for evidence of malicious cyber activity or threat actor presence on customer networks. The organization invited CISA to conduct a proactive hunt to determine if a threat actor had been present in the organization’s environment.
During this engagement, CISA did not identify evidence of malicious cyber activity or threat actor presence on the organization’s network, but did identify cybersecurity risks.
In coordination with the organization where the hunt was conducted, CISA and USCG are sharing cybersecurity risk findings and associated mitigations to assist other critical infrastructure organizations with improving their cybersecurity posture. Recommendations are listed for each of CISA’s findings, as well as general practices to strengthen cybersecurity for OT environments. These mitigations align with CISA and the National Institute for Standards and Technology’s (NIST) Cross-Sector Cybersecurity Performance Goals and with mitigations provided in the USCG Cyber Command’s 2024 Cyber Trends and Insights in the Marine Environment Report.
Although no malicious activity was identified during this engagement, critical infrastructure organizations are advised to review and implement the mitigations listed in this advisory to prevent potential compromises and better protect our national infrastructure. These mitigations are listed in order of importance.

Surge in Cryptocurrency Scams

The NJCCIC received reports of a surge in cryptocurrency scams in the past month. These scams aim to steal personally identifiable information (PII), private keys, wallet addresses, and funds. In fraudulent investment schemes, threat actors impersonate legitimate organizations, experienced investment advisors, or registered professionals as part of an investment group. They send unsolicited requests to convince their targets to deposit funds on fraudulent platforms with lures of high-yield, quick-return investments, gold trading, mining, and electric scooter rentals. Weeks or months later, the targets cannot withdraw funds from the fraudulent platforms, or they do not receive the promised payment on their investments. The reported losses from these fraudulent investment schemes ranged from approximately $2,500 to $310,000.
Threat actors also impersonate cryptocurrency platforms, such as Coinbase, in unsolicited emails, text messages, and phone calls. These scams create urgency with claims of compromised accounts, security concerns, and suspicious logins or account activity. Also, unsuspecting targets may search for legitimate customer service phone numbers, potentially revealing “poisoned” search results . If they take further action to “resolve” the urgent issue, the threat actors claim to require account verification or authentication. Once the targets divulge sensitive information and their private keys, funds are transferred to threat actor-controlled cryptocurrency wallets. The reported losses from these scams ranged from approximately $1,300 to $274,000.
Recommendations
Do your research when purchasing cryptocurrency and look for reputable sources. Check for reviews and performance history.
Never invest more than you can afford to lose.
Avoid clicking links, opening attachments, responding to, or acting on unsolicited communications.
Independently verify unsolicited offers and do not release any personally identifying information, financial details, or funds until you have confirmed the legitimacy of the offer.
Always refrain from sharing your private key or seed phrase with anyone. Keep systems and apps up to date.
Report these scams and malicious cyber activity to the NJCCIC, the FBI’s IC3, and the  FTC.
If victimized, monitor bank accounts, credit profiles, and other online accounts for any irregularities or suspicious behavior. 
Review the Identity Theft and Compromised PII 
NJCCIC Informational Report for additional recommendations and resources, including credit freezes and enabling MFA on accounts.
Review the NJCCIC Cryptocurrency Scams webpage for additional information, recommendations, and resources.

Imitation is the Sincerest Form of Flattery for Mobile Malware

Malicious cell phone applications can hide in plain sight, often disguised as legitimate programs. Threat actors aim to deceive users into installing malicious software and giving permissions far beyond what legitimate apps require.
Image Source: Zimperium
To avoid the inherent distrust that users may have toward apps outside of the official Google Play Store, threat actors imitate legitimate companies and find creative ways to distribute their malware. DoubleTrouble, a banking trojan, disguises itself as an extension, even using the Google Play icon to add a sense of trustworthiness. In a new campaign, threat actors have been utilizing Discord-hosted Android Packages ( APKs) to disseminate the most recent version of DoubleTrouble. This variant has many features, including screen capture, keylogging, stealing clipboard data, and employing obfuscation techniques to remain stealthy on an infected device.
Image Source: CTM360
In another campaign, dubbed ClickTok, threat actors impersonate TikTok’s in-app e-commerce platform, which includes TikTok’s Shop, Wholesale, and Mall. Utilizing AI-generated content, threat actors create fake ads and mimic influencers and brand ambassadors to lure users to fake websites. They use these fake TikTok Shops to attempt to trick users into sharing their credentials, purchasing bogus products, or installing malware, such as SparkKitty Spyware.
The PlayPraetor Android trojan has been distributed primarily across Portugal, Spain, France, Morocco, Peru, and Hong Kong, infecting over 11,000 devices. This campaign utilizes Meta ads that lead to thousands of pages imitating Google Play Store download pages. PlayPraetor has been observed harvesting card information, personally identifiable information (PII), and online banking credentials.
Recommendations
Users are advised to only download applications from official sources. Users who downloaded the malicious apps are urged to uninstall them promptly. Credentials used to log in to malicious apps should immediately be changed. Review the requested permissions and never grant access to the “Accessibility Services.” Keep Google Play Protect enabled on all Android devices. Provide personal or financial information or transfer money to only legitimate and verified websites. Regularly update your mobile device and its applications. Run updated and reputable anti-malware programs on devices.

Webinar on 8/20 | NIST’s Digital Identity Guidelines

NIST will host a public webinar to discuss the recently released final version of Special Publication 800-63, Digital Identity Guidelines, Revision 4, which intends to respond to the changing digital landscape that has emerged since the last major revision of this suite was published by NIST in 2017. 

This informative webinar featuring NIST’s identity team will cover the content changes recently made to the entire suite of Digital Identity Guidelines documents and will explore topics such as technical requirements for meeting digital identity assurance levels, requirements for security and privacy, and considerations for an improved customer experience relative to digital identity solutions and technology.  

Those interested are encouraged to join and bring questions. 

Register

NIST NCCoE Virtual Meeting Rescheduled – Cyber AI Profile Virtual Working Session #1: Securing AI System Components

The NCCoE Cyber AI Profile Virtual Working Session #1: Securing AI System Components was canceled and has been rescheduled to August 26, 2025. We apologize for the disruption and hope you will join us for the rescheduled session.

Session #1 Topic Background: Securing AI System Components

The adoption of AI into existing infrastructures introduces new threats and vulnerabilities across data, models, infrastructure, and applications, resulting in unique and diverse cybersecurity and business challenges. These new risks highlight the need for considerations in the areas of governance, risk management strategies, and supply chain, as well as changes to existing cybersecurity practices around access control and authorization policies, updated employee training, revised service agreements with 3rd party AI providers, and network baselines. This working session will explore how the Cyber AI Profile can support organizations in identifying and mitigating the cybersecurity risks associated with deploying systems in their organizational ecosystems.

Register Now!

You can register for this session and other Cyber AI Profile Working Sessions by visiting the NCCoE event page. Please come ready to share your knowledge and insights during these interactive working sessions!

There are no changes in the series plan for:

Session #2: Conducting AI-enabled Cyber Defense

Session #3: Thwarting AI-enabled Cyber Attacks.

Can’t make it?

No problem! If you are unable to attend your desired session, you are welcome to share feedback via email at cyberaiprofile@nist.gov.

Register Now!

Critical Patches Issued for Microsoft Products, August 12, 2025 – PATCH: NOW

Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLIGENCE:
There are currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED:

  • Microsoft Exchange Server
  • SQL Server
  • Role: Windows Hyper-V
  • Azure Virtual Machines
  • Microsoft Office SharePoint
  • Microsoft Edge for Android
  • Microsoft Graphics Component
  • Microsoft Dynamics 365 (on-premises)
  • Windows Routing and Remote Access Service (RRAS)
  • Windows Kernel
  • Windows Ancillary Function Driver for WinSock
  • Desktop Windows Manager
  • Windows File Explorer
  • Windows Push Notifications
  • Windows NTFS
  • Remote Access Point-to-Point Protocol (PPP) EAP-TLS
  • Windows Win32K – GRFX
  • Windows Distributed Transaction Coordinator
  • Windows Win32K – ICOMP
  • Windows SMB
  • Windows Cloud Files Mini Filter Driver
  • Remote Desktop Server
  • Windows DirectX
  • Windows Installer
  • Graphics Kernel
  • Windows Message Queuing
  • Windows Media
  • Windows PrintWorkflowUserSvc
  • Windows NT OS Kernel
  • Kernel Transaction Manager
  • Microsoft Brokering File System
  • Kernel Streaming WOW Thunk Service Driver
  • Storage Port Driver
  • Windows Local Security Authority Subsystem Service (LSASS)
  • Windows Connected Devices Platform Service
  • Windows Remote Desktop Services
  • Azure File Sync
  • Microsoft Office Visio
  • Microsoft Office
  • Microsoft Office Word
  • Microsoft Office Excel
  • Microsoft Office PowerPoint
  • Azure Stack
  • Windows GDI+
  • Azure OpenAI
  • Windows Security App
  • Web Deploy
  • GitHub Copilot and Visual Studio
  • Microsoft 365 Copilot’s Business Chat
  • Windows NTLM
  • Windows Kerberos
  • Microsoft Teams
  • Windows Subsystem for Linux
  • Windows StateRepository API
  • Azure Portal

RISK:
Government:

  • Large and medium government entities: High
  • Small government entities: Medium

Businesses:

  • Large and medium business entities: High
  • Small business entities: Medium

Home users: Low 

TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution.

A full list of all vulnerabilities can be found in the Microsoft link in the References section.

Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged-on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

  • Apply appropriate patches or appropriate mitigations provided by Microsoft to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
    • Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
    • Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
  • Apply the Principle of Least Privilege to all systems and services and run all software as a non-privileged user (one without administrative rights) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
    • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
    • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
  • Remind all users not to visit untrusted websites or follow links/open files provided by unknown or untrusted sources. (M1017: User Training)
    • Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
    • Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.
  • Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
    • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
    • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:

Microsoft:
https://msrc.microsoft.com/update-guide/releaseNote/2025-Aug
https://msrc.microsoft.com/update-guide

Wearable, Implantable and Ingestible Medical Devices Could Revolutionize Your Health Care

Wearable, Implantable and Ingestible Medical Devices Could Revolutionize Your Health Care By Kamran Sayrafian, a senior scientist in NIST’s Information Technology Laboratory

A few years ago, I heard on the news that many people were being hospitalized with a condition of excess fluid in the lungs, called pulmonary edema. It’s common in elderly patients. Pulmonary edema is dangerous and can lead to breathing difficulties and lung failure. Since it has the potential to develop suddenly, it can be a serious medical emergency.

As a NIST researcher interested in the application of technology in health care, I wondered: Is there a way to monitor this condition at home with a simple wearable device?

Read More

NIST Finalizes ‘Lightweight Cryptography’ Standard to Protect Small Devices

NIST Finalizes ‘Lightweight Cryptography’ Standard to Protect Small Devices It’s the little things that matter most, as the saying goes, and the National Institute of Standards and Technology (NIST) has got their back.

NIST’s newly finalized lightweight cryptography standard provides a defense from cyberattacks for even the smallest of networked electronic devices. Released as Ascon-Based Lightweight Cryptography Standards for Constrained Devices (NIST Special Publication 800-232), the standard contains tools designed to protect information created and transmitted by the billions of devices that form the Internet of Things (IoT) as well as other small electronics, such as RFID tags and medical implants.

Miniature technologies like these often possess far fewer computational resources than computers or smartphones do, but they still need protection from cyberattacks. The answer is lightweight cryptography, which is designed to defend these sorts of resource-constrained devices.
Read More

Microsoft Azure Virtual Training Day: Migrate and Modernize your Apps for AI-powered Solutions

Adapt your skills and master the tools you’ll need to thrive in an AI-powered world at a free Microsoft Azure Virtual Training Day from Microsoft Learn.

Join us at Migrate and Modernize Your Apps for AI-powered Solutions and learn how to discover and assess your workloads and efficiently manage your cloud migration.

Learn how to migrate on-premises web apps to Azure App Service with Azure Migrate—plus, see how migration optimizes costs, enhances security, and boosts developer innovation.

You’ll explore how to use GitHub Copilot to identify and resolve migration challenges with its AI coding assistance. You’ll also discover ways to deliver improved customer experiences in Azure App Service using security, load balancing, autoscaling, and automated management capabilities. After completing this training, you’ll be eligible to take the Microsoft Azure Fundamentals certification at 50% off the exam price.

You’ll have the opportunity to: Gain the skills needed to migrate your apps smoothly, efficiently, and with minimal code changes. Learn how to monitor the health and scale the performance of your app to maintain reliability and minimize downtime.

Explore methods that help secure access to your app and manage app configuration and secrets. Chat with Microsoft experts—ask questions and find solutions to common app migration challenges. Join us at an upcoming two-part

Migrate and Modernize Your Apps for AI-powered Solutions event:
September 9, 2025
9:00 AM – 11:45 AM | (GMT-07:00) Pacific Time (US & Canada)
10:00 AM – 12:45 PM | (GMT-06:00) Mountain Time (US & Canada)
11:00 AM – 1:45 PM | (GMT-05:00) Central Time (US & Canada)
12:00 PM – 2:45 PM | (GMT-04:00) Eastern Time (US & Canada)

September 10, 2025
9:00 AM – 11:45 AM | (GMT-07:00) Pacific Time (US & Canada)
10:00 AM – 12:45 PM | (GMT-06:00) Mountain Time (US & Canada)

Visit the Microsoft Virtual Training Days website to learn more about other event opportunities.
11:00 AM – 1:45 PM | (GMT-05:00) Central Time (US & Canada)
12:00 PM – 2:45 PM | (GMT-04:00) Eastern Time (US & Canada)

Delivery Language: English
Closed Captioning Language(s): English

MS-ISAC CYBERSECURITY ADVISORY – Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution – PATCH NOW

Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLEGENCE:

There are currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED:

  • Versions prior to iOS 18.6 and iPadOS 18.6
  • Versions prior to iPadOS 17.7.9
  • Versions prior to macOS Sequoia 15.6
  • Versions prior to macOS Sonoma 14.7.7
  • Versions prior to macOS Ventura 13.7.7
  • Versions prior to watchOS 11.6
  • Versions prior to tvOS 18.6
  • Versions prior to visionOS 2.6

RISK:
Government:

  • Large and medium government entities: High
  • Small government entities: Medium

Businesses:

  • Large and medium business entities: High
  • Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Details of the vulnerabilities are as follows:

TacticExecution (TA0002):

Technique: Exploitation for Client Execution (T1203):

  • Running an hdiutil command may unexpectedly execute arbitrary code. (CVE-2025-43187)
  • An app may be able to execute arbitrary code out of its sandbox or with certain elevated privileges. (CVE-2025-24119)

Additional lower severity vulnerabilities include:

  • Passcode may be read aloud by VoiceOver. (CVE-2025-31229)
  • Privacy Indicators for microphone or camera access may not be correctly displayed. (CVE-2025-43217)
  • Parsing a file may lead to an unexpected app termination. (CVE-2025-43186)
  • A non-privileged user may be able to modify restricted network settings. (CVE-2025-43223)
  • Processing a maliciously crafted audio file may lead to memory corruption. (CVE-2025-43277)
  • Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory. (CVE-2025-43210, CVE-2025-43224, CVE-2025-43221)
  • An app may be able to access user-sensitive data. (CVE-2025-43230)
  • Processing maliciously crafted web content may lead to an unexpected Safari crash. (CVE-2025-43209, CVE-2025-43214, CVE-2025-43213, CVE-2025-43212, CVE-2025-43216, CVE-2025-6558, CVE-2025-24188)
  • Processing a maliciously crafted image may result in disclosure of process memory. (CVE-2025-43226, CVE-2025-43215)
  • Processing a file may lead to memory corruption. (CVE-2025-43202, CVE-2025-7425)
  • Processing maliciously crafted web content may lead to memory corruption. (CVE-2025-7424, CVE-2025-31278, CVE-2025-31277, CVE-2025-31273)
  • Remote content may be loaded even when the ‘Load Remote Images’ setting is turned off. (CVE-2025-31276)
  • Processing a maliciously crafted texture may lead to unexpected app termination. (CVE-2025-43234)
  • Processing a maliciously crafted file may lead to unexpected app termination. (CVE-2025-31281, CVE-2025-43254, CVE-2025-43239)
  • Visiting a malicious website may lead to address bar spoofing. (CVE-2025-43228)
  • Processing maliciously crafted web content may disclose sensitive user information. (CVE-2025-43227)
  • Processing web content may lead to a denial-of-service. (CVE-2025-43211)
  • Processing maliciously crafted web content may disclose internal states of the app. (CVE-2025-43265)
  • An attacker may be able to cause unexpected app termination. (CVE-2025-43222, CVE-2025-43236)
  • An app may be able to access protected user data. (CVE-2025-43220, CVE-2025-43245, CVE-2025-43198, CVE-2025-43206, CVE-2025-43185)
  • An app may be able to fingerprint the user. (CVE-2025-31279)
  • A remote attacker may be able to cause unexpected system termination. (CVE-2025-24224)
  • An app may be able to access sensitive user data. (CVE-2025-43225, CVE-2025-43195, CVE-2025-43267, CVE-2025-43197, CVE-2025-43246)
  • An app may be able to read a persistent device identifier. (CVE-2025-24220)
  • An app may be able to cause a denial-of-service. (CVE-2025-43191, CVE-2025-43235, CVE-2025-43193)
  • An app may be able to cause unexpected system termination. (CVE-2025-43244, CVE-2025-43255, CVE-2025-43237, CVE-2025-43238)
  • An app may be able to gain root privileges. (CVE-2025-31243, CVE-2025-43249, CVE-2025-43196, CVE-2025-43256)
  • A malicious app may be able to launch arbitrary binaries on a trusted device. (CVE-2025-43253)
  • A malicious app may be able to gain root privileges. (CVE-2025-43248, CVE-2025-43199, CVE-2025-43188, CVE-2025-43268)
  • An app may be able to break out of its sandbox. (CVE-2025-43257, CVE-2025-43261, CVE-2025-43275, CVE-2025-43266, CVE-2025-43250)
  • A sandboxed process may be able to circumvent sandbox restrictions. (CVE-2025-43273, CVE-2025-43274)
  • iCloud Private Relay may not activate when more than one user is logged in at the same time. (CVE-2025-43276)
  • Account-driven User Enrollment may still be possible with Lockdown Mode turned on. (CVE-2025-43192)
  • A sandboxed process may be able to launch any installed app. (CVE-2025-31275)
  • Processing a maliciously crafted image may corrupt process memory. (CVE-2025-43264, CVE-2025-43219)
  • Processing a maliciously crafted file may lead to heap corruption. (CVE-2025-31280)
  • Processing a maliciously crafted USD file may disclose memory contents. (CVE-2025-43218)
  • An app may gain unauthorized access to Local Network. (CVE-2025-43270)
  • An app may be able to hijack entitlements granted to other privileged apps. (CVE-2025-43260)
  • A malicious app with root privileges may be able to modify the contents of system files. (CVE-2025-43247)
  • An app may be able to modify protected parts of the file system. (CVE-2025-43194, CVE-2025-43243)
  • An app may be able to bypass certain Privacy preferences. (CVE-2025-43232)
  • An app may be able to read files outside of its sandbox. (CVE-2025-43241)
  • A malicious app acting as a HTTPS proxy could get access to sensitive user data. (CVE-2025-43233)
  • A local attacker may gain access to Keychain items. (CVE-2025-43251)
  • A malicious app may be able to read kernel memory. (CVE-2025-43189)
  • Processing maliciously crafted web content may lead to universal cross site scripting. (CVE-2025-43229)
  • A download’s origin may be incorrectly associated. (CVE-2025-43240)
  • An attacker with physical access to a locked device may be able to view sensitive user information. (CVE-2025-43259)
  • A website may be able to access sensitive user data when resolving symlinks. (CVE-2025-43252)
  • A shortcut may be able to bypass sensitive Shortcuts app settings. (CVE-2025-43184)

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:

We recommend the following actions be taken:

  • Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
    • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
    • Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
    • Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
    • Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
    • Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
    • Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
    • Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
    • Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
  • Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
    • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
    • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
  • Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
    • Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
    • Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassessbi-annually, or more frequently.
    • Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
    • Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
  • Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
    • Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
  • Block execution of code on a system through application control, and/or script blocking. (M1038:Execution Prevention)
    • Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
    • Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
    • Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
  • Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
    • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
    • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:


Apple:

https://support.apple.com/en-us/100100

https://support.apple.com/en-us/124147

https://support.apple.com/en-us/124148

https://support.apple.com/en-us/124149

https://support.apple.com/en-us/124150

https://support.apple.com/en-us/124151

https://support.apple.com/en-us/124155

https://support.apple.com/en-us/124153

https://support.apple.com/en-us/124154

CVE:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-6558

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-7424

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-7425

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24119

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24188

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24220

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-24224

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31229

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31243

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31273

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31275

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31276

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31277

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31278

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31279

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31280

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31281

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43184

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43185

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43186

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43187

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43188

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43189

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43191

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43192

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43193

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43194

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43195

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43196

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43197

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43198

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43199

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43202

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43206

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43209

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43210

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43211

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43212

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43213

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43214

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43215

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43216

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43217

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43218

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43219

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43220

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43221

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43222

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43223

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43224

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43225

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43226

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43227

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43228

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43229

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43230

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43232

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43233

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43234

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43235

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43236

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43237

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43238

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43239

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43240

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43241

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43243

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43244

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43245

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43246

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43247

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43248

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43249

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43250

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43251

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43252

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43253

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43254

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43255

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43256

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43257

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43259

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43260

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43261

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43264

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43265

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43266

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43267

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43268

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43270

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43273

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43274

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43275

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43276

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43277