Beta

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

Releases

01/09/2026 22/07/2026 15/07/2026 08/07/2026 01/07/2026 24/06/2026 03/06/2026 06/05/2026 29/04/2026 22/04/2026

Subscribe to our RSS feed to stay up-to-date with our latest releases.

New feature

For companies

For researchers

Meet CrowdRecon: turning hacker reconnaissance into actionable exposure insights

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

New achievement: 1337 valid submissions

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

New achievements: Asset types

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

Payout share image

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

Retest updates via Slack

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

New researcher achievements: Payout badges

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

Sunsetting legacy statistics page

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

Pentest progress widget

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.

Changes

For companies

New “possible bounty” variable for message templates

06/05/2026

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Why we did it: This reduces manual edits and copy-paste errors when communicating payout expectations, and makes it easier to reuse consistent messaging across submissions (including when procurement or approvals are involved).

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

Note: The “possible bounty” is an estimate shown before acceptance. The final payout can differ in some cases, for example in PTaaS programs where the bounty can be lower than the possible bounty if the bounty pool is empty.

💡 Learn more about message templates

New feature

For companies

Find assets with AI skill suggestions faster

29/04/2026

What we did: Added a new sort option in the “Assets” view that surfaces assets with AI suggestions for required skills at the top, making pending suggestions easy to find and review.

Why we did it: In large asset inventories, AI suggestions can be scattered across many assets. Without a dedicated sort, it was time-consuming to identify which assets still had suggested skill updates awaiting review.

Who it helps: Company admins managing large numbers of assets can review and apply suggested required-skill updates faster, keep asset requirements more consistent, and reduce manual effort when maintaining skill coverage across the environment.

💡Learn more about how to make the most out of required skills in this article.

Changes

For companies

📊 New in Insights: Triage metrics

22/04/2026

What we did: We’ve added Triage insights to the Insights Review section with charts for triage review status, triage-to-final decision alignment, and time to first triage assignment.

Why we did it: To give clearer visibility into triage coverage, decision consistency, and triage responsiveness.

Who it helps: This helps program and security teams who want to monitor triage performance and ensure consistent decision-making across the submission review process.

Learn more in this article.

What we did: Added a new “possible bounty” variable to message templates, so templates can automatically include the estimated bounty amount for each submission.

Who it helps: Security teams informing researchers about upcoming payouts, and larger organizations that need procurement involvement or internal approval before issuing a payout.

💡 Learn more about message templates

AI Security & Safety

Product types

Platform

For customers

Industries we serve

Resources

Plans to suit your security testing needs

Learn more about our company

About Intigriti

Useful links

Blog

Hacking AI customer service agents

Reconnaissance unleashed: Meet CrowdRecon

Intigriti Bug Bytes #239 - August 2026 🚀

Platform changelog

Releases

Meet CrowdRecon: turning hacker reconnaissance into actionable exposure insights

New achievement: 1337 valid submissions

New achievements: Asset types

Payout share image

Retest updates via Slack

New researcher achievements: Payout badges

Sunsetting legacy statistics page

Pentest progress widget

New “possible bounty” variable for message templates

Find assets with AI skill suggestions faster

📊 New in Insights: Triage metrics

Releases

Meet CrowdRecon: turning hacker reconnaissance into actionable exposure insights

New achievement: 1337 valid submissions

New achievements: Asset types

Payout share image

Retest updates via Slack

New researcher achievements: Payout badges

Sunsetting legacy statistics page

Pentest progress widget

New “possible bounty” variable for message templates

Find assets with AI skill suggestions faster

📊 New in Insights: Triage metrics

AI Security & Safety

For teams using AI to build faster

For teams building AI into products

Product types

CrowdRecon

Bug bounty

PTaaS

Managed VDP

Live hacking events

Platform

Platform tour

Integrations

Trust center

For customers

Additional demos

Knowledge base

Uptime and status

Changelog

Industries we serve

Retail

Gaming and eSports

Finance and Insurance

Leisure and Hospitality

B2B SaaS

Telecommunications

Government and Public services

Transport & Logistics

Healthcare

News, media, published content

eCommerce and transactional websites

IoT and B2B ecosystems

Resources

Customer stories

Blog

Information sheets

Ebooks

Webinars

Shorts

Events

Bug bounty talks

Plans to suit your security testing needs

Core

Premium

Enterprise

Learn more about our company

About us

Leadership

Careers

Contact us

About Intigriti

How it works

Public programs

Intigriti Ambassador

Useful links

Leaderboard

Learn to hack

Swag shop

Newsletter

Bug bounty talks

Blog

Events

Bug Bounty Starter kit

Blog

Hacking AI customer service agents

Reconnaissance unleashed: Meet CrowdRecon

Intigriti Bug Bytes #239 - August 2026 🚀

Platform changelog

Releases

Meet CrowdRecon: turning hacker reconnaissance into actionable exposure insights

New achievement: 1337 valid submissions

New achievements: Asset types

Payout share image

Retest updates via Slack

New researcher achievements: Payout badges

Sunsetting legacy statistics page

Pentest progress widget

New “possible bounty” variable for message templates

Find assets with AI skill suggestions faster

📊 New in Insights: Triage metrics

Releases