Skip to content

First Steps

Use this checklist to turn a new CVEalert account into a useful alerting setup. The goal is focused monitoring, not a complete inventory on day one.

Onboarding Checklist

  • Add 5 to 10 important products.
  • Set alert thresholds before inviting the wider team.
  • Confirm the first alerts make sense.
  • Send a test alert to Slack or Telegram.
  • Enable 2FA and review organization access.

1. Add important software

Start with software that is internet-facing, business-critical, widely deployed, or historically noisy for your team. Use Catalog when possible, and use Search when you need a specific vendor or product.

2. Review monitoring thresholds

Open Software Monitoring and choose the minimum severity that should generate alerts for each product. Start with High for broad coverage, then adjust thresholds based on business impact and alert volume.

3. Check the first alerts

Use Alerts to review matching CVEs. Prioritize Critical and High findings first, then use KEV and PoC filters to find vulnerabilities with stronger exploitation signals.

4. Configure alert delivery

Set up Slack or Telegram in Integrations so new alerts reach the channel or chat your team monitors. Send a test alert before relying on the integration.

5. Secure the account

Enable 2FA for your account and review Logs after major account changes. For team usage, invite members through Organization settings and assign the least privilege role that fits their work.

Warning

Treat CVEalert as a prioritization system. Always confirm affected versions, deployment context, and remediation status in your own environment.

Main Pages