Put an artifact repository inside an accredited boundary and the paperwork has to describe it. Binaries, container images, dependency caches and model files are data at rest with a classification attached. If the store holding them sits outside the assessed system, the agency writes the exception itself. That is the operational content of what JFrog published: the scope, according to JFrog, runs from open-source ingestion and binary management through vulnerability scanning and policy control to signed distribution and runtime monitoring [4]. Scope is the load-bearing word, because a vendor holding an assessment over one component of a stack can describe itself in the same sentence.
What is public here is a blog post. The report is not, and the post does not give the assessment date, the deployment models or hosting regions covered, or any control the assessor recorded as not implemented [13]. An agency that asks CyberCX's client for the report gets those. A reader of the announcement does not.
JFrog does get the terminology right, which is worth saying because vendors routinely do not. IRAP is an assessment, there is no IRAP certificate, and the output is an independent report against the ISM that each agency then uses for its own Authority to Operate decision [2][3]. One strong assessment can feed many ATO decisions [3]. CyberCX did the evaluating; each agency still has to do the signing.
The ISM is built on four principles and updated quarterly [8], which puts four baseline revisions a year behind any report [1]. A Protected-level assessment is therefore a point-in-time statement against a rulebook that will have moved before most procurements close. Alongside it sits the Hosting Certification Framework, which governs data sovereignty and hosting, and which JFrog says the Department of Home Affairs moved to strengthen in April 2026 [6]. Sovereign assurance of this kind has to be renewed on the regulator's schedule, not settled once and shelved.
Two other numbers in the post are commercial rather than technical. JFrog says its platform runs at scale for more than 80 percent of the Fortune 100 [9], which is at least 80 of those companies [2], and that Gartner named it a Leader with the highest placement for Ability to Execute in the first Magic Quadrant for Software Supply Chain Security [10]. Both are measures of adoption and market standing, and an ATO decision turns on assessed controls, not installed base.
The reason any of this lands is the behaviour JFrog describes upstream: attackers working in the binaries, dependencies, container images and now the AI models that flow into production before anyone runs them [11]. Perimeter and finished-application assurance never covered the storage layer where those objects wait to be pulled.
