Skip to content

Commit 9817986

Browse files
rr404jdv
andauthored
updated betaprogram page (#892)
* updated betaprogram page --------- Co-authored-by: jdv <[email protected]>
1 parent fae3a28 commit 9817986

File tree

1 file changed

+38
-20
lines changed

1 file changed

+38
-20
lines changed

crowdsec-docs/unversioned/beta_program.mdx

Lines changed: 38 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -20,38 +20,56 @@ To join the CrowdSec Beta program, click the [Beta opt-in option directly in the
2020

2121
## Upcoming Betas
2222

23-
### CrowdSec Threat Forecast Blocklist - Beta starts 2024-10-25
23+
### Remediation Sync - Closed Beta starting October 10, 2025
2424

2525
#### What is it and what to expect?
2626

27-
The **Threat Forecast Blocklist** is a dynamic, adaptive blocklist customized to your organization's signals.
28-
By identifying attacks on similar profiles, it predicts threats that will likely target your organization in the coming days.
29-
It will update every 24 hours, and the signals of all your Security Engines will be considered to build the prediction.
27+
**Remediation Sync** enables automatic synchronization of security decisions across your entire CrowdSec infrastructure. Any decision from one Security Engine is automatically synced to all other Security Engines and your Blocklist-as-a-Service (BLaaS) endpoints, allowing for simple, consistent edge enforcement across your organization.
3028

31-
It's tailored to your organization; hence, we expect that it should allow preemptive remediation, resulting in a **drop in the number of alerts**.
32-
Optionally, if you have an iptables of nftables remediation component, you'll be able to see some [metrics about this blocklist's efficiency](https://docs.crowdsec.net/docs/next/observability/usage_metrics)
29+
This feature provides:
30+
- Centralized decision management across multiple Security Engines
31+
- Automatic propagation of blocking decisions to all enforcement points
32+
- Consistent security posture across distributed infrastructures
33+
- Simplified management of complex multi-site deployments
3334

3435
#### Who will have access to it?
3536

36-
If you have at least one enrolled security engine with an average of more than 100 alerts a week (total for your organization) you have a chance to be invited.
37-
You'll receive an email on Friday, October the 25th, 2024.
37+
This is a closed beta program. If you're interested in participating, reply to our beta invitation email with one short sentence on how this would improve your CrowdSec setup. We'll activate the feature on your organization once selected.
3838

39-
**Important note**: You will have 15 days to start using the Threat Forecast Blocklist and 30 days in total starting today to test it out. If you do not use it within 15 days, your access will be reallocated to someone else.
39+
#### How it works:
40+
- Decisions made by any Security Engine in your organization are automatically shared
41+
- All connected Security Engines receive and apply these decisions
42+
- BLaaS endpoints are updated to include the synchronized decisions
43+
- Provides unified protection across your entire infrastructure
4044

41-
#### How to subscribe to this blocklist
45+
## Past Beta Programs
4246

43-
- Log into your console account
44-
- Go to the blocklist catalog and search "forecast": https://app.crowdsec.net/blocklists?page=1&q=forecast
45-
- If you're part of the this beta, you should see the **Threat Forecast Blocklist**
46-
- Click on it
47-
- You should have landed in the details page for this blocklist
48-
- Click on subscribe to open the subscription popup and follow its instructions to subscribe to the blocklist.
49-
- We recommend subscribing your organization to the list as this will make sure that newly added security engines automatically benefit from the blocklist as well.
50-
-- If you want to have more finegrained controll, you can also select only specific engines to subscribe to the list.
51-
- Click confirm subscription
47+
### Console Notifications - Beta completed June 10, 2025
5248

53-
Note that you must have a [remediation component](https://doc.crowdsec.net/u/bouncers/intro) on those engines to effectively block the IPs.
49+
The **Console Notifications** feature allows you to set up custom notification rules and receive alerts via multiple channels. Key capabilities include:
50+
- Custom notification rules based on specific events or conditions
51+
- Multiple notification channels including Slack, Discord, webhooks, and more
52+
- Targeted notifications for different types of security events
53+
- Direct management from the CrowdSec Console
5454

55+
**Now available:** Navigate to your [Console Settings](/u/console/notification_integrations/overview) to configure notifications.
56+
57+
### Centralized Allow Lists - Beta completed March 31, 2025
58+
59+
The **Centralized Allow Lists** feature enables you to manage allowlists across all your Security Engines from a single location. This premium feature allows you to:
60+
- Create organization-wide allowlists with trusted IP addresses and ranges
61+
- Set expiration dates for allowlist entries
62+
- Subscribe integrations and Security Engines to specific allowlists
63+
- Prevent blocking of known safe IP addresses across your infrastructure
64+
65+
**Now available:** [Learn more about Centralized Allow Lists](/u/console/allowlists)
66+
67+
### CrowdSec Threat Forecast Blocklist - Beta completed 2024-10-25
68+
69+
The **Threat Forecast Blocklist** was a dynamic, adaptive blocklist customized to organizations' signals, predicting threats that would likely target similar infrastructure profiles.
70+
71+
**Now available:** This feature has been integrated into our premium blocklist offerings via the Enterprise plan.
72+
Learn more about the [Threat Forecast Blocklist](/u/console/threat_forecast).
5573
## Your feedback is key
5674

5775
As one of the first testers of the Threat Forecast Blocklist, your insights are crucial. Join the #beta-program channel on Discord, to share your experience and connect with fellow Beta Program members. At the end of the testing period, we'll also send a brief survey to gather your feedback.

0 commit comments

Comments
 (0)