Skip to content
Vulnerability, intelligence and service monitoring platform

Track vulnerabilities affecting your organisation in order of priority.

Identify vulnerabilities affecting your inventory, prioritise them and track remediation. Manage threat intelligence and research in the same panel.

Derbentçi / Overview

Inventory matching

Kullandığınız ürün ve sürümlere odaklanın.

Risk priority

KEV, EPSS ve varlık bilgisiyle değerlendirin.

Team notifications

İlgili bulguyu sorumlu ekibe iletin.

Remediation tracking

Aksiyonu ve uygulanan çözümü kaydedin.

Take a closer look

From inventory to remediation, in one workspace.

Choose a screen to explore that part of the product and how to use it.

Your organisation's products and versions

Start monitoring with your inventory.

Define the products you use, their installed versions and responsible teams. Assess published vulnerabilities in that context.

  • Asset records with vendor and product suggestions
  • Full version, responsible team and asset criticality
  • Track missing versions and matches requiring review
Inventory
Enlarge the image to inspect the details.
Intelligence and research

Explore intelligence and track changes.

Choose a topic group to explore the tools and application screens.

Screens contain sample data. Organisations and announcements in the KVKK image are illustrative.

Example workflow

Turn a new vulnerability into work you can track.

Imagine a firewall in your inventory. When a new record for that product arrives, the process follows these steps.

  1. 01

    Record imported

    A newly published vulnerability is imported during a scheduled source check.

  2. 02

    Matched to inventory

    Product and version details are compared. KEV, EPSS and asset criticality are assessed.

  3. 03

    Team notified

    The relevant team receives findings according to its preferences; an assignee and due date are set.

  4. 04

    Remediation recorded

    An update or other action is applied; remediation evidence and the new version are recorded.

Email notifications

Relevant information reaches the responsible team.

Explore examples of vulnerability, inventory, daily summary and service notifications.

Integrations

Works with the tools your team uses.

Send notifications through configured connections and create work items for findings.

Slack

Notifications to your chosen channels.

Microsoft Teams

Notifications in your team's workspace.

Webhook

Send events to your own systems.

Jira

Create work items for findings.

GitHub

Track findings through work items.

Current data from established sources.

Sources are checked regularly. New records enter the matching and notification process after import.

MITRE ATT&CK

Attack techniques, actors and campaign relationships

Threat feeds

Malicious and suspicious indicators from active sources

Certificate transparency

crt.sh for subdomain observations of verified domains

NVD

CVE records, descriptions and product/version information

CISA KEV

Vulnerabilities known to be actively exploited

EPSS

Scores estimating vulnerability exploitation probability

Vendor advisories

Security advisories from supported vendors

OSV

Vulnerability records for software packages and dependencies

KVKK

Public data breach announcements

Management reports

Turn your risk view into a report you can share.

PDF reports summarise severity distribution, KEV information, asset counts and priority open findings.

  • Open findings and risk distribution
  • Inventory and KEV matches
  • Priority finding summary
Read the user guide
Frequently asked questions

Before you begin.

Short answers about matching, notifications and data sources.

All questions and the user guide
Which vulnerabilities does Derbentçi associate with my organisation?

It compares vendor, product and version information with your inventory, separating exact or high-confidence matches from records requiring review. Records with missing version information need further assessment.

What do Malicious Links records show?

Malicious and suspicious indicators from threat feeds, with their sources and statuses. Suspicious records require analyst review; a listed record does not establish that your company experienced an attack.

When are domain verification and certificate checks performed?

Add the displayed TXT record to DNS for the domain. The worker checks hourly and processes up to 20 domains per run. DNS propagation and source availability can affect verification time.

Can I select notification severity levels?

Choose critical, high, medium and low levels for team notifications. Service and data breach notifications are configured separately.

Which SBOM formats are supported?

CycloneDX JSON and XML, and SPDX JSON and tag-value formats are supported. Upload files in the panel or send them from CI using a company-scoped import key.

What information is service status based on?

Public status sources from supported providers. A separately configured Microsoft Graph connection supports company-specific Microsoft 365 status. Provider status does not guarantee that every internal workflow is working.

Contact and access

Explore Derbentçi for your organisation.

Request a demonstration to discuss your organisation's needs.