- Products
- Learn
- Local User Groups
- Partners
- More
On-Premise SD-WAN Management
Register HereWhat's New in R82.10?
Watch Here AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
The Moment Before
PRHF probably is ??hotfix
but the others?
Anybody any idea?
Indeed these are all prefixes for various of bug types (P is for Product by the way). It is depend where these bugs were found and/or how it was release to the field.
The reason that we expose these values is, as mentioned previously in the thread - to give the option to compare between several SKs ( example - to see if specific issue was solved in the Jumbo)
PRHF - Private hotfix , found on the field and fixed as private hotfix ( PRHF)
PRJ- Fixed in the Jumbo
PMTR - Found and fixed on main-train
MBS - found/added as part of other projects ( MBS for example , but can be other projects as well)
Those look like prefixes for various bug types, with each one being relevant for a different R&D team.
In what precise context are you seeing it?
I see them in a SK relating to a bug reported by us (SK168881).
I would call them internal abbreviations without any use for others 8).
PRHF - private hotfix, PRJ - private jumbo, MBS is not important 🙂
Should not be exposed, I have escalated it to the relevant teams.
Should not be exposed? It is possible to compare the numbers from an SK (or a privat HF crs.xml file) to the numbers in the List of resolved issues per Jumbo HotFix Take - i find that valuable 8)
Indeed these are all prefixes for various of bug types (P is for Product by the way). It is depend where these bugs were found and/or how it was release to the field.
The reason that we expose these values is, as mentioned previously in the thread - to give the option to compare between several SKs ( example - to see if specific issue was solved in the Jumbo)
PRHF - Private hotfix , found on the field and fixed as private hotfix ( PRHF)
PRJ- Fixed in the Jumbo
PMTR - Found and fixed on main-train
MBS - found/added as part of other projects ( MBS for example , but can be other projects as well)
small correction - the prefixes have nothing to do to where the issues were found, just to where they were first added to the code. so PRHF was first delivered as a private fix, PRJ to a Jumbo, PMTR was first integrated to a main-train version, and the same for specific project prefixes.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 9 | |
| 7 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Thu 09 Jul 2026 @ 10:00 AM (CEST)
Schutz souveräner Workloads: Check Point & die AWS European Sovereign CloudThu 09 Jul 2026 @ 11:00 AM (CEST)
The Cloud Architects Series: Check Point Edge Protection SD-WAN & SASEThu 09 Jul 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #9 - What's New with Check Point Email SecurityFri 10 Jul 2026 @ 11:00 AM (IDT)
CheckMates Live Netherlands - Sessie 48: Nieuwe Check Point Workspace SecurityTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 09 Jul 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #9 - What's New with Check Point Email SecurityFri 10 Jul 2026 @ 11:00 AM (IDT)
CheckMates Live Netherlands - Sessie 48: Nieuwe Check Point Workspace SecurityTue 14 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E11: READY OR NOT: Securing the AI Enterprise 3/5 - AI Workforce SecurityThu 30 Jul 2026 @ 10:00 AM (PDT)
AI Security Masters E12: READY OR NOT: Securing the AI Enterprise 4/5 - AI GatewayThu 20 Aug 2026 @ 10:00 AM (PDT)
AI Security Masters E13: READY OR NOT: Securing the AI Ent 5/5 - AI Research & Threat LandscapeAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY