JFrog
JFrog declares 11 subprocessors, plus 4 of its own affiliates, in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Google Cloud and Microsoft. No published changes since we first read it on Sep 23, 2026.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors CSV of JFrog's subprocessors · Atom feed of JFrog's subprocessors DORA draft CSV of JFrog's subprocessors as declared by JFrog what's this? ·
11 third parties, 4 affiliates.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| Amazon | Application AI Functionality. United States. | ||
| Amazon Web Services, Inc. (AWS) | Cloud Computing Services. Controllers can choose the location and region in accordance with the list available here.; Logs cloud hosting services. United States. | ||
| Anthropic AI | Application AI Functionality. United States. | ||
| Coralogix, Inc. | Log aggregation and correlation services. United States. | ||
| Application AI Functionality. United States. | |||
| Google Cloud Platform, LLC (GCP) | Cloud Computing Services. Controllers can choose the location and region in accordance with the list available here. | ||
| Mailgun Technologies, Inc. | Email notification services. United States. | ||
| Meta | Application AI Functionality. United States. | ||
| Microsoft | Application AI Functionality. United States. | ||
| Microsoft Azure, Corp. (Azure) | Cloud Computing Services. Controllers can choose the location and region in accordance with the list available here. | ||
| SendGrid (Twilio, Inc.) | Email notification services. United States. |
Web TechnologiesCSV of JFrog's web technologies · Atom feed of JFrog's web technologies
JFrog's homepage made 187 requests to 5 domains, and 4 services controlled by another company.
4 third parties by category: Analytics 1Tag managers 1Cookie compliance 1Other 1
2 tracked companies loaded by the homepage are not in JFrog's subprocessor list. A website can use a service without it processing customer data.
ComplianceCSV of JFrog's compliance · Atom feed of JFrog's compliance
Security program
How JFrog says it manages cybersecurity risk, in its annual report to the SEC.
- Led by
- Chief Security Officer reporting to the Chief Information Officer
quote
Our information security program is managed by our Chief Security Officer (“CSO”) who reports to the Chief Information Officer (“CIO”), whose team (the “CIO Office”) leads, amongst other things, enterprise-wide cybersecurity strategy, policy, standards, architecture, technologies, and processes.
- Board oversight
- Audit Committee
quote
The Board has delegated to the Audit Committee the responsibility to oversee the information security program (see below) and is also updated regularly regarding matters discussed with the Audit Committee.
- Frameworks named
- NIST
- ISO 27001
- ISO 27701
- SOC 2
quote
Our risk management strategies are informed by the Cybersecurity Framework published by the National Institute of Standards and Technology (“NIST”), part of the U.S. Department of Commerce.
Our information security controls and practices are certified to globally recognized standards, including, without limitation, ISO 27001, ISO 27701, ISO 27017, SOC 2 Type II, CSA start level 1, TISAX and KY3P by S&P Global.
- Outside review
- Engages outside assessors or consultants
quote
Given the complexity and evolving nature of cybersecurity threats, we engage with a range of external experts, including cybersecurity assessors, consultants, and auditors in evaluating and testing our risk management systems.
- Its own suppliers
- Reviews their security
quote
Our third-party vendor risk management program addresses third party vendors with access to our systems or data, or who process data on our behalf.
- Practices named
- Incident response plan
- Penetration testing
- Bug bounty
- Vulnerability management
- Security training
- Phishing simulations
- Material incidents
- None so far, it says
quote
As of the date of this Annual Report on Form 10-K, we have not identified risks from known cybersecurity threats, including as a result of any prior cybersecurity incidents, that have materially affected or are reasonably likely to materially affect the Company, including our business strategy, results of operations, or financial condition.
Since the fiscal 2024 report: the leader reports to the Chief Information Officer (was the Chief Technology Officer).
Read Item 1C in full
Our products involve the collection, storage and processing of customer data (including, in some cases, personal data), and may provide business critical software and analytics necessary for our customers’ operations. JFrog develops, implements, and maintains cybersecurity measures designed to safeguard our products and protect the confidentiality, integrity, and availability of our customer data and our confidential information.
Risk Management and Strategy
We have developed an information security program intended to protect the confidentiality, integrity, and availability of our critical systems and information. Our information security program is managed by our Chief Security Officer (“CSO”) who reports to the Chief Information Officer (“CIO”), whose team (the “CIO Office”) leads, amongst other things, enterprise-wide cybersecurity strategy, policy, standards, architecture, technologies, and processes. Currently, the CIO is acting as interim CSO, until a new CSO is hired. Our CIO’s responsibilities include assessing, monitoring, and managing our cybersecurity risks. His background includes extensive experience as an enterprise CIO, with over 20 years of experience in the field of cybersecurity. Further, the CIO Office oversees our governance programs, tests our compliance with standards, remediates known risks, and leads our employee security training program.
The CIO Office implements and oversees processes for the regular monitoring of our information systems. This includes the deployment of security measures and compliance systems to identify and mitigate potential vulnerabilities. The CIO Office collaborates closely with key departments within the Company, including the office of our Chief Technology Officer (“CTO”), Engineering, IT, DevOps, Support, and Production, to implement our Vulnerability Management Remediation Plan. This collaboration is aligned with industry standards of the Software Development Life Cycle, underscoring our commitment to maintaining security protocols across all phases of our operations.
We have developed and maintained a cybersecurity incident response plan. JFrog’s cybersecurity incident response team has a strategy and policies in place for managing security incidents. Along with threat classification, containment, and eradication, the strategy includes notification procedures to promptly inform and support stakeholders in accordance with applicable data breach notification laws. Incident analysis is carried out in furtherance of determining root causes and drive continuous improvement.
Our information security controls and practices are certified to globally recognized standards, including, without limitation, ISO 27001, ISO 27701, ISO 27017, SOC 2 Type II, CSA start level 1, TISAX and KY3P by S&P Global. Our risk management strategies are informed by the Cybersecurity Framework published by the National Institute of Standards and Technology (“NIST”), part of the U.S. Department of Commerce.
Our third-party vendor risk management program addresses third party vendors with access to our systems or data, or who process data on our behalf. This program includes a risk-based approach and security assessments throughout the third-party life-cycle, from onboarding to termination, as well as through contractual controls and technological controls to monitor the vendors’ posture. Further, this program is designed to oversee and identify risks from cybersecurity threats associated with its use of third-party service providers.
Training and Awareness
Our employees undertake cybersecurity and data privacy training during onboarding. The majority of our employees complete annual refresher modules. JFrog also maintains a secure-code training program for developers and quarterly phishing simulation to improve our employees’ awareness. Any employee who does not meet our performance expectations in such simulations is required to undergo additional training.
Engagement with Third-Parties on Risk Management
Given the complexity and evolving nature of cybersecurity threats, we engage with a range of external experts, including cybersecurity assessors, consultants, and auditors in evaluating and testing our risk management systems. These partnerships enable us to leverage specialized knowledge and insights, and assist our cybersecurity strategies and processes in remaining consistent with applicable generally adopted industry practices. Our collaborations with these third parties include:
�€¢
regular audits, threat assessments and penetration testing;
�€¢
consultation on security enhancements;
�€¢
bug bounty program for identifying security weaknesses in our products and services;
�€¢
designing partnership with third party vendors;
�€¢
using our in-house security tools as customers; and
�€¢
global incident response experts for potential critical cybersecurity events.
As of the date of this Annual Report on Form 10-K, we have not identified risks from known cybersecurity threats, including as a result of any prior cybersecurity incidents, that have materially affected or are reasonably likely to materially affect the Company, including our business strategy, results of operations, or financial condition. However, we face ongoing cybersecurity risks, including threats that might become more sophisticated and effective over time, and we cannot anticipate when or the extent to which cybersecurity incidents or breaches will materially affect the Company. Additional information on the cybersecurity risks we face is discussed in Part I, Item 1A, “Risk Factors,” in this Annual Report on Form 10-K, including Risks Related to Privacy, Data Protection and Cybersecurity: “A breach of our security measures or unauthorized access to proprietary and confidential data, or a perception that any security breach or other incident has occurred, may result in our platform or products being perceived as not secure, lower customer use or stoppage of use of our products, and significant liabilities.”
Governance
Our Board of Directors considers cybersecurity as part of its overall risk oversight function and has established oversight mechanisms to support effective governance in managing risks associated with cybersecurity threats. All of our Board members have experience in the technology industry including Sigal Zarmi who is a former CIO of various technology companies, and our CTO, Yoav Landman. Data protection under their guidance and oversight remains a strategic priority at the highest levels of our organization. The Board has delegated to the Audit Committee the responsibility to oversee the information security program (see below) and is also updated regularly regarding matters discussed with the Audit Committee.
The Audit Committee is responsible for oversight of our information security program and receives reports (in particular, in connection with the meetings of the Cybersecurity Subcommittee of the Audit Committee) at least quarterly from executive management, including the CTO and CIO, concerning cybersecurity and other related matters. The Audit Committee’s charter directs that the committee oversee and periodically review the Company’s risks related to privacy, cybersecurity, and information and technology security, including:
�€¢
discussing with management the Company’s plans to mitigate cybersecurity risks and response to data breaches;
�€¢
reviewing any reports from management on data breaches, and
�€¢
overseeing the disclosure of any significant risks and incidents to the extent required by applicable law, including SEC rules and regulations.
Over the past two decades, our CIO has held various positions in information technology and information security, including as CIO in two public companies, managing and controlling cybersecurity long-term programs and risks. Both our CTO, who is a co-founder of JFrog and is also a member of our Board, and our CIO have extensive experience assessing and managing cybersecurity programs and cybersecurity risks, and they work closely to define the initiatives of our cybersecurity program, the CIO organization structure and cyber business continuity plan planning. Our CTO is updated regularly on the status of our cybersecurity program. This allows us to address emerging threats and make informed decisions in real-time and to protect our systems on a timely basis.
Our Chief Legal Officer coordinates the legal review of our privacy and cybersecurity programs, and our VP of Internal Audit leads an annual internal audit plan which includes a component either focused on cybersecurity, privacy, or information technology security. Internal audit findings are reported to the Audit Committee on a quarterly basis.
Security program from JFrog Ltd's Form 10-K for fiscal 2025, filed Feb 13, 2026, Item 1C, in its words (evidence)
Security recordCSV of JFrog's security record · Atom feed of JFrog's security record
What public security catalogs list for JFrog, in their words.
Known exploited vulnerabilities
4 vulnerabilities in JFrog's software that CISA lists as exploited in the wild.
| CVE | Product | Vulnerability | Listed |
|---|---|---|---|
| CVE-2026-42016 | Artifactory | JFrog Artifactory Incorrect Authorization Vulnerability | |
| CVE-2026-42018 | Artifactory | JFrog Artifactory Improper Authentication Vulnerability | |
| CVE-2026-82329 | Artifactory | JFrog Artifactory Improper Authentication Vulnerability | |
| CVE-2026-66384 | Artifactory | JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory Vulnerability |
Source: CISA Known Exploited Vulnerabilities catalog (evidence)
Service statusCSV of JFrog's status page incidents · Atom feed of JFrog's status page incidents
90 days agotoday
- 8 incidents in 90 days
- 3 major or critical
- 2 h 31 min typical time to resolve
- 6 h 6 min longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| JFrog Cloud Platform - OIDC Authentication Issues | minor | 3 h 4 min | |
| JFrog Cloud Platform - Multiple Service Disruptions in GCP Europe West | critical | 6 h 6 min | |
| JFrog Cloud Platform - Multiple Service Disruptions in Azure Southeast Asia | critical | 2 h 31 min | |
| JFrog Cloud Platform outage affecting subset of customers in AWS US East region | no impact stated | 29 min | |
| JFrog Cloud Platform - Xray Service Disruption in Azure US East | major | 2 h | |
| Potential slowdown on Maven remotes in AWS Europe Central | minor | 2 h 31 min | |
| JFrog Cloud Platform degraded performance for GCP regions | no impact stated | 1 min | |
| Potential UI bug for a subset of customers on JFrog Cloud Platform | no impact stated | — |
Incidents per month
critical major minor no impact stated
Components affected
| Component | Incidents | Bar |
|---|---|---|
| Artifactory | 6 | |
| Security - Catalog | 4 | |
| Security - Curation | 4 | |
| Security - JAS | 4 | |
| Security - Xray | 4 | |
| Security - Runtime | 3 | |
| Distribution | 2 | |
| Pipelines | 1 |
As JFrog's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by JFrog's subprocessorsCSV of incidents reported by vendors JFrog lists · Atom feed of incidents reported by vendors JFrog lists
208 reported incidents in the last 30 days, by 4 of the vendors JFrog lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that JFrog was involved.
And 183 more. All of them: CSV · Who is around them.
ChangesCSV of JFrog's changes · Atom feed of JFrog's changes
See the list as we read it on any date: Time machine
None since tracking began.