Platform changelog
Curious about the latest and greatest on Intigriti? You're in the perfect place! Dive in to see what's new, what's improved, and what's changed
Curious about the latest and greatest on Intigriti? You're in the perfect place! Dive in to see what's new, what's improved, and what's changed
Subscribe to our RSS feed to stay up-to-date with our latest releases.
Changes
For companies
For researchers
16/09/2026
What we did: We added support for equally splitting bounties when duplicate findings are submitted within a collaborative pentesting setup involving multiple researchers. When duplicate submissions are identified, the bounty can be distributed across the relevant researchers instead of rewarding only the first person to submit. Why we did it: Collaborative pentests work best when researchers combine their skills and knowledge to achieve the strongest possible outcome for the customer. If duplicate findings are handled purely on a first-to-submit basis, researchers may feel pushed to rush their submissions instead of collaborating, validating findings together, and producing the most complete result.
Who it helps: Researchers participating in collaborative pentests, by reducing competitiveness around being first and encouraging stronger collaboration.
💡 Why beta: We’re releasing this in beta so we can validate the approach with real collaborative pentests, including the slightly modified submission handling flow. Because equal bounty splits for duplicates require all submissions to be reviewed and duplicates to be correctly identified and linked before accepted findings are confirmed, we want to monitor if this works in practice, check for unintended side effects, and fine-tune the experience before making it generally available.
Changes
For companies
09/09/2026
What we did: We added severity filters for Slack and webhook notifications, so companies can choose which submission severities trigger notifications.
Why we did it: This helps teams reduce noise and focus notifications on the findings that matter most to their workflow.
Who it helps: This helps companies that use Slack or webhooks to route relevant vulnerability updates to the right teams and channels.
New feature
For companies
For researchers
02/09/2026
What we did: We added support for multi-researcher PTaaS programs, allowing one PTaaS program to include multiple researchers and pentests under the same engagement. Teams can set the number of researchers needed and coordinate submissions collaboratively within one streamlined flow.
Why we did it: Large scopes often need different specialist skills and parallel testing within a fixed customer testing window. Previously, this required duplicating programs and extra manual coordination. This update makes it easier to run coordinated multi-researcher pentests without splitting the work across separate programs.
Who it helps: Companies running larger or more complex pentests, by helping them cover more surface area faster through multiple researchers working together. It also stimulates collaboration by allowing researchers to add collaborators to submissions and split the bounty among them.
New feature
For companies
For researchers
01/09/2026
Before every vulnerability report comes reconnaissance. Hackers map assets, explore paths, and decide where to look deeper, but much of that valuable work disappears when it does not become an accepted report.
CrowdRecon captures signals from trusted hacker reconnaissance and turns them into insights security teams can act on, showing what hackers are finding and where they are focusing their attention. It also helps ethical hackers make their skills visible, build their reputation, and unlock recognition and potential rewards beyond accepted reports.
CrowdRecon is in beta. Soon, we’ll welcome more customers and ethical hackers to try it, share feedback, and help shape what comes next.
Want to be part of it? Join the CrowdRecon waitlist.
New feature
For researchers
22/07/2026
What we did: We introduced a new researcher achievement that unlock when a researcher makes a valid submission on specific asset types. These achievements are granted retroactively where applicable, with the unlock date reflecting when the submission was validated.
Why we did it: To better recognize researchers’ contributions across different types of assets and celebrate quality work in a way that’s accurate over time.
Who it helps: Researchers, by highlighting their achievements and impact.
Changes
For researchers
15/07/2026
What we did: We introduced new researcher achievement that unlock when a researcher makes a valid submission on specific asset types. These achievements are granted retroactively where applicable, with the unlock date reflecting when the submission was validated.
Why we did it: To better recognize researchers’ contributions across different types of assets and celebrate quality work in a way that’s accurate over time.
Who it helps: Researchers, by highlighting their achievements and impact.
New feature
For researchers
08/07/2026
What we did: We added new shareable images for payouts. Researchers can now share a dedicated visual on social media when they receive a payout. The payout can be shared from their payout overview page in the platform. The image is generated as a preview image when linking to the researcher profile, this also means that the sharing can be enabled individually per payout and also revoked if the researcher no longer want the image to be visible.
Why we did it: To make it easier for researchers to share their accomplishments. For a part of the community, receiving payouts is a validation of the good work they’ve been doing and it’s something they want to share on social media
Who it helps: Researchers who previously used screenshots of their payouts or valid submissions now have a streamlined way of sharing a visual when they are awarded with a payout.
Changes
For companies
01/07/2026
What we did: We added new Slack notification triggers for retest updates. Program admins can now choose which retest status changes should be pushed to their configured Slack channels.
Why we did it: To make it easier to keep internal teams aligned when retests move through key stages without needing to manually check the platform.
Who it helps: Companies who rely on Slack to stay on top of submission progress and want timely visibility into retest outcomes.
💡 Learn more in this article.
New feature
For researchers
01/07/2026
What we did: We added a new set of payout-based researcher achievements. Researchers can now unlock new badges automatically as they reach payout milestones (1, 5, 10, 25, 50, 100, 250, 500, and 1000 payouts).
Why we did it: To give researchers more ways to showcase progress and build a stronger profile over time.
Who it helps: Researchers who want more recognition for consistent performance and a clearer way to highlight experience through achievements.
💡Learn more in this article.
Changes
For companies
24/06/2026
What we did: We removed the legacy Statistics page and replaced it with Insights, which is generally available.
Why we did it: The old page duplicated what’s available in Insights, wasn’t perceived as user-friendly, and some of the metrics weren’t representative (for example, averages that can be skewed by clear outliers).
Who it helps: Company admins, who now have a single, clearer place to view program performance metrics in Insights.
New feature
For companies
03/06/2026
What we did: Added a pentest progress widget in the company view so company users can quickly see where an active pentest is. For Focused pentests, the widget shows test period progress only. For Comprehensive and Certified pentests, it shows both the test period progress and the researcher’s progress on the checklist.
Why we did it: Companies needed clearer, real-time visibility into where their pentest is in the process without having to ask for manual updates. This reduces uncertainty, status-check overhead, and helps set expectations on what’s happening next.
Who it helps: Company users (security, engineering, and other stakeholders) who need to track pentest progress, understand next steps, and align internal planning around the engagement timeline.
New feature
For companies
03/06/2026
What we did: Added a pentest progress widget in the company view so company users can quickly see where an active pentest is. For Focused pentests, the widget shows test period progress only. For Comprehensive and Certified pentests, it shows both the test period progress and the researcher’s progress on the checklist.
Why we did it: Companies needed clearer, real-time visibility into where their pentest is in the process without having to ask for manual updates. This reduces uncertainty, status-check overhead, and helps set expectations on what’s happening next.
Who it helps: Company users (security, engineering, and other stakeholders) who need to track pentest progress, understand next steps, and align internal planning around the engagement timeline.
