Over the last several weeks, the NJCCIC has observed an increase in compromised New Jersey public sector accounts. These accounts are often compromised after a user submits their account credentials to a fraudulent webpage navigated to via a phishing email. These phishing emails are typically sent from accounts known to the recipient and therefore appear legitimate and trustworthy; however, the trusted sender’s account has been compromised, unbeknownst to the recipient. Recently observed tactics include the use of encrypted emails and attachments, and calendar invites to deliver malicious links and attachments. Threat actors’ use of personalized subject lines and file names lends authenticity to the messages, making recipients more likely to engage with them.
These phishing emails often use similar lures, in which the communications reference a document, message, report, or file that needs to be viewed. Specifically, the NJCCIC has noted an increase in Docusign phishing. Once the user clicks the included link in the email or attachment, they are often directed to a website that requests account credentials to view the document. If account credentials are entered, they are stolen by the threat actors. There have also been increasing efforts to obtain multi-factor authentication codes in these phishing schemes. The threat URLs included in recent campaigns often reference the compromised account’s organization, Microsoft products such as SharePoint, or document creator or form builder resources including Docusign or Jotform.
Many of these phishing emails originate from familiar, yet compromised, accounts associated with county and local government entities, such as health departments, social services, school districts, mayors’ offices, and public safety offices. As a result, recipients are likely to trust these communications. However, these phishing emails are often sent without context, with minimal content in the email body, and may come from accounts with which the recipient does not typically share documents. Document signing platforms are also frequently impersonated in these schemes. If you do not normally electronically sign documents received from the sender, this could indicate that the message is suspicious.
Examples from these phishing messages are included below.
Recommendations
Avoid opening attachments or clicking links delivered in emails and meeting invites, even those from known contacts, unless they are expected and in line with an established relationship. Verify communications with the sender via a separate means of communication before taking any action on their requests. Type official website URLs into browsers manually and only submit sensitive information on official websites. Notify users of this and similar tactics to increase awareness and reduce the risk of account compromises. Review the Don’t Take the Bait! Phishing and Other Social Engineering Attacks NJCCIC product for more information on common phishing and social engineering attacks.
Reporting The NJCCIC encourages recipients who discover signs of malicious cyber activity to contact the NJCCIC via the cyber incident report form at www.cyber.nj.gov/report.
Due to the lapse in annual appropriations for the Department of Commerce, the NIST National Cybersecurity Center of Excellence (NCCoE) rescheduled the Cybersecurity Connections event that was originally scheduled for October 14, 2025. We apologize for the inconvenience and appreciate your understanding.
Event Date: January 13, 2026
Event Time: 11:00 a.m. – 1:30 p.m. (EST)
Event Location: 9700 Great Seneca Hwy, Rockville, MD 20850
Join the NIST NCCoE for a Cybersecurity Connections event highlighting exciting career opportunities in the cybersecurity field! Hosted in partnership with NICE (NIST), the Maryland Department of Commerce, and Montgomery County, this event is a unique opportunity to learn from industry experts and connect with cybersecurity professionals. By attending, you’ll gain valuable insights into the latest approaches to strengthening the cybersecurity workforce and network with like-minded professionals.
This event will feature a keynote presentation from Jessica Gulick, CEO and Founder of Katzcy and Commissioner of the U.S. Cyber Team. Jessica will discuss how the U.S. Cyber Games is advancing cybersecurity awareness, skills development, and cyber career preparation on a global scale. The keynote will also spotlight opportunities for Maryland-based individuals and organizations to engage with and support the initiatives of the U.S. Cyber Team.
In addition, our expert panel on building a robust cybersecurity workforce will discuss topics such as the critical skills and competencies needed to succeed in today’s cybersecurity landscape, the accessibility of cybersecurity education, and what workforce challenges critical infrastructure owners and operators may face in the future. This panel will be followed by a networking lunch, generously provided by the Montgomery County Economic Development Corporation on behalf of Montgomery County.
Register now to attend in-person or virtually! We look forward to connecting with you to foster collaboration and innovation in the cybersecurity community.
The initial public draft of NIST Special Publication (SP) 800-57 Part 1 Revision 6, Recommendation for Key Management: Part 1 – General, is available for comment through February 5, 2026. This recommendation provides general guidelines and best practices for managing cryptographic keying material.
Some of the proposed changes from Revision 5 include:
Ascon, as specified in SP 800-232, and the new quantum-resistant algorithms specified in Federal Information Processing Standards (FIPS) 203, 204, and 205 have been included.
The keys used for both key establishment and key storage are now discussed separately.
The security categories used in the Post-Quantum Cryptography (PQC) competition have been included, along with the quantum-resistant algorithms.
The time frames for algorithm approval status have been removed and replaced with references to SP 800-131A.
A section has been added to discuss keying material storage and mechanisms.
A complete list of changes is in Appendix F of the draft.
See the publication details for a copy of the draft and instructions for submitting comments.
NJCCIC: Beware of Holiday Travel Scams Threat actors continue their attempts to trick users making hotel reservations and other travel arrangements by impersonating major brands. In one large-scale phishing campaign, they target potential travelers using malicious spam linked through the Want Your Feedback service, which prompts them to click the link to visit a hotel’s website and confirm their reservation using a credit card.
If clicked, the target is redirected through various websites before landing on a customized phishing page featuring logos from companies such as Airbnb and Booking.com. In another scheme, threat actors use compromised email accounts to send customer service-themed requests to hotel reservation email addresses. These emails contain a malicious link and employ the ClickFix social engineering tactic to compromise booking platforms, such as Expedia, with infostealer malware that captures account credentials.
The NJCCIC advises users to scrutinize messages containing urgent language or confirmation of updates, changes, or requests. Additionally, type official website URLs into browsers manually and only submit personal or financial information on official websites. For more information, view the NJCCIC’s latest alerts and advisories.
Multiple vulnerabilities have been discovered in Mozilla products, the most severe of which could allow for arbitrary code execution.
Mozilla Firefox is a web browser used to access the Internet.
Mozilla Firefox ESR is a version of the web browser intended to be deployed in large organizations.
Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. 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:
Firefox versions prior to 146
Firefox ESR versions prior to 115.31
Firefox ESR versions prior to 140.6
RISK: Government:
Large and medium government entities: High
Small government: Medium
Businesses:
Large and medium business entities: High
Small business entities: Medium
Home Users: Low
TECHNICAL SUMMARY: Multiple vulnerabilities have been discovered in Mozilla products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows:
Use-after-free in the Audio/Video. (CVE-2025-14326)
Spoofing issue in the Downloads Panel component. (CVE-2025-14327)
Privilege escalation in the Netmonitor component. (CVE-2025-14328, CVE-2025-14329)
JIT miscompilation in the JavaScript Engine. (CVE-2025-14330)
Same-origin policy bypass in the Request Handling component. (CVE-2025-14331)
Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. 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 updates provided by Mozilla 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.
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 9.1: Ensure Use of Only Fully Supported Browsers and Email Clients: Ensure only fully supported browsers and email clients are allowed to execute in the enterprise, only using the latest version of browsers and email clients provided through the vendor.
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.
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™.
Restrict use of certain websites, block downloads/attachments, block JavaScript, restrict browser extensions, etc. (M1021:Restrict Web-Based Content)
Safeguard 9.2: Use DNS Filtering Services: Use DNS filtering services on all enterprise assets to block access to known malicious domains.
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.
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.
Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources. Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted 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.
This Multi-State Information Sharing and Analysis Center (MS-ISAC) Advisory is being provided to assist agencies and organizations in guarding against the persistent malicious actions of cybercriminals.
A vulnerability has been discovered FortiWeb, which could allow for remote code execution. FortiWeb is a web application firewall (WAF) developed by Fortinet. It’s designed to protect web applications and APIs from a wide range of attacks, including those targeting known vulnerabilities and zero-day exploits. Successful exploitation of this vulnerability could allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS requests.
Threat Intelligence
Fortinet has observed this to be exploited in the wild. The Cybersecurity and Infrastructure Security Agency (CISA) also added the vulnerability to the Known Exploited Vulnerabilities (KEV) Catalog.
Systems Affected
FortiWeb versions 8.0.0 through 8.0.1 FortiWeb versions 7.6.0 through 7.6.4 FortiWeb versions 7.4.0through 7.4.9 FortiWeb versions 7.2.0 through 7.2.11 FortiWeb versions 7.0.0 through 7.0.11
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
Recommendations
Apply appropriate updates provided by Fortiguard to vulnerable systems immediately after appropriate testing. 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. Use vulnerability scanning to find potentially exploitable software vulnerabilities to remediate them. Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.
Comment Period Extended! Sharpening the Focus on Product Requirements and Cybersecurity Risks: Updating Foundational Activities for IoT Product Manufacturers The comment period for Draft NIST IR 8259 Rev. 1, Second Draft, Foundational Cybersecurity Activities for IoT Product Manufacturers, has been extended through December 10, 2025. Over the past few months, NIST has been revising and updating Foundational Activities for IoT Product Manufacturers (NIST IR 8259 Revision 1 Initial Public Draft), which describes recommended pre-market and post-market activities for manufacturers to develop products that meet their customers’ cybersecurity needs and expectations. Thank you so much for the thoughtful comments and feedback throughout this process; 400+ participants across industry, consumer organizations, academia, federal agencies, and researchers shared feedback in both the December 2024 and March 2025 workshops—as well as through written comments on the initial public draft. Others came to the virtual Discussion Forum Event in June to discuss updates, share initial ideas for a worked example of NIST IR 8259, and explore topics from an essay on planned updates to NIST SP 800-213/213A. NIST shared two workshop summary reports and distilled the comprehensive changes that expand the focus on IoT products, highlighting product cybersecurity capabilities as central to IoT cybersecurity. What Happens Next? Serving as a culmination of this collaborative effort, our latest resource, NIST IR 8259 Revision 1 Second Public Draft, was recently released… Read MoreNIST Cybersecurity and Privacy Program Questions and comments can be directed to: IoTSecurity@nist.gov
Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for remote code execution. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
THREAT INTELLIGENCE: Google highlighted a severe zero-click vulnerability in the system’s core components that could allow attackers to execute malicious code remotely without any user interaction. This vulnerability requires no additional privileges or user engagement, making it particularly dangerous. (CVE-2025-48593)
SYSTEMS AFFECTED:
Android OS patch levels prior to 2025-11-01
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 Google Android OS, the most severe of which could allow for remote code execution in the context of the affected component. Following the MITRE ATT&CK framework, exploitation of these vulnerabilities can be classified as follows:
Tactic: Execution (TA0002) Technique:Exploitation for Client Execution (T1203):
A vulnerability in System could allow for remote code execution. (CVE-2025-48593)
A vulnerability in System could allow for privilege escalation. (CVE-2025-48581)
Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.
RECOMMENDATIONS: We recommend the following actions be taken:
Apply appropriate patches provided by Google 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.
Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. Inform and educate users regarding threats posed by hypertext links contained in emails or attachments, especially from un-trusted sources. (M1017: User Training)
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 Apple® System Integrity Protection (SIP) and Gatekeeper™.
Multiple vulnerabilities have been discovered in Cisco products, the most severe of which could allow for remote code execution. Cisco is a leading technology company best known for its networking hardware and software, such as routers and switches, that form the backbone of the internet and enterprise networks. Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution as root, which may lead to the complete compromise of the affected device.
THREAT INTELLIGENCE:
The Cisco Product Security Incident Response Team (PSIRT) is aware of attempted exploitation of CVE-2025-20354 and CVE-2025-20358. A detection guide can be found in the references section further down this advisory.
SYSTEMS AFFECTED:
Cisco Unified Contact Center Express versions 12.5 SU3 and earlier
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 Cisco products, the most severe of which could allow for remote code execution. Details of the vulnerability are as follows:
CVE-2025-20354: Cisco Unified CCX Remote Code Execution Vulnerability. The vulnerability exists in the Java Remote Method Invocation (RMI) process of Cisco Unified CCX, which originates from an improper authentication mechanism associated with specific Cisco Unified CCX features. An attacker could exploit this vulnerability by uploading a crafted file to an affected system through the Java RMI process. Successful exploitation of the vulnerability may allow an unauthenticated, remote attacker to upload arbitrary files and execute arbitrary commands with root permissions on an affected system.
CVE-2025-20358: Cisco Unified CCX Editor Authentication Bypass Vulnerability. The vulnerability exists in the Contact Center Express (CCX) Editor application of Cisco Unified CCX, which originates from an improper authentication mechanism in the communication between the CCX Editor and an affected Unified CCX server. An attacker could exploit this vulnerability by redirecting the authentication flow to a malicious server and tricking the CCX Editor into believing the authentication was successful. Upon successful exploitation, an attacker may create and execute arbitrary scripts on the underlying operating system of an affected Unified CCX server as an internal, non-root user account.
Successful exploitation of the most severe of these vulnerabilities could allow for remote code execution as root, which may lead to the complete compromise of the affected device.
RECOMMENDATIONS:
We recommend the following actions be taken:
Apply appropriate updates provided by Cisco or other vendors which use this software 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.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
Safeguard 7.5 : Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
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 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
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.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
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.
Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
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™.
